COMM-PRO

HNAS VnRnMn
Custom UserMod Enhancement Summary

(Custom user modifications provided by Comm-Pro directly to users requiring enhancements)

This document serves as a quick reference to identify custom user enhancements (CUSTMOD) as provided for specific HNAS VnRnMn organizations.  These enhancements, variations of, and new enhancements can be provided (usually at no cost) to organizations requiring extended features not provided in the standard support.  Please contact your HNAS support representative should you require additional information concerning this subject.

Our policy is to include all potential general use custom enhancements into the next HNAS product release as 'New Features' whenever possible.  This doesn't include all custom user modifications because some enhancements were done to specifically address a customers unique network, host or application requirements and are not suitable for general users.  Customer names were removed from the specific CUSTMOD entries to protect their privacy.  Not all custom user  enhancements are included in this list due to the proprietary nature of the enhancement or contractual restrictions. 

Please refer to the HNAS VnRnMn Maintenance (APAR and PTF) and HNAS VnRnMn Problem Information Summaries for additional information regarding APAR Enhancements and Problem Enhancement activity.


HNAS VnRnMn Custom UserMod Summary Matrix

CUSTMOD#
PROB_ID#
CLOSE_DATE
OPEN_DATE
SERVICE

CID_230
or TYPE

 DESCRIPTION
2005jdti mm-dd-2005 - - Pending - 
2004212A 11-11-2004
07-30-2004
Console Alert
Messages Option
<CustomUserMod>
NBG_230 CLOSED_OPERATIONAL
<User's Host Automation Monitor program has difficulty
filtering multi-line HNAS alert messages because all lines of multi-line messages start with the same string (e.g. NAS7717W).>
2004162A 08-26-2004
06-10-2004
PCNE/PAD CNFG
<CustomUserMod>
AMA_230 CLOSED_NOT-TESTED/Implemented, user decided not to employ usermod. - <SVC0= & SVC5= operands are limited to 511 SLU entries, increase to 1023>
2004138B 07-13-2004
05-17-2004
PCNE/PAD CNFG
<CustomUserMod>
NBG_230 CLOSED_OPERATIONAL
<Unique CUD values required for each callout DTE address in the SVC0= and SVC5= operand lists>.
2004091A 07-14-2004
03-29-2004
PCNE/PAD CICS
<CustomUserMod>
BIC_230 CLOSED_NOT-TESTED/IMPLEMENTED BY CUSTOMER -
<CICS UNBIND minidump condition. Issue CESF LOGOFF instead of UNBIND, etc.>
2003188A
(SWC001)
07-08-2003
07-08-2003
GATE Callin Balancing
<CustomUserMod>
SWC_230
SWC_220
CLOSED_OPERATIONAL
<
User wants to load balance inbound GATE calls across two CTCPs>
- - - - -
yyyy.... mm-dd-yyyy
..-..-yyyy
-
<CustomUserMod>
cid_230 In production on users system.
<...>.
Note N/A

N/A

N/A

This list
- - - - -

Please refer to the HNAS VnRnMn Maintenance (APAR and PTF) and HNAS VnRnMn Problem Information Summaries for additional information regarding APAR Enhancements and Problem Enhancement activity.
 


mm-dd-2005  - CUSTMOD 2005jdti

 CUSTMOD_ID:  2005jdtiP
     STATUS:  PENDING
  OPEN_DATE:  mm-dd-2005
REVISE_DATE:  N/A
 CLOSE_DATE:  mm-dd-2005
 SERVICE(S):  .

- - - - - - - - - - - - - - - -

11-11-2004  - CUSTMOD 2004212A

 CUSTMOD_ID:  2004212A
     STATUS:  CLOSED 

- - - - - - - - - - - - - - - -

