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.
| APAR# | CLOSE_DATE | SERVICE |
PTF_TYPE |
PROBLEM |
|---|---|---|---|---|
|
240nnnn 240nnnn_D 240nnnn_E 240nnnn_M 240nnnn_P 240nnnn_R 240nnnn_U |
yyyy-mm-dd-> |
(blank) Deferred Enhancement Circumvention Pending Refresh Upgrade |
-> -> -> -> -> -> -> |
Denotes a Standard APAR. Fix or Enhancement deferred to a later (future) release. A new function has been added by this APAR. Circumvention is available, see APAR memo. APAR type pending assignment. Refresh up to/above this APAR number has to be installed. Upgrade to denoted HNAS VnRnMn has to be installed. |
| 2400nnn thru 2400064 | <Link forward> | - | - |
HNAS V2R4M0 - 2008 MAINTENANCE SUMMARY (Link to APARs 2400064 thru 2400nnn) |
| + | + | + | + | + |
|
2400063_E |
2007-12-17 |
Cons-Subsystem |
OBJ/SRC |
Enhancement providing improved debug and run-time history information in the HNAS SYSPRINT output for TRCTRAP and Shutdown SNAP Dump activity. |
|
Notice |
2007-12-12 |
edistribution |
<n/a> |
The HNAS product *.zip distributions are now generated under PKWARE ZIP version 9.0.0-l8 (prior distributions were generated under version 5.5.0b). The newer ZIP level files are downward compatible with earlier *.zip formats. |
| 2007-12-07 |
GATE |
OBJ |
NAS4709W REMOTE mch-mm lu-nm LU lu-addr LUIQ TIMEOUT, LUIQ BFR CT=0002 condition. |
|
| 2007-12-03 |
PVC, VTAM |
OBJ |
When a PLU terminates a PVC VTAM session there can be a delay (up to 60 seconds) before a new session can start. |
|
| 2007-11-29 |
Cons-Subsystem |
OBJ |
Console session hangs when DMCH FMT3 is entered and |
|
|
2400059_E |
2007-11-29 |
PVC Setup |
OBJ/SRC |
PVC Setup control OPTIONS=: |
| 2007-11-19 |
PVC, VTAM |
SRC |
ABEND U198 (NASHALT) HALT AT LOC 8006DA0C IN MCHLXBA : VTAM REQ LOST. |
|
| 2007-10-29 |
Cons-Subsystem |
OBJ |
TRCMCH default of GBL is confusing when RNM=rmtname |
|
| 2007-10-29 |
Configuration |
OBJ |
NASHALT - 0198 ABEND during HNAS activation CDF pre-scan processing can occur if TYPE= operand is omitted from the LOCAL or REMOTE definition statement. |
|
|
2400055_E |
2007-10-17 |
TAP |
OBJ/SRC |
Enhancement (OPTIONS=NOCLOSEONTAPFAILURE) allowing users to activate TAP (XOT Keep Alive) processing without HNAS taking a REMOTE down (out of service) if a TAP Contact Lost failure occurs. Retry counter also added to end of NAS2511M XOT TAP TIMEOUT, RESPONSE NOT RECEIVED... monitor message. |
| 2007-10-10 |
GATE FC |
OBJ |
Due to an error introduced by APAR 2400035, parsing of |
|
| 2007-09-23 |
PVC |
OBJ |
PVC fixes and general improvements: |
|
|
2400052_E |
2007-09-17 |
TRCLMT= |
OBJ |
Enhancement providing larger trace table limits. |
|
2400051_E |
2007-09-14 |
Debug - Buffer processing. |
OBJ |
Enhancement providing buffer allocation and release timestamp and tracestamp. |
| 2007-09-05 |
BUILD ALRMFLTR= |
OBJ |
Alarm filtering may not be provided when the default disposition (first ALRMFLTR= suboperand) is omitted. |
|
| 2007-08-30 |
Callout |
OBJ |
Outbound call can fail (NAS7720W alert message) when the LOCAL statement has a SOCLMT= greater that 2000. |
|
|
2400048_E |
2007-08-22 |
Cons-Subsystem |
SRC |
Enhancement providing the ability to specify a larger number of start parameters in the HNAS EXEC PARM= operand by supporting abbreviated start parameter operands. |
| 2007-08-22 |
PVC support |
OBJ |
PVC fixes and general improvements: |
|
| 2007-08-20 |
Cons-Subsystem |
OBJ |
General console subsystem cleanup: |
|
| 2007-08-14 |
ALARM Logging |
SRC |
Some TCPIP and QLLC alarms are incorrectly counted resulting in an erroneous display when ALARM LOG=? is issued. |
|
|
2400044_E |
2007-08-14 |
Cons-Subsystem |
OBJ/SRC |
Enhancement providing XOT TAP monitoring filtering options and changes to the NAS2513M message produced during MON TAP to provide the same information that the NAS2613M message does for PING. |
| 2007-08-01 |
GATE |
OBJ |
OSI/CS ABEND after processing RESET CAUSE=03 DIAG=02 and |
|
|
2400042_E |
2007-07-13 |
TCP/IP |
OBJ/SRC |
Debugging enhancement that logs diagnostic information within each TCPIP external interrupt data record. |
| 2007-06-26 |
GATE Callout |
OBJ |
NAS5701E REMOTE mch-nm 2 MIN HDR BFR WAIT. NAS FREE |
|
| 2007-06-06 |
LOGTAB and USSTAB processing |
OBJ |
MCHSOL logon and/or USS table processing can fail and error message NAS5703W is generated when the LOGTAB= and/or USSTAB= is omitted from a REMOTE. |
|
|
2400039_E |
2007-06-06 |
Cons-Subsystem |
OBJ/SRC |
Enhancement providing destination IPADDR and DTEADDR |
| 2007-05-23 |
Product Install |
SRC |
During product
installation the assembly of VTMTR |
|
| 2007-05-09 |
Cons-Subsystem |
OBJ |
The last digit of the DTEADDR= value in a PING Call Request packet is dropped when an odd number of digits is specified and DCEADDR=NULL|NONE is in effect for a referenced TYPE=DMY REMOTE. |
|
|
2400036_E |
2007-04-26 |
|
OBJ/SRC |
Enhancement option is now available that when invoked will remove extraneous blanks from NASnnnns Configuration and Alert messages. |
|
2400035_E |
2007-04-20 |
GATE-FC |
OBJ/SRC |
Enhancement allowing decimal GATE Fast Connect SLU name generation based upon LUNAME=(sluname/pluname/pfxlu{-D} follower. |
| 2007-04-11 |
Cons-Subsystem |
OBJ/SRC |
General EXEC LIST code cleanup, no runtime problems. |
|
|
2400033_R |
2007-04-09 |
Cons-Subsystem |
<Refresh
Required |
1)
An 0198 ABEND (NASHALT) can occur when PING dmyname |
|
2400032_RE |
2007-04-09 |
Cons-Subsystem |
<Refresh |
Enhancement allowing
customers to modify and reload the LOGTAB=lgtbname and USSTAB=ustbname
via the MRMT type -R option. |
|
2400031_E |
2007-03-29 |
VTAM |
OBJ |
Enhancement providing new NAS3711W alert message providing PLU sense data when a -RSP condition causes a clear. |
| 2007-03-09 |
Cons-Subsystem |
OBJ/SRC |
NAS251xM MON TAP and NAS261xM PING messages are displayed on SYSCONS when they should not be. |
|
|
2400029_E |
2007-03-07 |
Configuration |
OBJ |
1)
HNAS configuration has been modified to pass MCH VTAM |
|
2400028_R |
2007-03-03 |
Cons-Subsystem, |
<Refresh |
This APAR contains a collection general maintenance |
| 2007-02-21 |
Cons-Subsystem |
OBJ/SRC |
This APAR
addresses the following console subsystem fixes: |
|
| 2007-02-08 |
Cons-Subsystem |
OBJ |
The PFXWTO command can be rejected when 'text' is given followed by another PFXWTO command. |
|
| 2007-02-01 |
Multiple router Callout Support |
OBJ |
HALT AT LOC xxxxxx IN XOTBXM : INV VC when multiple router are employed for callout operation. |
|
| 2007-01-31 |
Cons-Subsystem |
OBJ |
The MLCL command does not update NEWDEFN CDF correctly after APAR 2400021 is applied. |
|
| 2007-01-30 |
Cons-Subsystem |
OBJ |
DMAP command display can give erroneous information for some modules. |
|
|
2400022_E |
2007-01-30 |
Cons-Subsystem |
OBJ/SRC |
Ability to route NAS2xyyM PING and MON TAP monitor status messages to SYSCONS as well as SYSPRINT. |
|
2400021_E |
2007-01-26 |
Cons-Subsystem |
OBJ/SRC |
This Enhancement APAR
addresses the following console and debugging improvements: |
|
2007-01-17 see rev_date |
QLLC |
OBJ |
HALT AT LOC xxxxxx IN VCRCLR : QLLC CLEAR LOGIC ERR due to an unusual timing sequence. |
|
| 2007-01-15 |
Cons-Subsystem |
OBJ |
1)
Some forced alarm messages can be filtered out when they should not be. |
|
|
2007-01-13 see rev_date |
CNFG IDLETO= |
OBJ |
This APAR addresses the
following configuration, runtime and alert message problem issues: |
|
| - | - | - | - | - |
| 2400017 thru 2400000 | <Link back> | - | - |
HNAS V2R4M0 - 2006 MAINTENANCE SUMMARY (Link to APARs 2400000 thru 2400017) |
| - | - | - | - | - |
| 240nnnn_i | yyyy-mm-dd |
GATE/LLCn/ PVC/QLLC/... |
ZAP/SRC/ OBJ/DOC/ CNFG/... |
<-Brief Problem Description-> 240nnnn_i= APAR Type - (blank) Denotes as a Standard APAR. _D - Deferred to a later release. Memo only, no PTF (fix) issued. Corrective logic or support will be provided in a future release. _E - Enhancement-APAR assignment. Denotes enhancement introduced after initial product release date. A new function has been added by this APAR. _M - Circumvention available (C reserved for custom identification). _P - Pending assignment. _R - Refresh edistribution required. To benefit from this APAR, a refresh release, up to this APAR number or most recent, has to be installed. _U - Upgrade required to the designated release. Memo only, no PTF (fix) issued. See link vrmnnnn_i table for an expanded description. |
| - | <Deferred> |
- |
<-> |
Denotes that problem resolution was deferred to a latter release although an apar memo is present describing the problem/reference. |
|
- |
- | <Enhancement> |
<-> |
Depicts an enhancement, not a problem fix. |
Please refer to the X.25 HostNAS (HNAS) Product Notices web page
section HNAS V2R4M0 - Release Status for additional information.
2007-12-17 - APAR 2400063 (was unpublished problem 2007340A)
APAR: 2400063_E
STATUS: CLOSED
OPEN_DATE: 2007-12-06
CLOSE_DATE: 2007-12-17
SERVICE(S): TRCTRAP and Shutdown SNAP Dump Processing
MANDATORY: NO
ORIGIN/REF: 240_cpt
CPTECH: PRT/SFD
PTF_CLASS: ENHANCEMENT-APAR
PTF_TYPE: (OBJ) HNASOBJX and (SRC) HNASMACX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400063.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: 2007-11-29
With APAR: 2400059 applied.
Refresh recommended if you are below the 2400055 level.
SUPERSEDES: N/A
OBJECT(S): CONSDNAS , CONSTRTR , MCHUT2 , NASUTIL
SOURCE(S): NASMAIN , NASTCP , XFNASWA , XFIDR
PROBLEM
ENHANCEMENT: Enhancement providing improved debug & run-time
history information in the SYSPRINT output for
TRCTRAP and Shutdown SNAP Dump activity.
DESCRIPTION: SNAP dump now provides the following identifiers
and sections:
%%BEGIN-SNAP - Begin of SNAP dump identifier
DNAS AREA - Raw DNAS Cust Ship info (unformatted)
APAR AREA - Raw APAR Identifiers (unformatted)
ALARM AREA - Raw Alarm counters (unformatted)
%%END-SNAP - End of SNAP dump identifier
SOLUTION: HNAS logic added to provide these enhancements.
Note: In addition to the enhancement documented in
this memo, 2 other TRCTRAP related changes are
also included.
1) REMEALL in the NAS0050A message was changed
to RSMEALL which is the correct spelling.
2) The ddname in the NASC121E message which can
be displayed incorrectly has been fixed (The
incorrect ddname display occurred when a new
ddname was entered which was shorter than
the old ddname).
CIRCUMVENTION: Enter display commands before and after Snap dump.
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-12-07 - APAR 2400062
APAR: 2400062
STATUS: CLOSED
OPEN_DATE: 2007-12-05
CLOSE_DATE: 2007-12-07
SERVICE(S): GATE
MANDATORY: YES
ORIGIN/REF: 240_nbg
CPTECH: PRT
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400062.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: 2007-03-05
With APAR: 2400028 applied.
REFRESH recommended if you are below 2400055 level.
SUPERSEDES: N/A
OBJECT(S): VCCLEAR
SOURCE(S): N/A
PROBLEM: NAS4709W REMOTE mch-mm lu-nm LU lu-addr LUIQ
TIMEOUT, LUIQ BFR CT=0002
DESCRIPTION: The NAS4709W alert indicates that input messages
from the remote have been on the LU input queue
for over 4 minutes. In this case the alert
indicates a hung LU resource.
This occurs for a GATE session when a Clear packet
is received in the middle of an m-bit chain. The
Clear packet is placed after the message being
accumulated so that the clear can be sent to the
GATE CTCP. HNAS then, incorrectly, waits for a
data packet with M=0 to complete the m-bit chain
being received. Because of the Clear, this will
never happen.
SOLUTION: HNAS Clear processing changed to mark the queued
message complete. This will cause the message
fragment and the inbound clear to be delivered to
the CTCP.
This problem was originally 2300143. The problem
re-appeared in V2R4M0 because of an error made
when the V2R3M0 fix was copied to V2R4M0.
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-12-04 - APAR 2400061 (was unpublished problem 2007280A)
APAR: 2400061
STATUS: CLOSED
OPEN_DATE: 2007-10-07
REV_DATE: 2007-12-04 - XOTXMTC added to memo OBJECT(S): list
CLOSE_DATE: 2007-12-03
SERVICE(S): PVC
MANDATORY: RECOMMENDED if PVCs used.
ORIGIN/REF: 240_CSK
CPTECH: PRT
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400061.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: 2007-09-23
With APARs: 2400053 applied.
SUPERSEDES: N/A
OBJECT(S): VCRESET XOTXMTC
SOURCE(S): N/A
PROBLEM: When a PLU terminates a PVC VTAM session there can
be a delay (up to 60 seconds) before a new session
can start.
DESCRIPTION: When a PLU terminates a PVC VTAM session (UNBIND,
NOTIFY, CLEANUP, TPEND) HNAS closes the VTAM ACB
and sends a RESET to the remote session with an
appropriate diagnostic code. The ACB is reopened
by timer logic. The delay to the OPEN may be as
long as 60 seconds. During this time the PVC LU
cannot be acquired by the PLU. This may cause the
PLU to fail.
This condition was observed in an environment where
a batch program was utilized to open the session,
initiate the transaction and close the session.
The batch program failed if it was not able to re-
acquire the HNAS LU because the LU's ACB was not
open. HNAS timer logic, which could take up to 60
seconds, reopens the ACB.
SOLUTION: When a RESET-Confirm is received or transmitted to
a PVC HNAS (with this APAR) will re-open a closed
PVC LU's ACB without delay.
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-11-29 - APAR 2400060
APAR: 2400060
STATUS: CLOSED
OPEN_DATE: 2007-11-29
CLOSE_DATE: 2007-11-29
SERVICE(S): DMCH FMT3 processing
MANDATORY: YES
ORIGIN/REF: 240_CPT
CP_TECH: SFD
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400060.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): 2400042 and associated APAR chains.
SUPERSEDES: N/A
SOURCE(S): N/A
OBJECT(S): CONSDMCH
OVERVIEW: See Problem
PROBLEM: Console session hangs when DMCH FMT3 is entered and
RNM= is not set.
DESCRIPTION: Due to an error introduced with APAR 2400027, the DMCH
FMT3 command no longer works when an RNM= value is not
set. The console session hangs and no further input
can be processed. This occurs because of a bad branch
in the FMT3 logic that causes subsequent DMCH command
processing to be bypassed.
SOLUTION: The DMCH FMT3 processor has been modified to correct
the bad branch.
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-12-01 - APAR 2400059 (was problem 2006106A, 2006270A and
unpublished problem 2007288A)
APAR: 2400059_E
STATUS: CLOSED
OPEN_DATE: 2007-11-01 (various problem enhancement dates)
CLOSE_DATE: 2007-11-29
SERVICE(S): PVC Setup Enhancements
MANDATORY: NO
ORIGIN/REF: 240_CPT,230_FIS,240_CSK
CPTECH: SFD/PRT
PTF_CLASS: ENHANCEMENT-APAR
PTF_TYPE: (OBJ) HNASOBJX and (SRC) HNASMACX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400059.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: 2007-10-17
With APAR: 2400055 applied.
Refresh recommended for systems below the 2400055 level.
SUPERSEDES: N/A
OBJECT(S): CNFGOPTS , CONSDRMT , CONSMRMT , MCHHL0RQ , MCHHL5RQ ,
MCHNRQC , MCHPVCI , MCHTMR , VCCLRQ , VCUT1 ,
XOTRCV , XOTXMTC
SOURCE(S): VCDD , XFNASWA
OVERVIEW: PVC operational enhancements:
PROBLEM1: NO way to control the frequency of HNAS attempts to
establish the VTAM session between an XOT PVC VC and
the PLU.
PROBLEM2: No way to control the frequency of PVC SETUP packets
sent by HNAS to establish the a PVC session with the
router.
PROBLEM3: No way to specify PVC SETUP response status so that a
PVC can be shutoff at the router.
Solution 1: OPTIONS=PVCRECONTMR=secs may be coded on TYPE=MCH or
TYPE=MXT REMOTE statements. The value coded for secs
specifies how often HNAS tries to reconnect the VTAM
session between a PVC VC and the PLU.
If PVCRECONTMR= is omitted on a TYPE=MCH REMOTE a
default value of 60 seconds will be used. If
PVCRECONTMR= is omitted on a TYPE=MXT REMOTE no
default value is set and the root MCH value will be
used.
Values between 5 and 254 may be coded for secs.
Solution 2: OPTIONS=PVCSETUPTMR=secs may be coded on TYPE=MCH or
TYPE=MXT REMOTE statements. The value coded for secs
specifies how often HNAS should send a PVC SETUP
packet to establish a PVC session with the router.
The option only has meaning if the PVC definition in
the HNAS CDF identifies a router to be used for the
session (see PVC= operand description in Chapter 4).
If PVCSETUPTMR= is omitted on a TYPE=MCH REMOTE a
default value of 60 seconds will be used. If
PVCSETUPTMR= is omitted on a TYPE=MXT REMOTE no
default value is set and the root MCH value will be
used.
Values between 10 and 254 may be coded.
Solution 3: OPTIONS=PVCSETUPREJ=code may be coded on TYPE=MCH or
TYPE=MXT REMOTE statements. The value coded for code
specifies a hexadecimal PVC SETUP reject status value
that will be used any time HNAS receives a SETUP for
the PVC. Since a status code greater than X'0F' causes
the router to stop sending SETUP packets for the PVC,
this option may be used to make the router stop sending
SETUP packets for selected PVCs.
If PVCSETUPREJ= is omitted, SETUP packets are processed
normally (status code to connect or reject the session
generated by HNAS in accordance with RFC 1613).
code is specified as a hex value between 00 and 7F.
X'' framing characters are not to be used. The value
hex 12 is not allowed because this is the status code
used in a PVC CONNECTED SETUP response. The value 0
is treated the same as omitted (0 is not valid as a
SETUP response status code).
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-11-19 - APAR 2400058 (was unpublished problem 2007322A)
APAR: 2400058
STATUS: CLOSED
OPEN_DATE: 2007-11-18
CLOSE_DATE: 2007-11-19
SERVICE(S): PVC, VTAM
MANDATORY: YES
ORIGIN/REF: 240_CSK
CPTECH: PRT
PTF_CLASS: STANDARD-APAR
------------
PTF_TYPE: (SRC) HNASMACX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400058.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: 2007-04-09
With APAR: 2400032 applied.
SUPERSEDES: N/A
OBJECT(S): N/A
SOURCE(S): VTMUT1
PROBLEM: HALT AT LOC 8006DA0C IN MCHLXBA : VTAM REQ LOST
DESCRIPTION: Validity check ABEND. HNAS is processing a buffer
request for PLU data but there is no active request
in the LU.
When a CLEANUP request is received for an LU the LU
is refreshed (ACB closed, LU purged from queues). If
the LU has a PVC VC attached the VC buffer request
queue is not purged of PLU buffer requests. When the
VC request queue is serviced the HALT occurs because
the LU no longer has an active PLU request (because
of the CLEANUP).
SOLUTION: HNAS 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-10-29 - APAR 2400057 (was unpublished problem 2007277A)
APAR: 2400057
STATUS: CLOSED
OPEN_DATE: 2007-10-04
CLOSE_DATE: 2007-10-29
SERVICE(S): TRCMCH LCL|GBL processing
MANDATORY: NO
ORIGIN/REF: 240_SIK
CPTECH: SFD
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400057.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) APAR 2400055 and associated APAR chains.
SUPERSEDES: N/A
OBJECT(S): CONSTMCH
SOURCE(S): N/A
PROBLEM: TRCMCH default of GBL is confusing when RNM=rmtname
modifier is provided.
DESCRIPTION: Currently, GBL is the default parameter for the ICR,
OCR, ICRF, ICLR and OCLR parameters even when an
RNM= modifier value is given. For example:
HNASCMD-> TRCMCH MCH1 ICR
HNASXEQ-> TRCMCH RNM=MCH1 GBL ICR ON
For HNASCMD-> input, the user probably intended ICR
to have local significance for the MCH named MCH1.
However, the HNASXEQ-> echo of the command shows that
ICR has global significance even though RNM=MCH1 is
given.
SOLUTION: HNAS will be modified to force a default of LCL when
LCL|GBL is not specified but RNM= or ID= is specified.
GBL will still be the default when RNM= and ID= are
not set. Examples:
HNASCMD-> TRCMCH MCH1 ICR <- RNM provided
HNASXEQ-> TRCMCH RNM=MCH1 LCL ICR ON
HNASCMD-> TRCMCH ICR <- no RNM or ID
HNASXEQ-> TRCMCH GBL ICR ON
HNASCMD-> TRCMCH MCH1 GBL ICR <- RNM with GBL
HNASXEQ-> TRCMCH RNM=MCH1 GBL ICR ON
CIRCUMVENTION: Enter LCL or GBL as appropriate.
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-10-29 - APAR 2400056
APAR: 2400056
STATUS: CLOSED
OPEN_DATE: 2007-10-26
CLOSE_DATE: 2007-10-29
SERVICE(S): Configuration processing, LOCAL|REMOTE TYPE= operand.
MANDATORY: YES
ORIGIN/REF: 240_CPT
CPTECH: SFD
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400056.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) APAR 2400055 and associated APAR chains.
SUPERSEDES: N/A
OBJECT(S): NASCNFG
SOURCE(S): N/A
PROBLEM: NASHALT, 0198 ABEND can occur if TYPE= operand is
omitted from LOCAL or REMOTE definition statement.
DESCRIPTION: An ABEND can occur during CDF pre-scan processing if
the TYPE= operand is not specified for a LOCAL or
REMOTE definition statement. This is due to the
default type of XTP not being set during the CDF
pre-scan pass. The default type of XTP is set
during normal CDF scan processing but erroneously
was not set during the pre-scan pass.
SOLUTION: HNAS has been modified to set the default TYPE to
XTP during the CDF pre-scan pass as it does during
the normal CDF scan pass.
CIRCUMVENTION: Ensure that a TYPE= value is specified.
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-10-17 - APAR 2400055 (was unpublished problem 2007268A)
APAR: 2400055_E
STATUS: CLOSED
OPEN_DATE: 2007-09-25
CLOSE_DATE: 2007-10-17
SERVICE(S): TCP/IP TAP XOT processing
MANDATORY: NO, but recommended for improved diagnostics.
ORIGIN/REF: 240_CPT
CPTECH: SFD
PTF_CLASS: ENHANCEMENT-APAR
PTF_TYPE: (SRC) HNASMACX and (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400055.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) APARs 2400045 and associated APAR chains.
SUPERSEDES: N/A
OBJECT(S): CNFGOPTS, CONSDRMT, CONSMRMT, MCHFCI, MCHSVCI, NASCNFG
SOURCE(S): NASTCP, XFBLK, XFNASWA
ENHANCEMENT: Customers would like to activate TAP (XOT Keep Alive)
processing without taking a REMOTE down (out of
service) if a TAP Contact Lost failure occurs.
DESCRIPTION: Currently, if 2 consecutive TAP failures occur, HNAS
assumes that the remote router is down and then resets
all the active TCPIP sockets associated with the failed
router. All LU/VC connections to the router are also
closed.
Sometimes, a customer would like to monitor the TAP
process (MONTAP) and leave the connections active even
when it appears that the router is down.
SOLUTION: HNAS has been modified to accept NOCLOSEONTAPFAILURE as
a new REMOTE option. When OPTIONS=NOCLOSEONTAPFAILURE
is specified for a TYPE=XOT REMOTE, a TAP failure will
not cause all active connections to the router to be
closed. The sessions will remain active even though the
router is marked as down. When a TAP failure occurs,
the following message is generated based on the setting
of the {NO}CLOSEONTAPFAILRE option.
NAS2502E CLIENT=010.117.056.100(02704) SOCKID=0001
PCEID=000B NAME=R1CNIN
NAS2502E ROUTER CONTACT LOST, CLOSEONTAPFAILURE
OPTION IS IN EFFECT
NAS2505E CLIENT=010.117.056.100(02704) SOCKID=0001
PCEID=000B NAME=R1CNIN
NAS2505E ROUTER CONTACT LOST, NOCLOSEONTAPFAILURE
OPTION IS IN EFFECT
In addition, the new option can be toggled using the
MRMT command as follows:
MRMT rmtname OPTIONS={NO}CLOSEONTAPFAILURE
The DRMT command will display the current TAP failure
option. CLOSEONTAPFAILURE can only be specified as an
MRMT option and is the default when NOCLOSEONTAPFAILURE
is not specified in the CDF.
The MONTAP NAS2511M message was also modified to
display a retry count (ddddd). The count is reset
when a successful TAP response is received. The
count indicates the number of unsuccessful TAP
attempts.
NAS2511M CLIENT=010.117.056.100(02704) SOCKID=0001
PCEID=000B NAME=R1CNIN
NAS2511M XOT TAP TIMEOUT, RESPONSE NOT RECEIVED
FOR CONNECTION SETUP (ddddd)
Note: If MRMT rmtname OPTIONS=CLOSEONTAPFAILURE is
entered when NOCLOSEONTAPFAILURE was in effect
and router contact was lost (NAS2505E message
was issued), all active connections to the
down router are immediately closed and the
following message is generated:
NAS2507E CLIENT=010.117.056.100(02704) SOCKID=0001
PCEID=000B NAME=R1CNIN
NAS2507E ROUTER CONTACT LOST, CLOSEONTAPFAILURE
OPTION IS IN EFFECT
This message is identical to the NAS2502E message
except for the message ID.
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-10-10 - APAR 2400054
APAR: 2400054
STATUS: CLOSED
OPEN_DATE: 2007-10-10
REVISE_DATE: 2007-mm-dd
CLOSE_DATE: 2007-10-10
SERVICE(S): GATEFC LUNAME= decode processing
MANDATORY: YES
ORIGIN/REF: 240_BNP
CP_TECH: SFD
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400054.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): 2400040 and associated APAR chains.
SUPERSEDES: N/A
SOURCE(S): N/A
OBJECT(S): CNFGLUNM
OVERVIEW: See Problem
PROBLEM: Due to an error introduced by APAR 2400035, parsing of
the LUNAME= operand for GATEFC can cause the LUNAME=
operand to be rejected and HNAS to terminate during
activation.
DESCRIPTION: APAR 2400035 was issued to allow GATEFC data session
SLU names to be generated in decimal or hex. This
is accomplished by appending a -D or -H to the PFXLU
value (-H is assumed if omitted). The syntax for
the GATEFC LUNAME= operand is as follows:
REMOTE LUNAME=(...,SLUNM-{A|I}
/PLUNM{||*}
/PFXLU-{D|H}
/SFXST
/SLUCT,..)
The problem occurs when the SFXST value is zero (0).
This causes the initialization of the SLUCT limit
value to be bypassed. When the uninitialized SLUCT
limit value is compared against the given SLUCT value,
it causes the SLUCT to be rejected and hence HNAS
to terminate after the entire CDF is scanned.
SOLUTION: HNAS has been modified to initialize the SLUCT limit
value when zero is specified for SFXST.
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-09-23 - APAR 2400053 (was unpublished problem 2007263A)
APAR: 2400053
STATUS: CLOSED
OPEN_DATE: 2007-09-20
CLOSE_DATE: 2007-09-23
SERVICE(S): PVC
MANDATORY: YES
ORIGIN/REF: 240_FIS
CPTECH: PRT
PTF_CLASS: STANDARD-APAR
------------
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400053.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): N/A, REFRESH recommended (CONTACT SUPPORT SERVICES).
SUPERSEDES: N/A
OBJECT(S): MCHHL0RQ , MCHHL5RQ , MCHNRQC , MCHTMR ,
VCCLRQ , VCDAT , VCRESET , XOTBXM
SOURCE(S): N/A
------------
PROBLEM1: ABEND U198 HALT AT LOC 8008F252 IN VTMLUFM : LU DIRTY
DESCRIPTION1: When a PVC LU has no VTAM session inbound data causes:
NAS5705W RESET SCHEDULED ON MCH mch-nm VC vc-addr
lu-nm LU lu-addr CAUSE/DIAG=000/196 (00/C4) DIAGX=0000
DIAG=196 (VTAM FMD send error) indicates that PVC data
could not be sent to the PLU because there was no VTAM
session.
The NASHALT was caused when 2 consecutive inbound
messages arrived at nearly the same time. A logic
error occurs when processing of the second message
starts before processing of the first message has
completed.
SOLUTION1: HNAS logic corrected.
PROBLEM2: Meaning of the NAS5705 alert is not always clear.
DESCRIPTION2: The NAS5705 alert reports the failure of a VTAM SEND
macro. This can mean that a problem was reported by
VTAM or that there was no session with the PLU.
SOLUTION2: The NAS5705 alert will be issued with DIAG=196 and
DIAGX=0001 when the RESET reflects the fact that
the PVC VTAM session has not been bound.
PROBLEM3: The PVC VTAM session connect timer (used to control
how often HNAS issues a REQSESS VTAM macro to ask
the PLU for a BIND) has varying values.
DESCRIPTION3: The timer values varied depending on the type of
REQSESS failure. This has caused problems for some
PVC users.
SOLUTION3: A value of 60 seconds is now used. This will mean
that sessions will start more quickly and that the
NAS3702W REQSESS FAILED alert message will be issued
more often. The 60 second value matches the value
used for other 'permanent' sessions (callout, GATE
control).
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-09-17 - APAR 2400052
APAR: 2400052_E
STATUS: CLOSED
OPEN_DATE: 2007-09-17
CLOSE_DATE: 2007-09-17
SERVICE(S): TRCLMT= operand processing
MANDATORY: NO, but recommended
ORIGIN/REF: 240_CSP
CPTECH: SFD
PTF_CLASS: ENHANCEMENT-APAR
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400052.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) N/A
SUPERSEDES: N/A
OBJECT(S): CNFGTRLM
SOURCE(S): N/A
PROBLEM: Enhancement providing larger trace table.
DESCRIPTION: Some installations require a trace table larger than
current maximum of 32767 entries.
SOLUTION: HNAS has been modified to allow a TRCLMT= value up
to 1048575 entries.
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-09-14 - APAR 2400051
APAR: 2400051
OPEN_DATE: 2007-09-14
CLOSE_DATE: 2007-09-14
SERVICE(S): Buffer allocation and release processing.
MANDATORY: NO, but recommended
ORIGIN/REF: 240_CPT
CPTECH: SFD
PTF_CLASS: ENHANCEMENT-APAR
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400051.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) APAR 2400046 and associated APAR chains.
SUPERSEDES: N/A
OBJECT(S): NASUTIL
SOURCE(S): N/A
PROBLEM
ENHANCEMENT: Enhancement providing buffer allocation and release
timestamp and tracestamp.
DESCRIPTION: As an aid to diagnosing some types of problems, it is
advantageous to know when a buffer was allocated and
when it was released. Using the allocation timestamp
and release timestamp, it can be determined how long
a buffer has been in use. The current trace table
pointer is also saved at allocation and release so
these events can be correlated with trace activity.
SOLUTION: HNAS has been modified to log the current time and
current trace pointer when a buffer is allocated and
when it is released. These values are only used by
Comm-Pro support personnel for problem diagnosis.
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-09-05 - APAR 2400050
APAR: 2400050
STATUS: CLOSED
OPEN_DATE: 2007-09-05
REVISE_DATE: 2007-mm-dd
CLOSE_DATE: 2007-09-05
SERVICE(S): BUILD ALRMFLTR= operand processing
MANDATORY: NO, but recommended
ORIGIN/REF: 240_CPT
CP_TECH: SFD
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400050.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): 2400021 and associated APAR chains.
SUPERSEDES: N/A
SOURCE(S): N/A
OBJECT(S): CNFGAFLT
OVERVIEW: See Problem
PROBLEM: Alarm filtering may not be provided when the default
disposition (first ALRMFLTR= suboperand) is omitted.
DESCRIPTION: When the first ALRMFLTR= suboperand is not specified
but a comma place holder is, the ALRMFLTR= parser
erroneously treats the omitted disposition as an
alarm ID of ********(A). The means that all alarms
are allowed regardless of any subsequent alarm IDs
specified in the ALRMFLTR= list. For example if the
following is specified:
BUILD ALRMFLTR=(,
NAS2****(P),
NAS3701W(P))
The ALARM FILTER=? console command will display the
following:
HNASCMD-> ALARM FILTER=?
HNASXEQ-> ALARM FILTER=?
ALRMFLTR=ALLOW
********(A)
NAS2****(P)
NAS3701W(P)
The default disposition is set to ALLOW but a bogus
alarm ID entry of ********(A) is also set. Since the
filtering of alarms is processed from left to right
(first to last) in the ALRMFLTR= list, the ********(A)
alarm ID will allow all alarms to be sent to SYSCONS
before the other alarm IDs are tested.
SOLUTION: The ALRMFLTR= parser has been fixed to process the
omitted disposition correctly so that ALLOW is set
but the ********(A) alarm ID is not generated.
CIRCUMVENTION: Always specify a default disposition as the first
ALRMFLTR= suboperand. For example:
BUILD ALRMFLTR=(ALLOW,
NAS2****(P),
NAS3701W(P))
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-09-04 - APAR 2400049 (was unpublished problem 2007235A)
APAR: 2400049
STATUS: CLOSED
OPEN_DATE: 2007-08-07
CLOSE_DATE: 2007-08-30
SERVICE(S): CALLOUT
MANDATORY: YES
ORIGIN/REF: 240_SDD
CPTECH: PRT
PTF_CLASS: STANDARD-APAR
------------
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400049.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: 2004-08-22
With APAR: 2400047 applied.
SUPERSEDES: N/A
OBJECT(S): XOTUT1
SOURCE(S): N/A
------------
PROBLEM: NAS7720W MGO3 CALL OUT, CAN'T CALL CALLED
ADDR=9177374981000000 CALLING ADDR=6100121000000000
DESCRIPTION: When an outbound call is to be made HNAS refers to
the RTEOUT= operand on the LOCAL statement associated
with the MCH that has a call request (BIND received
for callout LU or GATE call request packet received
from a CTCP). RTEOUT=, in conjunction with the
called or calling DTE address, is used to identify a
TYPE=XOT REMOTE used for the call. This REMOTE
provides the target IP address for the XOT call and a
PCE control block used to maintain the TCP/IP session
for the call. As a validity check, the PCE allocation
routine ensures that the TYPE=XOT REMOTE's PCE points
at the original LOCAL statement. When the LOCAL
statement has a SOCLMT= greater that 2000 the validity
check can fail. This causes the outbound call to fail
with the NAS7720W alert.
CIRCUMVENTION: Code SOCLMT=2000 on the LOCAL statement (if possible).
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-08-22 - APAR 2400048
APAR: 2400048_E
STATUS: CLOSED
OPEN_DATE: 2007-08-16
REVISE_DATE: 2007-mm-dd
CLOSE_DATE: 2007-08-22
SERVICE(S): HNAS EXEC PARM= processing.
MANDATORY: NO
ORIGIN/REF: 240_CPT
CP_TECH: SFD
PTF_CLASS: ENHANCEMENT-APAR
PTF_TYPE: (SRC) HNASMACX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400048.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): 2400044 and associated APAR chains.
SUPERSEDES: N/A
SOURCE(S): NASMAIN
OBJECT(S): N/A
OVERVIEW: See Problem
PROBLEM
ENHANCEMENT: Provide the ability to specify a larger number of start
parameters in the HNAS EXEC PARM= operand by supporting
abbreviated start parameter operands.
DESCRIPTION: JCL restricts the PARM= value to 100 characters which
can be limiting for customers who need to specify many
HNAS start parameters.
SOLUTION: HNAS will be modified to allow abbreviations for new
and existing start parameters so that they will more
likely fit within the 100 character limit of the PARM=
operand. For example:
TLU MXDT for TRCLU MAXDATA will save 5 characters.
Abbreviated Existing Character
Parameter Parameter Savings
ALON ALLON 2
ALOF ALLOFF 3
CNCM CONCMDQ 3
MXDT MAXDATA 3
MNDT MINDATA 3
NODT NODATA 2
PKDT PKTDATA 3
APFX APFXEQ 2
ACHK AUTHCHK 3
CWRN CNFGWARN 4
FRUN FASTRUN 3
GNDF GENNWDF 3
MTAP MONTAP 2
PWTO PFXWTO 2
PCFG PRNTCNFG 4
PDAT PRNTDATE 4
PLU PRNTLU 3
POFF PRNTOFF 3
PON PRNTON 3
PQLC PRNTQLLC 4
PSYS PRNTSYS 3
PTCP PRNTTCP 3
PVC PRNTVC 3
PVTM PRNTVTAM 4
PXOT PRNTXOT 3
PXTP PRNTXTP 3
PCON RMTCONP 3
RCON RMTCONS 3
SCFG SHOWCNFG 4
SCMS SHOWCMSG 4
SCON SHOWCONS 4
SERR SHOWERR 3
SMOR SHOWMORE 4
SOFF SHOWOFF 3
SON SHOWON 3
SVRS SVRSTRT 3
TALL TRCALL 2
TBFR TRCBFR 2
TBRQ TRCBFRQ 3
TBST TRCBST 2
TCFG TRCCNFG 3
TCON TRCCONS 3
TDAT TRCDATA 3
TDBK TRCDBK 2
TDBG TRCDBUG 3
TDSP TRCDISP 3
TIO TRCIO 2
TLU TRCLU 2
TMCH TRCMCH 2
TMCX TRCMCHX 3
TPRT TRCPRNT 3
TSUB TRCSUBR 3
TTSK TRCTASK 3
TVC TRCVC 2
TWTO TRCWTO 2
CIRCUMVENTION: Most HNAS start parameters have console command
counterparts to toggle their value. For those that
do, specify these commands within the CONCMDQ=
operand on the BUILD definition statement.
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-08-22 - APAR 2400047 (was problem 2007198A)
APAR: 2400047
STATUS: CLOSED
OPEN_DATE: 2007-07-17
CLOSE_DATE: 2007-08-22
SERVICE(S): PVC Support
MANDATORY: RECOMMENDED
ORIGIN/REF: 240_BPS
CPTECH: PRT
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400047.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: 2007-04-09
With APARs: 2400032 Applied.
SUPERSEDES: N/A
OBJECT(S): MCHHL0RQ , MCHHL5RQ , XOTBXM , XOTUT1
SOURCE(S): N/A
PROBLEM 1: PVC VTAM session fails to restart after PVC SETUP
sequence completes.
PROBLEM 2: NAS3799I LU LBOF4BTL ENDING SESSION ON MCH XJ052 HNAS
CAUSE/DIAG=***/*** (**/**) DIAGX=****
PROBLEM 3: If VARY ID=pvc-pce-id is used to terminate a TCP/IP
session HNAS does not send a new PVC SETUP. The PVC
remains down.
DESCRIPTION 1: When a PVC SETUP sequence occurs HNAS sets a timer
that starts the VTAM session for the PVC. Under some
very unusual circumstances VC RESET processing can
clear the timer so that the VTAM session does not
start. The router normally sends a DIAG=0F RESET when
SETUP processing completes.
DESCRIPTION 2: When the PLU UNBINDs an HNAS PVC session the UNBIND
processor does not pass the cause code to the routine
that generates the NAS3799I message.
DESCRIPTION 3: If the ID for the VARY is the ID of the first PVC on a
TYPE=XOT REMOTE the active flag is reset for that PCE.
An error in the PCE allocation logic used to locate
a PCE for an outbound Call Request or PVC SETUP packet
incorrectly treats the flag as an indication that all
resources on the remote are inactive.
SOLUTION 1: HNAS RESET processing corrected.
SOLUTION 2: UNBIND routine corrected so that DIAG code appears in
NAS3799I alert.
SOLUTION 3: PCE allocation 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-08-20 - APAR 2400046
APAR: 2400046
STATUS: CLOSED
OPEN_DATE: 2007-08-17
REVISE_DATE: 2007-mm-dd
CLOSE_DATE: 2007-08-20
SERVICE(S): FASTRUN CONCMDQ and PFXWTO processing
MANDATORY: NO, but recommended
ORIGIN/REF: 240_CPT
CP_TECH: SFD
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400046.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): 2400042 and associated APAR chains.
SUPERSEDES: N/A
SOURCE(S): N/A
OBJECT(S): NASUTIL
OVERVIEW: See Problems
PROBLEM1: HNAS FASTRUN does not end after all queued console
commands are executed when CONCMDQ=cmdlist is
specified.
PROBLEM2: HNAS does not compress PFXWTO prefix text when the
SHOWCMSG option is in effect.
DESCRIPTION1: Logic added with APAR 2400001 causes HNAS to remain
active after all queued console commands have been
executed when FASTRUN CONCMDQ is in effect.
DESCRIPTION2: When the PFXWTO prefix text (via the PFXWTO text
follower or the NASNAME= value) is less than eight
characters and SHOWCMSG option is in effect, HNAS
does not remove the trailing blanks after the text
value.
SOLUTION1: HNAS FASTRUN CONCMDQ logic has been corrected so that
HNAS ends after all queued console commands have been
executed.
SOLUTION2: HNAS has been modified to remove trailing blanks from
the PFXWTO prefix text value when the SHOWCMSG option
is in effect.
CIRCUMVENTION1: Issue QY command to force HNAS to end.
CIRCUMVENTION2: 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-08-14 - APAR 2400045
APAR: 2400045
STATUS: CLOSED
OPEN_DATE: 2007-08-13
CLOSE_DATE: 2007-08-14
SERVICE(S): ALARM logging
MANDATORY: NO, but recommended.
ORIGIN/REF: 240_CPT
CPTECH: SFD
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (SRC) HNASMACX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400045.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) APARs 2400044 and associated APAR chains.
SUPERSEDES: N/A
OBJECT(S): N/A
SOURCE(S): NASTCP
PROBLEM: Some TCPIP and QLLC alarms are incorrectly counted
resulting in an erroneous display when ALARM LOG=?
is issued.
DESCRIPTION: Due to logic introduced by APAR 2400036, XFWTO flags
that used to be passed in register 0, byte 1 (R0B1)
are now passed in R0B2. Some XFWTO calls were not
adjusted for this new flag convention. The result is
that the 'more data' flag, which is used to associate
one message with another and which should be passed in
R0B2, is being passed in R0B1, the old convention.
When multiple line alarm is issued, the alarm is not
counted until the last line is written. All but the
last line carry the 'more data' flag. Because this
flag is being passed in R0B1 instead of R0B2, each
line of a multi-line message can look like the last
line, depending on the 'trash' in R0B2, which causes
causes the alarm count to be incremented more than it
should be. For example, the NAS2513M message below
can be counted 3 times instead of just once depending
on what value is in the uninitialized R0B2.
NAS2513M CLIENT=010.117.056.100(02704) SOCKID=0001 PCEID=000B
NAME=R1CNIN
NAS2513M XOT TAP SEQUENCE IS STARTING, TRANSMITTING CALL REQUEST
NAS2513M PKT=0000001F10010BA820360001303600010106420707430404 ...
SOLUTION: HNAS has been modified to pass the 'more data' flag in
R0B2, the correct byte.
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-08-14 - APAR 2400044 (was problem 2007114A)
APAR: 2400044_E
STATUS: CLOSED
OPEN_DATE: 2007-04-24
CLOSE_DATE: 2007-08-14
SERVICE(S): TCP/IP TAP Monitor processing
MANDATORY: NO, but recommended for improved diagnostics.
ORIGIN/REF: 240_HVB
CPTECH: SFD
PTF_CLASS: ENHANCEMENT-APAR
PTF_TYPE: (SRC) HNASMACX and (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400044.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) APARs 2400042, 2400039, 2400030
and associated APAR chains.
Note: Due to the large number of PREREQs, we
recommend a REFRESH distribution to pickup
this enhancement.
SUPERSEDES: N/A
OBJECT(S): CONSMON, CONSTALL, CONSTLU, CONSTVC, NASCONS,
SOURCE(S): NASMAIN, NASTCP, XFBLK, XFNASWA
ENHANCEMENT: Customer would like the NAS2513M message produced during
MON TAP to provide the same information that the NAS2613M
message does for PING.
DESCRIPTION: Currently, the NAS2513M message provides a hex display
of the Call Request packet fields while the NAS2613M
message lists the various fields by name making them
easier and faster to scan.
SOLUTION: HNAS has been modified to list Call Request fields for
the NAS2513M message by name in a manner similar to
what is done for the NAS2613M message.
This new feature is controlled by the new MON TAP
followers: PKTDATA, MAXDATA, MINDATA and NODATA.
PKTDATA (the default) causes the existing TAP monitor
messages with raw packet data to be displayed as
follows:
NAS2513M CLIENT=010.117.056.100(02704) SOCKID=0001 PCEID=000B
NAME=R1CNIN
NAS2513M XOT TAP SEQUENCE IS STARTING, TRANSMITTING CALL REQUEST
NAS2513M PKT=0000001F10010BA820360001303600010106420707430404 ...
NAS2515M CLIENT=010.117.056.100(02704) SOCKID=0001 PCEID=000B
NAME=R1CNIN
NAS2515M XOT TAP SEQUENCE IN PROGRESS, RECEIVED CLEAR REQUEST
NAS2515M PKT=000000051001130D40
NAS2513M CLIENT=010.117.056.100(02704) SOCKID=0001 PCEID=000B
NAME=R1CNIN
NAS2513M XOT TAP SEQUENCE IN PROGRESS, TRANSMITTING CLEAR CONFIRM
NAS2513M PKT=00000003100117
NAS2517M CLIENT=010.117.056.100(02705) SOCKID=0001 PCEID=000B
NAME=R1CNIN
NAS2517M XOT TAP SEQUENCE COMPLETED SUCCESSFULLY
MAXDATA causes the raw packet data to be withheld and
instead displays the values for the DTEADDR=, DCEADDR=
FAC= and CUD= operands as follows:
1 NAS2513M CLIENT=010.117.056.100(02704) SOCKID=0001 PCEID=000B
NAME=R1CNIN
2 NAS2513M XOT TAP SEQUENCE IS STARTING, TRANSMITTING CALL REQUEST
3 NAS2513M DTEADDR=20360001 DCEADDR=3036000101
4 NAS2513M FAC=06420707430404
5 NAS2513M CUD=01000000C8D5C1E2E3C1D7
6 NAS2515M CLIENT=010.117.056.100(02704) SOCKID=0001 PCEID=000B
NAME=R1CNIN
7 NAS2515M XOT TAP SEQUENCE IN PROGRESS, RECEIVED CLEAR REQUEST
8 NAS2515M DTEADDR=20360001
9 NAS2513M CLIENT=010.117.056.100(02704) SOCKID=0001 PCEID=000B
NAME=R1CNIN
10 NAS2513M XOT TAP SEQUENCE IN PROGRESS, TRANSMITTING CLEAR CONFIRM
11 NAS2513M DTEADDR=20360001 DCEADDR=3036000101
12 NAS2517M CLIENT=010.117.056.100(02705) SOCKID=0001 PCEID=000B
NAME=R1CNIN
13 NAS2517M XOT TAP SEQUENCE COMPLETED SUCCESSFULLY
MINDATA causes only the DTEADDR= and DCEADDR= values
to be displayed. Lines 4 and 5 are withheld.
NODATA causes text information to be displayed without
any packet data. This is still useful because the
REMOTE IPADDR= and NAME are displayed. Lines 3, 4, 5,
8 and 11 are withheld.
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-08-01 - APAR 2400043 (was unpublished problem 2007166A)
APAR: 2400043
STATUS: CLOSED
OPEN_DATE: 2007-06-15
CLOSE_DATE: 2007-08-01
SERVICE(S): GATE
MANDATORY: YES
ORIGIN/REF: 240_DBO
CPTECH: PRT
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (OBJ) HNASOBJX, but a REFRESH is recommended.
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400043.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: 2007-07-17
With refresh APAR: 2400042 applied.
SUPERSEDES: N/A
OBJECT(S): MCHBFR , MCHHL4RQ , MCHUT1 , VCRESET
SOURCE(S): N/A
PROBLEM: OSI/CS ABEND after processing RESET CAUSE=03 DIAG=02 and
an incorrect ERR/INFO packet from HNAS.
DESCRIPTION: If a RESET packet is received when the GATE PLU is sending
a large PIU and the X25 window for the session is closed
then HNAS processing of the RESET results in an ERR/INFO
packet being generated to report and invalid GATE command
byte from the PLU (CTCP). This ERR/INFO packet caused
the OSI/CS CTCP to ABEND.
The inbound RESET should have aborted the outbound PIU.
Because of an HNAS error only the first 128 bytes of
the PIU were discarded. Byte 129 was then processed as
a GATE command byte. This byte was not valid as a GATE
command so an ERR/INFO packet was generated to report
the 'problem'. The ERR/INFO packet header contains a
byte which has the current GATE command. The OSI/CS
CTCP ABENDs if the command in the ERR/INFO packet is not
a valid GATE command. An OSI/CS APAR has been issued
to fix this. HNAS is also being APARed because the RESET
should not have generated the bad command detection and
the subsequent ERR/INFO packet. While investigating this
problem we found out that the resource ID carried in the
ERR/INFO packet could have a non-zero leading hex digit
(in violation of GATE specifications). This problem is
also fixed by this APAR.
SOLUTION: HNAS RESET logic corrected and ERR/INFO packet's RES-ID
field leading digit zeroed.
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-07-13 - APAR 2400042 (created to help solve problem 2007178A)
APAR: 2400042_E
STATUS: CLOSED
OPEN_DATE: 2007-06-27
CLOSE_DATE: 2007-07-13
SERVICE(S): TCP/IP interface support
MANDATORY: NO, but recommended for improved debugging.
ORIGIN/REF: 240_BNP
CPTECH: SFD
PTF_CLASS: ENHANCEMENT-APAR
PTF_TYPE: (SRC) HNASMACX and (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400042.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) APARs 2400039, 2400038, 2400037, 2400034
and associated APAR chains.
Note: Due to the large number of PREREQs, we
recommend a REFRESH distribution to pickup
this enhancement.
SUPERSEDES: N/A
OBJECT(S): CNFGBFSZ, CNFGOPTS, CONSDLU, CONSDMCH, CONSDVC,
CONSMRMT, CONSPING, CONSTLU, CONSTLUQ, CONSTMCH,
CONSTMCX, CONSTVC, CONSTVCQ, MCHINI, NASCNFG,
NASUTIL, QLSSCP, XTPRCV
SOURCE(S): NASMAIN, NASTCP, XFBLK, XFPCE
PROBLEM
ENHANCEMENT: Enhancement that logs diagnostic information within
each TCPIP external interrupt data record.
DESCRIPTION: Customer has experienced a 0198 ABEND (NASHALT validity
check) after receiving the following alarm messages:
NAS2252E CLIENT=010.253.204.035(18640) SOCKID=0017
PCEID=010C NAME=XOTBNP3I
NAS2252E SELECT REQUEST INTERRUPT LOST,
SOCKET MUST BE CLOSED
These messages were followed by the following NASHALT:
HALT AT LOC 80061022 IN NASTCP : TCPIP REPLY ID FAILURE
ABEND dump contained TCPIP external interrupt table but
table did not contain enough information to determine
the cause of the NASHALT. Advised customer to run HNAS
TCPIP traces to collect additional diagnostic data.
SOLUTION: HNAS has been modified to log additional diagnostic
data within the TCPIP external interrupt area making
the need for HNAS TCPIP traces less of a requirement.
It should now be possible to resolve problem 2007178A
with the external interrupt table data only.
CIRCUMVENTION: Disable LU, MCH and VC traces and start global PCE
traces: TRCALL OFF TRCPCE ALLON
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-06-26 - APAR 2400041 (was unpublished problem 2007176A)
APAR: 2400041
STATUS: CLOSED
OPEN_DATE: 2007-06-25
CLOSE_DATE: 2007-06-26
SERVICE(S): GATE CALLOUT
MANDATORY: YES
ORIGIN/REF: 240_LBG
CPTECH: PRT
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400041.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-09-08
With APAR: 2400005 applied.
SUPERSEDES: N/A
OBJECT(S): MCHNRQC
SOURCE(S): N/A
PROBLEM: NAS5701E REMOTE mch-nm 2 MIN HDR BFR WAIT. NAS FREE
CT=00600 RMT BFR CT=00100 after Clear diag=195 (C3).
DESCRIPTION: When an internal clear is generated by HNAS during a
GATE callout operation an error in buffer release
logic keeps the MCH ownership count from being properly
updated. After 200 failures MCH xmit buffer allocation
stops waiting for buffers already allocated to be freed.
The buffers were freed but not properly accounted for
so transmit operations for the MCH will not resume.
The DIAG=195 internal clear occurs on a GATE callout
only if the call fails at the TCP/IP level -- in this
case with:
NAS2271W CONNECT REQUEST FAILED, RC=FFFFFFFF 00000041
This is an unusual event that resulted during a router
outage or router ipaddr problem.
SOLUTION: Buffer release 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-06-06 - APAR 2400040
APAR: 2400040
STATUS: CLOSED
OPEN_DATE: 2007-06-06
REVISE_DATE: N/A
CLOSE_DATE: 2007-06-06
SERVICE(S): LOGTAB and USSTAB processing
MANDATORY: YES
ORIGIN/REF: 240_TKK
CPTECH: SFD
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400040.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): 2400036 and associated APAR chains.
SUPERSEDES: N/A
SOURCE(S): N/A
OBJECT(S): CNFGLGTB, CNFGLUNM, CNFGUSTB, MCHSOL
OVERVIEW: See problem.
PROBLEM: MCHSOL logon and/or USS table processing can fail and
error message NAS5703W is generated when the LOGTAB=
and/or USSTAB= is omitted from a REMOTE.
DESCRIPTION: Due to an error introduced by APAR 2400032, it is
possible for logon and/or USS table processing to
fail when the associated table is not specified
for a REMOTE. This was discovered by a customer
using HNAS QLLC support (TYPE=SPU REMOTE).
When LOGTAB= and/or USSTAB= is omitted for a TYPE=SPU
REMOTE, corresponding value(s) from BUILD are not
propagated to the REMOTE. When MCHSOL gets control
it discovers a null LOGTAB= and/or USSTAB= value
which causes the error.
The error occurs because of a bad test in the MCHSOL
module that was not updated when APAR 2400032 was
introduced.
SOLUTION: Configuration logic has been modified to use the LOGTAB=
and/or USSTAB= value from BUILD if the corresponding
parameter is omitted for a TYPE=SPU REMOTE. In addition,
the MCHSOL module has been updated to correct the bad
table tests.
CIRCUMVENTION: Specify a LOGTAB= and/or USSTAB= value for the affected
TYPE=SPU REMOTE.
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-06-06 - APAR 2400039 (was unpublished problem 2007144A/2007130A)
APAR: 2400039_E
STATUS: CLOSED
OPEN_DATE: 2007-05-10 for 2007130A
2007-05-24 for 2007144A
CLOSE_DATE: 2007-06-06
SERVICE(S): PING console command processing.
MANDATORY: NO, but recommended
ORIGIN/REF: 240_NBG
CPTECH: SFD
PTF_CLASS: ENHANCEMENT-APAR
PTF_TYPE: (SRC) HNASMACX and (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400039.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) APAR 2400037 and 2400036 and associated APAR chains.
SUPERSEDES: N/A
OBJECT(S): CONSPING
SOURCE(S): XFBLK
PROBLEM
ENHANCEMENT: Enhancement providing destination IPADDR and DTEADDR
addresses in all PING response alarm messages as well
as providing a correlation sequence number in all
PING request and response messages.
DESCRIPTION: Customer has SYSPRINT alarm message scanning program
that isolates various HNAS alerts. Customer needs
the ability to easily correlate PING requests and
responses in SYSPRINT as well as easily identifying
the destination router IPADDR and network DTEADDR.
SOLUTION: HNAS has been modified to generate one line response
messages that provide succinct information for PING
and at the same time provide data that makes it easy
to correlate PING initiation and termination messages.
In lieu of the console name in PING response messages,
a correlation sequence number is provided along with
the target IPADDR= and DTEADDR= values. The following
sample messages illustrate the new PING information.
NAS2613M PINGING SOCKET=010.117.056.001(01998)
REQUESTED BY WACONPCE (00001)
NAS2613M DTEADDR=1036000103 DCEADDR=20361234
NAS2613M FAC=06420707430202
NAS2613M CUD=01000000
NAS2611M PING CALL TIMED OUT FOR SOCKET=010.117.056.001(01998)
DTEADDR=1036000103 (00001)
NAS2613M PINGING SOCKET=010.117.056.100(01998)
REQUESTED BY WACONPCE (00002)
NAS2613M DTEADDR=203643211 DCEADDR=20361234
NAS2613M FAC=06420707430202
NAS2613M CUD=01000000
NAS2615M PING CALL CLEARED (0D/40) FOR SOCKET=010.117.056.100(01998)
DTEADDR=203643211 (00002)
NAS2613M PINGING SOCKET=010.117.056.100(01998)
REQUESTED BY WACONPCE (00003)
NAS2613M DTEADDR=1036000103 DCEADDR=20361234
NAS2613M FAC=06420707430202
NAS2613M CUD=01000000
NAS2617M PING CALL ACCEPTED FOR SOCKET=010.117.056.100(01998)
DTEADDR=1036000103 (00003)
Note that the PING sequence number is displayed in
parentheses after the DTEADDR= value thus allowing
PING requests and responses to be correlated. The
requesting console name is provided in the NAS2613M
initiation message along with the PING sequence
number which becomes the correlation count in PING
responses.
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-05-24 - APAR 2400038 (was unpublished problem 2007143A)
APAR: 2400038
STATUS: CLOSED
OPEN_DATE: 2007-05-23
CLOSE_DATE: 2007-05-23
SERVICE(S): INSTALL, HNASMNT JOB & SMP RECEIVE JOB
MANDATORY: YES
ORIGIN/REF: 240_FIS
CPTECH: PRT
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (SRC) HNASMACX and (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400038.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: 2007-04-26
With APARs: 2400036 and 2400033 (refresh) applied.
SUPERSEDES: N/A
OBJECT(S): NASUTIL, OSUT1
SOURCE(S): XFMSG
PROBLEM: During product installation the assembly of VTMTR
receives CC=8 with the error message:
ASMA034E Operand PRTXBST beyond active USING ......
DESCRIPTION: This error occurs because APAR 2400036 introduced
changes to the XFMSG macro which increased it's
expansion size. The increased size moved the
PRTXBST symbol beyond addressability.
SOLUTION: VTMTR changed to move these symbols in range.
XFMSG has been modified to restore it's previous
expansion size. NASMSG service routine in module
OSUT1 and XFWTO service routine in module NASUTIL
modified to handle restored XFMSG macro.
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-05-09 - APAR 2400037
APAR: 2400037
STATUS: CLOSED
OPEN_DATE: 2007-05-09
REVISE_DATE: N/A
CLOSE_DATE: 2007-05-09
SERVICE(S): PING console command processing
MANDATORY: NO
ORIGIN/REF: 240_NBG
CPTECH: SFD
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400037.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): 2400033 and associated APAR chains.
SUPERSEDES: N/A
SOURCE(S): N/A
OBJECT(S): CONSPING
OVERVIEW: See problem.
PROBLEM: The last digit of the DTEADDR= value in a PING Call
Request packet is dropped when an odd number of digits
is specified and DCEADDR=NULL|NONE is in effect for
a referenced TYPE=DMY REMOTE.
DESCRIPTION: Logic introduced by APAR 2400033 that prevents trash
from being sent when DCEADDR=NONE|NULL is specified
inadvertently causes the last digit of an odd DTEADDR=
value to be dropped. The called DTE address field
ends up being an even number of digits even though
the called length is odd. This changes the position
of the facilities and call user data fields which can
confuse the router.
SOLUTION: The PING console command processor has been modified
to correct the problem with an odd DTEADDR= value and
a null DCEADDR= value.
CIRCUMVENTION: Ensure that a proper DCEADDR= value is specified
other than NONE|NULL.
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-04-26 - APAR 2400036 (was unpublished problem 2007103A)
APAR: 2400036_E
STATUS: CLOSED
OPEN_DATE: 2007-04-13
REVISE_DATE: 2007-mm-dd
CLOSE_DATE: 2007-04-26
SERVICE(S): WTO (Configuration & Alert Messages) processing
MANDATORY: NO, but recommended
ORIGIN/REF: 240_CPT
CP_TECH: SFD
PTF_CLASS: ENHANCEMENT-APAR
PTF_TYPE: (SRC) HNASMACX and (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the ace="Courier New">2400036.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): 2400035 and associated APAR chains.
SUPERSEDES: N/A
SOURCE(S): NASMAIN, NASTCP, XFBLK, XFMSG, XFNASWA,
XFWTO
OBJECT(S): CNFGDLNM, CNFGDXNM, CNFGIDTO, CNFGIPAD, CNFGLGTB,
CNFGLUNM, CNFGMSLM, CNFGPLSE, CNFGPVC, CNFGPWPR,
CNFGSVC0, CNFGSVC3, CNFGSVC4, CNFGSVC5, CNFGSYSL,
CNFGTAP, CNFGTRAN, CNFGUSTB, CNFGVLCM, CONSDNAS,
CONSEXEC, CONSMON, CONSMRMT, CONSPRNT, CONSSHOW,
CONSSTAT, CONSTRTR, NASCNFG, NASCONS, NASPRNT,
NASUTIL, OSUT1, QLSSCP, VCCLRQ
OVERVIEW: See Problem
PROBLEM
ENHANCEMENT: An option is now available that when invoked will
remove extraneous blanks from NASnnnns Configuration
and Alert messages.
DESCRIPTION: Currently, messages that contain names or other variable
text data can cause multiple blanks to appear in alarm
messages. Removing multiple blanks makes messages look
cleaner in SYSPRINT log and on SYSCONS.
SOLUTION: HNAS has been modified to allow the new XFWTO and XFMSG
macro COMPMSG= parameter to be selectively invoked for
certain messages that contain variable length text
data. This new operand by itself will not cause
compression but will require the new SHOWCMSG start
parameter to be set as well. This will allow customers
to control the compression process for those who use
message filtering tools that depend on fixed message
offsets. Consider the following message for example:
NAS3799I Without Compression:
0 1 2 3 4 5
012345678901234567890123456789012345678901234567890123
| |
NAS3799I LU MCH1PVC ENDING SESSION ON MCH MCH1
RMT CAUSE/DIAG=000/130 (00/82) DIAGX=0000
| |
456789012345678901234567890123456789012345
6 7 8 9
NAS3799I With Compression:
0 1 2 3 4
01234567890123456789012345678901234567890123456
| |
NAS3799I LU MCH1PVC ENDING SESSION ON MCH MCH1
RMT CAUSE/DIAG=000/130 (00/82) DIAGX=0000
| |
78901234567890123456789012345678901234567
5 6 7 8
Note1: While message compression does use additional
CPU cycles, the affect appears to be minimal.
However, HNAS environments with excessive alert
message activity should consider measuring the
effect upon CPU load with compression enabled
(SHOWCMSG ON) and disabled (SHOWCMSG OFF) to
see if compression is causing an unacceptable
percentage of CPU load. Our in-house testing
revealed a CPU seconds difference per WTO for
SHOWCMSG ON versus SHOWCMSG OFF to be an
additional 0.000011048 seconds per WTO or
approximately 0.002846% additional overhead
per WTO.
Note2: The SHOW console command processor has also
been modified to accept the new CMSG {ON|OFF}
argument in order to dynamically toggle the
SHOWCMSG start parameter setting.
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-04-20 - APAR 2400035 (was unpublished problem 2007108A)
APAR: 2400035_E
STATUS: CLOSED
OPEN_DATE: 2007-04-18
REVISE_DATE: 2007-mm-dd
CLOSE_DATE: 2007-04-20
SERVICE(S): GATEFC SLU name generation processing
MANDATORY: NO, but recommended
ORIGIN/REF: 240_SMB
CP_TECH: SFD, PRT
PTF_CLASS: ENHANCEMENT-APAR
PTF_TYPE: (SRC) HNASMACX and (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400035.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): 2400032 and associated APAR chains.
SUPERSEDES: N/A
SOURCE(S): XFNASWA
OBJECT(S): CNFGLUNM, CNFGVCLM, CONSDRMT, CONSMRMT,
MCIFCI, MCHINI, MCHSTRT, NASCNFG
OVERVIEW: See Problem
PROBLEM
ENHANCEMENT: Customer needs the ability to generate decimally
suffixed SLU names for GATEFC CTCP.
DESCRIPTION: Existing logic generates hexadecimally suffixed
SLU but customer's CTCP is setup to have SLU
names in decimal order.
SOLUTION: HNAS has been modified to allow the hex/decimal
identifier to be appended to the end of the the
SLU prefix value.
Old Syntax:
LUNAME=(sluname/pluname/pfxlu/sfxst/slucnt)
New Syntax:
LUNAME=(sluname/pluname/pfxlu{-H|-D}/sfxst/slucnt)
If pfxlu-D is specified, decimal SLU names will be
generated. If pfxlu-H or pfxlu (no -X) is specified,
hex SLU names will be generated as before.
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-04-11 - APAR 2400034
APAR: 2400034
STATUS: CLOSED
OPEN_DATE: 2007-04-06
REVISE_DATE: 2007-mm-dd
CLOSE_DATE: 2007-04-11
SERVICE(S): Console command list processing
MANDATORY: NO, but recommended
ORIGIN/REF: 240_CPT
CP_TECH: SFD
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (SRC) HNASMACX and (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400034.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): 2400032 and associated APAR chains.
SUPERSEDES: N/A
SOURCE(S): XFBLK
OBJECT(S): CONSEXEC, NASCONS
OVERVIEW: See Problems
PROBLEM: General EXEC LIST code cleanup, no runtime problems.
PROBLEM1: The following error message can be generated when a
large command list is provided via the EXEC ddname
command:
NASC054E EXEC CMDLIST1 FILE EXCEEDS QUEUED COMMAND
LIMIT, EXEC COMMAND ABORTED
PROBLEM2: EXEC LIST command does not generate an error message
when command list name is not provided.
DESCRIPTION1: If more than 512 bytes of command data and data length
bytes are listed in the command list identified by the
ddname argument, the NASC054E message will be generated
even if the command list contains an embedded EXEC
command (which ends the current command list) listed
early in the command list file. The problem occurs
because the decode of the embedded EXEC command is
not performed until after the entire command list is
read into memory. Some users like the ability to list
many commands in an EXEC command list beyond the EXEC
command for use at a later time. The current logic
prevents large numbers of saved commands to be listed
in a command list file.
DESCRIPTION2: If EXEC LIST is specified, the following messages are
generated:
HNASCMD-> EXEC LIST
HNASXEQ-> EXEC LIST
NASC055I EXEC SYSPRINT FILE HAS BEEN READ,
IT WILL NOW BE LISTED
EXEC COMMAND LIST CONTAINS THE FOLLOWING:
HNASCMD->
No data is listed.
SOLUTION1: The EXEC command processor has been modified to stop
queuing commands when it detects an embedded EXEC
command or the new END statement. This will allow you
to save commands beyond the EXEC or END command in a
command list file. For example, if a command list
file was constructed as follows:
DNAS JCL
ALARM LOG=?
SMSG 'THIS LONG MESSAGE IS DESIGNED TO FLOOD CONCMDQ'
END
SMSG 'THIS LONG MESSAGE IS DESIGNED TO FLOOD CONCMDQ'
SMSG 'THIS LONG MESSAGE IS DESIGNED TO FLOOD CONCMDQ'
SMSG 'THIS LONG MESSAGE IS DESIGNED TO FLOOD CONCMDQ'
SMSG 'THIS LONG MESSAGE IS DESIGNED TO FLOOD CONCMDQ'
SMSG 'THIS LONG MESSAGE IS DESIGNED TO FLOOD CONCMDQ'
SMSG 'THIS LONG MESSAGE IS DESIGNED TO FLOOD CONCMDQ'
SMSG 'THIS LONG MESSAGE IS DESIGNED TO FLOOD CONCMDQ'
SMSG 'THIS LONG MESSAGE IS DESIGNED TO FLOOD CONCMDQ'
SMSG 'THIS LONG MESSAGE IS DESIGNED TO FLOOD CONCMDQ'
SMSG 'THIS LONG MESSAGE IS DESIGNED TO FLOOD CONCMDQ'
SMSG 'THIS LONG MESSAGE IS DESIGNED TO FLOOD CONCMDQ'
and you entered: EXEC cmdlist1 LIST
the following output would be produced:
HNASXEQ-> EXEC CMDLIST1 LIST
NASC055I EXEC CMDLIST1 FILE HAS BEEN READ,
IT WILL NOW BE LISTED
EXEC CMDLIST1 COMMAND LIST CONTAINS THE FOLLOWING:
=> DNAS JCL
=> ALARM LOG=?
=> SMSG 'THIS LONG MESSAGE IS DESIGNED TO FLOOD CONCMDQ'
=> END
Note that if the LIST argument was omitted, only these
4 commands would be executed.
SOLUTION2: The EXEC command processor has been modified to issue
following message if EXEC LIST is specified without a
command list:
NASC052E EXEC COMMAND LIST WAS NOT PROVIDED,
REQUIRED FOR EXEC COMMAND
In addition, the following message will be issued if
EXEC ddname is specified but the named command list
dataset is empty (contains no commands or display
comments (# text) but may contain non-display comments
('* text')):
EXEC ddname FILE IS NULL, EXEC COMMAND ABORTED
CIRCUMVENTION1: Break a large command list into multiple smaller
command lists by chaining them together. For
example:
CMDLIST1: command11
command12
EXEC CMDLIST2
CMDLIST2: command21
command22
EXEC CMDLIST3
etc.
CIRCUMVENTION2: 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-04-09 - APAR 2400033 (was unpublished problem 2007085A)
APAR: 2400033_R
STATUS: CLOSED
OPEN_DATE: 2007-04-03
REVISE_DATE: N/A
CLOSE_DATE: 2007-04-09
SERVICE(S): PING console command processing
MANDATORY: YES
ORIGIN/REF: 240_NBG
CPTECH: SFD
PTF_CLASS: STANDARD-APAR
PTF_TYPE: REFRESH (due to 2400032 requirements)
PTF_LOC: Contact Support Services for Refresh E-distribution.
OVERVIEW: See problems.
PROBLEM1: An 0198 ABEND (NASHALT) can occur when PING dmyname
is entered and the REMOTE identified by dmyname has
FAC=NONE or CUD=NONE specified.
PROBLEM2: Bogus data can be transmitted when PING dmyname is
entered and the REMOTE identified by dmyname has
DTEADDR=NONE or DCEADDR=NONE specified.
DESCRIPTION1: When FAC=NONE or CUD=NONE is specified, internally
it is remembered by X'FF' as the FAC= or CUD= string
length. X'FF' can be used because the FAC= and CUD=
strings are limited to 63 (X'3F') bytes of data.
Unfortunately, the PING command 'forgot' that X'FF'
meant NONE and instead used the X'FF' as a valid
string length. This caused the next buffer in the
buffer pool to be overlaid which resulted in the
0198 ABEND. Note that the buffer length is not
checked to ensure that PING data will fit because
the minimum buffer size for the PING XOT packet was
was established to accommodate the maximum FAC= and
CUD= string lengths.
DESCRIPTION2: When DTEADDR=NONE or DCEADDR=NONE is specified,
internally it is remembered by X'FF' as the first
byte of the DTEADDR= or DCEADDR= string. The string
length is actually the first nibble of the first byte.
Like PROBLEM1, the PING command failed to recognize
X'FF' as meaning NONE and used the value as a bad
length. This resulted in corrupted data being sent
in the Call Request packet.
SOLUTION1: The PING command processor has been modified to
process FAC=NONE and CUD=NONE correctly.
SOLUTION2: The PING command processor has been modified to
process DTEADDR=NONE and DCEADDR=NONE correctly.
CIRCUMVENTION1: Manually code valid FAC= and CUD= values on the
REMOTE named dmyname.
CIRCUMVENTION2: Manually code valid DTEADDR= and DCEADDR= values
on the REMOTE named dmyname.
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-04-09 - APAR 2400032 (was problem 2005118A)
APAR: 2400032_RE
STATUS: CLOSED
OPEN_DATE: 2005-04-28
REVISE_DATE: N/A
CLOSE_DATE: 2007-04-09
SERVICE(S): Console MRMT LOGTAB= and USSTAB= reload enhancement.
MANDATORY: NO, but recommended.
ORIGIN/REF: 230_AXA
CPTECH: SFD
PTF_CLASS: ENHANCEMENT-APAR
PTF_TYPE: REFRESH
PTF_LOC: Contact Support Services for Refresh E-distribution.
OVERVIEW: See problem.
PROBLEM: Customer modifies LOGTAB while HNAS is running but
modified member is not loaded by MRMT LOGTAB=lgtbname
command.
DESCRIPTION: Currently, the way MRMT LOGTAB=lgtbname works is that if
the LOGTAB name is already known to HNAS when the MRMT
command is given (via LOGTAB= in the CDF), the original
version is used. HNAS keeps one copy in memory and
searches all references for it so does not have to load
a second copy into memory. Only when the name is new
is it loaded in. Thus, the existing logic will not
allow a modified LOGTAB (or USSTAB or NRITAB) to be
dynamically loaded if it was loaded from the CDF.
SOLUTION: The MRMT command has been modified to accept the new
reload option for the LOGTAB=, USSTAB= and NRITAB=
operands.
Syntax: MRMT rmtname LOGTAB=lgtbname-R
MRMT rmtname USSTAB=ustbname-R
MRMT rmtname OPTIONS=NRITAB=nrtbname-R
When the -R follower is omitted, the old logic is used.
That is, the given lgtbname, ustbname or nrtbname is
compared against all LOGTAB=, USSTAB= or NRITAB= names,
respectively, currently is use. If the name found, the
given LOGTAB=, USSTAB= or NRITAB= is copied from the
found REMOTE to the specified REMOTE. If the name is
not found, the given LOGTAB=, USSTAB= or NRITAB= is
LOADed in.
When the -R follower is specified, the given table is
loaded in unconditionally even if it is already present.
The new version of the table is propagated to all other
REMOTEs that share the table.
Note1: Because the transmission of a USSMSG in a USSTAB
can span task dispatches (and TCPIP interrupts),
HNAS will refuse to reload a USSTAB if it is
currently being used for a USSMSG transmission.
In this case, the following message is issued:
NASC031W USSTAB ISTINCDT IS CURRENTLY IN USE,
RETRY MRMT COMMAND LATER
This is the case because of a potential ABEND
that can result due to an addressing exception
if the new table alters USSMSGs currently being
transmitted.
Further, if you attempt to load a table that is
not appropriate for the specified operand, for
example a USSTAB for a LOGTAB (LOGTAB=ISTINCDT),
the following message is issued:
NASC030E LOGTAB ISTINCDT HAS INVALID FORMAT,
MRMT COMMAND ABORTED
Note2: The following message is also issued if you
specify the wrong table in the CDF, for example
a USSTAB for a LOGTAB (LOGTAB=ISTINCDT):
NAS1311E REMOTE mchname LOGTAB=ISTINCDT IS NOT
A VALID LOGON TABLE, REQUIRED
THIS NEW MESSAGE WILL PREVENT HNAS FROM STARTING.
Prior to this APAR, you would not have known that
a bad table was specified until it was accessed
during call setup.
For a bad USSTAB=, the following message is
issued and the call is cleared:
NAS5702E LU sluname ADDRESSES INV USSTAB
For a bad LOGTAB= value, no action is taken
(treated as if no LOGTAB= value was specified).
In this case USSTAB= is used. If the USSTAB=
operand is (also) missing, the following message
is issued and the call is cleared:
NAS5703E LU sluname MISSING USSTAB
Note3: Effective with APAR 2400032, most console error
messages will now include the name of the command
that generated the message. For example:
NASC013E UNSUPPORTED FUNCTION,
cmdname COMMAND ABORTED
In addition to the MRMT change, the DRMT command has
been modified to display the time and date that a
LOGTAB, USSTAB or NRITAB is loaded in. This allows the
operator to tell whether the table was loaded in when
the CDF was scanned (HNAS start time) or subsequently
via the MRMT command.
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-03-29 - APAR 2400031 (was problem 2007015B)
APAR: 2400031_E
STATUS: CLOSED
OPEN_DATE: 2007-01-15
CLOSE_DATE: 2007-29
SERVICE(S): VTAM Alert Messages
MANDATORY: NO
ORIGIN/REF: 240_CMB
CPTECH: PRT
PTF_CLASS: ENHANCEMENT-APAR
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400031.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: 2007-03-03
With APAR: 2400028 applied.
SUPERSEDES: N/A
OBJECT(S): MCHHRSP
SOURCE(S): N/A
OVERVIEW: See Problem
PROBLEM: LLC0 session ends with DIAG=219 after PLU rejects FMD
with a -RSP and SENSE=0811082C but sense not shown.
DESCRIPTION: HNAS clears the call when a PIU is rejected in order
to ensure that the remote is aware of the undelivered
data. The SENSE information, which could help with
problem diagnosis is not shown. For example:
FAPL: "Break: Asks the receiver of this sense code to
to terminate the present chain with CANCEL ...").
081C indicates that the PLU does not support inbound
RH chains.
SOLUTION: Sense data has been added to the NAS3711 alert message.
In addition the severity code will be 'W' if HNAS will
terminate the VTAM session because of the -RSP and 'I'
otherwise.
NAS3711{I|W} LU lu-name RECEIVED -RSP SENSE=xxxxxxxx
FROM PLU plu-nm LUBST1/2=yyyy LUBSST1/2=zzzz
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-03-09 - APAR 2400030 (was unpublished problem 2007043A)
APAR: 2400030
STATUS: CLOSED
OPEN_DATE: 2007-02-12
REVISE_DATE: 2007-mm-dd
CLOSE_DATE: 2007-03-09
SERVICE(S): Console PING/MON TAP Command SYSCONS Messages
MANDATORY: NO
ORIGIN/REF: 240_CPT
CP_TECH: SFD
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (SRC) HNASMACX and (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400030.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): 2400028 and associated APAR chains.
SUPERSEDES: N/A
SOURCE(S): NASTCP, XFWTO
OBJECT(S): CONSALRM, CONSPING, CONSPRNT, CONSSHOW, CONSTALL,
CONSTPRT, CONSTRTR, CONSVARY, NASUTIL
OVERVIEW: See Problem
PROBLEM: NAS251xM MON TAP and NAS261xM PING messages are
displayed on SYSCONS when they should not be.
DESCRIPTION: Logic introduced by APARs 2400021 and 2400022 that
allows monitor messages to be routed to SYSCONS using
ALRMFLTR=(...,NAS2***M(FC),...) has a side affect that
allows these messages to go to SYSCONS when ALRMFLTR=
is omitted. This is because the default alarm action
is ALLOW when ALRMFLTR= is not specified. When ALLOW
is in effect, the SHOW state is then used to filter
alarm messages. The default SHOW state is SHOWERR
which prevents severity I (Informational) and severity
M (Monitor) alarms from going to SYSCONS but allows
severity W (Warning), E (Error) and S (Severe Error)
to be routed to SYSCONS.
MON TAP and PING messages are issued using the XFWTO
macro with FLOW=BISYNC which allows messages to be
processed as console command output and as alarm
messages. When FLOW=BISYNC is specified, the message
severity is erroneously set to W (Warning) instead
of M (Monitor). Since the message severity is set
W, it passes the SHOWERR test and is written to
SYSCONS.
SOLUTION: The XFWTO interface has been modified to set the
message severity for MON TAP and PING messages to
M (Monitor) so that they will be prevented from
going to SYSCONS when ALLOW is the default ALRMFLTR=
action. These messages will only be routed to
SYSCONS when the (FC) or (FU) action override is
used for the monitor messages in the ALRMFLTR=
message list.
CIRCUMVENTION: Specify ALRMFLTR=(SUPPRESS)
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-03-07 - APAR 2400029 (was problem 2006247B)
APAR: 2400029_E
STATUS: CLOSED
OPEN_DATE: 2006-09-04
REVISE_DATE: N/A
CLOSE_DATE: 2007-03-07
SERVICE(S): Configuration, AMNF generation - GATE
MANDATORY: NO
ORIGIN/REF: 230_ZAG
CPTECH: SFD
PTF_CLASS: ENHANCEMENT-APAR
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400029.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): 2400028 and associated APAR chains.
SUPERSEDES: N/A
SOURCE(S): N/A
OBJECT(S): CNFGVTAM, NASCNFG
OVERVIEW: See problems.
PROBLEM1: Currently, VTAM parameters (parms) that are specified
on an MCH are not propagated to the GATE control
session SLUs defined on APPL statements in the AMNF
during a FASTRUN execution.
PROBLEM2: Currently, VTAM parameters (parms) that are specified
on an MXT associated with a PVC SLU are not propagated
to the SLU defined on the APPL statement in the AMNF
during a FASTRUN execution.
DESCRIPTION1: HNAS will propagate MCH VTAM parms for GATE data
session SLUs but NOT for GATE control session SLUs.
For the latter, the configuration will force only
DLOGMOD=INTERACT,EAS=1 as VTAM parms when the APPL
statements are created during a FASTRUN execution.
DESCRIPTION2: HNAS will propagate MCH VTAM parms for a PVC SLU but
NOT MXT VTAM parms when an MXT is associated with a
PVC SLU, e.g., :
PVC=(...,sluname/llc/apid/lcn/ifnm/rmtnm/mxtnm,...
The VTAM parms on the MXT named mxtnm are ignored for
a PVC SLU.
SOLUTION1: The HNAS configuration has been modified to pass MCH
VTAM parms to the GATE control session SLUs as is done
now for the GATE data session SLUs when the AMNF is
generated during FASTRUN execution.
In a FUTURE enhancement, we will consider allowing an
MXT to be associated with the control session SLUs so
that VTAM parms specified on the MXT could be used to
override the VTAM parms on the MCH for control session
SLUs only. This would allow separate VTAM parms for
control and data session SLUs. THIS CHANGE IS NOT
INCLUDED WITH THIS APAR.
SOLUTION2: The HNAS configuration has been modified to pass MXT
VTAM parms to a PVC SLU when the AMNF is generated
during FASTRUN execution if an MXT is associated with
the SLU in the PVC operand. This makes PVC AMNF
processing consistent with SVC0 and SVC5 processing.
CIRCUMVENTION1: Manually code VTAM parms in the AMNF for GATE control
session SLUs if the default values are not correct.
CIRCUMVENTION2: Manually code VTAM parms in the AMNF for PVC SLUs
if the MCH values are not correct.
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-03-05 - APAR 2400028 (was problem 2006163A & unpublished
problems 2007046A, 2007057A)
APAR: 2400028_R +E
STATUS: CLOSED
OPEN_DATE: 2006-06-12 for problem 2006163A
2007-02-15 for problem 2007046A
2007-02-26 for problem 2007057A
REVISE_DATE: N/A
CLOSE_DATE: 2007-03-03
SERVICE(S): Configuration and Console processing for LOCAL,
REMOTE and SLU INIT= parameter and other related
console command processors.
MANDATORY: NO, but recommended.
ORIGIN/REF: 240_CPT
CPTECH: SFD/PRT
PTF_CLASS: STANDARD-APAR also includes enhancements
PTF_TYPE: REFRESH
PTF_LOC: Contact Support Services for Refresh E-distribution.
OVERVIEW: This APAR contains a collection general maintenance
bug fixes, console VARY LCL abend fix as well as
product enhancements. See Problems:
PROBLEM1: V sluname {ON|OFF} console command allows an SLU to
be varied offline and back online but there is no CDF
operand that allows SLU to be configured initially
offline.
PROBLEM2: An ABEND can occur when RTEIN= pointer is referenced
after V lclname LCL {ON|OFF} command is issued.
PROBLEM3: DLU and DVC commands do not distinguish between
dedicated SVC callout SLUs and PVC SLUs in display
output.
PROBLEM4: The wrong error message is generated when the specified
vclmt value for PVC= or SVCi= operand exceeds the array
size.
PROBLEM5: NAS7719T FOR SPU (QLLC) CALLOUT (TRCMCH OCR message)
contains bad characters for the LU name when the call
is placed on behalf of a QLLC SPU.
DESCRIPTION1: See problem.
DESCRIPTION2: V lclname LCL {ON|OFF} command processor modifies a
field in the LOCAL configuration area (LCOPT6OF)
but erroneously uses the offset into the REMOTE
configuration area (RMOPT6OF) which happens to be
the RTEIN= pointer in the LOCAL. The result is
that the RTEIN= pointer is corrupted which causes
an ABEND the next time it is referenced.
DESCRIPTION3: The DLU command display for dedicated SVC callout SLUs
and PVC SLUs shows 'P' (permanent) in the LUOPT column.
Unless the SLU name is known to be a PVC, there is no
way to know if the SLU is an SVC callout SLU or a PVC
SLU.
DESCRIPTION4: When the vclmt value that is specified for the PVC= and
SVCi= operands exceed their respective array sizes, the
following error message is generated (for example):
NAS1321E ERROR: REMOTE PVC=(256,
The appropriate message should be:
NAS1303E LIMIT: REMOTE PVC=(256,
When the vclmt value is too large subsequent, PVC=
and/or SVCi= values will get the NAS1321E value because
the vclmt value has not been set. The maximum vclmt
values are as follows:
PVC SVC0 SVC3 SVC4 SVC5
255 511 255 511 511
DESCRIPTION5: See PROBLEM 5.
SOLUTION1: HNAS has been modified to accept an initial state value
after the sluname in the LUNAME=, PVC= and SVCi=
operands. Syntax: SVCi=(...,sluname-{A|I}/.....)
-A is for active and -I is for inactive or idle with
active being the default.
SOLUTION2: V lclname LCL {ON|OFF} command processor has been
modified to update LCOPT6OF instead of RMOPT6OF.
SOLUTION3: The DLU command processor has been modified to prefix
the VCN for a PVC with the character 'P' to indicate
that the SLU is for a PVC. The VCN that follows the
'P' can range from 000 to 255. For an SVC, the VCN
column will show a 4 character VCN that can range
from 0000 to 4095.
SOLUTION4: The PVC= and SVCi= processors have been modified to
generate the NAS1303E message rather than the NAS1321E
message when their respective vclmt value is too large.
SOLUTION5: Logic corrected to display the QLLC SPU name when the
callout is for an HNAS QLLC SPU.
CIRCUMVENTION1: N/A
CIRCUMVENTION2: N/A
CIRCUMVENTION3: Refer to the configuration file to determine if
the resource is configured as a PVC or SVC.
CIRCUMVENTION4: N/A
CIRCUMVENTION5: 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-02-21 - APAR 2400027 (includes unpublished problem 2007045A)
APAR: 2400027
STATUS: CLOSED
OPEN_DATE: 2007-02-14 for problem 2007045A
REVISE_DATE: 2007-mm-dd
CLOSE_DATE: 2007-02-21
SERVICE(S): Console subsystem, queued commands.
MANDATORY: YES
ORIGIN/REF: 240_CPT
CPTECH: SFD
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (SRC) HNASMACX and (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400027.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): 2400024, 2400022, 2400021, 2400017, 2400016
and associated APAR chains.
SUPERSEDES: N/A
SOURCE(S): NASTCP, XFNASWA
OBJECT(S): CONSDMCH, CONSEXEC, CONSMLCL, NASCONS, NASUTIL
OVERVIEW: See problems.
PROBLEM1: After APAR 2400016 is applied, EXEC (cmd1,...,cmdn)
no longer executes cmd1 through cmdn, but only
executes cmdn.
PROBLEM2: The DLU command that results from the DMCH FMT3
command can be executed out of order if DMCH FMT3
is part of a command list.
PROBLEM3: The VARY lclname LCL ON|OFF command that results from
the MLCL lclname INIT=ACTIVE|IDLE command can be
executed out of order if MRMT lclname INIT=ACTIVE|IDLE
is part of a command list.
PROBLEM4: The EXEC cmdlist command that results from the TRCTRAP
TRAPACTION=(EXEC=ddname) operand can be executed out
of order if trace trap occurs when a command list is
already running.
DESCRIPTION1: Logic introduced with APAR 2400016 resets queued
counts before each command in the inline command
list is processed which causes each command in the
list to be placed at the beginning of the queue.
Since cmdn is the last command in the list, it
becomes the only command in the queue.
DESCRIPTION2: The DMCH FMT3 command schedules the DLU command by
enqueing it in the queued command area. The problem
can occur because the enqueue is FIFO and not LIFO
which means the DLU command is queued after all
other queued commands in the list.
DESCRIPTION3: Same reason as Problem #2, that is, the VARY command
is enqueued FIFO instead of LIFO.
DESCRIPTION4: Same reason as Problem #2, that is, the EXEC command
is enqueued FIFO instead of LIFO. This can delay the
processing of the new command list that is intended to
be executed immediately when a trace trap hit occurs.
SOLUTION1: The EXEC console command processor has been modified
to reset the queued command counts before the command
list is processed and not between commands in the list.
SOLUTION2: The DMCH FMT3 command has been changed to enqueue the
DLU command in a LIFO manner so that it immediately
follows the DMCH command.
SOLUTION3: The MRMT lclname INIT=ACTIVE|IDLE command has been
changed to enqueue the VARY command in a LIFO manner
so that it immediately follows the MRMT command.
SOLUTION4: The trace trap logic has been modified to enqueue the
EXEC command in a LIFO manner so that it is executed
immediately on a trace trap hit.
CIRCUMVENTION1: N/A
CIRCUMVENTION2: N/A
CIRCUMVENTION3: N/A
CIRCUMVENTION4: 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-02-08 - APAR 2400026
APAR: 2400026
STATUS: CLOSED
OPEN_DATE: 2007-02-08
REVISE_DATE: N/A
CLOSE_DATE: 2007-02-08
SERVICE(S): PFXWTO command fix after APAR 2400014 applied
MANDATORY: YES
ORIGIN/REF: 240_CPT
CPTECH: SFD
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400026.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): 2400014 and associated APAR chains.
SUPERSEDES: N/A
SOURCE(S): N/A
OBJECT(S): CONSPWTO
OVERVIEW: See problem.
PROBLEM: The PFXWTO command can be rejected when 'text' is given
followed by another PFXWTO command.
DESCRIPTION: Due to changes introduced by APAR 2400014, the following
sequence (which appears in the HNAS console subsystem
documentation) no longer works.
PFXWTO pfxtext PFXWTO OFF PFXWTO CONS ON
This sequence now generates the following error message:
NASC512E PARAMETERS DUPLICATED, REQUIRED
The error occurs because the second occurrence of PFXWTO
in the command string is being interpreted as another
pfxtext value.
SOLUTION: The PFXWTO command processor has been modified to
terminate parsing and execute the parameter data
already collected when it decodes the string PFXWTO.
The second occurrence of PFXWTO will be executed as
separate PFXWTO command.
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-02-01 - APAR 2400025 (was unpublished problem 2007030A)
APAR: 2400025
STATUS: CLOSED
OPEN_DATE: 2007-01-30
CLOSE_DATE: 2007-02-01
SERVICE(S): CALLOUT
MANDATORY: YES
ORIGIN/REF: 240_SDD
CPTECH: PRT
PTF_CLASS: STANDARD-APAR
------------
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400025.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-10-02
With APAR: 2400007 applied.
Users who have not installed 2400015 should consider
a REFRESH.
SUPERSEDES: N/A
OBJECT(S): XOTBXM
SOURCE(S): N/A
PROBLEM: HALT AT LOC xxxxxx IN XOTBXM : INV VC
DESCRIPTION: When multiple routers are used for outbound HNAS call
requests (RTEOUT=(R1,R2,R3)) the above HALT can occur
if a session terminated RPL completion:
RECV RPL COMP, R15=04 R0=0C FDB2=0B
is posted while HNAS is in the middle of the RTEOUT=
list. The error occurs because the session terminated
completion can release the HNAS LU. After the release,
if a clear is received from router R1 HNAS will retry the
call using router R2. The HALT occurs when the call
request packet builder detects that the VC has no LU.
The session terminated RPL completion can be posted when
the program owning the PLU is canceled.
SOLUTION: Logic corrected so that the callout operation ends
correctly when a session terminated is posted.
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-31 - APAR 2400024
APAR: 2400024
STATUS: CLOSED
OPEN_DATE: 2007-01-31
REVISE_DATE: N/A
CLOSE_DATE: 2007-01-31
SERVICE(S): MLCL command fix after APAR 2400021 applied
MANDATORY: YES
ORIGIN/REF: 240_CPT
CPTECH: SFD
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400024.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): 2400021 and associated APAR chains.
SUPERSEDES: N/A
SOURCE(S): N/A
OBJECT(S): CONSMLCL
OVERVIEW: See problem.
PROBLEM: The MLCL command does not update NEWDEFN CDF correctly
after APAR 2400021 is applied.
DESCRIPTION: Due to changes to the XFCNFGWA macro for APAR 2400021
which were not picked up by assembling the CONSMLCL
module, the NEWDEFN file is not updated correctly
when MLCL lclname RTEIN=mchname/dteaddr is entered.
This causes bogus information to be displayed when
the DNWDF lclname LOCAL command is entered.
SOLUTION: The MLCL command processor has been assembled to pick
up the changes to XFCNFGWA for APAR 2400021.
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-30 - APAR 2400023
APAR: 2400023
STATUS: CLOSED
OPEN_DATE: 2007-01-29
REVISE_DATE: N/A
CLOSE_DATE: 2007-01-30
SERVICE(S): DMAP trace entry list display
MANDATORY: YES
ORIGIN/REF: 240_CPT
CPTECH: SFD
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400023.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): 2400021 and associated APAR chains.
SUPERSEDES: N/A
SOURCE(S): N/A
OBJECT(S): CONSDMAP
OVERVIEW: DMAP display can give erroneous information for some
modules.
PROBLEM: The DMAP command does not always display the correct
value in the LGTM column when TRIDxxxx is displayed
in the REFID column.
DESCRIPTION: For example, when DMAP NASTCP is entered, the following
is displayed:
MODULE ADDRESS SIZE ASMDATE REFNO REFOF REFID LGTM
NASTCP 0005FC30 9A80 2007/01/30 01 964A TRIDDBUG NO
02 8A2E TRIDIBFR YES
03 868C TRIDIPRM YES
04 8B5C TRIDRBFR NO
05 8758 TRIDSBFR YES
06 8D22 TRIDTDAT YES
07 88EE TRIDTDAT NO
01 3EE6 2400004
02 0410 2400022
The LGTM column in the above display is incorrect for
the NASTCP module. The correct display is as follows:
MODULE ADDRESS SIZE ASMDATE REFNO REFOF REFID LGTM
NASTCP 0005FC30 9A80 2007/01/30 01 964A TRIDDBUG YES
02 8A2E TRIDIBFR YES
03 868C TRIDIPRM YES
04 8B5C TRIDRBFR NO
05 8758 TRIDSBFR NO
06 8D22 TRIDTDAT NO
07 88EE TRIDTDAT NO
01 3EE6 2400004
02 0410 2400022
The error occurs because of bad address arithmetic
while locating the trace flags in modules that are
greater than X'7FFF' in length.
SOLUTION: The DMAP command processor has been modified to correct
the address arithmetic that is used to locate the trace
flags.
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-02-01 - APAR 2400022 (was problem 2006342A)
APAR: 2400022_E
STATUS: CLOSED
OPEN_DATE: 2006-12-07
REVISE_DATE: 2007-02-01 - remove WIP notation
PRVCHG_DATE: 2007-01-30
CLOSE_DATE: 2007-01-30
SERVICE(S): Console PING/MON TAP Command SYSCONS Message Option
MANDATORY: NO
ORIGIN/REF: 240_CPT
CP_TECH: SFD
PTF_CLASS: ENHANCEMENT-APAR
PTF_TYPE: (SRC) HNASMACX and (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400022.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): 2400014 and associated APAR chains.
SUPERSEDES: N/A
SOURCE(S): NASTCP
OBJECT(S): CONSPING
PROBLEM
ENHANCEMENT: Would like to be able to route NAS2xyyM PING and MON TAP
monitor status messages to SYSCONS as well as SYSPRINT.
DESCRIPTION: PING dmyname will now produce monitor status messages
for SYSPRINT that can also (optionally) be displayed
on the SYSCONS.
NAS2613M PINGING SOCKET=a.b.c.d(port) FOR consname
NAS2613M DTEADDR=lddd...ddd DCEADDR=lddd...ddd
NAS2613M FAC=xx...xxx
NAS2613M CUD=xx...xxx
NAS2615M PING COMPLETED FOR consname, CLEAR REQUEST
RECEIVED, CAUSE/DIAG=ccdd
NAS2617M PING COMPLETED FOR consname, CALL ACCEPT
RECEIVED
NAS2611M PING TIMED OUT FOR consname
MON rmtname TAP will continue to generate standard
TAP monitor status messages for SYSPRINT that can also
(optionally) be displayed on the SYSCONS.
NAS2513M CLIENT=010.117.056.100(02190)
SOCKID=0002 PCEID=000B NAME=R1CNIN
NAS2513M XOT TAP SEQUENCE IS STARTING,
TRANSMITTING CALL REQUEST
NAS2513M PKT=0000001010010B000001000000C8D5C1E2E3C1D7
NAS2515M CLIENT=010.117.056.100(02190)
SOCKID=0002 PCEID=000B NAME=R1CNIN
NAS2515M XOT TAP SEQUENCE IN PROGRESS,
RECEIVED CLEAR REQUEST
NAS2515M PKT=000000051001130342
NAS2513M CLIENT=010.117.056.100(02190)
SOCKID=0002 PCEID=000B NAME=R1CNIN
NAS2513M XOT TAP SEQUENCE IN PROGRESS,
TRANSMITTING CLEAR CONFIRM
NAS2513M PKT=00000003100117
NAS2517M CLIENT=010.117.056.100(02190)
SOCKID=0002 PCEID=000B NAME=R1CNIN
NAS2517M XOT TAP SEQUENCE COMPLETED SUCCESSFULLY
SOLUTION: HNAS has been modified to allow new PING messages of the
form NAS261xM to be routed to SYSPRINT and optionally
to SYSCONS using the ALRMFLTR= (FU) mechanism as follows:
ALRMFLTR=(...,NAS261*M(FU),...) on BUILD or
ALARM FILTER=(...,NAS261*M(FU),...) console command.
HNAS has been modified to allow MON TAP messages of the
form NAS251xM to be routed to SYSCONS using the ALRMFLTR=
operand as follows:
ALRMFLTR=(...,NAS251*M(FU),...) on BUILD or
ALARM FILTER=(...,NAS251*M(FU),...) console command.
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-27 - APAR 2400021 (was problem 2006334D and unpublished
problem 2006020A)
APAR: 2400021_E
STATUS: CLOSED
OPEN_DATE: 2006-01-20 for problem 2006020A
2006-11-30 for problem 2006334D
REVISE_DATE: 2007-01-27 - Memo updated.
PRVCHG_DATE: 2007-01-26
CLOSE_DATE: 2007-01-26
SERVICE(S): Heartbeat alarm message and SYSCONS alarm routing
MANDATORY: NO
ORIGIN/REF: 230|240_CPT
CPTECH: SFD
PTF_CLASS: ENHANCEMENT-APAR
PTF_TYPE: (SRC) HNASMACX and (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400021.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): 2400018 and associated APAR chains.
SUPERSEDES: N/A
SOURCE(S): SYSLIN, XFBLK, XFCNFGWA, XFMODMAP, XFNASWA, XFXTRN
OBJECT(S): CNFGAFLT, CNFGPLSE, CNFGPVC, CNFGSVC0, CNFGSVC3
CNFGSVC5, CONSALRM, CONSDMAP, CONSDNWD, CONSMRMT
NASCNFG, NASUTIL
OVERVIEW: This Enhancement APAR addresses the following console
and debugging improvements:
PROBLEM1: Requirement for a new CDF parameter and console
command capable of generating a heartbeat or pulse
message at a designated interval.
PROBLEM2: Require the ability to route Information messages
to SYSCONS that are normally only logged to SYSPRINT
due to current SHOW state.
DESCRIPTION1: Customer reported a five hour hung condition between
router and HNAS. The HNAS SYSPRINT log shows a five
hour time gap when normal session event activity
should be present. It was as if HNAS is not being
dispatched. It appears that the CPU or task
initiator has been stopped or HNAS has been swapped
out for a higher priority task (HNAS is supposed to
run non-swappable with the same dispatch priority as
TCPIP and VTAM).
Once the SYSPRINT log activity resumed, sessions
that were previously connected during the unusual
stop or hung condition encountered Clear response
timeout indications. Customer cannot explain the
five hour gap in the SYSPRINT log file and claims
that the CPU and initiator were not stopped.
During the 'gap' period, customer reports that 2000
callin sessions failed. There is no record as to
why the calls failed in the HNAS SYSPRINT log (HNAS
did not see them).
Note that the same router used by this HNAS was
operating correctly with other HNAS images.
If HNAS would have been issuing heartbeat alarm
messages at regular intervals, their absence from
absence from the SYSPRINT log would prove that HNAS
was not being dispatched and this would explain the
2000 callin failures.
DESCRIPTION2: Would like the ability to route specific Informational
alarms messages to SYSCONS without having to set the
SHOWON start parameter or SHOW ON console command.
SOLUTION1: HNAS has been modified to accept the new PULSE operand
on the BUILD definition statement. The syntax is as
follows:
|<-------------------- pulse start time (PST)
|
| |<----------- pulse end time (PET)
| |
| | |<-- pulse frequency (PR)
| | |
V V V
PULSE=(hh:mm:ss,hh:mm:ss,seconds)
The pulse (or heartbeat) message will be issued every
PR seconds between the times of PST to PET. PET may
be smaller than PST in which case the pulse interval
wraps through midnight. If PST=PET, pulsing will be
continuous. The pulse alarm message has the
following form:
NAS0299I HNAS PULSE TAKEN AT ff:mm:ss ON yyyy/mm/dd
The purpose of the message is to provide an indication
that HNAS is being dispatched on a regular basis.
The SYSPRINT log file will contain the NAS0299I
message. The message can also be sent to SYSCONS if
ALRMFLTR=(...,NAS0299I(FU),...) is also specified on
BUILD or if the ALARM FILTER=(...,NAS0299I(FU),...)
console command is issued (see problem2 for new
ALRMFLTR= suffix values.
The PULSE operand can also be modified dynamically
using the ALARM PULSE=(hh:mm:ss,hh:mm:ss,seconds)
console command.
SOLUTION2: HNAS has been modified to accept new suffix values for
the ALRMFLTR= operand. In addition to existing override
actions of (A), (S) and (P), HNAS now accepts (FC) for
force conditionally and (FU) for force unconditionally.
(FC) specifies that the filtered alarm message is to be
sent to SYSCONS subject to the current SHOW state.
For example, if ALRMFLTR=(...,NAS2020I(FC),...) is
specified, the NAS2020I alarm messages will be sent
to SYSCONS except when SHOWOFF is effect.
(FU) specifies that the filtered alarm message is to be
sent to SYSCONS regardless of the current SHOW state.
For example, if ALRMFLTR=(...,NAS0299I(FU),...) is
specified, the NAS0299I alarm messages will be sent to
SYSCONS even when SHOWOFF is in effect.
CIRCUMVENTION1: N/A
CIRCUMVENTION2: 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-18 - APAR 2400020 (was unpublished problem 2007011A)
APAR: 2400020
STATUS: CLOSED
OPEN_DATE: 2007-01-11
REV_DATE: 2007-01-18 - ZIP file repackaged to correct ASM library.
Do not use 2007-01-17 *.zip file.
CLOSE_DATE: 2007-01-17 - edistribution correct as of this date.
SERVICE(S): QLLC
MANDATORY: RECOMMENDED
ORIGIN/REF: 230_CPA (2300205)
CPTECH: PRT
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400020.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-08-30
With APAR: 2400003 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-15 - APAR 2400019
APAR: 2400019
STATUS: CLOSED
OPEN_DATE: 2006-12-21 - Problem 1
2007-01-12 - Problem 2
REVISE_DATE: N/A
CLOSE_DATE: 2007-01-15
SERVICE(S): Console Alarm Messages
MANDATORY: NO
ORIGIN/REF: 240_CPT
CPTECH: SFD
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400019.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): 2400017, 2400016, 2400014 and associated APAR chains.
SUPERSEDES: N/A
SOURCE(S): N/A
OBJECT(S): CONSSHOW, CONSTALL, CONSTRTR, NASPRNT
OVERVIEW: This APAR is an extension to APAR 2400016 (1) and a
correction to APAR 2400017 (2).
PROBLEM1: Some forced alarm messages can be filtered out when
they should not be.
PROBLEM2: Two independent alarm messages use the same message
ID of NAS0111W.
DESCRIPTION1: For example:
NAS0204E SYSPRINT LOG FILE IS FULL, LOGGING TERMINATED
This message is important because it tells the operator
the HNAS SYSPRINT logging has been stopped. Operator
can then either restart HNAS or open a new SYSPRINT log
file (see PRNT console command for details).
Messages like the above are subject to filtering when
they should not be because the message severity
defaults to 'E' (the last character of the message ID).
DESCRIPTION2: Prior to APAR 2400017, the NAS0111W alarm message
was reserved for ALARMS LOST notification. With
the introduction of the PRNT and SHOW command alarm
messages in enhancement APAR 2400017, the NAS0111W
message ID was inadvertently used for the SHOW OFF
alarm.
SOLUTION1: Messages that deal with SYSCONS and SYSPRINT problems
are now issued with MSGSEV=U (unconditional) rather
with MSGSEV= defaulting to the last character of the
message ID. This prevents them from being filtered
using the BUILD ALRMFLTR= operand. These messages
are considered critical and must not be allowed to be
filtered out.
SOLUTION2: The SHOW alarm message IDs have been changed from
NAS011xs to NAS012xs in order to avoid conflicts.
CIRCUMVENTION1: N/A
CIRCUMVENTION2: 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-18 - APAR 2400018 (was problem 2006254A & 2300204)
APAR: 2400018
STATUS: CLOSED
OPEN_DATE: 2006-12-20
REV_DATE: 2007-01-18 - ZIP file repackaged to correct ASM library.
Do not use 2007-01-13 *.zip file.
CLOSE_DATE: 2007-01-13 - edistribution correct as of this date.
SERVICE(S): Configuration: CDF parsing, IDLETO= operand processing
and new information messages
MANDATORY: YES
ORIGIN/REF: 230/240_CPA,240_CPT
CPTECH: PRT/SFD
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400018.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-12-28
With APAR: 2400017 applied.
SUPERSEDES: N/A
SOURCE(S): N/A
OBJECT(S): CNFGIDTO , CNFGPVC , CNFGSVC0 , CNFGSVC3 , CNFGSVC5 ,
CNFGTYPE , CONSDRMT , CONSMRMT , MCHHL0RQ , MCHHL5RQ ,
MCHPVCI , NASCNFG , NASUTIL , QLSSCP , VCUT1 ,
XOTFCDC , XOTGTCC , XOTRCV
OVERVIEW: This APAR addresses the following configuration,
runtime and alert message problem issues:
PROBLEM1: HNAS unaware of a lost TCP/IP session after remote
network outage -- the IDLETO= parameter is not
working properly.
PROBLEM2: NASHALT 0198 ABEND can occur during TYPE= operand
processing.
PROBLEM3: Configuration messages cannot be filtered from the
SYSPRINT log.
PROBLEM4: It is not always obvious which MCH operands are
overridden by those from an MXT that is associated
with a PVC= or SVC0/3/5= operand entry.
DESCRIPTION1: 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.
DESCRIPTION2: If the TYPE= operand is specified on the same record
as another operand and the operands are separated by
a space character rather than a comma, the TYPE= value
will not be decoded properly. This results in the
NASHALT in the CNFGRTYP subroutine. This ABEND can
also occur if an invalid TYPE= operand value is
specified.
DESCRIPTION3: Heretofore, HNAS specifically prevented configuration
messages (NAS1xxxs) from being filtered using the
BUILD ALRMFLTR= operand. This prevents the user from
deleting repetitive (although potentially interesting)
messages from the SYSPRINT log.
DESCRIPTION4: When a user associates an MXT with a PVC= or SVC0/3/5=
operand entry, he is asking HNAS to override operands
on the root MCH with those from the MXT. In some cases,
this can lead to confusion if one does not remember to
review the HNAS documentation to see which operands can
be overridden based on the associated resource type.
SOLUTION1: The configuration logic has been modified 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 BUILD value (with a zero default).
SOLUTION2: The configuration logic has been modified to allow a
space as well as a comma to be used as an operand
separator character (this is the case in V2R3 but
was erroneously changed for V2R4). In addition,
HNAS will now default to TYPE=XTP if an invalid
TYPE= operand value is specified. This will almost
surely cause HNAS to terminate at the end of the
CDF scan with RC=12. However, error messages will
be issued instead of an ABEND so the problem can be
easily corrected.
SOLUTION3: HNAS has been modified to allow configuration messages
to be filtered using the BUILD ALRMFLTR= operand.
Filtering will commence as soon as the ALRMFLTR=
operand is processed. This logic was added primarily
for the new NAS1391I message (see below).
SOLUTION4: The configuration logic has been modified to display,
for each SLU or SPU defined in the PVC= or SVC0/3/5=
operands with an associated MXT (or SVC), those MXT
operands that will override operands of the same name
on the root MCH.
Not all MXT operands are valid overrides for all SLUs
or SPUs. For example, IDLETO= is a valid override
when specified for an MXT that is associated with
a SVC0/5= SLU but is not used for a PVC SLU.
MXT override messages are listed at the end of the CDF
scan in NAS1391I messages. Only those MXT operands
that are specified and, of these, only those that are
valid as overrides for an SLU or SPU are displayed.
If an MXT operand is not listed, it is because it was
either omitted from the MXT (an hence cannot override
the MCH operand) or, if specified, is not valid as
an override for the SLU or SPU resource. Consider
the following configuration example:
MCH1 REMOTE TYPE=MCH
IDLETO=2
PAD=INTEG
PADPARM=(1/1,
2/1,
13/7,
21/0,
110/0)
PVC=(3,
MCH1P001/5/255/01/SERIAL0-1/R2CNOT1/MXT0,
MCH1P002/5/255/02/SERIAL0-1//MXT2,
MCH1P003/5/255/03/SERIAL0-1)
SVC0=(2,
MCH10011/1234-X1234-<MXT1>T01/MXT0
MCH10012/1234-<MXT0>-X1234T1)
SVC5=(2,
MCH15001/1234-X1234-<MXT1>T01/MXT0
MCH15002/1234-<MXT0>-X1234T1)
SVC3=(1,Q1990100//MXT0)
:
MXT0 REMOTE TYPE=MXT
CUD=(01111111)
DCEADDR=1111
DTEADDR=9999
FAC=(420808
430404)
IDLETO=15
PADPARM=(1/1,
2/1,
3/2,
4/0,
5/2,
7/2,
12/1,
13/7,
21/0,
110/0)
MXT1 REMOTE TYPE=MXT
CUD=(01222222)
DCEADDR=2222
FAC=(0101420A0A430202)
PADPARM=(1/1,
2/1,
7/2,
12/1,
13/7,
21/0,
110/0)
MXT2 REMOTE TYPE=MXT
CUD=(01222222)
DCEADDR=2222
Q1990100 REMOTE TYPE=SPU
LUNAME=(,
Q1990102/201/201/1/PVCMXT,
Q1990103)
DTEADDR=20361234
DCEADDR=20364321
FAC=420707430707
CUD=C3000000
IDBLK=199
IDNUM=00001
:
Based on this configuration, the following messages
are generated at the end of the CDF scan.
NAS1391I THE FOLLOWING OPERANDS FOR SLU MCH1P001 (DEFINED ON MCH MCH1
NAS1391I AS PVC ENTRY 000) COME FROM MXT MXT0 RATHER THAN THE MCH
NAS1391I --> FAC=420808430404
NAS1391I THE FOLLOWING OPERANDS FOR SLU MCH1P002 (DEFINED ON MCH MCH1
NAS1391I AS PVC ENTRY 001) COME FROM MXT MXT2 RATHER THAN THE MCH
NAS1391I --> NO OVERRIDES
NAS1391I THE FOLLOWING OPERANDS FOR SLU MCH10011 (DEFINED ON MCH MCH1
NAS1391I AS SVC0 ENTRY 0000) COME FROM MXT MXT0 RATHER THAN THE MCH
NAS1391I WHEN CONNECTION IS NOT ESTABLISHED VIA A <RMTNAME>
NAS1391I --> CUD=01111111
NAS1391I --> DCEADDR=1111
NAS1391I --> DTEADDR=9999
NAS1391I --> FAC=420808430404
NAS1391I --> IDLETO=00015
NAS1391I THE FOLLOWING OPERANDS FOR SLU MCH10011 (DEFINED ON MCH MCH1
NAS1391I AS SVC0 ENTRY 0000) COME FROM MXT MXT1 RATHER THAN THE MCH
NAS1391I WHEN CONNECTION IS ESTABLISHED VIA <MXT1>
NAS1391I --> CUD=01222222
NAS1391I --> DCEADDR=2222
NAS1391I --> FAC=0101420A0A430202
NAS1391I THE FOLLOWING OPERANDS FOR SLU MCH10012 (DEFINED ON MCH MCH1
NAS1391I AS SVC0 ENTRY 0001) COME FROM MXT MXT0 RATHER THAN THE MCH
NAS1391I WHEN CONNECTION IS ESTABLISHED VIA <MXT0>
NAS1391I --> CUD=01111111
NAS1391I --> DCEADDR=1111
NAS1391I --> DTEADDR=9999
NAS1391I --> FAC=420808430404
NAS1391I --> IDLETO=00015
NAS1391I THE FOLLOWING OPERANDS FOR SPU Q1990100 (DEFINED ON MCH MCH1
NAS1391I AS SVC3 ENTRY 0000) COME FROM MXT MXT0 RATHER THAN THE MCH
NAS1391I WHEN THEY ARE OMITTED FOR THE SPU
NAS1391I --> CUD=01111111
NAS1391I --> DCEADDR=1111
NAS1391I --> DTEADDR=9999
NAS1391I --> FAC=420808430404
NAS1391I --> IDLETO=00015
NAS1391I THE FOLLOWING OPERANDS FOR SLU MCH15001 (DEFINED ON MCH MCH1
NAS1391I AS SVC5 ENTRY 0000) COME FROM MXT MXT0 RATHER THAN THE MCH
NAS1391I WHEN CONNECTION IS NOT ESTABLISHED VIA A <RMTNAME>
NAS1391I --> CUD=01111111
NAS1391I --> DCEADDR=1111
NAS1391I --> DTEADDR=9999
NAS1391I --> FAC=420808430404
NAS1391I --> IDLETO=00015
NAS1391I --> PADPARM=001/001 002/001 003/002 004/000 005/002 007/002 ...
NAS1391I THE FOLLOWING OPERANDS FOR SLU MCH15001 (DEFINED ON MCH MCH1
NAS1391I AS SVC5 ENTRY 0000) COME FROM MXT MXT1 RATHER THAN THE MCH
NAS1391I WHEN CONNECTION IS ESTABLISHED VIA <MXT1>
NAS1391I --> CUD=01222222
NAS1391I --> DCEADDR=2222
NAS1391I --> FAC=0101420A0A430202
NAS1391I --> PADPARM=001/001 002/001 007/002 012/001 013/007 021/000 ...
NAS1391I THE FOLLOWING OPERANDS FOR SLU MCH15002 (DEFINED ON MCH MCH1
NAS1391I AS SVC5 ENTRY 0001) COME FROM MXT MXT0 RATHER THAN THE MCH
NAS1391I WHEN CONNECTION IS ESTABLISHED VIA <MXT0>
NAS1391I --> CUD=01111111
NAS1391I --> DCEADDR=1111
NAS1391I --> DTEADDR=9999
NAS1391I --> FAC=420808430404
NAS1391I --> IDLETO=00015
NAS1391I --> PADPARM=001/001 002/001 003/002 004/000 005/002 007/002 ...
Note 1: The NAS1391I message for SLU MCH1P001 above only
displays the FAC= operand for MXT0 even though
other operands were specified. This is because
only the FAC= operand is used as a PVC SLU
override operand.
Note 2: The NAS1391I message for SLU MCH1P002 shows 'NO
OVERRIDES' because the FAC= operand for was
omitted for MXT2. Note that no NAS1391I message
is issued for SLU MCH1P003 since no MXT was
associated with this SLU.
Note 3: The NAS1391I messages for the SVC3= operand
above list MXT overrides when operands are
omitted from the SPU. The order is MXT first,
SPU then MCH. This only applies when SPU
connections are established via the MCH and
not by IDBLK/IDNUM matching which is MCH
independent.
Note 4: The SVC0= and SVC5= operands above are identical
except for the SLU names. Note that the NAS1391I
messages for the SVC0= and SVC5= operands are
the same except that the PADPARM= operand is
listed for SVC5= SLUs (when specified on the MXT)
while it is not for SVC0 SLUs. This is because
only SVC5= SLUs use the PADPARM= operand.
Note 5: The NAS1391I messages are generated only when an
SLU or SPU has an associated MXT as provided in
the PVC= or SVC0/3/5= operand. If you wish to
withhold the NAS1391I messages from the SYSPRINT
log, specify ALRMFLTR=(...,NAS1391I(P),...)
on the BUILD definition statement.
Note 6: If you plan on filtering NAS1391I messages from
SYSPRINT, we highly recommend that you first
run a FASTRUN pass without filtering so that
these important messages are at least displayed
once for your perusal.
CIRCUMVENTION1: 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.
CIRCUMVENTION2: Specify a valid TYPE= value.
CIRCUMVENTION3: N/A
CIRCUMVENTION4: 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).
Last Update - December 31, 2007