COMM-PRO

HNAS V2R3M0 - 2007
MAINTENANCE SUMMARY

(Refresh/Upgrade maintenance is currently available directly from Comm-Pro or their agents)

The individual APAR hyperlink *.ZIP files provide all of the necessary SRC (source) and OBJ (object) updates for the respective PTF.  Most APARs have  PREREQ(S) as designated in the APAR memos (multiple APAR PTF's may be required to install a particular APAR PTF).  If a product refresh or upgrade is required you will need to contact your HNAS support representative to order the appropriate edistribution.  HNAS product edistributions are provided via our ftp server and build as requested (e-mail attachment can also be provided upon special request).  We suggest that you contact your HNAS support representative to request that an FTP userid account be set-up for your organization if you haven't already done so.

HNAS V2R3M0 APAR Summary Matrix

              Please refer to the X.25 HostNAS (HNAS) Product Notices web page
              section HNAS V2R3M0 - Release Status for additional information.

2007-mm-dd  - APAR 230nnnn  (was problem 200n---A ) -or- (was unpublished problem 200n___A)

       APAR:  230nnnn_P  
     STATUS:  PENDING
     
         END: 

2006-04-01  - APAR 2309999 

       APAR:  2309999  
     STATUS:  SERVICE_NOTICE-[END_OF_MAINTENANCE/APAR_CYCLE]
  OPEN_DATE:  ----------
  MEMO_DATE:  2006-12-27
 CLOSE_DATE:  2007-04-01
 SERVICE(S):  ALL_V2R3M0
  MANDATORY:  NO, (PLEASE_READ_THIS_NOTICE)
 ORIGIN/REF:  N/A
   PTF_TYPE:  N/A
  PREREQ(S):  N/A
   MACRO(S):  N/A
  OBJECT(S):  N/A
  SOURCE(S):  N/A

     NOTICE:  V2R3M0 General Maintenance/APAR's no longer provided.

DESCRIPTION:  We no longer issue standard maintenance for this
              HNAS distribution level as of April 1, 2007.

              If you are unable to find a problem description in
              the V2R3M0 APAR logs we suggest that you review the
              V2R4M0 or V2R4Mn APAR logs for potential problem
              resolution.

              Comm-Pro will make every effort to provide emergency
              support for this distribution level although you may
              be required to upgrade to a newer level to resolve
              the problem.

   SOLUTION:  Refer to the HNAS V2R4Mn or higher maintenance logs
              and upgrade to a latter release (as required) which
              provides the corrective logic or enhancement.

 APPLY_INFO:  Upgrade HNAS distribution to V2R4Mn or higher. 

2007-01-16  - APAR 2300205  (was unpublished problem 2007011A)

       APAR:  2300205  
     STATUS:  CLOSED
  OPEN_DATE:  2007-01-11
 CLOSE_DATE:  2007-01-16
 SERVICE(S):  QLLC
  MANDATORY:  RECOMMENDED
 ORIGIN/REF:  230_CPA
     CPTECH:  PRT
  PTF_CLASS:  STANDARD-APAR
   PTF_TYPE:  (OBJ) HNASOBJX
    PTF_LOC:  FTP Server Directory /hnas_maint/hnas230m/apars/
              (Complete FIX is contained in the 2300205.ZIP file)
              SMP/E PTFs are provided via user request because the
              Comm-Pro supplied MCS is unique to each customer.
   COREQ(S):  N/A
  PREREQ(S):  Distribution dated after: 2005-08-20
              With APAR: 2300153 applied.
 SUPERSEDES:  N/A
  OBJECT(S):  VCCLEAR
  SOURCE(S):  N/A

    PROBLEM:  HALT AT LOC xxxxxx IN VCRCLR  : QLLC CLEAR LOGIC ERR
              due to an unusual timing sequence.

DESCRIPTION:  This problem is a result of a logic error in the HNAS
              QLLC receive Clear routine.  At our lab the problem
              occurred when a QLLC session was terminated with a
              VTAM command while HNAS was shutting down.

   SOLUTION:  Clear logic corrected.

CIRCUMVENTION: N/A

 APPLY_INFO:  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). 

2007-01-07  - APAR 2300204  (was problem 2006254A)

       APAR:  2300204  
     STATUS:  CLOSED
  OPEN_DATE:  2006-12-20
 CLOSE_DATE:  2007-01-07
 SERVICE(S):  CNFG IDLETO=
  MANDATORY:  YES
 ORIGIN/REF:  230_CPA
     CPTECH:  PRT
  PTF_CLASS:  STANDARD-APAR
   PTF_TYPE:  (OBJ) HNASOBJX and (SRC) HNASMACX
    PTF_LOC:  FTP Server Directory /hnas_maint/hnas230m/apars/
              (Complete FIX is contained in the 2300204.ZIP file)
              SMP/E PTFs are provided via user request because the
              Comm-Pro supplied MCS is unique to each customer.
   COREQ(S):  N/A
  PREREQ(S):  Distribution dated after 2006-05-18
              With APAR: 2300196 applied.
 SUPERSEDES:  N/A

  OBJECT(S):  CNFGIDTO , CONSDRMT , CONSMRMT , MCHHL0RQ , MCHHL5RQ
              MCHPVCI  , NASCNFG  , QLSSCP   , VCUT1    , XOTFCDC
              XOTGTCC  , XOTRCV

  SOURCE(S):  XFNASWA

    PROBLEM:  HNAS unaware of a lost TCP/IP session after remote
              network outage -- the IDLETO= parameter is not
              working properly.

DESCRIPTION:  Customer is having problems with hung LLC0 LUs.  The
              LUs are unaware that the TCP/IP session is gone. The
              problems relate to network difficulties.  The HNAS
              BUILD IDLETO=15 parameter was coded so that HNAS would
              clean up sessions that were inactive for 15 minutes.
              The parameter does not appear to be working.  HNAS
              becomes aware of the lost session when a 120 minute
              TCP keepalive operation fails.  Using VTAM to INACT/ACT
              the HNAS SLU with lost session also corrects the problem.

              This situation occurs when a SVC0=, SVC3= or SVC5=
              string on a TYPE=MCH REMOTE addresses a TYPE=MXT REMOTE
              coded without an IDLETO= parameter.  When this is done
              a 0 IDLETO value is recorded for the MXT and this value
              incorrectly overrides the IDLETO= value coded on BUILD
              or on the TYPE=MCH REMOTE.

   SOLUTION:  Revise configuration logic so that run time code can
              detect that no IDLETO= value was coded on an MCH/MXT/SPU
              REMOTE.  HNAS call setup logic will set the IDLE timeout
              interval using the SPU value (if coded), the MXT value
              (if coded), the MCH value (if coded) and lastly the
              the BUILD value (with a zero default).

CIRCUMVENTION: When a SVC0/3/5= definition string uses a MXT pointer
              code IDLETO=value on the named TYPE=MXT REMOTE if idle
              timeout logic is required.

 APPLY_INFO:  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).  

Last Update - March 31, 2007