11-11-2004  - PROBLEM 2004212A

 PROBLEM_ID:  2004212A
     STATUS:  CLOSED   
  OPEN_DATE:  07-30-2004
 CLOSE_DATE:  11-11-2004
 SERVICE(S):  Alarm messages
  MANDATORY:  N/A
 ORIGIN/REF:  230_NBG
    CP_TECH:  SFD/PWB
    PUBLISH:  YES
   PTF_INFO:  Shipped as a user mod.
              Contact Comm-Pro for current location.
  PTF_CLASS:  CUSTOM-USER-MOD.
   PTF_TYPE:  (OBJ) HNASOBJX and (SRC) HNASMACX
   COREQ(S):  N/A
  PREREQ(S):  2300051, 2300047
 SUPERSEDES:  N/A
  OBJECT(S):  XOTTR  (NAS7... alarm messages)
  SOURCE(S):  NASTCP (NAS2... and NAS8... alarm messages)

    PROBLEM:  User's Host Automation Monitor program has difficulty
              filtering multi-line HNAS alert messages because all
              lines of the message start with the same string (e.g.
              NAS7717W).

DESCRIPTION:  See problem.

   SOLUTION:  A custom mod to install sequence numbers in multi-line
              alarm messages is available.  For example, NAS7717W
              alarm will be displayed as two lines starting with
              NAS7717W1 and NAS7717W2.  Insertion of the sequence
              number shifts the message text to the right.

CIRCUMVENTION: N/A

 APPLY_INFO:  The custom mod is applied like an APAR.
              See Chapter 6 (Product Maintenance Installation
              section) from the HNAS Guide and Reference Manual
              for instructions on how to install PTF's (Object,
              Source and ZAPs) or Refresh/Upgrade maintenance. 

09-08-2004  - CUSTMOD 2004162A

 CUSTMOD_ID:  2004162A
     STATUS:  CLOSED,NOT-TESTED
              User decided not to employ this HNAS usermod.
  OPEN_DATE:  06-10-2004
 CLOSE_DATE:  08-26-2004
 SERVICE(S):  PCNE/PAD Enhancement
  MANDATORY:  N/A
 ORIGIN/REF:  230_AMA


DESCRIPTION:  The SVC0= and SVC5= operand arrays (SLUs) have been
              increased from 511 to 1023 entries so that a larger
              number of PCNE/PAD SLUs can be defined per MCH.

- - - - - - - - - - - - - - - -

07-13-2004  - CUSTMOD 2004138B

 CUSTMOD_ID:  2004138B
       NOTE:  CUSTMOD_ID USES SAME MEMO AS PROBLEM_ID. 

- - - - - - - - - - - - - - - -
07-13-2004  - PROBLEM 2004138B

 PROBLEM_ID:  2004138B
     STATUS:  CLOSED 
  OPEN_DATE:  05-17-2004
REVISE_DATE:  07-12-2004 (use extra MXTs for CUD, FAC & DCEADDR)
 CLOSE_DATE:  07-13-2004
 SERVICE(S):  PCNE/PAD Configuration Enhancement
  MANDATORY:  N/A
 ORIGIN/REF:  230_NBG
    CP_TECH:  PWB/SFD
    PUBLISH:  YES
  PTF_CLASS:  CUSTOM-USER-MOD
   PTF_TYPE:  (OBJ) HNASOBJX
    PTF_LOC:  N/A
   COREQ(S):  N/A
  PREREQ(S):  N/A
 SUPERSEDES:  N/A
  OBJECT(S):  XOTBXM
  SOURCE(S):  N/A

    PROBLEM:  A unique MXT is required to provide DCEADDR=, FAC=
(ENHANCEMENT) and CUD= values for each callout DTE address in the
              SVC0= and SVC5= operand lists.

DESCRIPTION:  When multiple called DTE addresses are associated
              with an SLU in the SVC0= and/or SVC5= operand list,
              (alternate callout) it may be necessary to associate
              different MXT values with each called DTE address.

   SOLUTION:  Outbound call request packet processing modified to
              assume that the MXT addressed by an SVC0= or SVC5=
              entry is followed by additional MXTs (one for each
              dteaddri entry for the LU defined by the SVC0/5=
              entry).

              Assume the following SVCi= operand entry:

              SVCi=(vclmt,
                    :
                    sluname/dteaddr1-dteaddr2-dteaddr3O/MXT1,
                    :

              Also assume the following MXT REMOTE definitions.

              MXT1    REMOTE TYPE=MXT
                             CUD=cud1 FAC=fac1 DCEADDR=dce1
              MXT2    REMOTE TYPE=MXT
                             CUD=cud2 FAC=fac2 DCEADDR=dce2
              MXT3    REMOTE TYPE=MXT
                             CUD=cud3 FAC=fac3 DCEADDR=dce3

              When dteaddr1 is used, CUD/FAC/DCEADDR come from MXT1.
              When dteaddr2 is used, CUD/FAC/DCEADDR come from MXT2.
              When dteaddr3 is used, CUD/FAC/DCEADDR come from MXT3.

              Notes:

              For CUD, the new logic operates only if a CUD0 value
              is not specified in the SVC0/SVC5= entry for the LU
              and an MXT name is specified.

              If there is no value in the MXT then a value is
              obtained from the MCH.

              If the MXTs are not generated contiguously as shown,
              values come from the MXT addressed by the SVC0/SVC5=
              entry (MXT1).

              With this change on there should be an MXT for every
              DTE address in the LU's called address list (up to 3).

 APPLY_INFO:  N/A - Provided to user encountering the problem.
              This problem FIX is applied like an APAR.  

07-14-2004  - CUSTMOD 2004091A

 CUSTMOD_ID:  2004091A
       NOTE:  CUSTMOD_ID USES SAME MEMO AS PROBLEM_ID.

- - - - - - - - - - - - - - - - 
07-14-2004  - PROBLEM 2004091A

 PROBLEM_ID:  2004091A
     STATUS:  CLOSED, (NOT TESTED/IMPLEMENTED BY CUSTOMER)
  OPEN_DATE:  03-29-2004
REVISE_DATE:  04-03-2004
REVISE_DATE:  04-13-2004
REVISE_DATE:  04-20-2004  (Awaiting customer test)  
REVISE_DATE:  07-08-2004  (Reclassified as CUSTOM-USER-MOD)
 CLOSE_DATE:  07-14-2004   (Never tested by user)  
 SERVICE(S):  PCNE/PAD CICS LU SESSION END PROCESSING
  MANDATORY:  N/A
 ORIGIN/REF:  230_BICS
    CP_TECH:  SFD
    PUBLISH:  YES
  PTF_CLASS:  CUSTOM-USER-MOD
   PTF_TYPE:  N/A
    PTF_LOC:  N/A
   COREQ(S):  N/A
  PREREQ(S):  N/A
  OBJECT(S):  MCHHL0RQ,MCHHL5RQ,MCHNRQB,MCHSUP
  SOURCE(S):  LUD

    PROBLEM:  An UNBIND request from HNAS to CICS to end an LU session
              causes CICS to take a minidump of the users storage area
              and issue a DFHZC3434 error message.

              04-03-2004 <begin>
              LUSTAT instead of UNBIND caused error message to change
              from DFHZC3434 to DFHZC3447.
              04-03-2004 <end>

              04-13-2004 <begin>
              Corrected LUSTAT DFHZC3447 error message.  ACB close
              logic (activated by ZAP) results in DFHZC3437 error
              message with the SLU task ABENDing.
              04-13-2004 <end>

 DESCRIPTION: HNAS can send an UNBIND request to the PLU if the LU/VC
              session is cleared by the remote DTE.  UNBIND is an SNA
              request that is valid for both PLU and SLU.  For some
              CICS applications, however, the HNAS UNBIND is treated
              as an error which causes CICS to take a minidump of the
              users storage area and issue a DFHZC3434 error message.
              This is more of an annoyance than a severe problem
              because it increases the size of the CICS SYSOUT.

              04-03-2004 <begin>
              LUSTAT solution did not work.  In fact, it only changed
              the error message to DFHZ3447.  Error in the mod caused
              trash to be used as sense.
              04-03-2004 <end>

              04-13-2004 <begin>
              Corrected LUSTAT solution still did not work.  ACB
              close solution also did not work.  CICS still does
              not terminate the SLU connection cleanly.
              04-13-2004 <end>

   SOLUTION:  HNAS has been modified so that instead of issuing an
              UNBIND to end an LU session, it will issue an LUSTAT
              with 0831 sense (LU component disconnected) if the LU
              is bound and in data transfer state (SDT received).
              The thought is that the LUSTAT will solicit an UNBIND
              from CICS to end the LU session.  If the LU is not
              in data transfer state, the ACB is simply closed and
              the LU is released.  In this case we expect that the
              ACB closure will tell CICS that the LU session has
              ended.

              04-03-2004 <begin>
              Rework LUSTAT mod so that correct sense (0831) is
              presented.  Also included logic (activated by ZAP)
              that closes ACB instead of issuing LUSTAT when a
              Clear is received.
              04-03-2004 <end>

              04-20-2004 <begin>
              HNAS has been modified so that instead of issuing
              an UNBIND to end an LU session, it will issue a CESF
              LOGOFF message if the LU is bound and in data transfer
              state (SDT received).  Once the LOGOFF is presented
              to CICS, subsequent PLU output is simply ended with
              normal sense and not transferred to the remote DTE
              whose connection was cleared.
              04-20-2004 <end>

 APPLY_INFO:  This problem FIX is applied like an APAR.

              See Chapter 6 (Product Maintenance Installation
              section) from the HNAS Guide and Reference Manual
              for instructions on how to install PTF's (Object,
              Source and ZAPs) or Refresh/Upgrade maintenance.

              Corrective logic included in distributions created
              after CLOSE_DATE.  Otherwise, apply maintenance as
              directed in the APPLY_INFO (PTF). 

07-20-2004  - CUSTMOD 2003188A

 CUSTMOD_ID:  2003188A
       NOTE:  CUSTMOD_ID USES SAME MEMO AS PROBLEM_ID.

- - - - - - - - - - - - - - - - 
07-20-2004  - PROBLEM 2003188A

 PROBLEM_ID:  2003188A
     STATUS:  CLOSED, OPERATIONAL
  OPEN_DATE:  07-08-2003
 CLOSE_DATE:  07-08-2003  (posted 07-20-2004)
 SERVICE(S):  GATE
  MANDATORY:  N/A (CUSTMOD)
 ORIGIN/REF:  220/230_SWC  (SWC001)
    CP_TECH:  PRT
    PUBLISH:  YES
  PTF_CLASS:  CUSTOM-USER-MOD
   PTF_TYPE:  (OBJ) HNASOBJX
    PTF_LOC:  Customer specific fix sent as email attachment.
   COREQ(S):  N/A
  PREREQ(S):  N/A
 SUPERSEDES:  N/A
  OBJECT(S):  VCCLRQ
  SOURCE(S):  N/A

    PROBLEM:  User wants to load balance inbound GATE calls across
              two CTCPs.

DESCRIPTION:  See Problem

   SOLUTION:  HNAS VCCLRQ routine modified to send inbound GATE
              Call request packets to alternating CTCPs in the
              LUNAME= list (which has only two entries).

CIRCUMVENTION: N/A

 APPLY_INFO:  N/A - PROVIDED TO USER AS REQUIRED.

 HNAS Product Documentation Information

HNAS Page - HNAS Maintenance Page -  Contact/Information

List of Abbreviations and Terms


Last Update - April 28, 2006