APAR memo entries with PTF_TYPE: (ZAP) designations in the HNAS 23n HTML Maintenance Summaries now contain hyperlinks to their respective APAR Memo's in ASCII (*.txt) format. This will allow for immediate ZAP retrieval without having to access the HNAS userid/password based FTP Server. Please be aware that all PTF_TYPE: SRC (source) and OBJ (object) maintenance is provided on the HNAS FTP Server. Please 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 |
|---|---|---|---|---|
|
230nnnn 230nnnn_D 230nnnn_E 230nnnn_M 230nnnn_P 230nnnn_R 230nnnn_U |
mm-dd-yyyy-> |
(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. |
| - | - | - | - | - |
| 2300nnn thru 2300095 | <Link forward> | - | - |
HNAS V2R3M0 - 2005 MAINTENANCE SUMMARY (Link to APARs 2300095 thru 2300nnn) |
| 2300094_E | 12-17-2004 |
TRCTRAP=(, TRAPACTION=) <Diagnostic Enhancement> |
OBJ/SRC | TRAPACTION=SNAP|NOSNAP and SUSP|NOSUSP options added to TRCTRAP= parameter improves debugging and trace suspension processes for environments where systems operations are automated or unattended. |
| 2300093 | 12-14-2004 |
ALL, Alert Messages |
SRC | The NAS3799I (session end message) can have an incorrect DIAGX= value. For example, the HNAS diagnostic value of 216 should always have a non-zero DIAGX= value. |
| 2300092 | 12-09-2004 |
GATE Diag. Packet |
OBJ | NAS7703W alarm issued when remote sends X.25 Diagnostic packet. |
| 2300091 | 12-03-2004 |
CDF/CNFG - PVC TYPE=MCH REMOTE |
OBJ | A configuration error message is not generated when a non-XOT REMOTE name is specified as the last suboperand in a PVC= operand entry for an MCH. |
| 2300090 | 12-01-2004 | Cons-Subsystem DLU |
OBJ/SRC | The HNAS DLU console command does not always display the unbound PLU name when the DLU SHOWUNBAPPL argument is specified. |
| 2300089 | 11-22-2004 | Cons-Subsystem DNAS |
OBJ | DNAS display of unapplied maintenance shows 'MISSING' for the module name when an APAR is not on. Some users have reported concern over the MISSING text terminology. |
| 2300088 | 11-19-2004 |
TCPIP interface, GATE, Console Subsystem |
OBJ/SRC |
This APAR fix and enhancement addresses the following: 1) Original problem description indicated the customer's CTCP (TOM) ABENDed during load tests. Additionally, X.25 Network load test can cause HNAS to issue NAS2201W RC=FFFFFFFF 000027DD and NAS7717W CAUSE/DIAG=000/195 (00/C3) DIAGX=0000. After this, outbound call requests fail and HNAS must be reloaded. 2) Unable to determine reason for 27DD error condition (ENHANCEMENT) with existing trace and SYSPRINT logging facilities. SHOWMORE debugging tools developed. 3) HNAS can terminate abnormally with ABEND 0198 (NASHALT) after a TCPIP stack is stopped. |
| 2300087 | 11-18-2004 | PCNE/PAD
CNFG (Two-ways) and Cons
Subsystem MRMT SLU names |
OBJ | 1) Logic introduced by enhancement APAR 2300083 that allow the SVC0= and SVC5= operands to specify SLUs as callin (I) or callout (O) and twoway (T) causes a NAS1321E ERROR: message to be generated when no Xidnum or DTE-addr is specified but an MXT is. Example: MCH15001//MXT1 2) Logic introduced by enhancement APAR 2300084 can cause a NASHALT 0198 ABEND to occur when MRMT is used to modify an SVC5= operand entry. |
| 2300086 | 11-18-2004 | QLLC | SRC |
This APAR fixes several QLLC problems. 1) NASHALT 0198 ABEND can occur when a NOTIFY PIU request is received. 2) ACTPU text in NAS8110I message is being overlaid. 3) QLLC sessions for devices on an SPU hang at session start. |
| 2300085 | 11-16-2004 | GATE (LLC4) | OBJ/SRC | HNAS display shows bound GATE data LUs with no VC. These LUs are not available for new sessions (hung LU). |
| 2300084_E | 11-15-2004 | Cons-Subsystem MRMT SVCn=(sluname <Enhancement> |
OBJ/SRC | The HNAS MRMT console command processor is has been modified to allow PCNE/GATE/PAD SLU names to be added or changed for the SVC0=/SVC4=/SVC5= operands on a TYPE=MCH REMOTE. |
| 2300083_E | 11-15-2004 |
CDF/CNFG PCNE/PAD <Enhancement> |
OBJ/SRC | Bidirectional (both-ways/two-ways) VC support. SVC0= and SVC5= operands now allow you to specify SLUs as two way (T) as well as the existing callin (I) and callout (O). |
| 2300082_E | 10-20-2004 | Cons-Subsystem DLU and DVC <Enhancement> |
OBJ/SRC | 1)
The PLU name is displayed by the DLU command even
when the PLU is no longer bound. 2) It is difficult to identify the router, MCH or SPU that is associated with an SLU using the DLU command. 3) It is difficult to identify the router, MCH, SPU or SLU that is associated with a VC using the DVC command. 4) Console Subsystem error messages are not always generated when conflicting parameters are entered. |
| 2300081 | 10-18-2004 | Cons-Subsystem | OBJ/SRC | Alarm messages are not routed to SYSCONS when APAR 2300080 is on system. |
| 2300080 | 10-11-2004 | Cons-Subsystem | OBJ |
1) Information alarm messages are not filtered by the
ALRMFLTR= operand when SHOWERR is in effect. 2) PFXWTO CONS is required in addition to SHOWCONS so that console output is routed back to NETVIEW. |
| 2300079 | 10-07-2004 | QLLC | OBJ/SRC | QLLC session hangs after SIGNAL is received from the PLU. PLU must reset the HNAS SLU for operation to continue. |
| 2300078 | 10-06-2004 | QLLC | OBJ | QLLC User 198 ABEND - HALT AT LOC 8xxxxxxx IN MCHLUIN: LUSVMSG INVALID |
| 2300077 | 10-06-2004 |
CDF/CNFG PVC= and TRCLMT= General Cleanup |
OBJ | 1) Omitted PVC= operand on a TYPE=MCH REMOTE definition statement causes NAS1301W warning message when it should be and Informational message. 2) TRCLMT= operand value on BUILD definition statement is limited to 32767 (increase to 1048575). |
| 2300076 | 10-04-2004 | QLLC | OBJ | QLLC PIU's can be rejected beginning with sequence number X'8000' due to a sequence number compare logic boundary condition in HNAS. Subsequent input messages generate similar alarms. |
| 2300075 | 09-30-2004 |
QLLC SYSL= General Clean-up |
OBJ | NAS1301D REMOTE SYSL OMITTED, MCHSOL ASSUMED configuration warning message is generated when the SYSL= operand is omitted even though all SLUs in the LUNAME= operand have an associated applid value (APPLNAME= index). |
| 2300074 | 09-22-2004 |
GATE STRIPRTEIN |
OBJ | GATE resource in conjunction with STRIPRTEIN can cause 0C4 ABEND or Clear DIAG=138 when callin session starts. |
| 2300073 | 09-21-2004 |
QLLC CNFG |
OBJ | NASHALT 0198 ABEND can occur immediately after HNAS is started when a new MCH definition is added to the CDF. |
| 2300072 | 09-21-2004 | ALL, IDLETO= | OBJ | Value specified by IDLETO= parameter not processed correctly. Sessions prematurely cleared with DIAG=198 (X'C6'). Clears with DIAG=130 occurred as a result of the premature inactivity timeouts. |
| 2300071 | 09-11-2004 | TAP CDF Default Warning Message | OBJ | Configuration warning messages are generated when TAP=value and OPTIONS=TAPWITHCLR are specified but CUD=, DCEADDR=, DTEADDR= and/or FAC= are omitted. |
| 2300070 | 09-10-2004 | Cons-Subsystem WTOR Support |
OBJ/SRC | Session manager (including Netview/NCCF console I/O) support for HNAS console routing and unsolicited messages delivery. |
| 2300069_E | 08-30-2004 |
Distribution and Maintenance <Enhancement> |
OBJ/SRC | Product distribution enhancement improving CustomUserMod maintenance identification including DNAS APAR XFFIX ID assignment for HNASMACX and HNASOBJX. |
| 2300068 | 08-18-2004 | Cons-Subsystem | OBJ | Console commands are rejected when HNAS initialization does not complete. |
| 2300067 | 08-16-2004 | NASAUTH
Authorization Validation |
OBJ/SRC | Descriptive HNAS WTO message not provided when NASAUTH Authorization failure occurs (ABEND 198 'AC FAILURE) due to customer coding error (//AUTH DD statement). |
| 2300066 | 08-15-2004 | Cons-Subsystem MLCL | OBJ | MLCL INIT=DELAYTIME=0|RETRYLMT=0 is rejected due to an error in the convert logic. |
| 2300065_E | 08-13-2004 | Cons-Subsystem DNAS
APAR <Fix/Enhancement> |
OBJ/SRC | 1) Enhancement to DNAS command providing a display of custom-user-mods applied to the users HNAS system (as appropriate) when the DNAS command argument USERMODS is specified. 2) Some remote console DNAS APAR display output is routed to the local console (SYSCONS) rather than to the remote console that solicited the output. |
| 2300064 | 08-11-2004 | Cons-Subsystem MRMT | OBJ | ABEND 0C4-10 or ABEND 198 (NASHALT INV LU-2) can result if the MRMT console command is used to add a new SLU to the LUNAME= operand for a TYPE=SPU REMOTE definition statement. |
| 2300063 | 08-10-2004 | Cons-Subsystem MLCL | OBJ | ABEND 0C4-10 can result if MLCL command is used to delete an RTEIN= or RTEOUT= operand entry. |
| 2300062_E | 08-02-2004 | Cons-Subsystem <Enhancement> |
OBJ/SRC | Enhancement to DNAS command providing a display of missing maintenance (not applied) when the distribution APAR ID is different than the most recent APAR ID value. |
| 2300061_E | 07-29-2004 |
Cons-Subsystem Rmt-Access <Enhancement> |
OBJ/SRC | Enhancement allowing users to disable remote console access in their CDF via CONLMT=0. Eliminate NAS1101W message for users that previously disabled remote console access by omitting the CONPSWD=value. |
| 2300060_E | 07-26-2004 |
LLC0|LLC5 <Enhancement> |
OBJ/SRC | Enhancement providing users control of Call Accept logic for LLC0 and LLC5 sessions using a CTCP (as is done with DATE). |
| 2300059 | 07-23-2004 |
GATE FC CNFG |
OBJ | Config. error messages generated for GATE FC MCH's when OPTIONS=LCN0USED| RESIDSTART= are specified. RESIDs generated for GATE FC data session LUs do not start at zero when LCN0USED is specified. |
| 2300058 | 07-21-2004 |
Cons-Subsystem DLCL, DRMT, |
OBJ | Some console commands (DLCL, DRMT, etc) are rejected if a null modifier override (LNM= for DLCL or RNM= for DRMT) is entered on right side of command (decode error). |
| 2300057 | 07-21-2004 |
QLLC CNFG <Enhancement> |
OBJ | Enhancement supporting SVC3=ALLOW option to improve SVC3= MCH SPU coding. |
| 2300056_E | 07-20-2004 |
All Callin <Enhancement> |
OBJ/SRC | MLCL enhancement provides ability to insert new entries in the LOCAL RTEIN= and RTEOUT= operand lists. |
| 2300055 | 07-14-2004 | QLLC (RJE) | OBJ | Inbound call request from QLLC RJE station fails with SENSE=08350027 due to mishandling of URC field in the BIND request by HNAS. |
| 2300054_E | 07-07-2004 |
Alert Msgs. <Enhancement> |
SRC | New NAS3703W NOTIFY and NAS3704W CLEANUP alert messages improve REQSESS diagnostics. |
| 2300053 | 07-07-2004 | Alert Msgs. | OBJ | NAS7715W alarm message can display incorrect decimal value for the clear diag= code and diagx= bytes are not displayed. |
| 2300052_E | 07-06-2004 |
GATE Callout <Enhancement> |
OBJ/SRC | New option PFXDCEADDR to insert the HNAS DCEADDR=value in front of the GATE callout calling address digits. |
| 2300051 | 06-29-2004 |
TRACING (TRCTRAP) |
OBJ/SRC | Assembly error in VTMTR module introduced by apar 2300047 due to missing symbol. |
| 2300050 | 06-27-2004 | QLLC | SRC | HNAS terminates with a USER 198 Abend and message: HALT AT LOC xxxxxx IN VTMRSPC: RECV RPL BUSY. |
| 2300049 | 06-24-2004 |
Cons-Subsystem WTOR Support |
OBJ | Two (2) WTO replies can be outstanding after a console command (like DPARM) is entered when USEMDFY option is NOT specified. |
| 2300048 | 06-23-2004 |
SMPE Install 2300045 maint |
SRC | Misc. SMP/E installation and maintenance related issues. |
| 2300047_E | 06-23-2004 |
TRACING and ALARM Console <Enhancement> |
OBJ/SRC | Improvements in console TRCTRAP= activation alert message indication and TRCTRAP SHOW TRACE STATE: status. |
| 2300046_E | 06-18-2004 |
Trace Entry <Enhancement> |
OBJ | New NASnnnnT trace entries for callin and callout packet logging activity. |
| 2300045_E | 06-15-2004 |
TRACING and ALARM Console <Enhancement> |
OBJ/SRC |
1) New TRCTRAP= provides automation tools for improved debugging and
trace suspension. 2) ALRMFLTR= console command improvements. |
| 2300044 | 06-03-2004 |
TCPIP Server Init |
SRC | HNAS will not SHUTDOWN if a server (LOCAL) is taken offline when HNAS cannot bind its IP address to the stack. |
| 2300043 | 06-03-2004 |
TCPIP - TAPPING |
OBJ/SRC | HNAS does not perform Keep Alive service even when a value is specified for the TAP= operand due to bug in APAR 2300042. |
| 2300042 | 06-02-2004 | TCPIP | OBJ/SRC | HNAS does not always process TCPIP stack sever properly. |
| 2300041 | 06-02-2004 | QLLC | OBJ | 1) HNAS logic error causes an IPR to be sent with the expedited flow bit set in the PIU's TH (violates SNA rules) 2) Pacing problem causes SLU TERM-SELF session disconnect. |
| 2300040 | 06-02-2004 | QLLC | OBJ | Reset 05/02 can be received for a QLLC VC. |
| 2300039_E | 05-28-2004 |
QLLC Alarm <Enhancement> |
OBJ/SRC | NAS8000I QLLC VC session start message enhanced to include calling/called DTE addresses as well as direction of call. |
| 2300038 | 05-26-2004 | QLLC | OBJ | 1) Session connect unsuccessful APPLNAME= ACQUIRE is erroneously treated as a PLU name by the UNBIND processor. 2) An 0198 ABEND (NASHALT - IN VTMLUFM : LU DIRTY) can occur after LU UNBOUND. |
| 2300037 | 05-21-2004 | GATE/GATEFC | OBJ/SRC | GATE control session not properly re-activated when PLU taken down & restarted. Inbound calls are cleared with DIAG=138 (X'8A'). NAS3702W message issued. |
| 2300036 | 05-19-2004 | QLLC Callout | OBJ | When a BIND initiated Call Request fails due to a Clear condition, a subsequent BIND will not initiate another Call Request. |
| 2300035 | 05-15-2004 |
LLC0-LLC5, CNFG |
OBJ | A configuration warning messages can be erroneously generated when an SVCi= vclmt value is coded without SLU/SPU components. |
| 2300034 | 05-13-2004 | QLLC | OBJ | QLLC session can hang due to a bug in the pacing logic after a non-FMD BID request. |
| 2300033_E | 05-13-2004 |
QLLC, CNFG <Enhancement> |
OBJ | Comma coding improvement for TYPE=SPU REMOTE LUNAME= LOCADDR index values. |
| 2300032 | 05-12-2004 | Cons-Subsystem | OBJ | Remote console PAD access Reset 05/27 loop condition can occur due to a bug introduced in APAR 2300022 WTOR form changes. |
| 2300031 | 05-12-2004 | QLLC | OBJ | 1) Session hang can occur during processing of a formatted FMD. 2) 0198 ABEND (NASHALT) can occur using QLLC callout OPTIONS= CLOTINITYP=BIND. |
| 2300030 | 05-12-2004 | QLLC | OBJ | Printer SLU cannot be bound for multiple application unless 'ACQUIRE' is enabled. |
| 2300029 | 05-12-2004 | QLLC | SRC | Wrong MCH name can be displayed in NAS3798I message and trace table when QLLC OPTIONS= CLOTINITYP=BIND is enabled. |
| 2300028 | 05-12-2004 | QLLC | OBJ | Application connection via INIT-SELF or user LOGON data can fail. |
| 2300027 | 05-07-2004 | Cons-Subsystem | OBJ | Bug prevents NAS3798I & NAS3799I alarms from displaying on SYSCONS when the SHOWON option is in affect. |
| 2300026_E | 05-06-2004 |
HNAS Console <Enhancement> |
OBJ/SRC | PFXWTO enhancement allowing a user defined prefix name for alarm messages and console output. NASNAME= option is still supported. |
| 2300025 | 05-05-2004 | Cons-Subsystem | OBJ | An 0C1 ABEND can occur after the SHOW CONS ON console command is issued. |
| 2300024 | 05-04-2004 | LLC0|LLC5 Callout | OBJ | HNAS User 198 ABEND - HALT AT LOC xxxxxxxx IN XOTBXM: INV VC. Bug in multiple RTEOUT= callout support. |
| 2300023 | 05-04-2004 | QLLC Callout | OBJ | HNAS can ABEND with 0C4 when the QLLC BIND initiated callout (CLOTINITYP=BIND) is used. |
| 2300022 | 05-02-2004 |
Cons-Subsystem WTOR Support |
OBJ/SRC | Non-USEMDFY support - Two WTO replies are outstanding when HNAS starts when USEMDFY parameter is not specified. |
| 2300021 | 04-22-2004 | HNAS Console | OBJ | PING command does not process a called DTE address override value properly when the IP address is omitted. |
| 2300020 | 04-21-2004 |
LLC0|LLC3| LLC5 CNFG |
OBJ | LOGTAB and USSTAB for a TYPE=MXT REMOTE definition statement are not resolved (problem introduced with APAR 2200076). |
| 2300019_E | 04-19-2004 |
Minor Fixes & <Enhancement> |
OBJ/SRC | General product cleanup of CDF processing, Console Subsystem and Alarm filtering. |
| 2300018 | 04-16-2004 | QLLC | OBJ/SRC | UNBIND bind forthcoming created by CLSDST OPTCD=PASS is incorrectly processed. |
| 2300017 | 04-15-2004 | TCPIP, TAP= | OBJ/SRC | TAP TCPIP socket can close prematurely when a firewall/router open socket timer expires before the TAP=seconds value. |
| 2300016_E | 04-14-2004 |
HNAS Console <Enhancement> |
OBJ | Improved DMCH FMT3 Local console command now provides display of LUs associated with MCH. |
| 2300015 | 04-13-2004 | Multi-LOCAL TCPIP, CNFG. | OBJ | Users unable to define multiple LOCAL definition statements with the same IPADDR= and PORT= operand values after 230 upgrade. |
| 2300014 | 04-07-2004 | PVC Only | OBJ | PVC environment with no SVCi= resources defined encounters CDF CC-8 condition. |
| 2300013 | 04-06-2004 | LLC3 USSTAB and LOGTAB | OBJ | USSTAB for TYPE=SPU REMOTE is not resolved properly when APPLNAME= defaults. |
| 2300012 | 04-03-2004 | HNAS Console | OBJ | PING command default incorrectly decoded. |
| 2300011 | 04-01-2004 | QLLC | OBJ | HNAS QLLC SLU UNBIND response processing can be prematurely terminated. |
| 2300010_E |
04-01-2004 - 04-19-2004 |
HNAS Tracing <Enhancement> -> |
SRC - -> |
Improved trace event identification for HNAS LU tracing of BIND, SDT,
UNBIND, etc. See note in apar memo dated 04-19-2004. |
| 2300009 | 03-30-2004 | Cons-Subsystem | OBJ | PFXWTO option can cause display message truncation on long messages. |
| 2300008 | 03-30-2004 | HNAS Console | OBJ/SRC | PING command decode error, Abend condition. |
| 2300007_E | 03-29-2004 |
CDF CNFG. <Enhancement> |
OBJ/SRC |
FASTRUN AMNF VBUILD statement name origin improvement (APPLNAME= instead of NASNAME=). |
| 2300006_E | 03-29-2004 |
HNAS Console <Enhancement> |
OBJ/SRC | New start parameter option PFXWTO CONS uses existing NASNAME= values for HNAS console output prefix. |
| 2300005_E | 03-29-2004 |
HNAS Console <Enhancement> |
OBJ/SRC | Console diagnostic trace event improvements. |
| 2300004 | 03-19-2004 |
HNAS Console APAR List |
OBJ/SRC | DMAP APAR command operation and display limitations corrected. |
| 2300003 | 03-16-2004 | GATE | OBJ/ZAP | GATE REPDCEADDR call requests fails. |
| 2300002 | 03-11-2004 | TCPIP | SRC | HNAS can ABEND with 0C4 when LOCAL socket limit threshold NAS2601W/NAS2602I occurs. |
| 2300001 | 03-09-2004 | QLLC | OBJ | HNAS can ABEND with 0C4 if an SPU is defined but is not referenced in any SVC3= operand. |
| 2300000 | 03-04-2004 | ALL | N/A | Service_Notice-Begin_Maintenance/APAR_Cycle |
| 230beta | 03-01-2004 | ALL | N/A | Beta SMP/E Installation product testing. |
| - | - | - | - | - |
| 230nnnn_i | mm-dd-yyyy |
GATE/LLCn/ PVC/QLLC/... |
ZAP/SRC/ OBJ/DOC/ CNFG/... |
<-Brief Problem Description-> 230nnnn_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 V2R3M0 - Release Status for additional information.
12-17-2004 - APAR 2300094 (was unpublished problem 2004347A)
APAR: 2300094
STATUS: CLOSED
OPEN_DATE: 12-09-2004
CLOSE_DATE: 12-17-2004
SERVICE(S): DIAGNOSTIC ENHANCEMENT
MANDATORY: NO, BUT RECOMMENDED ENHANCEMENT
ORIGIN/REF: 230_POR
PTF_CLASS: ENHANCEMENT-APAR
PTF_TYPE: (OBJ) HNASOBJX and (SRC) HNASMACX members
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300094.ZIP file)
COREQ(S): N/A
PREREQ(S): APAR 2300088, 2300047, 2300045
(and associated APARs PREREQ chains)
OBJECT(S): CNFGTRTR, CONSHELP, CONSTALL, CONSTRTR,
NASCNFG, NASUTIL
SOURCE(S): NASMAIN, NASTCP, XFBLK, XFNASWA
PROBLEM: Unable to capture the cause of certain problems when
systems operation is automated/unattended.
DESCRIPTION: Customer reports that it is difficult and sometimes
impossible to trap an error and SHUTDOWN HNAS before
debugging control block information is lost. This
may be the be the case even when operations personnel
are present and is certainly the case when no one is
around.
SOLUTION: To avoid the need for an operator initiated SHUTDOWN
or a forced ABEND, the TRCTRAP= operand logic has been
modified to allow an action operand (,TRAPACTION=) as
follows:
TRCTRAP=(ALRMLIST=(...),
RCVLIST=(...),
XMTLIST=(...),
TRAPACTION={ALL|NONE|
({SUSP|NOSUSP},{SNAP|NOSNAP})})
The action taken when a TRCTRAP 'hit' occurs currently
defaults to TRAPACTION=SUSP which causes HNAS tracing
and SYSPRINT trace logging to be suspended.
The new TRAPACTION=SNAP operand will allow a snapshot
of all HNAS control blocks and trace entries to be
logged in SYSPRINT when a 'hit' occurs.
If SUSP is required in addition to SNAP, both must be
specified so that both functions are performed. For
example, TRCTRAP=(TRAPACTION=(SUSP,SNAP)) or simply
TRCTRAP=(TRAPACTION=ALL).
If either SUSP or SNAP is specified by itself, only
that action is performed on a hit. If the TRAPACTION=
suboperand is omitted, SUSP is assumed (downward
compatibility with operation under implementation
of Enhancement APAR 2300045).
If you wish to define trap filters but postpone
any action on a trap hit until the TRCTRAP RSME,
TRCTRAP RSMESNAP or TRCTRAP RSMEALL console command
is entered, specify TRAPACTION=(NOSUSP,NOSNAP) or
simply TRAPACTION=NONE.
Note: The TRCTRAP console command has been modified to
accept TRAPACTION=({SUSP|NOSUSP},{SNAP|NOSUSP})
as well as TRAPACTION={ALL|NONE} as an argument
in order to provide equivalent functions for the
TRCTRAP= configuration operand.
The TRCTRAP HELP display has been modified as well.
The following display will now be presented when
HELP TRCTRAP or TRCTRAP ? is entered:
TRCTRAP *TRACE TRAP CONTROL
ENTER> TRCTRAP {ALRMLIST={?|*|(idm,...,idn)}}
{RCVLIST={?|*|
(protm||pktm,...,protn||pktn)}}
{XMTLIST={?|*|
(protm||pktm,...,protn||pktn)}}
{TRAPACTION={?|*|ALL|NONE|
({SUSP|NOSUSP},
{SNAP|NOSNAP})}}
{SHOW} {SUSP|RSME}
{SNAP|RSMESNAP} {RSMEALL}
NOTE: enter ? as first operand value to display operand
* as first operand value to reset operand
idi=NASxxxxs (*=wildcard)
proti=00 for XTP, proti=04 for XOT
pkti=ttdd...dd where tt=pkttype, dd=pktdata
(FF=wildcard)
TRCTRAP=SUSP to suspend tracing
on a trap hit
TRCTRAP=NOSUSP to inhibit trace suspension
on a trap hit
TRCTRAP=SNAP to take a snapshot dump
on a trap hit
TRCTRAP=NOSNAP to inhibit a snapshot dump
on a trap hit
TRCTRAP=ALL|(SUSP,SNAP) to enable all
trap actions
TRCTRAP=NONE|(NOSUSP,NOSNAP) to disable all
trap actions
SHOW to display all operand values
SUSP to suspend tracing manually
RSME to resume suspended tracing
SNAP to take snapshot dump manually
RSMESNAP to allow another SNAP dump
after a trap hit
RSMEALL to resume all specified actions
after a trap hit
NOTE: RSME|RSMEALL must be entered to resume suspended
tracing after a trap hit
RSMESNAP|RSMEALL must be entered to allow another
SNAP dump after a trap hit
TRAPACTION=SUSP suspends tracing and TRCPRNT
logging on a trap hit
TRAPACTION=SNAP requires additional CPU cycles
on a trap hit but is only a momentary
spike while the snapshot dump is taken
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).
12-18-2004 - APAR 2300093
APAR: 2300093
STATUS: CLOSED
OPEN_DATE: 12-14-2004
REV_DATE: 12-18-2004 Because of an error when the object module
for this APAR was generated, the DMAP APAR
command would not reflect the fact that this
APAR was installed. Object module corrected
so that the APAR shows as installed.
CLOSE_DATE: 12-14-2004
SERVICE(S): ALL
MANDATORY: RECOMMENDED
ORIGIN/REF: 230_MAT
CPTECH: PRT
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (SRC) HNASMACX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300093.ZIP file)
COREQ(S): N/A
PREREQ(S): Distribution dated after: 12-01-2004
With APAR: 2300090 applied.
SUPERSEDES: N/A
OBJECT(S): N/A
SOURCE(S): VTMUT1
PROBLEM: The NAS3799I (session end message) can have an
incorrect DIAGX value. For example, the HNAS
diagnostic value of 216 should always have a
non-zero DIAGX value.
DESCRIPTION: See problem.
SOLUTION: Display routine corrected to display the correct
DIAGX value.
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).
12-09-2004 - APAR 2300092 (was problem 2004264A)
APAR: 2300092
STATUS: CLOSED
OPEN_DATE: 09-20-2004
CLOSE_DATE: 12-09-2004
SERVICE(S): GATE
MANDATORY: YES
ORIGIN/REF: 230_SWC,HVB
CPTECH: PRT
PTF_CLASS: STANDARD-APAR, refresh recommended.
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300092.ZIP file)
COREQ(S): N/A
PREREQ(S): Distribution dated after: 11-16-2004
with APAR: 2300085
SUPERSEDES: N/A
OBJECT(S): VCCLEAR, XOTRCV, XOTXMTC
SOURCE(S): N/A
PROBLEM: NAS7703W alarm issued when HNAS receives a Diagnostic
packet from a router.
DESCRIPTION: HNAS GATE session termination logic does not release
the VC and LU control blocks for the session until
the CTCP has been sent a Clear or Clear-Confirm
packet. If the CTCP does not have a RECEIVE active
to accept the HNAS termination message then the
VC's TCPIP session is left active. In this state
a new call can be received. HNAS treats this as an
error and tries to clear the new call. HNAS sees
the second clear for the VC as an error and does not
send the clear. After 10 minutes the router sends a
diagnostic packet which causes the alarm messages:
NAS7703W DIAG FROM ip-addr(port)
NAS7799I PKT=1000F132 1001.
SOLUTION: Correct HNAS logic to release the VC control block
and close the TCP/IP without waiting for the SEND
macro notifying the CTCP of the clear to complete.
In order to detect failues of this kind before the
router starts sending Dianostic packets a new alarm
has been created:
NAS7797W CALL FROM ip-addr(port). PCE HAS VC AT LOC
hex-addr LCST=st LU=lu-name LU ADDR=hex-addr
This alarm indicates that a TCP/IP session may not
have been terminated correctly. If this alarm is
received please contact customer support.
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).
12-03-2004 - APAR 2300091
APAR: 2300091
STATUS: CLOSED
OPEN_DATE: 12-02-2004
CLOSE_DATE: 12-03-2004
SERVICE(S): PVC - HNAS CONFIGURATION PROCESSING
MANDATORY: YES, IF PVCs ARE REQUIRED
ORIGIN/REF: 230_CP
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300091.ZIP file)
COREQ(S): N/A
PREREQ(S): N/A
OBJECT(S): CNFGHOME
SOURCE(S): N/A
PROBLEM: A configuration error message is not generated when
a non-XOT REMOTE name is specified as the last
suboperand in a PVC= operand entry for an MCH.
DESCRIPTION: If a REMOTE name is specified as the last suboperand
of a PVC entry or an MXT name is specified in an
SVC0/3/5= operand entry, the name is not resolved into
an address until after the entire CDF is processed
(GENEND). This is due to the fact that the referenced
REMOTE may appear later in the CDF. In addition to
resolving the REMOTE address, the configuration GENEND
process also checks to ensure that the named REMOTE
is the correct type. For the PVC= operand, the named
REMOTE must be TYPE=XOT.
The following message is generated if the named REMOTE
cannot be found in the CDF:
NAS1311E REMOTE mchname PVC index RMTNAME rmtname
NOT FOUND, REQUIRED
The following message is generated if the named REMOTE
was found in the CDF but is not TYPE=XOT:
NAS1311E REMOTE mchname PVC index RMTNAME rmtname
IS NOT TYPE=XOT, REQUIRED
These messages are not generated because of a bug
in the HOME= resolution processor. This logic is
also executed at GENEND time. The missing error
messages result because the REMOTE type remembrance
is being overlayed by the HOME= GENEND processor. By
the time the PVC= GENEND processor receives control,
the remembered REMOTE type has been switched from MCH
to XOT and so the PVC= GENEND processor essentially
NOPs.
CIRCUMVENTION: N/A
SOLUTION: The HNAS configuration process has been corrected
to prevent the remembered REMOTE type from being
overlayed during HOME= GENEND processing.
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).
12-01-2004 - APAR 2300090 (was unpublished problem 2004331A)
APAR: 2300090
STATUS: CLOSED
OPEN_DATE: 11-26-2004
CLOSE_DATE: 12-01-2004
SERVICE(S): CONSOLE SUBSYSTEM DLU COMMAND
MANDATORY: NO, BUT RECOMMENDED
ORIGIN/REF: 230_MAT,230_CP
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (SRC) HNASMACX and (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300090.ZIP file)
COREQ(S): N/A
PREREQ(S): APAR 2300083, 2300082
(and all associated APARs PREREQ chains)
OBJECT(S): CONSDLU
SOURCE(S): VTMUT1
PROBLEM: The HNAS DLU console command does not always display
the unbound PLU name when the SHOWUNBAPPL argument is
specified.
DESCRIPTION: The DLU command displays the PLU name from the LUAPPLID
field in the LU control block (LUB). This field is
normally set when an inbound REQSESS is scheduled to
solicit a BIND from the PLU. When a BIND is unsolicited
(for example callout), the LUAPPLID field is not set.
Conversely, the LUBPLUNM field is always set when the
SLU is bound. LUBPLUNM will be the same as LUAPPLID
for BINDs that are solicited by REQSESS. For all
SLUs except QLLC, the LUBPLUNM field survives across
BINDs. For a QLLC SLU, the LUBPLUNM field is reset
as part of UNBIND cleanup (call to the VTMLUFM routine
clears LUB workarea including BIND image that contains
the LUBPLUNM field). For this reason, the LUBPLUNM
field will be preserved when LUB cleanup takes place
so it will be available for the SHOWUNBAPPL request
for all SLU types.
SOLUTION: The HNAS UNBIND processor has been modified to
preserve the LUBPLUNM field during cleanup and the
DLU console command has been modified to use the
LUBPLUNM field instead of the LUAPPLID field so the
current PLU name or most recent PLU name (when the
SHOWUNBAPPL option is requested) will display under
the PLUNAME column.
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).
11-22-2004 - APAR 2300089
APAR: 2300089
STATUS: CLOSED
OPEN_DATE: 11-19-2004
CLOSE_DATE: 11-22-2004
SERVICE(S): CONSOLE SUBSYSTEM
MANDATORY: NO, BUT RECOMMENDED
ORIGIN/REF: 230_CAI
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300089.ZIP file)
COREQ(S): N/A
PREREQ(S): APAR 2300081 (and associated APARs PREREQ chains)
OBJECT(S): CONSDNAS
SOURCE(S): N/A
PROBLEM: DNAS display of unapplied maintenance shows 'MISSING'
for the module name when an APAR is not on. Some
users have reported concern over the 'MISSING' text
terminology.
DESCRIPTION: Some users have commented that the 'MISSING' text
is confusing and a cause for concern because they
felt it implied that all maintenance through the
'MOST RECENT' must be applied. This is not
necessarily the case. Many users apply only the
maintenance that is applicable to problems that
they have encountered. This can leave 'holes' in
applied APAR list. In this case, the missing APARs
should not be a cause for concern. They are simply
not required.
SOLUTION: The DNAS command processor has been modified to display
'MAINTENANCE STATUS' instead of 'MISSING MAINTENANCE'
in the header text and 'NOT INSTALLED' instead of
'MISSING' under MODULE when an APAR is not applied.
When all APARs are installed (up to the most recent
APAR ID), 'ALL MAINTENANCE ON ...' will be displayed
instead of 'NOTHING MISSING'. Hopefully, these
changes will eliminate customer concerns and confusion
when some maintenance is not installed.
OLD display:
APARID MODULE (MISSING MAINTENANCE)
230xxxx MISSING
:
230xxxx MISSING
-OR-
APARID MODULE (MISSING MAINTENANCE)
NOTHING MISSING
NEW display:
APARID MODULE (MAINTENANCE STATUS)
230xxxx NOT INSTALLED
:
230xxxx NOT INSTALLED
-OR-
APARID MODULE (MAINTENANCE STATUS)
ALL MAINTENANCE ON THROUGH MOST RECENT APAR xxxxxxx
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).
11-19-2004 - APAR 2300088 (was problems 2004204A and 2004252A)
APAR: 2300088
STATUS: CLOSED
OPEN_DATE: 07-22-2004 for PROBLEM1/2, 09-08-2004 for PROBLEM3
CLOSE_DATE: 11-19-2004
SERVICE(S): GATE, TCPIP interface, Console Subsystem
MANDATORY: YES
ORIGIN/REF: 230_BNP
PTF_CLASS: STANDARD-APAR and ENHANCEMENT-APAR
PTF_TYPE: (SRC) HNASMACX and (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300088.ZIP file)
COREQ(S): N/A
PREREQ(S): APAR 2300084, 2300042
(and all associated APARs PREREQ chains)
OBJECT(S): CONSDPRM, CONSHELP, CONSSHOW, CONSSTAT, CONSTBFR,
CONSTDAT, CONSTDSP, CONSTIO, NASCNFG, NASUTIL
SOURCE(S): NASMAIN, NASTCP, XFBLK, XFNASWA, XFPCE
PROBLEM1: Original problem description indicated the customer's
CTCP (TOM) ABENDed during load tests.
Additionally, X.25 Network load test can cause HNAS
to issue the following alarm message:
NAS2201W SOCKET REQUEST FAILED, RC=FFFFFFFF 000027DD
NAS7717W LU lu-name CALL TO DTE ADDR dte-addr VIA
REMOTE xxxxxxxx FAILED
NAS7717W CAUSE/DIAG=000/195 (00/C3) DIAGX=0000
After this, outbound call requests fail and HNAS must
be reloaded.
PROBLEM2: Unable to determine reason for 27DD error condition
(ENHANCEMENT) with existing trace and SYSPRINT logging facilities.
PROBLEM3: HNAS can terminate abnormally with ABEND 0198 (NASHALT)
after a TCPIP stack is stopped.
DESCRIPTION1: Customer analysis showed that the CTCP ABEND was a
result of a TOM CTCP bug (APAR-ID=xxxxxxxxx) caused
by the load generating program (calls wrapped at
the router). With the TOM fix applied the load test
continued to generate the NAS2201W error message with
the 27DD ERNO. After this message has been issued HNAS
requires a reload.
At the time of the failure the customer was conducting
stress tests using a CTCP named TOM. The above error
message indicates that HNAS is trying to use a socket
that the stack thinks is already in use. This
indicates that an error has been made in the recording
of active sockets.
DESCRIPTION2: Existing trace and SYSPRINT logging facilities do not
provide enough information to determine the reason
for the 27DD error condition. This necessitates
the need for additional trace and SYSPRINT logging
capabilities.
DESCRIPTION3: The 0198 ABEND (NASHALT) can occur when a customer
takes the stack down underneath HNAS. This is a
new problem, related to but different than the problem
corrected by APAR 2300042. APAR 2300042 addressed a
problem with the HNAS stack 'SEVER' logic which was
fixed and extensively tested on our z/OS V1R4 system.
It turns out that the SEVER correction logic introduced
by APAR 2300042 is working just fine. However, the
subsequent logic that attempts to re-establish contact
with the SEVERed stack has found a problem. Briefly:
When HNAS is first started OR after a connection
between a stack and an HNAS LOCAL is SEVERed (the stack
is taken down), HNAS continually attempts to establish
contact with the stack for the LOCAL. As part of this
processing, HNAS interrogates all the stacks to see if
the stack identified by the LOCAL TCPNAME= operand can
accept an API connection. HNAS uses the GETIBMOPT
command to do this. This command is processed by the
z/OS MVS system (UNIX kernel) on behalf of all stacks
running on the system. The command produces a map of
the installed stacks and has the following format:
byte contents
00-03 stack count => number of TCPIP images
(0=> no images present)
04-0F map for first stack image
04-05 status: 8xxx => stack is active
4xxx => stack is terminating
2xxx => stack is down
1xxx => stack has stopped
or is stopping
06-07 stack version
08-0F stack name (TCPNAME=)
10-1B map for second stack image
:
etc.
When the GETIBMOPT command ends, HNAS interrogates
the map produced by GETIBMOPT.
If the stack count is zero, HNAS waits and then retries
the GETIBMOPT command after a forced delay.
If the stack count is non-zero, HNAS steps through the
map looking for a stack name match with the TCPNAME=
operand on the requesting LOCAL.
If a name match is not found, HNAS waits and then retries
the GETIBMOPT command after a forced delay.
If a name match is found, HNAS tests the status flags.
If the status flags are 8xxx, HNAS assumes that the
named stack is active. In this case, HNAS attempts
to establish an API connection to the stack using
the INITAPI command. The ABEND 0198 is occurring
because the INITAPI command is being rejected with
ERNO=040C which says 'TCP/IP is not installed or
is not active'. This makes no sense because the
GETIBMOPT command indicated that the named stack
was active. HNAS is now confused and this results
in the NASHALT - 0198 ABEND. We do NOT believe that
this is an HNAS problem. HNAS is being tricked into
thinking that the SEVERed stack is actually active.
SOLUTION1: HNAS has been modified to record every socket
allocation request. Previously, SOCKET and ACCEPT
socket allocations were recorded but TAKESOCKET
socket allocations were not. This resulted in the
in the 27DD error condition due to collision when a
SOCKET call for an outbound request and a TAKESOCKET
call for inbound request occurred simultaneously.
Because TAKESOCKET socket allocation requests are
now recorded, a SOCKET request will not be able to
use the same socket that is being used by TAKESOCKET.
This will eliminate the 27DD error condition.
SOLUTION2: In order to find the cause of the ERNO=27DD condition,
it was necessary to develop additional tracing and
logging capabilities. This lead to the creation of
a new start parameter and console command to control
the additional logging. The SHOWMORE start parameter
and SHOW MORE console command are provided so that
HNAS can create additional diagnostic information.
When SHOWMORE is in affect, the following trace
message is logged in SYSPRINT:
NAS2711I PCESOCDS=FFFAF10B 03FEFDFF 00000000 00000000
NAS2711I 00000000 00000000 00000000 00000000
NAS2711I 00000000 00000000 00000000 00000000
NAS2711I 00000000 00000000 00000000 00000000
:
These messages display a bit map of the sockets
currently in use. When SHOWMORE is active, this
sequence of messages is logged anytime a socket
is allocated via a SOCKET, ACCEPT or TAKESOCKET
call or is released via a CLOSE call. This data
was critical to finding the cause of the 27DD
error condition. Once the cause of the condition
was determined, HNAS was modified to correct the
error.
SOLUTION3: HNAS TCPIP logic has been modified to treat an INITAPI
failure as though the GETIBMOPT command showed that
the stack was down. The 0198 ABEND will be prevented
and HNAS will retry the GETIBMOPT command after a
forced delay. The GETIBMOPT/INITAPI commands will
continue to be executed until the named stack comes
active or HNAS is shutdown.
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).
11-18-2004 - APAR 2300087 (was unpublished problem 2004321A)
APAR: 2300087
STATUS: CLOSED
OPEN_DATE: 11-16-2004
CLOSE_DATE: 11-18-2004
SERVICE(S): PCNE/PAD Cnfg (Two-ways) and MRMT SLU names
MANDATORY: YES if APAR 2300083 and 2300084 have been applied
ORIGIN/REF: 230_CP
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300087.ZIP file)
COREQ(S): N/A
PREREQ(S): APAR 2300084 (and associated APARs PREREQ chains)
OBJECT(S): CNFGSVC0, CNFGSVC5, CONSDRMT, CONSMRMT
SOURCE(S): N/A
PROBLEM1: Logic introduced by enhancement APAR 2300083 that
allow the SVC0= and SVC5= operands to specify SLUs
as callin (I) or callout (O) and twoway (T) causes
a NAS1321E ERROR: message to be generated when
no Xidnum or DTE address is specified but an MXT is.
Example: MCH15001//MXT1
PROBLEM2: Logic introduced by enhancement APAR 2300083 and
2300084 can cause a NASHALT 0198 ABEND to occur when
MRMT is used to modify an SVC5= operand entry.
DESCRIPTION1: See problem/solution.
DESCRIPTION2: ABEND 0198 occurs in module MCHPQ because an SVC0
QCB is being used in place of an SVC5 QCB.
SOLUTION1: The SVC0= and SVC5= operand logic has been corrected
to accept the missing Xidnum or DTE address value.
SOLUTION2: The MRMT command processor has been modified to
process the SVC5= update request as SVC5 not SVC0.
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).
11-18-2004 - APAR 2300086 (was problems 2004279A and 2004307A)
APAR: 2300086
STATUS: CLOSED
OPEN_DATE: 10-05-2004 (2004279A) , 11-02-2004 (2004307A)
CLOSE_DATE: 11-18-2004
SERVICE(S): QLLC
MANDATORY: YES if QLLC resources used.
ORIGIN/REF: 230_RWE
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300086.ZIP file)
COREQ(S): N/A
PREREQ(S): Distributions dated after: 07-06-2004 with APARS
2300039 and 2300052 and their PREREQs applied.
SUPERSEDES: N/A
OBJECT(S): QLSSCP, XOTUT1
SOURCE(S): N/A
PROBLEMS: This APAR fixes several QLLC problems.
1) NASHALT 0198 ABEND can occur when a NOTIFY request
is received.
2) ACTPU text in NAS8110I message is being overlaid.
3) QLLC sessions for devices on an SPU hang at session
start.
DESCRIPTIONS:
1) When a QLLC SLU is configured for auto logging
(applid value is specified for the SLU in the
LUNAME= operand), an ABEND can occur due to a
timing problem when a NOTIFY request with the
power on indicator is received. The following
NASHALT text is generated:
HALT AT LOC xxxxxx IN QLALOG: QLCLOT BIND INIT FAILURE.
The name of the routine (QLALOG) is not displayed
correctly and the failure reason is misleading.
It is a BIND initialization failure but not because
of callout but rather because of a timing problem.
2) ACTPU text in a NAS8110I message is being overlaid
when a NAS8141W INVALID REQ message is issued.
3A) Transmission of a large RU causes HNAS to build a
chain of X25 data packets connected by M (more data)
bits. Once transmission of an m-bit chain is started
the chain must be properly terminated. If HNAS
receives a NOTIFY POWER OFF during transmission of an
m-bit chain, the chain is not properly terminated and
other LUs on the remote PU will hang.
3B) When a HNAS QLLC PU activates HNAS sends an ACTLU PIU
to every LU defined for the PU. These PIU flow on
the LU-LU session. If activity occurs on the HNAS
to remote PU session (such as a NMVT request) a
situation can occur where HNAS is waiting for an
an ACTLU response before it sends the NMVT response
and the remote is waiting for an NMVT response before
sending an ACTLU response.
SOLUTIONS:
1) AUTOLOG timing problem corrected. Logic corrected so
that correct routine name displayed in NASHALT message.
2) NAS8110I message overlay problem corrected.
3A) Logic changed to ensure that m-bit chain is properly
terminated when a NOTIFY power of is received.
3B) HNAS scheduling logic revised to avoid the deadlock
during the ACTLU flood at session start.
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).
11-16-2004 - APAR 2300085 (was problem 2004286A)
APAR: 2300085
STATUS: CLOSED
OPEN_DATE: 10-12-2004
CLOSE_DATE: 11-16-2004
SERVICE(S): GATE
MANDATORY: RECOMMENDED
ORIGIN/REF: 230_RBG
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (OBJ) HNASOBJX and (SRC) HNASMACX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300085.ZIP file)
COREQ(S): N/A
PREREQ(S): Distribution dated after: 11-15-2004
With APAR: 2300083 and prerequisite chains.
SUPERSEDES: N/A
OBJECT(S): MCHNRQC , MCHTMR , VCCLEAR , XOTGTDC
SOURCE(S): VCD
PROBLEM: HNAS LU display shows bound GATE data LUs with no VC.
These LUs are not available for new sessions.
DESCRIPTION: When HNAS sends a a clear packet to a CTCP an UNBIND
is expected in response. If there is no UNBIND the
HNAS LU is 'lost' (unavailable for new calls).
SOLUTION: The following improvements have been made in GATE
session end processing:
1) When a clear is sent to the CTCP HNAS starts a
3 second timer. If the timer expires the LU is
released (PLU will receive a NOTIFY). The
diagnostic byte in the NAS3799I session end message
will be 221 (X'DD').
2) Some CTCPs send a final message after receiving a
clear packet from HNAS. This message is rejected
by HNAS since there is no session. The rejection
makes the CTCP think there is an error. With this
apar on the message is silently discarded. Tests
indicate that if HNAS sends the message to the
remote it will be silently discarded by the router.
3) If HNAS receives a clear to a VC that is already
clearing then the second clear is ignored. In
order to detect this session end error an alarm
message
NAS7713W SECOND CLEAR FROM ip-addr ON rmt-name
MCH mch-nm LU lu-nm
is issued to record the error. Additionally, the
session is ended with a diagnostic code of 222
(X'DE').
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).
11-15-2004 - APAR 2300084 (was Problem 2004208B)
APAR: 2300084
STATUS: CLOSED
OPEN_DATE: 07-26-2004
CLOSE_DATE: 11-15-2004
SERVICE(S): Modify PCNE/GATE/PAD SLU names
MANDATORY: OPTIONAL
ORIGIN/REF: 230_SDD
PTF_CLASS: ENHANCEMENT-APAR
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300084.ZIP file)
COREQ(S): 2300083 (APAR 2300083 must be applied first)
PREREQ(S): APAR 2300083 (and associated APARs PREREQ chains)
OBJECT(S): CONSDRMT, CONSHELP, CONSMLCL, CONSMRMT
MCHSVCI, MCHUT1, NASCNFG
SOURCE(S): N/A
PROBLEM: Customer requires the ability to modify SLU names in
(ENHANCEMENT) their PCNE, GATE and PAD CFT environment.
DESCRIPTION: Some users need the ability to add or modify SLU
names for LLC0 (PCNE), LLC4 (GATE) and/or LLC5 (PAD)
connections. Normally, SLU names for PCNE/GATE/PAD
resources are fixed by the configuration. This means
that HNAS must be stopped and restarted in order to
and or change a PCNE/GATE//PAD SLU name.
SOLUTION: The HNAS MRMT console command processor has been
modified to allow PCNE/GATE/PAD SLU names to be
added or changed for the SVC0=/SVC4=/SVC5= operands
on TYPE=MCH REMOTE's in a manner similar to what is
now done for the LUNAME= operand on a TYPE=SPU REMOTE.
The following HELP MRMT display illustrates the syntax
that is used for the enhanced MRMT SVC0=|SVC4=|SVC5=
console command processor:
{SVC0=sluname{={*|newname}}
/{*|{X}dd...dd||I{applid}
|dd...dd-dd...dd-dd...dd||O
|{X}dd...dd-{X}dd...ddd-{X}dd...dd||T{applid}}
/{*|mxtname}
/{*|cud}}
{SVC4=sluname{={*|newname}}}
{SVC5=sluname{={*|newname}}
/{*|{X}dd...dd||I{applid}
|dd...dd-dd...dd-dd...dd||O
|{X}dd...dd-{X}dd...ddd-{X}dd...dd||T{applid}}
/{*|mxtname}
/{*|cud}}
NOTE: enter * for dd...dd|applid|mxtname|cud|rcvcnt|
sndcnt to delete the value
* after sluname= to delete an existing
SLU entry
a newname after sluname= to change an
existing SLU name
the same sluname after sluname= to add a
new SLU name
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).
11-15-2004 - APAR 2300083 (was Problem 2004162B)
APAR: 2300083
STATUS: CLOSED
OPEN_DATE: 06-10-2004
CLOSE_DATE: 11-15-2004
SERVICE(S): PCNE/PAD Configuration Enhancement
MANDATORY: NO, new configurable feature.
ORIGIN/REF: 230_SDD
PTF_CLASS: ENHANCEMENT-APAR
PTF_TYPE: (SRC) HNASMACX and (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300083.ZIP file)
COREQ(S): 2300084 (APAR 2300083 must be applied first)
PREREQ(S): APAR 2300082 (and associated APARs PREREQ chains)
OBJECT(S): CNFGSVC0, CNFGSVC5, CONSDRMT, CONSHELP, CONSMRMT
MCHHRQ, MCHNRQC, MCHSVCI, VCCLRQ, VCDAT, XOTBXM
SOURCE(S): VTMUT1
PROBLEM: The SVC0= and SVC5= operands allow you to specify SLUs
(ENHANCEMENT) as callin (I) or callout (O) but not twoway (T).
DESCRIPTION: See problem/solution.
SOLUTION: The SVC0= and SVC5= operand logic has been modified
to accept a T value (for twoway) following the DTE
address so that the same SLU can be used for callin
and callout connections. When a T is detected, the
ACB for the SLU is opened so that it can be acquired
(bound). If an inbound call arrives before the SLU is
bound and the calling DTE address matches one of the
called DTE addresses associated with the SLU or the
CUD field contains an IDNUM value that matches one of
Xidum values associated with the SLU (there can be up
to 3 DTE addresses and/or Xidnum values specified for
a twoway SLU), the SLU will be allocated to the inbound
VC.
If a BIND arrives prior to an inbound call, the SLU
will be processed in the same fashion as an SLU defined
with the 'O' (for callout) option. In other words, if
the SLU is bound (acquired) before any inbound Call
Request is received, the DTE addresses in the list will
be used (successively) for outbound call attempts as
the called DTE address. Any Xidnum values in the list
will be skipped.
Example:
SVC0=(vclmt,
:
slunm/dteaddr1-Xidnum1-dteaddr2T01/mxtnm/cud,
| | | | || | |
| | | | || | |<-CUD
| | | | || | for OT
| | | | || | call
| | | | || |
| | | | || |<-MXT name
| | | | ||
| | | | ||<-APPLNAME index
| | | | |
| | | | |<- IT/OT SLU flag
| | | |
| | | |<- 2nd callin/callout DTE
| | |
| | |<- callin Xidnum
| |
| |<- 1st callin/callout DTE
|
|<- twoway SLU name
:
Sample: SVC0=(2,
SLU1/12345-12346-12347T//C0000000,
SLU2/23456-23457-X034560T//C0000000)
In the above sample, SLU1 and SLU2 are defined as
twoway SLUs. SLU1 has 3 called DTE addresses with
it while SLU2 has 2 DTE addresses and 1 Xidnum
value associated with it.
For callin, a calling DTE address of 12345, 12346 or
12347 will select SLU1 while a calling DTE address
of 23456 or 23457 will select SLU2. If no match is
made using the calling DTE address but the IDNUM value
in the CUD field (CUD byes 1 through 4) is 034560,
SLU2 will be allocated. If no DTE address or Xidnum
match is made, the call will be cleared.
For callout, a called DTE address of 12345, 12346 or
12347 will be used successively for SLU1 when it is
bound until a call is established. For SLU2, a called
DTE address of 23456 or 23457 will be used successively
when the SLU is bound until a call is established. For
both SLUs, an UNBIND is presented to the PLU if a call
cannot be established using any of the defined DTE
addresses.
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).
10-20-2004 - APAR 2300082
APAR: 2300082
STATUS: CLOSED
OPEN_DATE: 10-04-2004
CLOSE_DATE: 10-20-2004
SERVICE(S): CONSOLE SUBSYSTEM, MISCELLANEOUS ENHANCEMENTS
MANDATORY: NO, BUT RECOMMENDED
ORIGIN/REF: 230_JPM
PTF_CLASS: ENHANCEMENT-APAR
PTF_TYPE: (SRC) HNASMACX and (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300082.ZIP file)
COREQ(S): N/A
PREREQ(S): APAR 2300070 (and associated APARs PREREQ chains)
OBJECT(S): CONSDLU, CONSDVC, CONSHELP, NASCONS
SOURCE(S): XFBLK
PROBLEMS: 1) The PLU name is displayed by the DLU command even
when the PLU is no longer bound.
2) It is difficult to identify the router, MCH or SPU
that is associated with an SLU using the DLU command.
3) It is difficult to identify the router, MCH, SPU
or SLU that is associated with a VC using the DVC
command.
4) Console Subsystem error messages are not always
generated when conflicting parameters are entered.
DESCRIPTIONS: 1) When the SLU is unbound, HNAS remembers the PLU name
for the original connection. This residual name is
displayed in the PLUNAME column even though the SLU
is no longer connected to the PLU (it is IDLE).
2) Prior to this APAR, only the router name was
displayed for an SLU using the DLU command.
3) Prior to this APAR, only the SLU or SPU name was
displayed for an SLU using the DVC command. The
SLU name was displayed for a PCNE, GATE or PAD
connection while the SPU name was displayed for a
QLLC connection.
4) The DLU command did not report a parameter conflict
error when, for example, TYPE=QLLC was entered as a
command argument and RNM=mchname was provided as
command modifier. These are mutually exclusive
options since QLLC SLUs are not configured on a
TYPE=MCH REMOTE. They are identified in the LUNAME=
operand on a TYPE=SPU REMOTE.
SOLUTIONS: 1) The DLU command processor has been modified to
withhold displaying the PLU name if the SLU is
not bound. If you wish to see the last PLU that
the SLU was connected to, enter the SHOWUNBAPPL
argument.
2) The DLU command processor has been modified to
accept SHOWNAME=RTR (RTR=router, same as SHOWNAME
SHOWNAME with no follower), SHOWNAME=SPU and
SHOWNAME=MCH as arguments. The ADDRESS/NAME column
will then display the name of the resource type
you requested if one is associated with the SLU.
If the SLU does not have an associated resource
of the type you requested, the ADDRESS/NAME
column will be blank.
3) The DVC command processor has been modified to
accept SHOWNAME=SLU (same as SHOWNAME with no
follower), SHOWNAME=SPU, SHOWNAME=MCH and
SHOWNAME=RTR as arguments. The ADDRESS/NAME column
will then display the name of the resource type
you requested if one is associated with the SLU.
If the SLU does not have an associated resource
of the type you requested, the ADDRESS/NAME
column will be blank.
4) The DLU and DVC command processors have been
modified to test for conflicting parameters
and to issue an error message if detected.
For example, if:
RNM=spuname DLU TYPE=GATE
is specified, the following error message will
be generated:
NASC311E RNM=spuname TYPE=SPU INVALID, REQUIRED
or if:
RNM=mchname DLU TYPE=QLLC
is specified, the following error message will
be generated:
NASC311E RNM=mchname TYPE=MCH INVALID, REQUIRED
APPLY_INFO: See Chapter 6 (Product Maintenance Installation
section) from the HNAS Guide and Reference Manual
for instructions on how to install PTF's (Object,
Source and ZAPs) or Refresh/Upgrade maintenance.
Corrective logic included in distributions created
after CLOSE_DATE. Otherwise, apply maintenance as
directed in the APPLY_INFO (PTF).
10-18-2004 - APAR 2300081
APAR: 2300081
STATUS: CLOSED
OPEN_DATE: 10-13-2004
CLOSE_DATE: 10-18-2004
SERVICE(S): CONSOLE SUBSYSTEM
MANDATORY: YES
ORIGIN/REF: 230_CP
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (SRC) HNASMACX and (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300081.ZIP file)
COREQ(S): N/A
PREREQ(S): APAR 2300080, 2300069, 2300061, 2300045
(and associated APARs PREREQ chains)
OBJECT(S): CONSALRM, CONSDNAS, NASUTIL
SOURCE(S): XFNASWA
PROBLEM: Alarm messages are not routed to SYSCONS when APAR
2300080 is on system.
DESCRIPTION: See problem.
SOLUTION: Missing logic added so that alarm messages that
pass the ALRMFLTR= tests are processed for SHOWERR
and SHOWON.
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).
10-11-2004 - APAR 2300080
APAR: 2300080
STATUS: CLOSED
OPEN_DATE: 10-08-2004
CLOSE_DATE: 10-11-2004
SERVICE(S): CONSOLE SUBSYSTEM
MANDATORY: NO, BUT RECOMMENDED
ORIGIN/REF: 230_BNP,230_NBG
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300080.ZIP file)
COREQ(S): N/A
PREREQ(S): APAR 2300070 (and associated APARs PREREQ chains)
OBJECT(S): NASUTIL
SOURCE(S): N/A
PROBLEMS: 1) Information alarm messages are not filtered by the
ALRMFLTR= operand when SHOWERR is in effect.
2) PFXWTO CONS is required in addition to SHOWCONS so
that console output is routed back to NETVIEW.
DESCRIPTIONS: 1) The ALRMFLTR= operand is only processed for
informational alarm messages when SHOWON is active.
SHOWERR causes informational alarms to be inhibited
from SYSCONS but not from SYSPRINT. This is because
alarms are first filtered based on SHOWERR before
they are filtered via the ALRMFLTR= operand.
2) Console output should be routed back to NETVIEW
based on SHOWCONS only but PFXWTO CONS is currently
also required. NETVIEW routing should not be
dependent on whether each console output message
has a prefix. The prefix should be optional.
SOLUTIONS: 1) HNAS WTO interface logic has been modified to change
the order of alarm filtering. All alarm messages
will now be subject to ALRMFLTR= processing before
SHOWERR filtering. This ensures that informational
alarms identified in ALRMFLTR= will be processed
for the PURGE option (withheld from SYSCONS and
SYSPRINT) before they are processed for SHOWERR
(withheld from SYSCONS only).
2) HNAS WTO interface logic has been modified to
provide NETVIEW routing based solely on the
SHOWCONS option. Console output routed back to
NETVIEW may or may not be prefixed based on the
setting of the PFXWTO CONS option.
NOTE: The PFXWTO CONS option is only effective
if SHOWCONS is also in affect. If SHOWCONS
is not active, PFXWTO CONS is ignored. This
means that console output logged in SYSPRINT
will only contain a prefix if it is also
sent to SYSCONS, that is, SHOWCONS is active.
CIRCUMVENTION: Specify SHOWON and use the ALRMFLTR= operand to
filter informational alarms.
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).
10-07-2004 - APAR 2300079
APAR: 2300079 (was Problem 2004272A)
STATUS: CLOSED
OPEN_DATE: 09-28-2004
CLOSE_DATE: 10-07-2004
SERVICE(S): QLLC
MANDATORY: YES
ORIGIN/REF: 230_RWE
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (SRC) HNASMACX and (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300079.ZIP file)
COREQ(S): N/A
PREREQ(S): APAR 2300018 or distribution after April 16, 2004
SOURCE(S): VTMEXIT
OBJECT(S): MCHHL3RQ
PROBLEM: QLLC session hangs. PLU must reset the HNAS SLU for
operation to continue.
DESCRIPTION: An incorrect PIU is built by HNAS when a SIGNAL is
received from the PLU. Use of SIGNAL by the PLU is
unusual.
In addition when the incorrect PIU is built the LU's
state is incorrectly modified.
SOLUTION: HNAS modified to correctly process a PLU SIGNAL
request.
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).
10-06-2004 - APAR 2300078
APAR: 2300078
STATUS: CLOSED
OPEN_DATE: 10-06-2004
CLOSE_DATE: 10-06-2004
SERVICE(S): QLLC
MANDATORY: YES
ORIGIN/REF: 230_RWE
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300078.ZIP file)
COREQ(S): N/A
PREREQ(S): N/A
OBJECT(S): MCHLUIN
SOURCE(S): N/A
PROBLEM: User 198 ABEND with the following message:
HALT AT LOC 8xxxxxxx IN MCHLUIN : LUSVMSG INVALID
DESCRIPTION: When sending a null QLLC PIU to the PLU the internal
send completion routine is not set correctly. When
the wrong completion routine is used the LU control
gets in an invalid state (send complete, buffer not
released). This problem requires an unusual QLLC
event sequence.
SOLUTION: Set the correct completion routine when processing
the null QLLC PIU.
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).
10-06-2004 - APAR 2300077
APAR: 2300077
STATUS: CLOSED
OPEN_DATE: 08-31-2004
CLOSE_DATE: 10-06-2004
SERVICE(S): GENERAL CLEANUP/MINOR FIXES:
CDF PROCESSING - PVC= and TRCLMT=.
MANDATORY: NO, BUT RECOMMENDED
ORIGIN/REF: 230_SAM, 230_BNP
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300077.ZIP file)
COREQ(S): N/A
PREREQ(S): N/A
OBJECT(S): CNFGPVC, CNFGTRLM
SOURCE(S): N/A
PROBLEMS: 1) Omitted PVC= operand on a TYPE=MCH REMOTE definition
statement causes NAS1301W warning message.
2) TRCLMT= operand value on BUILD definition statement
is limited to 32767.
DESCRIPTIONS: See problems above.
SOLUTIONS: 1) The configuration processor has been modified to
set PVC=NONE as the default when the PVC= operand is
omitted. A NAS1301D message will now be produced.
2) The configuration processor has been modified to
allow a maximum TRCLMT= value of 1048575 so that
very large traces can be accommodated.
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).
10-05-2004 - APAR 2300076
APAR: 2300076
STATUS: CLOSED
OPEN_DATE: 10-04-2004
CLOSE_DATE: 10-04-2004
SERVICE(S): QLLC
MANDATORY: YES
ORIGIN/REF: 230_NBG
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300076.ZIP file)
COREQ(S): N/A
PREREQ(S): APAR 2300041 or distributions after June 6, 2004.
OBJECT(S): MCHRL3RR
SOURCE(S): N/A
PROBLEM: QLLC session receives the following alert message:
NAS7601W MCH Q11N LU RMT8601 DECODE RC=0C
TH/RH=2C000102 80000091 00358400 E70000C5
Subsequent input messages generate similar alarms.
DESCRIPTION: This error message indicates that HNAS is receiving
a QLLC PIU with an invalid sequence number. The
sequence number (X'8000') is valid although HNAS
processes the number incorrectly.
SOLUTION: Sequence number compare logic boundary condition
corrected.
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).
09-30-2004 - APAR 2300075
APAR: 2300075
STATUS: CLOSED
OPEN_DATE: 09-29-2004
CLOSE_DATE: 09-30-2004
SERVICE(S): GENERAL CLEANUP/MINOR FIXES:
QLLC SYSL= CDF PROCESSING FOR TYPE=SPU REMOTE
MANDATORY: NO, BUT RECOMMENDED
ORIGIN/REF: 230_RWE
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300075.ZIP file)
COREQ(S): N/A
PREREQ(S): APAR 2300019
OBJECT(S): CNFGSYSL
SOURCE(S): N/A
PROBLEM: NAS1301D REMOTE SYSL OMITTED, MCHSOL ASSUMED
configuration warning message is generated when
the SYSL= operand is omitted even though all
SLUs in the LUNAME= operand have an associated
applid value (APPLNAME= index).
DESCRIPTION: This warning condition occurs when an LOCADDR entry
in the LUNAME= operand is skipped. For example:
LUNAME=(,sluname2///m,sluname3///n). It will not
occur if all LOCADDR entries are specified and all
specified SLU names have applid values. For example:
LUNAME=(sluname1///i,sluname2///m,sluname3///n).
SOLUTION: The HNAS configuration process has been modified to
ignore missing LOCADDR entries and only test for an
applid value when an SLU name is provided. If the
SYSL= operand is omitted or MCHSOL is not specified
but all specified SLU entries have an applid value,
the NAS1301D message is inhibited. Conversely, if the
SYSL= operand is omitted or MCHSOL is not specified
and any specified SLU entry does not have an applid
value, the NAS1301D message is generated.
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).
09-22-2004 - APAR 2300074
APAR: 2300074 (was unpublished Problem 2004265B)
STATUS: CLOSED
OPEN_DATE: 09-21-2004
CLOSE_DATE: 09-22-2004
SERVICE(S): GATE
MANDATORY: YES, if GATE resources are used
ORIGIN/REF: 230_CMF
CP_TECH: PRT
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars
(Complete FIX is contained in the 2300074.zip file)
COREQ(S): N/A
PREREQ(S): Distribution dated after: 07-29-2004
With APAR: 2300061 and associated prereqs.
SUPERSEDES: N/A
OBJECT(S): VCCLRQ
SOURCE(S): N/A
PROBLEM: GATE resource in conjunction with STRIPRTEIN can
cause 0C4 ABEND or Clear DIAG=138 (8A) when callin
session starts.
DESCRIPTION: When a GATE FC session is started with the STRIPRTEIN
option and CONNECT=CUD0 specified the above ABEND or
clear can occur because of errors in STRIPRTEIN and
CONNECT=CUD0 processing.
SOLUTION: Call request packet processor logic corrected.
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).
09-21-2004 - APAR 2300073
APAR: 2300073 (was unpublished Problem 2004265A)
STATUS: CLOSED
OPEN_DATE: 09-21-2004
CLOSE_DATE: 09-21-2004
SERVICE(S): QLLC - CONFIGURATION
MANDATORY: YES, if QLLC resources are used
ORIGIN/REF: 230_CIN
CP_TECH: SFD
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars
(Complete FIX is contained in the 2300073.zip file)
COREQ(S): N/A
PREREQ(S): APAR 2300004
SUPERSEDES: N/A
OBJECT(S): MCHINI
SOURCE(S): N/A
PROBLEM: NASHALT 0198 ABEND can occur immediately after HNAS
is started when a new MCH definition is added to the
CDF. This problem does not occur during a FASTRUN
execution.
DESCRIPTION: Customer reports that after they added a new MCH to
their existing CDF, a NASHALT occurred in module
MCHUT2 with the following reason:
HALT AT LOC 8005621E IN MCHGETMN: MCH STORAGE BLOCK
EXHAUSTED
The problem occurs because of an error in the
computation of the SLU count for all QLLC SLUs in
the CDF. The amount of memory reserved for SLU
and VC control blocks is padded to a 1-megabyte
boundary. Normally, the padding provides enough
space so that the QLLC SLU count error is not a
factor. However, when the pad is too small, the
addition of any other SLU resources, be that from
an MCH or SPU, will cause the ABEND.
SOLUTION: HNAS has been modified to properly compute the
SLU count for QLLC resources. This guarantees
that there will always be enough memory allocated
for all SLU and VC control blocks.
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).
09-21-2004 - APAR 2300072
APAR: 2300072 (was Problem 2004243A)
STATUS: CLOSED
OPEN_DATE: 09-10-2004
CLOSE_DATE: 09-21-2004
SERVICE(S): All - IDLE timer processing
MANDATORY: YES, when IDLETO=1 used
NO, but recommended when IDLETO=xx used
ORIGIN/REF: 230_SWC
CP_TECH: PRT
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars
(Complete FIX is contained in the 2300072.zip file)
COREQ(S): N/A
PREREQ(S): N/A
SUPERSEDES: N/A
OBJECT(S): MCHTMR
SOURCE(S): N/A
PROBLEM: Value specified by IDLETO= parameter not processed
correctly. Sessions prematurely cleared with DIAG=198
(X'C6'). Clears with DIAG=130 occurred as a result of
the premature inactivity timeouts.
DESCRIPTION: An incorrect instruction in timer code causes an
IDLETO=1 to be processed as an interval in the range
0 to 1 minute. The correct interval is the range 1
to 2 minutes.
SOLUTION: HNAS modified to properly process the IDLETO interval.
As part of this APAR, the timer processor (MCHTMR)
has been modified to monitor the system for active
VC control blocks that have no LU or PCE attachments
(these control blocks control VTAM and TCP/IP
operations). Such a VC is effectively lost to the
system. When one is found it is released and the
following alarm is issued:
NAS5999W SCHEDULING RELEASE FOR VC, MCH=mch-name
PREV LU=lu-name
The message indicates that a problem has occurred.
If you are receiving this alarm, please contact
your HNAS support services representative.
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).
09-11-2004 - APAR 2300071
APAR: 2300071
STATUS: CLOSED
OPEN_DATE: 09-09-2004
CLOSE_DATE: 09-11-2004
SERVICE(S): CONFIGURATION, TAP PROCESSING
MANDATORY: NO, BUT RECOMMENDED WHEN OPTIONS=TAPWITHCLR IS USED
ORIGIN/REF: 230_SDD
CP_TECH: SFD
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars
(Complete FIX is contained in the 2300071.ZIP file)
COREQ(S): N/A
PREREQ(S): N/A
SUPERSEDES: N/A
OBJECT(S): CNFGCUD, CNFGDCAD, CNFGDTAD, CNFGFAC
SOURCE(S): N/A
PROBLEM: Configuration warning messages are generated when
TAP=value and OPTIONS=TAPWITHCLR are specified but
CUD=, DCEADDR=, DTEADDR= and/or FAC= are omitted.
DESCRIPTION: TAP=value enables 'Keep Alive' processing for
a TYPE=XOT REMOTE definition statement but
OPTIONS=TAPWITHCLR specifies that a Clear Request
packet rather than a Call Request packet should be
used as the TAP request. In this case, the CUD=,
DCEADDR=, DTEADDR= and/or FAC= operands are not
required and yet the following configuration
warning messages are generated:
NAS1301D REMOTE CUD OMITTED, 01000000C8D5C1E2E3C1D7
ASSUMED
NAS1301W REMOTE DCEADDR OMITTED, NO CALLING DTE ADDRESS
WILL BE USED FOR TAPPING
NAS1301W REMOTE DTEADDR OMITTED, NO CALLED DTE ADDRESS
WILL BE USED FOR TAPPING
NAS1301W REMOTE FAC OMITTED, NO FACILITIES
WILL BE USED TAPPING
SOLUTION: The HNAS configuration process has been modified to
ignore the missing (optional) TAPWITHCLR CUD=,
DCEADDR=, DTEADDR= and/or FAC= operands. This will
prevent the configuration warning messages from being
generated.
We do recommend that users code these values to fine
tune tapping control between HNAS and the router.
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).
09-10-2004 - APAR 2300070
APAR: 2300070 (was Problem_ID 2004196B)
STATUS: CLOSED
OPEN_DATE: 07-14-2004
CLOSE_DATE: 09-10-2004
SERVICE(S): CART= and CONSNAME= NETVIEW/NCCF/Session_Manager Support
MANDATORY: YES if HNAS console commands issued via NETVIEW/NCCF/SM
ORIGIN/REF: 230_RBS,FDK(RWG),NBG
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (SRC) HNASMACX and (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300070.ZIP file)
COREQ(S): N/A
PREREQ(S): Distribution dated after: 08-18-2004
with APAR 2300068 (and its prereqs)
SUPERSEDES: N/A
OBJECT(S): NASCONS, NASUTIL
SOURCE(S): XFBLK
PROBLEM: HNAS console subsystem command output is not routed back
to command initiator session window.
DESCRIPTION: Output from HNAS console commands are not routed back
to the requesting console when commands are PIPEd from
NETVIEW or issued via MODIFY (MVS F) from NETVIEW.
SOLUTION: The HNAS WTO interface logic has been modified to issue
the MF=E form WTO for synchronous console command output
with CART=PCECART and CONSNAME=PCECNNM where PCECART
comes from the CIBXCART field and PCECNNM comes from
the CIBXCNNM field of the Command Input Buffer.
This allows console output to be routed back to the
requesting console regardless of whether the command
was issued using a MODIFY request or was PIPEd to HNAS.
Note: The SHOWCONS option must be set in order for
console WTOs to be routed. If this option is
not set, console command output is only logged
in SYSPRINT.
The CONSNAME=cibxcnnm-value parameter support
is new as of this APAR.
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).
08-30-2004 - APAR 2300069
APAR: 2300069
STATUS: CLOSED
OPEN_DATE: 08-27-2004
CLOSE_DATE: 08-30-2004
SERVICE(S): Custom Product Distribution Support (Non-SMP/E)
MANDATORY: N/A
ORIGIN/REF: 230_CP
PTF_CLASS: ENHANCEMENT-APAR
PTF_TYPE: (SRC) HNASMACX and (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300069.ZIP file)
COREQ(S): N/A
PREREQ(S): Distribution dated after: 08-16-2004
with APAR 2300065
SUPERSEDES: N/A
OBJECT(S): CONSDNAS, NASEND
SOURCE(S): XFCSTDEF
PROBLEM: When a standard or enhancement non-SMP/E APAR is applied
(ENHANCEMENT) against an HNAS product distribution, it is unwittingly
possible to overlay a macro and/or object member that
contains custom user modifications.
DESCRIPTION: Prior to this APAR, custom macros were placed in the
product distribution MACLIB (HNASMAC) and custom object
members were placed in the product distribution OBJLIB
(HNASOBJ). The extension MACLIB (HNASMACX) and the
extension OBJLIB (HNASOBJX) were used solely for user
applied maintenance, holding macros and object members
that were installed via APAR. As a result, if an APAR
replaces a custom macro and/or object member the APARed
macro and/or object member in the corresponding
extension library will override the custom macro and/or
object member in the product distribution libraries.
This means that the custom modification will have been
nullified, a fact that the customer may not realize.
SOLUTION: Starting with this APAR, custom macros will be placed
in the extension MACLIB (HNASMACX) and custom object
members will be placed in the extension OBJLIB
(HNASOBJX) during the customers product distribution
process, as required. If maintenance is about to be
applied that will overlay a macro and/or object member
of the same name in the extension libraries, it should
be treated as a 'red flag' to remind the customer
that a conflict may exist which could cause a custom
modification to 'fall off'. In this case, the
customer should contact Comm-Pro before applying the
maintenance. This will allow Comm-Pro to recreate the
custom macro and/or object member with the APAR fix
included which can then be transmitted to the customer
via email attachment or FTP download.
Note that the majority of customers don't have custom
enhancements (CustomUserMods) although this enhancement
APAR was developed to improve their support services.
Additionally, the HNAS distribution process has been
modified to generate an 'APARID' of HNASMACX and/or
HNASOBJX if a custom MACLIB and/or OBJLIB has been
included in the distribution. These APARIDs are
contained in the NASEND module and will be displayed
in the HNAS SYSPRINT when the DMAP APAR console command
is executed when HNAS is started. These APARIDs will
also display whenever the DNAS APAR console command is
executed. These APARIDs are intended to provide an
additional reminder that custom modifications are on
the HNAS system and, hence, caution should be exercised
when applying maintenance.
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).
08-18-2004 - APAR 2300068
APAR: 2300068
STATUS: CLOSED
OPEN_DATE: 08-13-2004
CLOSE_DATE: 08-18-2004
SERVICE(S): Console Subsystem Access
MANDATORY: N/A
ORIGIN/REF: 230_CP
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300068.ZIP file)
COREQ(S): N/A
PREREQ(S): Distribution dated after: 08-02-2004
with APAR 2300062
SUPERSEDES: N/A
OBJECT(S): NASCONS
SOURCE(S): N/A
PROBLEM: Console commands are rejected when HNAS initialization
does not complete.
DESCRIPTION: Normally, HNAS initialization process completes and the
following message is generated:
NAS0001I HOST NAS INITIALIZATION COMPLETE,
ALL FUNCTIONS READY
This message is deferred if HNAS is unable to complete
all server initialization. Server initialization
involves binding the LOCAL IP addresses to the stack.
When a BIND failure occurs, the following message is
generated:
NAS2231W SERVER=010.117.056.170(01998) SOCKID=0000
PCEID=0007 NAME=LXOT
NAS2231W BIND REQUEST FAILED, RC=00000000 00000000
BIND retry logic is controlled via the RETRYLMT= and
DELAYTIME= suboperands of the INIT= operand on the
LOCAL definition statement. During the delay/retry
processing, the NAS0001I 'INITIALIZATION COMPLETE'
continues to be withheld. It is during this period
that console requests are rejected. The reason for
this is that the console reply buffer is not being
reinitialized so that subsequent console input
overlays, but does not replace prior console input.
Problem introduced with Enhancement APAR 2300004.
SOLUTION: The console subsystem has been modified to ensure that
the console reply buffer is initialized at all times
after each input is processed.
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).
08-16-2004 - APAR 2300067
APAR: 2300067 (was Problem_ID 2004228A)
STATUS: CLOSED
OPEN_DATE: 08-15-2004
CLOSE_DATE: 08-16-2004
SERVICE(S): NASAUTH Authorization File Validation
MANDATORY: NO
ORIGIN/REF: 230_NBG
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (SRC) HNASMACX and (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300067.ZIP file)
COREQ(S): N/A
PREREQ(S): Distribution dated after: 06-24-2004
with APAR 2300049
SUPERSEDES: N/A
OBJECT(S): NASUTIL
SOURCE(S): HALT
PROBLEM: Descriptive WTO message not provided when NASAUTH
Authorization failure occurs (ABEND 198 'AC FAILURE)
due to customer coding error (//AUTH DD statement).
DESCRIPTION: When a bad NASAUTH file is supplied, HNAS will ABEND
at startup time with NASHALT 198 'AC FAILURE' but
it is not always easy to tell why the NASAUTH file
is bad. HNAS issues a WTO before the NASHALT to
identify the reason for the failure but sometimes
the WTO can be purged by the system during the ABEND
processing. This appears to be timing related.
SOLUTION: Instead of a 'catchall' ABEND reason for the NASHALT,
a specific description will be provided in addition
to the WTO which may or may not be displayed. The
WTO text will also be used as the NASHALT description.
This will make it easy to tell why the failure occurred
in the event the WTO is purged during ABEND processing.
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).
08-16-2004 - APAR 2300066
APAR: 2300066
STATUS: CLOSED
OPEN_DATE: 08-15-2004
CLOSE_DATE: 08-15-2004
SERVICE(S): MLCL console command
MANDATORY: Required if MLCL INIT= used.
ORIGIN/REF: 230_CPT
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300066.ZIP file)
COREQ(S): N/A
PREREQ(S): Distribution dated after: 08-10-2004
with APARs 2300063
SUPERSEDES: N/A
OBJECT(S): CONSMLCL
SOURCE(S): N/A
PROBLEM: MLCL INIT=DELAYTIME=0|RETRYLMT=0 is rejected.
DESCRIPTION: An error in the convert logic for the DELAYTIME= and
RETRYLMT= suboperands of the INIT= operand causes the
command to be rejected if a zero (0) value is specified.
SOLUTION: The MLCL command has been modified to correct the zero
convert logic.
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).
08-16-2004 - APAR 2300065
APAR: 2300065
STATUS: CLOSED
OPEN_DATE: 08-13-2004
CLOSE_DATE: 08-13-2004
SERVICE(S): DNAS console command
MANDATORY: Required if APAR 2300062 is on
ORIGIN/REF: 230_CPT
PTF_CLASS: STANDARD-APAR and ENHANCEMENT-APAR
PTF_TYPE: (SRC) HNASMACX and (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300065.ZIP file)
COREQ(S): N/A
PREREQ(S): Distribution dated after: 08-02-2004
with APARs 2300062, 2300019
SUPERSEDES: N/A
OBJECT(S): CONSDNAS, CONSHELP
SOURCE(S): XFBLK, XFGBLS, XFIDR
PROBLEM1: You cannot easily determine if custom modifications
(ENHANCEMENT) (USERMODS) are on the HNAS system.
PROBLEM2: Some remote console DNAS APAR display output is routed
(FIX) to the local console (SYSCONS) rather than to the
remote console that solicited the output.
DESCRIPTION: See problems.
SOLUTION1: The DNAS console command processor has been modified to
accept USERMODS as a command argument. When specified,
DNAS will only search for non-maintenance APAR IDs, that
is, APAR IDs that do not start with vrm (e.g., 230).
If no custom modifications or problem fixes are found,
'NO USERMODS PRESENT' will be displayed.
Note: Prior to this change, you could use the DMAP APAR
or DNAS APAR command to display all APAR IDs on
the system then manually look for custom or
problem APAR IDs like P04212A or USER001. The
DNAS USERMODS command restricts the display to
custom modification and problem fix IDs only.
SOLUTION2: The XFWTO calls that caused remote output to be routed
to local console was do to missing comma that indicated
a continuation card. This has been fixed.
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).
08-11-2004 - APAR 2300064
APAR: 2300064
STATUS: CLOSED
OPEN_DATE: 08-10-2004
CLOSE_DATE: 08-11-2004
SERVICE(S): MRMT (LUNAME) console command enhancement
MANDATORY: YES, when MRMT is employed
ORIGIN/REF: 230_CP
CP_TECH: SFD
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnasproblem/
(Complete FIX is contained in the 2300064.ZIP file)
COREQ(S): N/A
PREREQ(S): APAR 2300060
(and associated APARs PREREQ chains)
SUPERSEDES: N/A
OBJECT(S): CONSMRMT
SOURCE(S): N/A
PROBLEM: ABEND 0C4-10 or ABEND 198 (NASHALT INV LU-2) can result
if the MRMT console command is used to add a new SLU to
the LUNAME= operand for a TYPE=SPU REMOTE definition
statement.
DESCRIPTION: When the MRMT command is used to add an entry in the
LUNAME= operand list without an associated MXT, an
ABEND 0C4-10 occurs because the MXT address is left
uninitialized in the LUNAME= list. The result is that
an MXT address of X'40404040' is erroneously used.
If a new SLU is added with an associated MXT so that
the MXT address is resolved in the LUNAME= list, an
ABEND 198 can occur if the SPU is also configured for
timer initiated callout (OPTIONS=CLOTINITYP=TIMER).
This occurs because the MCH pointer in the LU control
block (LUB) is left uninitialized. If a Clear is
received, the VTMCLOA routine is called for the SLU.
This routine issues the NASHALT INV LU-2 because it
finds the 'bad' MCH pointer. Normally, the MCH
pointer is initialized after the XID exchange has
completed.
SOLUTION: The MRMT command has been modified to set the MXT
address to zero (0) when an MXT name is not provided.
A zero address is treated as no MXT.
Logic has also been added to initialize the MCH
pointer in the LUB when the SLU is allocated by
the MRMT command. This will satisfy the validity
check in VTMCLOA and prevent the ABEND 198.
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).
08-10-2004 - APAR 2300063
APAR: 2300063
STATUS: CLOSED
OPEN_DATE: 08-10-2004
CLOSE_DATE: 08-10-2004
SERVICE(S): MLCL (RTEIN/RTEOUT) console command enhancement
MANDATORY: YES, when MLCL is employed
ORIGIN/REF: 230_CP
CP_TECH: SFD
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnasproblem/
(Complete FIX is contained in the 2300063.ZIP file)
COREQ(S): N/A
PREREQ(S): APAR 2300056
(and associated APARs PREREQ chains)
SUPERSEDES: N/A
OBJECT(S): CONSMLCL
SOURCE(S): N/A
PROBLEM: ABEND 0C4-10 can result if MLCL command is used to
delete an RTEIN= or RTEOUT= operand entry.
DESCRIPTION: When the MLCL command is used to delete an entry in
RTEIN= or RTEOUT= operand list, the corresponding
array is compressed. The ABEND occurs because the
array count is being corrupted during the compression
step. This occurs because the source and target
address for the compress are off by 2 (the array count
size). This was discovered when the first entry of
the RTEIN= array was deleted via MLCL RTEIN=1,* and
the array had multiple elements. The ABEND will not
occur if the corresponding array has only one element
or if the entry being deleted is not the first.
SOLUTION: The MLCL command has been modified to take the array
count into consideration before the compress is
performed.
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).
08-02-2004 - APAR 2300062
APAR: 2300062
STATUS: CLOSED
OPEN_DATE: 07-28-2004
CLOSE_DATE: 08-02-2004
SERVICE(S): Console Subsystem - DNAS enhancement
MANDATORY: OPTIONAL
ORIGIN/REF: 230_CPT
PTF_CLASS: ENHANCEMENT-APAR
PTF_TYPE: (SRC) HNASMACX and (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300062.ZIP file)
COREQ(S): N/A
PREREQ(S): Distribution dated after: 07-28-2004
with APARs 2300061, 2300060, 2300047, 2300004
SUPERSEDES: N/A
OBJECT(S): CONSDNAS, CONSHELP, NASCONS, NASEND
SOURCE(S): XFBLK
PROBLEM: The DNAS command displays the highest APAR ID at the
(ENHANCEMENT) time the distribution was created as well as the APAR
ID for the most recent maintenance applied at the
customer site but the latter does not identify any
missing maintenance.
DESCRIPTION: See problem.
SOLUTION: The DNAS command processor has been modified to
display all missing maintenance if the distribution
APAR ID is different than the most recent APAR ID.
This missing maintenance is only displayed if the
DNAS command is entered by itself, that is, without
the APAR argument. The missing maintenance is
displayed after the standard DNAS output. For example:
APARID MODULE (MISSING MAINTENANCE)
230xxxx MISSING
230yyyy MISSING
:
If the distribution APAR ID is different than the most
recent APAR ID but no maintenance is missing, the
display will look as follows:
APARID MODULE (MISSING MAINTENANCE)
NOTHING MISSING
Note also that the DNAS APAR command has been extended
to accept an APAR ID follower so that only that APAR ID
is displayed.
Example: DNAS APAR 2300062
If the specified APAR ID is not found, the following
error response is returned:
NASC101E SEARCH ARGUMENT NOT FOUND, REQUIRED
The DNAS APAR header display has also been changed
as follows:
APARID MODULE (APPLIED MAINTENANCE)
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).
07-29-2004 - APAR 2300061
APAR: 2300061 (was Problem_ID 2004209A-not-published)
STATUS: CLOSED
OPEN_DATE: 07-28-2004
CLOSE_DATE: 07-29-2004
SERVICE(S): Configuration - Remote Console Access
MANDATORY: OPTIONAL
ORIGIN/REF: 230_IZB/230_CPT
PTF_CLASS: ENHANCEMENT-APAR
PTF_TYPE: (SRC) HNASMACX and (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300061.ZIP file)
COREQ(S): N/A
PREREQ(S): Distribution dated after: 07-23-2004
with APARs 2300060, 2300058, 2300056, 2300045
SUPERSEDES: N/A
OBJECT(S): CNFGCNLM, CNFGCNPW, CONSRCON, NASCNFG, NASCONS,
VCCLRQ, VCDAT
SOURCE(S): VCDD, XFNASWA, XFXTRN
PROBLEM: Users unable disable remote console in CDF although
(ENHANCEMENT) execution start parameter does. Eliminate NAS1101W
message for those that prefer not to define remote
console in the CDF.
DESCRIPTION: Remote console access can be suppressed when the
CONPSWD= operand is omitted but this will also
generate the following error message.
NAS1999W
NAS1101W BUILD CONPSWD OMITTED,
REMOTE CONSOLE ACCESS WILL NOT BE ALLOWED
SOLUTION: Allow CONLMT=0 to be specified on BUILD definition
statement so that the remote console access is
blocked and the NAS1101W message is suppressed.
MORE INFO: The following trace message is generated when a
remote console connect attempt is rejected:
mchname VC yyyyyyyy ******** LU ******** CLEARED BY
VCNMCLRQ CAUSE/DIAG=0082 DIAGX=xxxx LCST=P3
Where: mchname is the target MCH for the remote call.
yyyyyyyy is the VC control block address.
0082 is the clear cause/diagnostic codes.
xxxx is the clear extended diagnostic code.
0014 => all remote console buffers allocated.
0015 => CONLMT=0 or RMTCONS|RMTCONP not set.
0016 => CONPSWD= not configured for rmt access.
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).
07-26-2004 - APAR 2300060
APAR: 2300060 (was Problem_ID 2004201A)
STATUS: CLOSED
OPEN_DATE: 07-19-2004
CLOSE_DATE: 07-26-2004
SERVICE(S): LLC0 & LLC5
MANDATORY: NO, OPTIONAL
ORIGIN/REF: 230_BNP
PTF_CLASS: ENHANCEMENT-APAR
PTF_TYPE: (SRC) HNASMACX and (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300060.ZIP file)
COREQ(S): N/A
PREREQ(S): Distribution dated after: 07-23-2004
with APARs 2300039, 2300052, 2300056, 2300057, 2300059
SUPERSEDES: N/A
OBJECT(S): CNFGOPTS, CONSDRMT, CONSMRMT, CONSHELP, VCCLRQ
SOURCE(S): VCDD, XFNASWA
PROBLEM: Users lack control of Call Accept logic for LLC0 and
LLC5 sessions using a CTCP (as is done with DATE).
DESCRIPTION With DATE, a CTCP processes call request packets. If
the CTCP in not active, the inbound call is cleared
immediately (a Call Accept is not sent). There is a
Transpac option that will, under these circumstances,
retry the call using different addresses. This
allows the session to be switched to a different MCH.
HNAS does not currently support DATE. When an LLC0
or LLC5 call arrives a Call Accept will be sent by
HNAS if a USSTAB or LOGTAB process is used (MCHSOL)
or if a session is started with a PLU (applindex
coded on SVC0= or SVC5= operand). This means that
the Transpac call retry option cannot be used.
SOLUTION: Two options have been created for TYPE=MCH REMOTEs
to optionally enable this processing:
OPTIONS=LLC0CTCPCHK and OPTIONS=LLC5CTCPCHK
When an LLC0 or LLC5 call is received and the
LLC0CTCPCHK or LLC5CTCPCHK option is set, HNAS will
look at the first GATE CTCP SLU in the LUNAME= list.
If this CTCP SLU is not bound, the new call is
cleared with a diagnostic of 254 (X'FE'). If the
CTCP is bound, call request processing is performed
as usual.
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).
07-23-2004 - APAR 2300059
APAR: 2300059 (was Problem_ID 2004198A)
STATUS: CLOSED
OPEN_DATE: 07-16-2004
REVISE_DATE: N/A
CLOSE_DATE: 07-23-2004
SERVICE(S): GATE Fast Connect
MANDATORY: YES if OPTIONS=LCN0USED|RESIDSTART=value is required
ORIGIN/REF: 230_CMF,230_CPT
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnasproblem/
(Complete FIX is contained in the 2300059.ZIP file)
COREQ(S): N/A
PREREQ(S): 2300052
SUPERSEDES: N/A
OBJECT(S): CNFGOPTS, MCHFCI
SOURCE(S): N/A
PROBLEM: Configuration error messages can be generated for
a GATE FC MCH when certain options are specified.
DESCRIPTION: Error messages:
NAS1311W REMOTE OPTIONS=LCN0USED REQUIRES SVC4=
RESOURCES, IGNORED
NAS1311W REMOTE OPTIONS=RESIDSTART REQUIRES SVC4=
RESOURCES, IGNORED
are issued when an MCH is configured for GATE Fast
Connect (FC) resources and OPTIONS=LCN0USED and/or
OPTIONS=RESIDSTART=value are also specified.
Additionally, the RESIDs generated for GATE FC data
session LUs do not start at zero when LCN0USED is
specified.
SOLUTION: HNAS has been modified to allow the OPTIONS=LCN0USED
and OPTIONS=RESIDSTART=value for a GATE FC MCH.
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).
07-21-2004 - APAR 2300058
APAR: 2300058
STATUS: CLOSED
OPEN_DATE: 07-21-2004
REVISE_DATE: N/A
CLOSE_DATE: 07-21-2004
SERVICE(S): CONSOLE Decode Correction
MANDATORY: N/A
ORIGIN/REF: 230_CP
PTF_CLASS: STANDARD-APAR (bug fix)
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnasproblem/
(Complete FIX is contained in the 2300058.ZIP file)
COREQ(S): N/A
PREREQ(S): 2300045
SUPERSEDES: N/A
OBJECT(S): NASCONS
SOURCE(S): N/A
PROBLEM: Some commands like DLCL and DRMT will be rejected
if a null modifier override (LNM= for DLCL or RNM=
for DRMT) is entered on the right side of the command.
DESCRIPTION: When a null modifier override is entered on right side
of a command (for example: LNM=lclname DLCL LNM=),
console parsing logic steps over all blank characters
until it reaches the end of the input area. When
control is passed to a console command processor,
many of the command processors will do another decode
to determine what command specific arguments were
entered. In the case of DLCL and DRMT, when the LNM=
or RNM= modifier overrides are entered (which will
temporarily reset the active LOCAL or REMOTE names
respectively), the command processors are supposed
to display a list of the LOCAL or REMOTE definitions
in the CDF. However, because a validity check is
performed to ensure that no command argument is
present when the LNM= or RNM= modifier is not set,
the command is rejected and the following message is
generated: NASC522E INPUT DATA INVALID, REQUIRED .
The reason that this occurs is because the input
parsing pointer winds up beyond the input area and
thus does not point at a blank character which the
commands require.
SOLUTION: The HNAS console command decoder has been modified
to detect when the input parsing area is beyond
the input area and if so, back it up to the last
character position which is then set to a blank
character. This will ensure that all console
command processors 'see' at least one blank
character within the input area and thus prevent
commands like DLCL and DRMT from being rejected
when LNM= and RNM= are 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).
07-21-2004 - APAR 2300057
APAR: 2300057 (was Problem_ID 2004154A)
STATUS: CLOSED
OPEN_DATE: 06-02-2004
REVISE_DATE: N/A
CLOSE_DATE: 07-21-2004 (tested in-house)
SERVICE(S): QLLC Configuration Enhancement
MANDATORY: N/A
ORIGIN/REF: 230_AMA
PTF_CLASS: ENHANCEMENT-APAR
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnasproblem/
(Complete FIX is contained in the 2300057.ZIP file)
COREQ(S): N/A
PREREQ(S): 2300035, 2300052
SUPERSEDES: N/A
OBJECT(S): CNFGSVC3, CONSDRMT
SOURCE(S): N/A
PROBLEM: SVC3=1 is required when MCH supports QLLC resources
(ENHANCEMENT) even when SPU allocation is exclusively by IDBLK/IDNUM
and not DTE address.
DESCRIPTION: A vclmt value is required in the SVC3= operand (first
suboperand) even if no SPU names are specified. The
MCH will not allow QLLC connections unless an LLC3
vclmt value is given. This can be confusing when SPU
allocation is done using IDBLK/IDNUM match only. Any
MCH defined for QLLC support can access any SPU in the
CDF.
SOLUTION: Rather than requiring that SVC3=1 be specified to mark
the MCH for QLLC support, option SVC3=ALLOW will now
be accepted. This new keyword indicates that the MCH
allows any number of QLLC connections.
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).
07-20-2004 - APAR 2300056
APAR: 2300056 (was Problem_ID 2004170A)
STATUS: CLOSED
OPEN_DATE: 06-18-2004
CLOSE_DATE: 07-20-2004
SERVICE(S): MLCL (RTEIN/RTEOUT) console command enhancement
MANDATORY: N/A
ORIGIN/REF: 230_NBG
CP_TECH: SFD
PTF_CLASS: ENHANCEMENT-APAR
PTF_TYPE: (SRC) HNASMACX and (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnasproblem/
(Complete FIX is contained in the 2300056.ZIP file)
COREQ(S): N/A
PREREQ(S): APAR 2300045
(and associated APARs PREREQ chains)
SUPERSEDES: N/A
OBJECT(S): CONSHELP, CONSMLCL, NASCNFG
SOURCE(S): XFCNFGWA
PROBLEM: Unable to insert new entries in the LOCAL RTEIN= and
(ENHANCEMENT) RTEOUT= operand lists.
DESCRIPTION: Currently, if a new entry is added to the RTEIN= or
RTEOUT= operand, it can only be added to the end of
each operand's list. If the associated DTE address
is a superset of a previous entry, the new entry will
never be used. For example, assume the following
RTEIN= operand list:
RTEIN=(ABCD/47113456,
EFGH/23456,
IJKL/345689)
When MLCL RTEIN=XYZA/2345678 is entered, the RTEIN=
operand list will look as follows:
RTEIN=(ABCD/47113456,
EFGH/23456,
IJKL/345689,
XYZA/2345678)
Because DTE address 23456 occurs earlier in the
RTEIN= list (for MCH EFGH), the new entry for MCH
XYZA will not be accessed.
SOLUTION: The MLCL command has been modified so that a new
entry can be inserted at a specific position in the
RTEIN= and RTEOUT= operand lists. In this way the
the entry will be tested before the old entry that
has a subset of the new DTE address. Using the
example above, to insert XYZA/2345678 as the second
entry in the RTEIN= operand list, prefix the MCH
name (XYZA) with a decimal entry number value as
follows:
MLCL RTEIN=2,XYZA/2345678 <- comma before XYZA
is optional
This command changes the RTEIN= operand list to look
as follows:
RTEIN=(ABCD/47113456,
XYZA/2345678,
EFGH/23456,
IJKL/345689)
Note also that logic has been added that allows you
to delete an entire entry, not just its DTE address.
To remove the entry for MCH EFGH in the RTEIN= list
above, enter the following command:
MLCL RTEIN=3,* <- comma before * is
optional
This command changes the RTEIN= operand list to look
as follows:
RTEIN=(ABCD/47113456,
XYZA/2345678,
IJKL/345689)
The following description is now produced when HELP
MLCL or MLCL ? is entered:
DESCRIPTION (* => PRIVILEGED)
MODIFY LOCAL CONFIGURATION PARAMETERS
ENTER> LNM=lclname MLCL {INIT={ACTIVE|IDLE},
DELAYTIME=min,
RETRYLMT=cnt}
{OPTIONS={BALANCERTEOUT|NOBALANCERTEOUT}}
{RTEIN={entnum}mchname{-refnum}/dd...dd}
{RTEOUT={entnum}rmtname{-refnum}/dd...dd
||{S|T}
NOTE: enter entnum as the position of an entry to be inserted or
deleted
refnum as the position of an entry relative to like
named entries
* for mchname|rmtname to delete entry when entnum
is given to
* for dd...dd to delete DTE address for a selected
entry
NOTE: entnum and refnum, if entered, are relative to one
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).
07-14-2004 - APAR 2300055
APAR: 2300055 (was Problem_ID 2004194A)
STATUS: CLOSED
OPEN_DATE: 07-12-2004
CLOSE_DATE: 07-14-2004
SERVICE(S): QLLC (RJE)
MANDATORY: RECOMMENDED
ORIGIN/REF: 230_NBG
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300055.ZIP file)
COREQ(S): N/A
PREREQ(S): Distribution dated after: 06-02-2003
With APARs: 2300034 and 2300041 applied.
SUPERSEDES: N/A
OBJECT(S): XOTBXM2
SOURCE(S): N/A
PROBLEM: Inbound call request from QLLC RJE station fails with
SENSE=08350027 (connect error with pointer).
The remote is rejecting the BIND from HNAS.
DESCRIPTION: The remote RJE station starts a session with INIT-SELF.
This PIU contains the PLU name and a password. No URC
(User Request Correlation) is present. A REQSESS is
sent to the PLU and a BIND results. The BIND PIU is
rejected by the remote with 08350027 sense.
SOLUTION: The BIND sent by HNAS does not have the length bytes
for user data, URC data and SLU name. The fix adds
3 bytes of zeroes to the HNAS BIND PIU.
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).
07-08-2004 - APAR 2300054
APAR: 2300054 (was Problem_ID 2004181A)
STATUS: CLOSED
OPEN_DATE: 06-29-2004
CLOSE_DATE: 07-07-2004
SERVICE(S): All - Alert Messages
MANDATORY: NO, RECOMMENDED ENHANCEMENT
ORIGIN/REF: 230_POR
CP_TECH: PRT
PTF_CLASS: ENHANCEMENT-APAR
PTF_TYPE: (SRC) HNASMACX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars
(Complete FIX is contained in the 2300054.zip file)
COREQ(S): N/A
PREREQ(S): N/A
OBJECT(S): N/A
SOURCE(S): VTMRCV1, VTMEXIT
PROBLEM: Diagnosis is difficult when the PLU rejects a REQSESS
<ENHANCEMENT> from HNAS. The only notification is the following:
NAS3799I LU lu-name ENDING SESSION ON MCH mch-name
HNAS CAUSE/DIAG=000/145 (00/91) DIAGX=0000
DESCRIPTION: The 145 (X'91') diagnostic value indicates that HNAS
received a NOTIFY or CLEANUP PIU from VTAM indicating
that the session is over.
NOTIFY is used when session setup fails (HNAS gets
+RSP to it's REQSESS then session is rejected (BIND
not forthcoming)).
CLEANUP is used when a session is terminated after
setup completes (e.g. PLU closes it's ACB mid session).
SOLUTION: 1) A new message NAS3703W is issued when a NOTIFY is
received for an LU:
NAS3703W mch-nm VC addr lu-nm LU addr RECEIVED
NOTIFY CODE=aabbcc00 SENSE=ssssssss
aa = control vector type (X'03' expected)
bb = status 00 = OLU & DLU SSCPs not connected.
01 = session terminated
02 = session setup received
03 = procedure error
cc = xxxxxxxx BIT values
||||||||___ reserved
|||||||____ 1 = session rejected at SSCP
||||||_____ reserved
|||||______ 0 = setup procedure error
|||| 1 = takedown procedure error
||||_______ 1 = setup rejected at SLU
|||________ 1 = setup rejected at PLU
||_________ 1 = error sending BIND to SLU
|__________ 1 = error sending CINIT to PLU
ssssssss = sense data from PLU or VTAM.
2) A new message NAS3704W is issued when a CLEANUP is
received for an LU:
NAS3704W mch-nm VC addr lu-nm LU 0013E3D0 RECEIVED
CLEANUP CODE=aa00000
aa= xxxxxxxx Reason Bits
||_________ 1 = Network Manager
|__________ 1 = Abnormal
For remaining bits see SNA Format & Protocol.
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).
07-07-2004 - APAR 2300053
APAR: 2300053
STATUS: CLOSED
OPEN_DATE: 07-07-2004
CLOSE_DATE: 07-07-2004
REV_DATE: 11-18-2004 (DIAGX= reference added to Problem: area)
SERVICE(S): ALL (Inbound Call Alert Message NAS7715W)
MANDATORY: YES
ORIGIN/REF: 230_BNP
CP_TECH: PRT
PTF_CLASS: STANDARD-APAR (BUG FIX)
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars
(Complete FIX is contained in the 2300053.zip file)
COREQ(S): N/A
PREREQ(S): APAR 2300051
(and associated APARs PREREQ chains)
SUPERSEDES: N/A
OBJECT(S): XOTTR
SOURCE(S): N/A
PROBLEM: The NAS7715W alarm message can display an incorrect
decimal value for the clear diagnostic code. In
addition, the diagnostic extension bytes (DIAGX=)
are not displayed.
DESCRIPTION: See problem.
SOLUTION: Module corrected to display the correct decimal
value and to display the diagnostic extension
value.
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).
07-06-2004 - APAR 2300052
APAR: 2300052 (was Problem_ID 2004161B)
STATUS: CLOSED
OPEN_DATE: 06-09-2004
CLOSE_DATE: 07-06-2004
SERVICE(S): GATE_CALLOUT (PFXDCEADDR)
MANDATORY: NO, ENHANCEMENT
ORIGIN/REF: 230_BNP
CP_TECH: SFD
PTF_CLASS: ENHANCEMENT-APAR
PTF_TYPE: (SRC) HNASMACX and (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars
(Complete FIX is contained in the 2300052.zip file)
COREQ(S): N/A
PREREQ(S): N/A
SUPERSEDES: N/A
OBJECT(S): CNFGDCAD, CNFGOPTS, CONSDRMT, CONSHELP, CONSMRMT,
NASCNFG, XOTUT1
SOURCE(S): XFNASWA
PROBLEM: Users unable to employ REPDCEADDR features for GATE
callout sessions when GATE calling address contains
subaddress only digits for application routing.
DESCRIPTION: The REPDCEADDR feature was initially designed to
associate GATE callout sessions (via the calling
address) with routers (via the RTEOUT=values) and
interfaces (via x25 route, substitution filtering)
for proper application to router interface mapping.
REPDCEADDR logic will only replace the GATE calling
address when the CTCP's call request packet has no
calling address field (calling address length = 0).
Some GATE callout applications require that the
subaddress digits in the calling address portion
of the CTCP's call request packet be prefixed
with the DCEADDR= digits in the HNAS CDF.
SOLUTION: PFXDCEADDR -
This new option will cause HNAS to insert the
DCEADDR=value in front of the calling address
supplied in a GATE CTCP's call request packet.
If the generated calling address is longer than
15 digits then a clear diag=147 is returned to
the CTCP.
If there is no calling address in the CTCP's
call request packet then the calling address
will be the DCEADDR.
REPDCEADDR -
This existing option will continue to only
insert the HNAS DCEADDR=values into the GATE
calling address filed when no digits are
provided (calling address length of zero).
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).
06-29-2004 - APAR 2300051
APAR: 2300051 (fix for APAR 2300047)
STATUS: CLOSED
OPEN_DATE: 06-29-2004
CLOSE_DATE: 06-29-2004
SERVICE(S): TRACE TRAP PROCESSING
MANDATORY: YES, if APAR 2300047 is on system
ORIGIN/REF: 230_POR
PTF_TYPE: (SRC) HNASMACX and (OBJ) HNASOBJX members
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300051.ZIP file)
COREQ(S): N/A
PREREQ(S): APAR 2300047
(and associated APARs PREREQ chains)
OBJECT(S): MCHTR, VCTR, XOTTR, XTPTR
SOURCE(S): VTMTR
PROBLEM: Assembly error in VTMTR module due to missing symbol.
DESCRIPTION: Symbol TRSWSUSP was replaced with TRSWSUSC and the new
symbol TRSWSUST was added by APAR 2300047. However,
a few trace modules did not pick this change up.
SOLUTION: The trace modules have been modified to test for the
new symbols.
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).
06-27-2004 - APAR 2300050
APAR: 2300050
STATUS: CLOSED
OPEN_DATE: 06-26-2004
CLOSE_DATE: 06-27-2004
SERVICE(S): QLLC
MANDATORY: Yes
ORIGIN/REF: 230_POR
PTF_TYPE: (SRC) HNASMACX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300050.ZIP file)
COREQ(S): N/A
PREREQ(S): N/A
OBJECT(S): N/A
SOURCE(S): VTMSND2
PROBLEM: HNAS terminates with a USER 198 Abend and message:
HALT AT LOC xxxxxx IN VTMRSPC : RECV RPL BUSY
DESCRIPTION: The above indicates that a logic error has occurred.
An RPL (used for VTAM operations) that should be
available is not.
The error occurs when HNAS is sending a PLU output
sequence and the remote device rejects a PIU. The
QLLC send -RSP routine uses the LU's transmit RPL
to send the response to the PLU but sets the busy
for the receive RPL. If HNAS is collecting an
output message when this happens the HALT occurs.
SOLUTION: HNAS modified to set the correct busy bit.
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).
06-24-2004 - APAR 2300049
APAR: 2300049
STATUS: CLOSED
OPEN_DATE: 06-24-2004
CLOSE_DATE: 06-24-2004
SERVICE(S): CONSOLE - WTOR SUPPORT (NON-USEMDFY)
MANDATORY: NO, BUT RECOMMENDED
ORIGIN/REF: 230_POR
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300049.ZIP file)
COREQ(S): N/A
PREREQ(S): APAR 2300047
OBJECT(S): NASUTIL
SOURCE(S): N/A
PROBLEM: When the USEMDFY parameter is NOT specified, it is
possible for 2 WTO replies (WTORs) to be outstanding
after a console command like DPARM is entered.
DESCRIPTION: APAR 2300022 corrected a problem that caused 2 WTORs
to be outstanding after HNAS starts but failed to
correct a similar problem that occurs after a console
command is entered.
SOLUTION: The HNAS WTO interface routine has been modified to
treat the display header message for a command like
DPARM as a WTO instead of a WTOR so that only the
console prompt message (BUILD CONPRMT= operand)
solicits a WTO reply.
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).
06-23-2004 - APAR 2300048
APAR: 2300048
STATUS: CLOSED
OPEN_DATE: 06-22-2004
CLOSE_DATE: 06-23-2004
SERVICE(S): SMP/E Install Problems
MANDATORY: YES
ORIGIN/REF: 230_CP
PTF_TYPE: SMP/E customization EXEC.
PTF_LOC: N/A
COREQ(S): N/A
PREREQ(S): N/A
OBJECT(S): N/A
SOURCE(S): smpgjob.bin
PROBLEM(S): The FTPGET job (used to obtain SMP/E distribution
files from the Comm-Pro FTP server) fails.
Examination of the job will show an extra cd
(change directory) statement with no operands.
New TRCTRAP command does not work when HNAS is
installed with SMP/E.
Description: The FTPGET job is generated by the smbgjob REXX
exec. The exec contains an error which produces
the extra statement when the user directory is a
short name (##UD= customization statement).
Additionally, the exec was not updated to include
the two ++MOD statements required for TRCTRAP
support.
smpgjob.bin is the exec's name on our server. The
name on your system is determined when the file
is uploaded.
Solution: Obtain a revised copy of the EXEC from us.
Circumvention: To circumvent the FTPGET problem simply edit the
hlq.SLNSCNTL(FTPGET) job and remove the extra
statement.
APPLY_INFO: N/A
Corrective logic included in distributions created
after CLOSE_DATE.
06-23-2004 - APAR 2300047
APAR: 2300047 (fix for problem 2004167A/2300045)
STATUS: CLOSED
OPEN_DATE: 06-16-2004
CLOSE_DATE: 06-23-2004
SERVICE(S): TRACE TRAP PROCESSING
MANDATORY: NO, BUT RECOMMENDED ENHANCEMENT
ORIGIN/REF: 230_CP
PTF_TYPE: (OBJ) HNASOBJX and (SRC) HNASMACX members
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300047.ZIP file)
COREQ(S): N/A
PREREQ(S): APAR 2300045
(and associated APARs PREREQ chains)
OBJECT(S): CONSTALL, CONSTRTR, NASUTIL
SOURCE(S): NASMAIN, NASTCP, XFBLK, XFNASWA
PROBLEM1: Existing TRCTRAP logic does not generate an alert
(ENHANCEMENT) message when trace trapping is enabled via the
TRCTRAP console command.
PROBLEM2: Existing TRCTRAP logic does not display the current
(ENHANCEMENT) trace state when TRCTRAP SHOW is specified.
DESCRIPTION1: Existing TRCTRAP logic issues various alert messages
when trace trapping is enabled at startup and as
tracing is suspended or resumed but not when trapping
is enabled by command.
DESCRIPTION2: Existing TRCTRAP logic displays the current trap
filters when TRCTRAP SHOW is entered by not the
current trace state.
SOLUTION1: The console subsystem TRCTRAP logic was modified to
generate additional alert messages:
The following alert is provided when the trace
trapping option is enabled via the TRCTRAP
console command:
NAS0070W TRACE TRAP FILTERING ACTIVATED BY COMMAND
The following alert is provided when the trace
trapping option is disabled via the TRCTRAP
console command:
NAS0070W TRACE TRAP FILTERING DEACTIVATED BY COMMAND
The following alert is provided when the trace
trapping option is modified via the TRCTRAP
console command:
NAS0070W TRACE TRAP FILTERING UPDATED BY COMMAND
The following alert is provided as a trapping state
indication after the NAS0050A alert (TRCTRAP SUSP)
or NAS0060W alert (TRCTRAP RSME) is issued:
NAS0070W TRACE TRAP FILTERING ACTIVE
- or -
NAS0070W TRACE TRAP FILTERING INACTIVE
SOLUTION2: The console subsystem TRCTRAP logic was modified to
generate the following additional state display when
TRCTRAP SHOW, TRCTRAP ALRMLIST=?, TRCTRAP RCVLIST=?
or TRCTRAP XMTLIST=? is entered:
TRACE STATE: IDLE <- logging inactive
LOGGING <- logging active
SUSPENDED BY COMMAND <- logging suspended
SUSPENDED BY TRAP <- logging suspended
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).
06-18-2004 - APAR 2300046
APAR: 2300046
STATUS: CLOSED
OPEN_DATE: 06-03-2004
CLOSE_DATE: 06-18-2004
SERVICE(S): Call request packet trace processing
MANDATORY: NO (recommended enhancement)
ORIGIN/REF: 230_RBS
PTF_TYPE: (OBJ) HNASOBJX members
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300046.ZIP file)
COREQ(S): N/A
PREREQ(S): N/A
OBJECT(S): XOTBXM, XOTFCDC, XOTGTCC, XOTRCV, XOTTR
SOURCE(S): N/A
PROBLEM: Customer requested a way to see information in call
(ENHANCEMENT) request packets processed by HNAS.
SOLUTION: When a TRCMCH ICR command is entered the following
records will be sent to SYSPRINT when HNAS receives a
call request from the network:
NAS7718T 010.117.056.100(24321) CALL REQ TO MCH MCH1
NAS7798T CALLED: 20360005 CALLING: 262199
NAS7798T FAC-LN: 06 FAC: 42070743 0707
NAS7798T USER DATA: 01000000
The records reflect the call request packet as
received. HNAS processing (e.g. STRIPRTEIN) has
not been performed. Records are created for all
LLC types.
When a TRCMCH OCR command is entered the following
records will be sent to SYSPRINT when HNAS is ready
to send a call request packet to the link:
NAS7719T OUTBOUND CALL REQ GENERATED FOR LU MCH14001
PLU=NASCTCP REMOTE=R2CNOT1
NAS7798T CALLED: 10360003 CALLING: 1
NAS7798T FAC-LN: 06 FAC: 42070743 0202
NAS7798T USER DATA: 5C5C5C5C
OCR records are created for LLC0, LLC4 and LLC5 calls.
NAS8000I messages provide this information for LLC3.
The above trace records are sent only to SYSPRINT
(provided that the print limit has not been reached).
Records are sent whether or not TRCPRNT ON is set.
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).
06-16-2004 - APAR 2300045
APAR: 2300045
STATUS: CLOSED
OPEN_DATE: 06-01-2004
CLOSE_DATE: 06-15-2004
SERVICE(S): TRACE AND ALARM PROCESSING
MANDATORY: NO, BUT RECOMMENDED ENHANCEMENT
ORIGIN/REF: 230_CP
PTF_TYPE: (OBJ) HNASOBJX and (SRC) HNASMACX members
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300045.ZIP file)
COREQ(S): N/A
PREREQ(S): APAR 2300005, 2300006, 2300007, 2300019, 2300022,
2300026, 2300037, 2300042, 2300043 and 2300044
(and associated APARs PREREQ chains)
OBJECT(S): CNFGAFLT, CNFGTRTR, CONSALRM, CONSDMAP, CONSDRMT,
CONSHELP, CONSPWTO, CONSTALL, CONSTRTR, MCHTR,
NASCNFG, NASCONS, NASUTIL, VCTR, XOTTR, XTPTR
SOURCE(S): NASMAIN, NASTCP, SYSLIN, VTMTR, XFBLK, XFCNFGWA,
XFMODMAP, XFNASWA, XFXTRN
PROBLEM1: Enhancement providing TRCTRAP automation tools to
(ENHANCEMENT) stop HNAS tracing when operator enabled events occur.
PROBLEM2: Enhancement allowing ALARM FILTER= console command
(ENHANCEMENT) to append alarm ID's to existing filter list rather
than replacing existing list.
DESCRIPTION1: TRCTRAP enhancement:
Sometimes it is difficult to capture the cause of a
problem in the HNAS internal trace table when tracing
has to be stopped manually.
In many cases, the only way to resolve a problem is
to run HNAS traces. If a problem is intermittent,
TRCPRNT is not a viable option because it can create
an inordinate amount of SYSPRINT and consume valuable
CPU cycles. Internal tracing is the next best option
but it must be stopped as soon as possible after the
problem has occurred. This may be difficult and, in
some cases, may even be impossible.
DESCRIPTION2: ALARM FILTER enhancement:
The initial implementation of the HNAS ALARM console
command processor replaced existing FILTER= values
instead of appending values to the ALRMFLTR= array.
This restriction forced users to reenter existing
alarm list entries (previous specified on the BUILD,
ALRMFLTR=) so that they could add new message ID's
via the console.
SOLUTION1: TRCTRAP enhancement:
HNAS has been modified to accept a new configuration
operand and console command that will provide the
ability to suspend internal tracing (and TRCPRNT)
based on alarm message ID match, an input packet
match or an output packet match. Multiple alarm IDs
and packets may be specified so that a collection
of values may be monitored (trapped).
Once the trace and TRCPRNT activity is suspended
(NAS0050A message generated), HNAS must be shutdown
with QY/password so that the internal trace table
can be formatted. Because the trace is suspended
(frozen), HNAS need not be shutdown immediately
but can be shutdown at your convenience.
If the trap was performed with TRCPRNT enabled,
the SYSPRINT file can be manually switched (see
PRNT CLOSE|OPEN dsname|CLSOPN dsname console for
additional information on HNAS SYSPRINT dataset
switching). This will allow you to send us the
closed SYSPRINT file without having to shutdown
HNAS. If multiple SYSPRINT datasets are used,
make sure that DISP=SHR is specified for all so
that they can be accessed by ISPF or another
program (like IEBCOPY or IEBGENER).
Note: A second phase of this enhancement will be
provided which will locate the trace data into a
separate SYSOUT or DSN= file so that a shutdown
is not required.
The following text identifies the new HNAS BUILD
TRCTRAP configuration operand and console command
that may be used for trace trap processing.
CONFIGURATION ENHANCEMENT:
--------------------------
BUILD TRCTRAP=(ALRMLIST=(id1,...,idn),
RCVLIST=(prot1||pkt1,...protn||pktn),
XMTLIST=(prot1||pkt1,...protn||pktn))
CONSOLE COMMAND ENHANCEMENT:
----------------------------
TRCTRAP {ALRMLIST=?|*|(id1,...,idn)}
{RCVLIST=?|*|(prot1||pkt1,...protn||pktn)}
{XMTLIST=?|*|(prot1||pkt1,...protn||pktm}}
{SHOW} {SUSP} {RSME}
FOR BOTH CONFIGURATION AND CONSOLE COMMAND:
-------------------------------------------
idi => alarm ID (e.g, NAS1001I) that may
contain asterisks (*) as wildcards
(e.g., NAS1****).
A maximum of 16 idi entries may be
specified.
proti => packet protocol (00=>XTP, 04=>XOT).
pkti => packet data from PKTTYPE for length m
that can contain all ones as wildcards
(e.g., 13FFFF).
A maximum of 512 bytes for protocol
and packet data may be specified which
include a length byte (m) for each
packet. The packet data is compared
only for the length (m) that is given.
PAD sessions operating with non-space
parity will encounter data mismatches
with the filter list when non-qualified
data is specified. You may specify the
same data with different parity settings
as required.
Note: A match on any value in the ALRMLIST=,
RCVLIST= or XMTLIST= operands can suspend
tracing. The first match in any of these
operands is the winner. Multiple operands
with multiple values are provided to allow
for the greatest flexibility.
FOR CONSOLE COMMAND ONLY:
-------------------------
Enter: * as first operand value to reset operand
? as first operand value to display operand
SHOW to display all operand values
SUSP to suspend trace manually
RSME to resume suspended trace
Note: When values are specified for the ALRMLIST=
RCVLIST= and XMTLIST= command arguments,
they are appended to the end of the
corresponding table in the order in which
the values are entered. For example:
If BUILD TRCTRAP=(ALRMLIST=(NAS8***I)
was specified in the CDF and if
TRCTRAP ALRMLIST=(NAS2021I,NAS2100I) then
TRCTRAP ALRMLIST=(NAS2201I) are issued
as console commands, the TRCTRAP ALRMLIST=?
command would produce the following display:
ALRMLIST=NAS8***I
NAS2021I
NAS2100I
NAS2201I
CONFIGURATION EXAMPLES:
-----------------------
Trap multiple events:
TRCTRAP=(ALRMLIST=(NAS3701W, <- LU ACB open failed
NAS3798I), <- LU starting session
RCVLIST=(041B0502, <- Reset 05/02
041309A5, <- Clear 09/A5
04F1FFFF), <- any Diag packet
XMTLIST=(041BFFFF, <- any Reset packet
0413FFFF)) <- any Clear packet
Trap PAD logon request:
TRCTRAP=(RCVLIST=(04FF6CA063F0, <- l cp (even)
04FFEC20E370, <- l cp (odd)
04FF6C206370, <- l cp (none)
04FFCCA0C350, <- L CP (even)
04FF4C2043D0, <- L CP (odd)
04FF4C204350)) <- L CP (none)
Trap QLLC Terminate-Self PIU:
TRCTRAP=(RCVLIST=(04FF2C0000FFFFFF0B8000010683)) <-|
|
TERM-SELF <-|
TRCTRAP ALERT MESSAGES:
-----------------------
The following alerts are provided when tracing is
suspended due to an alarm ID or packet match.
NAS0050A TRACING SUSPENDED DUE TO TRAPPED
ALARM ddddddd
NAS0050A TRACING SUSPENDED DUE TO TRAPPED
INPUT PACKET xx...xx
NAS0050A TRACING SUSPENDED DUE TO TRAPPED
OUTPUT PACKET xx...xx
The following alert is provided when tracing is
suspended via the TRCTRAP SUSP or TRCALL SUSP
command.
NAS0050A TRACING SUSPENDED BY COMMAND
The following alert is provided when tracing is
resumed via the TRCTRAP RSME or TRCALL RSME
command.
NAS0060W TRACING RESUMED BY COMMAND
The following alert is provided when trace
trapping option is enabled via the TRCTRAP
configuration operand.
NAS0070W TRACE TRAPPING ENABLED
GENERAL NOTES (SUMMARY):
------------------------
1) The current tracing parameters are not altered
when tracing is suspended. To restart trace
logging, you need to issue the TRCTRAP RSME or
TRCALL RSME console command.
2) When tracing is suspended, TRCPRNT trace entry
logging in SYSPRINT is also suspended.
3) Since TRCTRAP processing is global (not directly
associated with enabled trace options or resource
TRCtype filtering), it is important to have the
appropriate traces activated so that the events
leading up to the suspended trace will be captured
in the internal trace table. For example, if a
RCVLIST= or XMTLIST= is provided, TRCVC MINDATA or
TRCVC MAXDATA should be active.
4) TRCTRAP logic was added primarily as a tool for
Comm-Pro in order to provide a way of simplifying
problem diagnosis. In the past, Comm-Pro had to
develop custom modifications to trap certain
events. The TRCTRAP logic now standardizes this
processing.
In most cases, Comm-Pro will be advising customers
on what to enter for TRCTRAP arguments rather than
giving them a custom trap modification.
This memo is intended to provide some information
about the TRCTRAP function. We do not, however,
expect customers to use TRCTRAP functions without
Comm-Pro involvement.
SOLUTION2: ALARM FILTER= enhancement:
The HNAS ALARM console command processor has been
modified to append FILTER= values to the existing
ALRMFLTR= array rather than resetting the array
first. This eliminates the need to enter an entire
list of alarm IDs in order to add just one entry
to the end of the list. For example:
If BUILD ALRMFLTR=(ALLOW,NAS2***I(P)) was specified
in the CDF and if ALARM FILTER=(NAS3701W(P)) is
issued as a console command, the ALARM FILTER=?
command would produce the following display:
ALRMFLTR=ALLOW
NAS2***I(P)
NAS3701W(P)
If you wish to clear the ALRMFLTR= array before
entering new values, enter ALARM FILTER=* to clear
the entries followed by ALARM FILTER=(disp,list)
for the new filter entries.
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).
06-03-2004 - APAR 2300044
APAR: 2300044
STATUS: CLOSED
OPEN_DATE: 06-03-2004
CLOSE_DATE: 06-03-2004
SERVICE(S): TCPIP INTERFACE, SERVER INITIALIZATION
MANDATORY: YES
ORIGIN/REF: 230_CP
PTF_TYPE: (SRC) HNASMACX members
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300044.ZIP file)
COREQ(S): N/A
PREREQ(S): APAR 2300043
(and associated APARs PREREQ chains)
OBJECT(S): N/A
SOURCE(S): NASTCP
PROBLEM: HNAS will not SHUTDOWN if a server (LOCAL) is taken
offline when HNAS cannot bind its IP address to the
stack.
DESCRIPTION: When INIT=ACTIVE (the default) is specified for a
LOCAL definition statement, HNAS allocates a socket
for the server component and then attempts to bind
its IP address (the HOME IP address) to the stack.
If the bind is unsuccessful, it is retried after a
forced delay. If the bind retry limit is reached
(INIT=(,RETRYLMT=n)), HNAS takes the server offline.
The problem occurs because the socket that was
allocated to the server component is not closed
when the server is taken offline. This means
that SHUTDOWN will not complete because the
count of active TCPIP server sockets (WALCCNAC)
is non-zero. When WALCCNAC=0, HNAS knows that
all server sockets have been closed and SHUTDOWN
can complete. The following alarm messages are
generated during bind retry/failure processing
when RETRYLMT=1 is specified:
NAS2231W SERVER=192.040.060.100(03065) SOCKID=0000
PCEID=0008 NAME=LXTP
NAS2231W BIND REQUEST FAILED, RC=FFFFFFFF 00000031
NAS2231W SERVER=192.040.060.100(03065) SOCKID=0000
PCEID=0008 NAME=LXTP
NAS2231W BIND REQUEST FAILED, RC=FFFFFFFF 00000031
NAS2021W SERVER=192.040.060.100(03065) SOCKID=0000
PCEID=0008 NAME=LXTP
NAS2021W SERVER INITIALIZATION FAILED, LOCAL VARIED
OFFLINE
SOLUTION: The HNAS server bind retry logic has been corrected
to close the server socket after the NAS2021W message
is generated. This will maintain the WALCCNAC count
validity and allow SHUTDOWN processing to complete.
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).
06-03-2004 - APAR 2300043
APAR: 2300043
STATUS: CLOSED
OPEN_DATE: 06-03-2004
CLOSE_DATE: 06-03-2004
SERVICE(S): TCPIP INTERFACE, TAPPING (KEEP ALIVE PROCESSING)
MANDATORY: YES
ORIGIN/REF: 230_CP
PTF_TYPE: (OBJ) HNASOBJX and (SRC) HNASMACX members
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300043.ZIP file)
COREQ(S): N/A
PREREQ(S): APAR 2300005, 2300022, 2300042
(and associated APARs PREREQ chains)
OBJECT(S): NASUTIL
SOURCE(S): NASTCP, XFBLK and XFPCE
PROBLEM: HNAS does not perform Keep Alive service even when
a value is specified for the TAP= operand.
DESCRIPTION: Logic provided by APAR 2300042 causes the TAP=n
operand value to be erroneously reset which makes
HNAS think that TAP=0 was specified (TAP=0 option
is used to suppress Keep Alive processing). The
problem occurs because the TCPIP stack sever flag
remembrance (PCEIPTYP field) was equated to the
PCETAPLM field. The latter is used to remember
the TAP= operand value.
SOLUTION: The Process Control Element (PCE) control block
has been modified to set PCEIPTYP to an unused
(previously reserved) field.
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).
06-02-2004 - APAR 2300042
APAR: 2300042 (was Problem_ID 2004149A)
STATUS: CLOSED
OPEN_DATE: 05-28-2004
CLOSE_DATE: 06-02-2004
SERVICE(S): TCPIP INTERFACE, STACK STOPPED PROCESSING
MANDATORY: NO, BUT RECOMMENDED
ORIGIN/REF: 230_BNP
PTF_TYPE: (OBJ) HNASOBJX and (SRC) HNASMACX members
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300042.ZIP file)
COREQ(S): N/A
PREREQ(S): APAR 2300026, 2300032, 2300039
(and associated APARs PREREQ chains)
OBJECT(S): NASUTIL
SOURCE(S): NASMAIN and NASTCP
PROBLEM: HNAS does not always process TCPIP stack sever
properly.
DESCRIPTION: If the TCPIP stack is stopped while HNAS is still
running, an unsolicited interrupt is presented to
HNAS indicating that the connection to the stack
has been severed.
When the SVRSTRT option is in affect, HNAS is
supposed to recover from the sever condition.
When the SVRSTRT option is not in affect, HNAS is
supposed to automatically shut down when the sever
condition is detected.
In some cases, HNAS behavior can be unpredictable
when a sever occurs.
Because of logic introduced with multiple stack
support, shutting HNAS down when a sever occurs is
wrong if HNAS is connected to another stack that
is still operational. In this case, HNAS must
continue running regardless of the SVRSTRT option.
Existing logic causes HNAS to remain running after
a sever occurs if the SVRSTRT option is active but
sever cleanup processing erroneously releases all
VC and LU memory. The result is that HNAS still
runs but cannot process new connections.
SOLUTION: HNAS TCPIP sever logic has been modified to prevent
HNAS from stopping (shutting down) when a stack is
is stopped if multiple stacks are defined (multiple
LOCAL definitions with different TCPNAME= operand
values) regardless of the SVRSTRT option. In
addition, VC and LU resources will only be released
when HNAS is shut down. When the SVRSTRT is not
active, HNAS will automatically shut down only when
all LOCAL and REMOTE connections to all stacks are
closed or severed.
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).
06-02-2004 - APAR 2300041
APAR: 2300041 (was Problem_ID 2004148A)
STATUS: CLOSED
OPEN_DATE: 05-27-2004
CLOSE_DATE: 06-02-2004
SERVICE(S): QLLC
MANDATORY: N/A
ORIGIN/REF: 230_IZB
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300041.ZIP file)
COREQ(S): N/A
PREREQ(S): N/A
SUPERSEDES: N/A
OBJECT(S): XOTBXM2, MCHRL3RR
SOURCE(S): N/A
PROBLEM: QLLC SLU sending PIUs to HNAS. HNAS sends a pacing
response, SLU responds with TERM-SELF. The QLLC
session ends.
DESCRIPTION: 1) An HNAS logic error causes an IPR (Isolated Pacing
Response) to be sent with the expedited flow bit
set in the PIU's TH. This violates SNA rules.
2) When SLU send pacing is set in the BIND image the
SLU sets a PI (pacing indicator) in the first
request PIU sent in the window. The SLU can
suppress pacing by never setting the PI bit. HNAS
sends an incorrect pacing response when no PI has
been received. This leads to the SLU TERM-SELF.
SOLUTION: HNAS modified to not set the TH expedited flow bit in
an IPR and to disable pacing logic if no request with
a PI is received from the 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).
06-02-2004 - APAR 2300040
APAR: 2300040 (was Problem_ID 2004111A)
STATUS: CLOSED
OPEN_DATE: 04-20-2004
CLOSE_DATE: 06-02-2004
SERVICE(S): QLLC SUPPORT
MANDATORY: YES
ORIGIN/REF: 230_SNC
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300040.ZIP file)
COREQ(S): N/A
PREREQ(S): N/A
OBJECT(S): MCHRL3RR
SOURCE(S): N/A
PROBLEM: Reset 05/02 can be received for a QLLC VC.
DESCRIPTION: When HNAS is processing inputs from different LUs
connected via the same X25 virtual circuit, it is
possible for an incorrect P(R) value to be sent.
This causes an X25 RESET to occur and the QLLC
sessions on the VC to be taken down.
SOLUTION: HNAS P(R) (packet level acknowledgement) logic
corrected.
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).
05-28-2004 - APAR 2300039
APAR: 2300039
STATUS: CLOSED
OPEN_DATE: 05-11-2004
CLOSE_DATE: 05-28-2004
SERVICE(S): QLLC SUPPORT Enhancement
MANDATORY: NO, BUT RECOMMENDED ENHANCEMENT
ORIGIN/REF: 230_IZB
PTF_TYPE: (OBJ) HNASOBJX and (SRC) HNASMACX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300039.ZIP file)
COREQ(S): N/A
PREREQ(S): APAR 2300017, 2300038
OBJECT(S): QLSSCP and VCCLRQ
SOURCE(S): NASTCP
PROBLEM: The NAS8000I QLLC VC session start message does
(ENHANCEMENT) not display the calling and called DTE address or
direction of call.
DESCRIPTION: -
For both inbound and outbound Call Requests, the
following message is generated after a call is
successfully established.
NAS8000I CLIENT=ipad(port) SOCKID=sid PCEID=pid NAME=rnm
NAS8000I VC xxxxxxxx STARTING SESSION ON MCH mnm (cnt)
SOLUTION: -
The QLLC Call Request processor has been modified to
generate the following enhanced NAS8000I message:
NAS8000I CLIENT=ipad(port) SOCKID=sid PCEID=pid NAME=rnm
NAS8000I VC xxxxxxxx STARTING SESSION ON MCH mnm (cnt)
NAS8000I INBOUND CLGADDR=lddd...ddd CLDADDR=lddd...ddd
The QLLC Call Accept processor has been modified to
generate the following enhanced NAS8000I message:
NAS8000I CLIENT=ipad(port) SOCKID=sid PCEID=pid NAME=rnm
NAS8000I VC xxxxxxxx STARTING SESSION ON MCH mnm (cnt)
NAS8000I OUTBOUND CLGADDR=lddd...ddd CLDADDR=lddd...ddd
For all messages above:
ipad(port) is the IP address and Port number for the call
sid is the TCPIP stack socket ID for the call
pid is the PCE ID for the REMOTE used for the call
rnm is the REMOTE name
xxxxxxxx is VC control block (VCB) address
mnm is the MCH name used for the call
cnt is the current active VC count for the MCH
lddd...ddd is the DTE address length and digits
(CLGADDR => calling) (CLDADDR => called)
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).
05-26-2004 - APAR 2300038
APAR: 2300038 (Problem_ID 2004140A)
STATUS: CLOSED
OPEN_DATE: 05-19-2004
CLOSE_DATE: 05-26-2004
SERVICE(S): QLLC SUPPORT
MANDATORY: YES
ORIGIN/REF: 230_IZB
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300038.ZIP file)
COREQ(S): N/A
PREREQ(S): APAR 2300031 and 2300036
OBJECT(S): MCHRL3RR and QLSSCP
SOURCE(S): N/A
PROBLEM: 1) APPLNAME=ACQUIRE is treated as a PLU name by the
UNBIND processor.
2) 0198 ABEND (NASHALT - IN VTMLUFM : LU DIRTY) can
occur after LU is UNBOUND.
DESCRIPTION: 1) The UNBIND processor fails to recognize ACQUIRE as
a reserved keyword and uses it as a PLU name in a
REQSESS request if the SLU in the LUNAME= operand
has an associated applid. The REQSESS is rejected
by VTAM which causes the LU's ACB to be closed, a
DACTLU to be transmitted and a delay imposed before
an ACTLU is transmitted. The delay timeout routine
calls the LU format routine (VTMLUFM) before
scheduling the ACTLU transfer. This leads to the
problem 2.
2) If a PIU is received after an LU is unbound and
before it is bound again via REQSESS solicitation,
the PIU is enqueued for host transfer on the LU
input queue (LUIQ). A PIU may be received after an
UNBIND has been transmitted if the UNBIND has not
actually reached the remote LU (like trains passing
in the night). If a REQSESS fails, the sequence
described in problem 1 occurs. Because LUIQ is
non-empty when the VTMLUFM routine receives control,
it ABENDs because it 'knows' that LUIQ should be
empty.
SOLUTION: 1) The UNBIND processor has been modified to test for
APPLNAME=ACQUIRE when an applid is present. If
ACQUIRE is specified, the LU's ACB is opened and a
SETLOGON request is passed to VTAM. This conditions
the LU to wait for and accept a new BIND.
2) The QLLC input processor has been modified to test
the LU state for BIND/BIND-PENDING before enqueing
any PIU to the LU input queue. In LU IDLE state
or REQSESS-PENDING state, no PIUs are expected from
the remote LU. Any residual PIUs that are received
in the IDLE/REQSESS-PENDING states are discarded.
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).
05-21-2004 - APAR 2300037
APAR_ID: 2300037 (230 version of 2200090 PROBLEM_ID 2004084A)
STATUS: CLOSED
OPEN_DATE: 03-24-2004
CLOSE_DATE: 05-21-2004
SERVICE(S): GATE and GATE Fast Connect (FC) Support
MANDATORY: YES for GATE users
ORIGIN/REF: 220_NMP
PTF_TYPE: (OBJ and SRC) HNASOBJX and HNASMACX members
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300037.ZIP file)
COREQ(S): N/A
PREREQ(S): N/A
OBJECT(S): MCHSTRT, MCHNRQC
SOURCE(S): VTMTR, LUD
PROBLEM: GATE control sessions and GATE FC data sessions not
properly reactivated when PLU taken down and restarted.
Inbound calls are cleared with DIAG=138 (X'8A'), which
means the GATE control session was not bound. NAS3702W
message issued.
DESCRIPTION: When a GATE PLU is terminated HNAS can receive a NOTIFY
request which takes down the HNAS SLU. After a time
delay (OPTIONS=MCHTMR=xx on the TYPE=MCH REMOTE)
a GATE control session or FC data session LU's ACB is
reopened and a REQSESS is sent to the PLU (assuming
a PLU name was coded in the HNAS CDF). If the REQSESS
fails, HNAS waits for the PLU to acquire it's SLUs.
The acquire operation results in HNAS receiving a BIND
which activates the HNAS session. If no BIND is
received, all inbound calls requiring the control
session will fail and no FC data session LUs will be
available for GATE FC inbound call request processing.
Thus, CTCPs that do not acquire their SLUs will not
be useable after the PLU takedown / restart sequence.
SOLUTION: HNAS modified to retry the REQSESS operation based
on the OPTIONS=MCHTMR=xx parameter. The ACB remains
open so that a BIND from the PLU will be accepted.
With this APAR on all REQSESS failures are reported
with a NAS3702W message.
If your installation leaves HNAS active while CTCP
PLUs are not up you will see an increased number of
NAS3702W messages.
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).
05-19-2004 - APAR 2300036
APAR: 2300036 (Problem_ID 2004138A)
STATUS: CLOSED
OPEN_DATE: 05-17-2004
CLOSE_DATE: 05-19-2004
SERVICE(S): QLLC CALLOUT SUPPORT
MANDATORY: YES
ORIGIN/REF: 230_IZB
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300036.ZIP file)
COREQ(S): N/A
PREREQ(S): APAR 2300031
OBJECT(S): QLSSCP and VCUT1
SOURCE(S): N/A
PROBLEM: When a BIND initiated (OPTIONS=CLOTINITYP=BIND) Call
Request fails (Clear received), a subsequent BIND will
not initiate another Call Request.
DESCRIPTION: When a Clear is received as a response to a QLLC Call
Request, the VCVCRL routine is called to release the
VC. As part of the clear processing, the ACBs for
the SLUs on the SPU associated with the VC are closed
but the VC control block remembrance (LUVC) is not
reset. When a subsequent BIND is received, the BIND
is queued rather than initiating another Call Request
because the LUVC filed is non-zero. The result is
that the SLU session is hung. When displayed from
VTAM, the SLU state will be PSEST. A VTAM INACT/ACT
command does not fix the problem.
SOLUTION: The callout initiator logic has been modified to set
LUVC=0 when a Clear is received as a response to a
Call Request. This will permit a subsequent BIND to
initiate a new call.
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).
05-17-2004 - APAR 2300035
APAR: 2300035
STATUS: CLOSED
OPEN_DATE: 05-14-2004
CLOSE_DATE: 05-15-2004
SERVICE(S): CONFIGURATION - LLC0-5 SUPPORT
MANDATORY: NO, BUT RECOMMENDED
ORIGIN/REF: 230_CP
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300035.ZIP file)
COREQ(S): N/A
PREREQ(S): APAR 2300014, 2300020
OBJECT(S): CNFGLGTB, CNFGLLC0, CNFGLLC3, CNFGLLC4, CNFGLLC5,
CNFGSVC0, CNFGSVC3, CNFGSVC4, CNFGSVC5, CNFGUSTB,
CNFGVCLM
SOURCE(S): N/A
PROBLEM: A configuration warning messages can be generated if
the vclmt value in the SVCi= operand is specified but
no SLU/SPU entries are not provided.
DESCRIPTION: The first suboperand of the SVCi= operand specifies
the number of LLCi VCs (vclmt) that can be supported.
This vclmt value is propagated to a vccnt value when
the SVCi= operand is reviewed at the end of REMOTE
definition processing. This is done so that SVCi=
name entries can be validated or defaulted. Because
this processing can occur after other, codependent
operands are tested, HNAS can erroneously generate
configuration warning messages. For example, when
GATE=NO,SVC3=(n) is specified, the following warning
message is generated:
NAS1301E REMOTE SVC0 OMITTED, REQUIRED FOR PCNE
This message should be inhibited because GATE=NO says
that either SVC0= or SVC3=, but not necessarily both,
must be specified.
SOLUTION: The HNAS configuration process has been modified to
test the vclmt value rather than the vccnt value.
Since the vclmt value is set when the SVCi= operand
is decoded, it will be set at the end of REMOTE
definition statement processing. This will prevent
the erroneous warning messages from being generated.
CIRCUMVENTION: Specify SVCi=NONE.
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).
05-13-2004 - APAR 2300034
APAR: 2300034 (Problem_ID 2004133A)
STATUS: CLOSED
OPEN_DATE: 05-12-2004
CLOSE_DATE: 05-13-2004
SERVICE(S): QLLC SUPPORT
MANDATORY: YES
ORIGIN/REF: 230_IZB
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP SERVER DIRECTORY /HNAS_MAINT/HNAS230M/APARS/
(COMPLETE FIX IS CONTAINED IN THE 2300034.ZIP FILE)
COREQ(S): N/A
PREREQ(S): N/A
OBJECT(S): XOTBXM2
SOURCE(S): N/A
PROBLEM: QLLC session can hang. Requests from the PLU are not
sent to the SLU because HNAS (incorrectly) thinks a
pacing response is owed. This problem occurs when a
non-FMD request (e.g. BID) closes the HNAS send window
after a pace response is received in the middle of the
window.
DESCRIPTION: See problem.
SOLUTION: HNAS modified to properly process it's send pacing
window.
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).
05-13-2004 - APAR 2300033
APAR: 2300033
STATUS: CLOSED
OPEN_DATE: 05-13-2004
CLOSE_DATE: 05-13-2004
SERVICE(S): CONFIGURATION - QLLC SUPPORT
MANDATORY: NO, BUT RECOMMENDED ENHANCEMENT
ORIGIN/REF: 230_RBS
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300033.ZIP file)
COREQ(S): N/A
PREREQ(S): N/A
OBJECT(S): CNFGLUNM
SOURCE(S): N/A
PROBLEM: If there is a gap in the LOCADDR values for the SLUs
(ENHANCEMENT) on a TYPE=SPU REMOTE definition statement, commas
must be specified in the LUNAME= operand as place
holders for the unused LOCADDR values.
DESCRIPTION: Normally, the LOCADDR values for SLUs are sequential
but they do not have to be. Gaps in LOCADDR values
in the LUNAME= operand on a TYPE=SPU REMOTE definition
statement require commas to be used as place holders.
For example, the following LUNAME= operand must be
coded for SLUs at LOCADDR=2-3 and LOCADDR=10.
1
1 2 3456789 0 <- LOCADDR values
LUNAME=(,slunm2,slunm3,,,,,,,slunm10)
This can be cumbersome and can result in the wrong
LOCADDR values being used if care is not taken when
coding the comma place holders.
SOLUTION: The HNAS configuration process has been modified to
accept a decimal gap count in place of repetitive
commas which makes it less likely to configure an
SLU at the wrong LOCADDR entry. For the example
above, the LUNAME= operand would be coded as
follows:
1
1 2 34-9 0 <- LOCADDR values
LUNAME=(,slunm2,slunm3,6,slunm10)
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).
05-12-2004 - APAR 2300032
APAR: 2300032
STATUS: CLOSED
OPEN_DATE: 05-11-2004
CLOSE_DATE: 05-12-2004
SERVICE(S): CONSOLE - REMOTE SUPPORT
MANDATORY: YES
ORIGIN/REF: 230_CP
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300032.ZIP file)
COREQ(S): N/A
PREREQ(S): APAR 2300027
OBJECT(S): NASUTIL
SOURCE(S): N/A
PROBLEM: A Reset 05/27 loop condition can occur after the
initial console prompting message is sent to a
remote console user after the password exchange.
DESCRIPTION: Due to logic introduced by APAR 2300022, the console
prompting message has been changed from the extended
form WTOR to a short form WTOR. When the short form
WTOR is converted into a packet that is sent to a
remote console, it is treated as a long form WTOR.
This can result in an invalid packet size being
transmitted. The invalid packet size causes a Reset
to be returned to HNAS by the router. Because HNAS
attempts to resend the same invalid packet with a
new PR/PS, a loop results which only stops when the
console connection is broken.
SOLUTION: The HNAS WTOR remote console interface routine was
modified to properly convert the short form WTOR
into a packet. This ensures that a valid packet
length will be used and prevents the Reset loop
condition.
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).
05-12-2004 - APAR 2300031
APAR: 2300031 (Problem_ID 2004127A and 2004127B)
STATUS: CLOSED
OPEN_DATE: 05-06-2004
CLOSE_DATE: 05-12-2004
SERVICE(S): QLLC SUPPORT
MANDATORY: YES
ORIGIN/REF: 230_IZB
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300031.ZIP file)
COREQ(S): N/A
PREREQ(S): APAR 2300018, 2300030
OBJECT(S): MCHBFR, MCHRL3RR, QLSSCP
SOURCE(S): N/A
PROBLEM: 1) Following message issued, QLLC session hangs:
NAS7601W MCH mch-nm LU lu-nm DECODE RC=20
TH/RH=2C000102 00010BB0 A0021030 3C1280C6
2) 0198 ABEND (NASHALT) can occur when QLLC callout
is BIND initiated (OPTIONS=CLOTINITYP=BIND).
DESCRIPTION: 1) HNAS is unable to decode a formatted FMD request
or response from the SLU in a QLLC session. When
this happens, the NAS7601W message is issued and
the PIU is discarded.
2) NASHALT can occur if OPTIONS=CLOTINITYP=BIND is
specified when an ACTLU response is received for an
SLU that is in BIND pending state (LUBST1=LUBSTBN).
Problem occurs because the BIND remembrance field
(LUSVFREQ=LURQBIND) is only set in the LU control
block for the SLU whose BIND initiated the Call
Request.
When the ACTLU response is received, HNAS performs
a validity check and if LUBST1=LUBSTBN is set but
LUSVFREQ<>LURQBIND, the NASHALT is issued.
SOLUTION: 1) HNAS changed to pass the FMD PIU it can't decode to
the PLU.
2) The callout initiator has been modified to set
LUSVFREQ=LURQBIND for all SLUs on the SPU if a BIND
is received during the callout procedure.
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).
05-12-2004 - APAR 2300030
APAR: 2300030 (Problem_ID 2004120A)
STATUS: CLOSED
OPEN_DATE: 04-29-2004
CLOSE_DATE: 05-12-2004
SERVICE(S): QLLC SUPPORT
MANDATORY: YES
ORIGIN/REF: 230_SNC
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300030.ZIP file)
COREQ(S): N/A
PREREQ(S): APAR 2300028
OBJECT(S): QLSSCP
SOURCE(S): N/A
PROBLEM: Printer SLU cannot be bound.
DESCRIPTION: HNAS will OPEN the ACB for an SLU when an applid
value is associated with the SLU in the LUNAME=
operand (dedicated PLU support) or when input is
received from the SLU as part of LOGON processing.
Since printers cannot enter input, there is no way
to OPEN its ACB to accept a BIND unless an applid
is specified. However, this will restrict the
printer SLU to one PLU application only. Printers
are generally shared among multiple applications.
SOLUTION: The QLLC ACTLU response and NOTIFY request logic has
been modified to OPEN the ACB for an SLU and wait
for a BIND if the applid index value associated with
the SLU identifies the keyword 'ACQUIRE' in the
APPLNAME= operand on the TYPE=SPU REMOTE definition
statement. This will place the SLU in a state that
will allow it to be bound. Note that the keyword
ACQUIRE becomes a reserved keyword like MCHSOL and
CONSOLE and thus cannot be the name of a real PLU
application.
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).
05-12-2004 - APAR 2300029
APAR: 2300029 (Problem_ID 2004112A)
STATUS: CLOSED
OPEN_DATE: 04-21-2004
CLOSE_DATE: 05-12-2004
SERVICE(S): QLLC SUPPORT
MANDATORY: NO
ORIGIN/REF: 220_ITL
PTF_TYPE: (SRC) HNASMACX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300029.ZIP file)
COREQ(S): N/A
PREREQ(S): APAR 2300010
OBJECT(S): N/A
SOURCE(S): VTMTR and VTMUT1
PROBLEM: The wrong MCH name can be displayed in the NAS3798I
message and logged in the HNAS trace table when an SLU
ACB is opened for an SPU with OPTIONS=CLOTINITYP=BIND.
DESCRIPTION: When OPTIONS=CLOTINITYP=BIND is specified for a
TYPE=SPU REMOTE definition statement, the ACB for all
SLUs on the SPU are opened when the OPTIONS=MCHTMR=
value expires for the first MCH in the CDF. This
MCH may or may not be related to the SPU in question.
Hence, using it's name in the NAS3798I message and
HNAS trace table entry can be misleading.
SOLUTION: When an SLU ACB is opened for a TYPE=SPU REMOTE
definition statement with OPTIONS=CLOTINITYP=BIND,
the MCH name and active connection count are
displayed as asterisks (********).
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).
05-12-2004 - APAR 2300028
APAR: 2300028 (Problem_ID 2004112A)
STATUS: CLOSED
OPEN_DATE: 04-21-2004
CLOSE_DATE: 05-12-2004
SERVICE(S): QLLC SUPPORT
MANDATORY: YES
ORIGIN/REF: 220_ITL
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300028.ZIP file)
COREQ(S): N/A
PREREQ(S): N/A
OBJECT(S): MCHNRQC and QLSSCP
SOURCE(S): N/A
PROBLEM: Application connection via INIT-SELF or user LOGON
data can fail.
DESCRIPTION: LOGON data from INIT-SELF PIU is being truncated
resulting in missing data being passed to VTAM
causing eventual session connect failure. HNAS
extracts the PLU name from the INIT-SELF PIU and
passes it to VTAM in the REQSESS request. HNAS
ignores any other data that may be present.
In addition, a REQSESS failure due to an invalid PLU
application name or invalid LOGON data carried in an
INIT_SELF or via USSTAB processing causes subsequent
logon attempts to fail. REQSESS failure forces the
LU to be deactivated (DACTLU) but does not close the
LU ACB. When a subsequent connection is attempted,
the ACB open routine is called, but because the
LU ACB is still open, the OPEN fails with RC=0858
and USSMSG7 is transmitted before the DACTLU occurs.
Problem was seen when INIT_OTHER_CD was processed.
A subsequent OPEN (via a new connection) can also
fail when a REQSESS timeout occurs because, like the
REQSESS failure, a DACTLU is scheduled but the LU ACB
is left open. Furthermore, a REQSESS timeout can be
actually be inhibited if an FMD response is received
after the REQSESS has been been passed to the PLU.
SOLUTION: The INIT-SELF PIU processing logic has been modified
so that all data is passed to VTAM in the REQSESS
request.
The REQSESS failure routine has been modified to
close the LU ACB before the DACTLU is scheduled.
This will allow subsequent login attempts that
reopens the ACB to work properly.
The SLU/SSCP FMD response processor has been modified
to only reset the SLU clock if a response timeout is
running. This will allow a possible REQSESS timeout
to be left running. The REQSESS timeout processor
has been modified to close the LU ACB before a
DACTLU is scheduled. This will allow subsequent
login attempts that reopen the ACB to work properly.
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).
05-07-2004 - APAR 2300027
APAR: 2300027
STATUS: CLOSED
OPEN_DATE: 05-06-2004
CLOSE_DATE: 05-07-2004
SERVICE(S): CONSOLE SUBSYSTEM
MANDATORY: NO, BUT RECOMMENDED
ORIGIN/REF: 230_BNP
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300027.ZIP file)
COREQ(S): N/A
PREREQ(S): APAR 2300026 (and associated APARs PREREQ chains)
OBJECT(S): NASUTIL
SOURCE(S): N/A
PROBLEM: The NAS3798I and NAS3799I alarms are not displayed on
the SYSCONS even when the SHOWON option is in affect.
DESCRIPTION: The HNAS WTO interface prevents informational alarm
messages from being written to SYSCONS if SHOWERR
(the default) is in affect. When SHOWON is set, all
alarm messages are supposed to be written to SYSCONS.
The problem occurs because the WTO interface tests
for the absence of the SHOWERR option instead of the
presence of the SHOWON option. These options are
mutually exclusive.
SOLUTION: HNAS WTO interface logic has been modified to bypass
the test for informational alarms when the SHOWON
option is in affect rather than when the SHOWERR
option is not in affect.
NOTE: The NAS3798I and NAS3799I alarm messages are designed
to be written to SYSCONS and SYSPRINT unconditionally
regardless of the state of the SHOW option. This
will be the case after this APAR is applied.
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).
05-06-2004 - APAR 2300026
APAR: 2300026
STATUS: CLOSED
OPEN_DATE: 04-08-2004
CLOSE_DATE: 05-06-2004
SERVICE(S): CONSOLE SUBSYSTEM
MANDATORY: NO, BUT RECOMMENDED ENHANCEMENT
ORIGIN/REF: 230_SWC
PTF_TYPE: (OBJ) HNASOBJX and (SRC) HNASMACX members
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300026.ZIP file)
COREQ(S): N/A
PREREQ(S): APAR 2300022 (and associated APARs PREREQ chains)
OBJECT(S): CNFGNSNM, CONSDPRM, CONSHELP, CONSPWTO and NASUTIL.
SOURCE(S): NASMAIN and XFNASWA.
PROBLEM: You are currently able to prefix alarm messages and
(ENHANCEMENT) console output with the NASNAME= operand value only.
DESCRIPTION: Currently, the PFXWTO option allows alarm messages
and console output to be prefixed with the NASNAME=
operand value only. Some customers prefer a unique
message id for automation purposes. This will make
it easier to route and filter console command output
from NetView.
SOLUTION: HNAS logic has been modified for the new 'PFXWTO text'
start parameter and console command so that all WTOs
can be prefixed with a unique text value other than
the NASNAME= operand value. This will allow NetView
to capture console output using the ASSIGN command
with the MSG= operand set equal to the text value.
You will be able to specify up to 8, non-blank
characters.
SYNTAX: The following prefix and WTO options are valid for
Start Parameters PARM= and Console Command input.
- 'PFXWTO text' <- special prefix for ALARM WTOs.
String 'PFXWTO text' will be treated as 'PFXWTO ON'
in addition to setting the WTO prefix text. This
will cause prefixing of alarm WTOs only. If you
want console output to be prefixed you will also
require:
- 'PFXWTO CONS ON'
String 'PFXWTO CONS ON' will also need to be coded
if you also want console output to be prefixed with
the text value.
- 'PFXWTO text', 'PFXWTO OFF', 'PFXWTO CONS'
String 'PFXWTO text','PFXWTO OFF','PFXWTO CONS'
must be coded if you only want console output
to be prefixed with the text value.
If PFXWTO is specified without the text argument,
the NASNAME= operand value will be used as the
default WTO prefix text.
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).
05-05-2004 - APAR 2300025
APAR: 2300025
STATUS: CLOSED
OPEN_DATE: 05-04-2004
CLOSE_DATE: 05-05-2004
SERVICE(S): CONSOLE - SHOW CONS ON problem
MANDATORY: YES
ORIGIN/REF: 230_CP
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300025.ZIP file)
COREQ(S): N/A
PREREQ(S): APAR 2300022
OBJECT(S): NASUTIL
SOURCE(S): N/A
PROBLEM: An 0C1 ABEND can occur after the SHOW CONS ON console
command is issued.
DESCRIPTION: Due to logic introduced by APAR 2300022, an 0C1 ABEND
can occur after the SHOW CONS ON console command is
entered. This occurs because the console prompting
message was changed by APAR 2300022 from a long form
to a short form WTO. Unfortunately, the SHOW CONS
ON logic was not also modified for the new prompting
message format. The result is that a long form WTO
call is issued for a short form WTO which results in
a memory overlay and hence the ABEND.
SOLUTION: The HNAS WTO interface routine has been modified to
check for the short form WTO so that a short form
WTO call will be issued.
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).
05-04-2004 - APAR 2300024
APAR: 2300024 (Problem_ID 2004119A)
STATUS: CLOSED
OPEN_DATE: 04-28-2004
CLOSE_DATE: 05-04-2004
SERVICE(S): LLC0 and LLC5 Callout Support
MANDATORY: YES
ORIGIN/REF: 230_CIN
PTF_TYPE: (OBJ) HNASOBJX members
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300024.ZIP file)
COREQ(S): N/A
PREREQ(S): N/A
OBJECT(S): VCCLEAR , MCHHL0RQ and MCHHL5RQ .
SOURCE(S): N/A
PROBLEM: HNAS User 198 ABEND with the message:
HALT AT LOC xxxxxxxx IN XOTBXM: INV VC
when LLC 0 or LLC 5 callout fails.
DESCRIPTION: Event Sequence:
PLU BINDs an HNAS LLC0/5 callout LU.
HNAS sends call request packet to network.
PLU sends first FMD request (request held by HNAS
because there is, as yet, no session).
Remote rejects call with CLEAR.
HNAS (incorrectly) sends -RSP to the PLU's FMD.
The -RSP should not be sent because if multiple
RTEOUT= entries are coded or if multiple DTE
callout addresses are coded for the LU then the
FMD could be sent if a call succeeds.
HNAS schedules new call (multiple RTEOUT= entries).
PLU UNBINDs (because of the -RSP).
HNAS detaches VC and LU but (incorrectly) leaves
call request pending in VC. Call request packet
builder detects a validity check when a VC with a
call request has no LU (required to supply called
DTE address).
SOLUTION: HNAS changed to leave a PLU FMD request pending
until all callout paths have been tried. UNBIND
logic changed to abort a pending call request.
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).
05-04-2004 - APAR 2300023
APAR: 2300023
STATUS: CLOSED
OPEN_DATE: 04-29-2004
CLOSE_DATE: 05-04-2004
SERVICE(S): QLLC CALLOUT PROCESSING (OPTIONS=CLOTINITYP=BIND)
MANDATORY: YES, IF QLLC CALLOUT IS USED
ORIGIN/REF: 230_IZB
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300023.ZIP file)
COREQ(S): N/A
PREREQ(S): APAR 2300011
OBJECT(S): MCHBFR
SOURCE(S): N/A
PROBLEM: HNAS can ABEND with 0C4 when QLLC BIND initiated
callout is used.
DESCRIPTION: When OPTIONS=CLOTINITYP=BIND is in affect for a
TYPE=SPU REMOTE definition statement, HNAS will
condition all SLUs on the SPU to accept a BIND
request. The first SLU that is bound causes a
QLLC VC to be allocated and a Call Request to
be transmitted. The routine that schedules the
Call Request installs a pointer to the VC control
block within the LU control block (LUVC) but this
pointer is being corrupted. The 0C4 ABEND occurs
when the VC control block (addressed via LUVC) is
used because the LUVC pointer contains an invalid
address (40404040).
SOLUTION: The HNAS QLLC BIND callout initiator has been
corrected to save the correct VC control block
address in the LUVC.
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).
05-03-2004 - APAR 2300022
APAR: 2300022
STATUS: CLOSED
OPEN_DATE: 04-30-2004
CLOSE_DATE: 05-02-2004
SERVICE(S): CONSOLE - WTOR SUPPORT (NON-USEMDFY)
MANDATORY: NO, BUT RECOMMENDED
ORIGIN/REF: 220_POR
PTF_TYPE: (OBJ) HNASOBJX and (SRC) HNASMACX members
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300022.ZIP file)
COREQ(S): N/A
PREREQ(S): APAR 2300004, 2300019 and 2300021
OBJECT(S): CNFGCNPR, CONSMMEM, CONSQUIT, NASCONS and NASUTIL
SOURCE(S): XFBLK and XFWTO
PROBLEM: Two WTO replies are outstanding when HNAS starts when
USEMDFY parameter is not specified.
DESCRIPTION: Due to logic introduced by APAR 2300004, 2 WTO replies
will be outstanding after HNAS starts because the
reply from the DMAP APAR command is not remembered
after HNAS initialization completes. The result is
that a second console WTOR prompt is issued.
SOLUTION: The HNAS WTO interface routine has been modified to
withhold the WTOR that is issued as part of the
DMAP APAR command. This will allow only one WTOR
to be issued after HNAS initialization completes.
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).
04-22-2004 - APAR 2300021
APAR: 2300021 (PROBLEM_ID 2004105A)
STATUS: CLOSED
OPEN_DATE: 04-08-2004
CLOSE_DATE: 04-22-2004
SERVICE(S): CONSOLE SUBSYSTEM - PING COMMAND
MANDATORY: YES
ORIGIN/REF: 230_SWT
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300021.ZIP file)
COREQ(S): N/A
PREREQ(S): APAR 2300012, 2300017 and 2300019
OBJECT(S): CONSPING and NASUTIL
SOURCE(S): N/A
PROBLEM: PING command does not process the called DTE address
override value properly when an IP address argument
is omitted.
DESCRIPTION: APAR 2300012 was generated to correct an error that
allows a DTE address override to be specified without
an IP address comma place holder.
In some cases, the first character of the override
DTE address is being clipped before the DTE address
is decoded which causes the first character to be
deleted and the DTE address length to be reduced
by one.
SOLUTION: The PING command decode logic has been modified to
prevent the first character of the override DTE
address from being deleted.
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).
04-21-2004 - APAR 2300020
APAR: 2300020
STATUS: CLOSED
OPEN_DATE: 04-20-2004
CLOSE_DATE: 04-21-2004
SERVICE(S): LLC0|LLC3|LLC5 - HNAS CONFIGURATION PROCESSING
MANDATORY: YES, IF USSTABs AND/OR LOGTABs ARE REQUIRED
ORIGIN/REF: 220_GME
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300020.ZIP file)
COREQ(S): N/A
PREREQ(S): N/A (APAR 2200076 integrated into 230 base release)
OBJECT(S): CNFGLGTB and CNFGUSTB
SOURCE(S): N/A
PROBLEM: The LOGTAB and USSTAB for a TYPE=MXT REMOTE definition
statement are not resolved.
DESCRIPTION: The LOGTAB= and USSTAB= operands on a TYPE=MXT REMOTE
definition statement are not being resolved. Current
logic tests to ensure that MCHSOL was specified as
one of APPLNAME= operand values before testing the
LOGTAB= and USSTAB= operands. Problem occurs because
APPLNAME= is not a valid TYPE=MXT operand but LOGTAB=
and USSTAB= are.
This bug was introduced into the 230 base code when
APAR 2200076 was developed.
SOLUTION: The HNAS configuration process has been corrected
to bypass the APPLNAME=MCHSOL test for a TYPE=MXT
REMOTE definition statement thus allowing the
LOGTAB= and USSTAB= operands to be resolved.
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).
04-19-2004 - APAR 2300019
APAR: 2300019
STATUS: CLOSED
OPEN_DATE: 04-02-2004
CLOSE_DATE: 04-19-2004
SERVICE(S): GENERAL CLEANUP/MINOR FIXES:
CDF PROCESSING, CONSOLE SUBSYSTEM AND ALARM FILTERING
MANDATORY: NO, BUT RECOMMENDED
ORIGIN/REF: 230_CP
PTF_TYPE: (OBJ) HNASOBJX and (SRC) HNASMACX members
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300019.ZIP file)
COREQ(S): N/A
PREREQ(S): APAR 2300005 and 2300016
OBJECT(S): CNFGAFLT, CNFGSYSL, CONSDMAP, CONSDMCH, NASCONS and
NASUTIL
SOURCE(S): XFBLK and XFIDR
PROBLEMS: 1) The ALRMFLTR= operand value is not always being
propagated to the local console.
2) An omitted SYSL= operand generates a warning message
even when all LUs defined for a REMOTE are wired to
an application.
3) A LOAD failure for a USSTAB= or LOGTAB= operand
will cause the FASTRUN process to bypass AMNF
creation.
4) The DMCH FMT3 command issued from a remote console
generates the 'DECODE FAILURE' error message rather
than the 'UNSUPPORTED FUNCTION' error message.
5) The DMAP module command shows module name, address,
size and APARs applied but does not show assembly
date.
DESCRIPTIONS: 1) When ALRMFLTR=(PURGE) is specified, the local
console PCE still defaults to ALRMFLTR=(ALLOW).
This is due to the fact that the ALRMFLTR= operand
value is only propagated when filters are present.
When a default disposition (first suboperand) only
is specified, the value is not propagated.
2) When all LUs defined in the SVCi= operand for
an MCH or the LUNAME= operand for an SPU have
dedicated applid values, there is no need for a
SYSL= operand. The configuration process fails
to detect this condition and issues a warning
message. Specifying a dummy SYSL= operand value
is a way to circumvent the warning message.
3) If a USSTAB= or LOGTAB= operand value identifies a
module that is not present in the VTAMLIB dataset,
the LOAD will fail and a NAS1052E error message
will be generated. Because the message severity
is 'E', HNAS will terminate after the CDF has been
completely scanned. If this error occurs during
a FASTRUN execution, the AMNF is not produced.
4) See problem 4 above.
5) See problem 5 above.
SOLUTIONS: 1) The ALRMFLTR= operand processor has been corrected
to propagate the ALRMFLTR= operand even when only
one value (the default disposition) is specified.
2) The SYSL= operand processor has been modified to
interrogate the SVCi= operands on an MCH and the
LUNAME= operand on an SPU so that the omitted
SYSL= operand warning message is withheld if all
LUs have a dedicated application connection.
3) The HNAS LOAD processor has been modified to set
the NAS1052 message severity from 'E' to 'W' if
the failure occurs during a FASTRUN execution.
This will allow an AMNF to be produced even if the
USSTAB= or LOGTAB= modules are not present in the
VTAMLIB dataset. This change was done so that
FASTRUN tests conducted by Comm-Pro using CDF's
provided by customers will generate an AMNF even
when LOAD failures occur.
4) The DMCH console command processor has been modified
to reject the FMT3 argument (for remote consoles
only) with an 'UNSUPPORTED FUNCTION' error message
rather than 'DECODE FAILURE' error message to more
correctly identify the reject reason.
5) The DMAP console command processor has been modified
to display the module assembly date after the module
size. This additional information will assist
Comm-Pro with problem determination and resolution.
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).
04-16-2004 - APAR 2300018
APAR: 2300018 (PROBLEM_ID 2004098A)
STATUS: CLOSED
OPEN_DATE: 03-25-2004
CLOSE_DATE: 04-16-2004
SERVICE(S): QLLC
MANDATORY: YES
ORIGIN/REF: 230_CIN-(220_ITL)
PTF_TYPE: (SRC and OBJ) HNASOBJX and HNASMACX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300018.ZIP file)
COREQ(S): N/A
PREREQ(S): N/A
OBJECT(S): MCHHL3RQ, MCHRL3RR, MCHHRQ
SOURCE(S): VTMSND1, VTMSND2
PROBLEM: HNAS does not treat the sequence BIND, UNBIND (bind
forthcoming), BIND correctly. The new session
(second BIND) fails in various ways. Additionally,
if a QLLC LU has an application index (i.e. dedicated
PLU) HNAS sends USSMSG 10 after an UNBIND instead
of starting a new session with the PLU.
UNBIND bind forthcoming is created by CLSDST
OPTCD=PASS. VTAM error messages will refer to this
operation.
DESCRIPTION: See problem.
SOLUTION: HNAS modified to treat the CLSDST OPTCD=PASS sequence
properly and to reconnect to the PLU after an UNBIND
is processed for a QLLC LU with an application index.
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).
04-15-2004 - APAR 2300017
APAR: 2300017
STATUS: CLOSED
OPEN_DATE: 04-02-2004
CLOSE_DATE: 04-15-2004
SERVICE(S): TCPIP SUPPORT - TAP PROCESSING
MANDATORY: NO, BUT RECOMMENDED
ORIGIN/REF: 230_SWC
PTF_TYPE: (OBJ) HNASOBJX and (SRC) HNASMACX members
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300017.ZIP file)
COREQ(S): N/A
PREREQ(S): APAR 2300008 and 2300009
OBJECT(S): NASUTIL
SOURCE(S): NASTCP
PROBLEM: HNAS TAP TCPIP socket can close prematurely (prior
to delivery of TAP request) when a firewall or router
open socket timer expires before the TAP=seconds
value.
DESCRIPTION: Existing TAP logic opens a TCPIP socket then waits
for the TAP timeout value to expire before sending
the TAP request (XOT Call Request or Clear Request
if the TAPWITHCLR option is in affect). If the
target router is behind a firewall, the firewall
can close the socket before the TAP request is
actually sent (the firewall starts a data timer when
the socket is opened and if the data timeout interval
is shorter than the TAP value, the timeout condition
will occur). This condition may also occur with some
router configurations although firewall timers values
are typically shorter than the router default timer
values. When the socket is closed prematurely it
will void out the TAP processing and may lead to a
HNAS Keep Alive failure although this wasn't observed.
SOLUTION: HNAS TAP logic has been modified to defer opening the
TAP socket until the TAP timeout value expires and
the TAP request is ready to send. This eliminates
all delays between socket opening and data transfer.
This will ensure that firewall data transfer timeouts
or router open socket timeouts will not occur.
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).
04-14-2004 - APAR 2300016
APAR: 2300016
STATUS: CLOSED
OPEN_DATE: 04-13-2004
CLOSE_DATE: 04-14-2004
SERVICE(S): LOCAL CONSOLE SUBSYSTEM ENHANCEMENT
MANDATORY: NO, BUT RECOMMENDED
ORIGIN/REF: 230_BNP
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300016.ZIP file)
COREQ(S): N/A
PREREQ(S): N/A
OBJECT(S): CONSDLU, CONSDMCH and CONSHELP
SOURCE(S): N/A
PROBLEM: The DMCH command displays MCHs but not the LUs
(ENHANCEMENT) on the MCHs.
DESCRIPTION: See problem description above.
SOLUTION: HNAS logic has been changed so that the DMCH FMT3
command automatically executes the DLU command after
the DMCH command completes so that LUs associated
with the displayed MCHs are also displayed.
This command isn't currently supported for remote
console sessions.
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).
04-13-2004 - APAR 2300015
APAR: 2300015
STATUS: CLOSED
OPEN_DATE: 04-08-2004
CLOSE_DATE: 04-13-2004
SERVICE(S): Multi-LOCAL Support, TCPIP CNFG.
MANDATORY: YES
ORIGIN/REF: 230_RBS
PTF_TYPE: (OBJ) HNASOBJX MEMBER
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300015.ZIP file)
COREQ(S): N/A
PREREQ(S): N/A (2200075 logic integrated in the 230 base release)
OBJECT(S): CNFGIPAD
SOURCE(S): N/A
PROBLEM: Users unable to define multiple LOCAL definition
statements with the same IPADDR= and PORT= operand.
DESCRIPTION: When multiple LOCAL definition statements with the
same IPADDR= and PORT= operand values are specified,
the following error message is generated and HNAS
terminates after the CDF has been entirely scanned:
NAS1321E REMOTE IPADDR/PORT DUPLICATED,
INVALID CONFIGURATION
Some customers use 2 LOCAL statements with identical
IPADDR= and PORT= operand values but different names
in order to be able to use 2 different RTEOUT=
operands without providing any DTE address values.
Each RTEOUT= operand points at different routers.
One router can be used for ISDN and the other for
X.25 traffic. In this way, the selected SLUNAME
determines if the outgoing call is leaving via
ISDN or X.25.
With APAR 2200075 applied, LOCAL resources will
fail to activate if a previously defined LOCAL has
the same IPADDR= and PORT= operand values and
the TCPIP SHAREPORT option is not in affect. This
will result in the following alarm message being
generated:
NAS2231W SERVER=... NAME=local-name
NAS2231I BIND REQUEST FAILED, RC=FFFFFFFF 00000030
SOLUTION: The HNAS configuration process has been corrected
to restore the original logic prior to APAR 2200075
which allows multiple LOCALs with the same IPADDR=
and PORT= operand values. This requires that the
SHAREPORT option must be specified in the TCPIP
PROFILE.
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).
04-07-2004 - APAR 2300014
APAR: 2300014
STATUS: CLOSED
OPEN_DATE: 04-06-2004
CLOSE_DATE: 04-07-2004
SERVICE(S): PVC - HNAS CONFIGURATION PROCESSING
MANDATORY: YES, IF PVC SUPPORT IS REQUIRED
ORIGIN/REF: 230_NBG
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300014.ZIP file)
COREQ(S): N/A
PREREQ(S): N/A
OBJECT(S): CNFGSVC0, CNFGSVC3 and CNFGSVC5
SOURCE(S): N/A
PROBLEM: The following HNAS configuration error messages can
be generated when SVCi=NONE is specified or when the
SVCi= operand is omitted even though LLCi VCs are
defined in the PVC= operand (i=0|3|5).
NAS1311E REMOTE SVCi=NONE INVALID, REQUIRED FOR xxxx
NAS1301E REMOTE SVCi OMITTED, REQUIRED FOR xxxx
DESCRIPTION: The configuration processor fails to account for the
fact that LLCi VCs can be specified in the PVC=
operands making the SVCi= operands optional rather
than required.
This problem was observed in an HNAS XOT environment
with no TYPE=MCH REMOTE SVC resources defined.
SOLUTION: The HNAS configuration process has been corrected to
allow SVCi=NONE to be specified or the SVCi= operand
to be omitted if an LLCi VC is identified in the PVC=
operand.
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).
04-06-2004 - APAR 2300013
APAR: 2300013
STATUS: CLOSED
OPEN_DATE: 04-06-2004
CLOSE_DATE: 04-06-2004
SERVICE(S): LLC3 - HNAS CONFIGURATION PROCESSING
MANDATORY: YES, IF USSTABs AND/OR LOGTABs ARE REQUIRED
ORIGIN/REF: 220_ITL_(2200082)
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300013.ZIP file)
COREQ(S): N/A
PREREQ(S): N/A
OBJECT(S): CNFGAPNM
SOURCE(S): N/A
PROBLEM: The USSTAB for a TYPE=SPU REMOTE definition statement
is not always resolved (problem introduced with APAR
2200076/230_base).
DESCRIPTION: When the APPLNAME= operand is omitted from a TYPE=SPU
REMOTE definition statement, MCHSOL is assumed.
MCHSOL is required to process the USSTAB= and LOGTAB=
operands. However, the remembrance of MCHSOL is only
set when it is specifically coded in the APPLNAME=
operand and not when it is set by default.
CIRCUMVENTION: Specify APPLNAME=MCHSOL instead of omitting the
APPLNAME= operand when the USSTAB= and/or LOGTAB=
operands are specified for a TYPE=SPU REMOTE
definition statement.
SOLUTION: The HNAS configuration process has been corrected
to set the MCHSOL remembrance when the APPLNAME=
operand is omitted for a TYPE=SPU REMOTE 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).
04-04-2004 - APAR 2300012
APAR: 2300012
STATUS: CLOSED
OPEN_DATE: 04-01-2004
CLOSE_DATE: 04-03-2004
SERVICE(S): CONSOLE SUBSYSTEM - PING COMMAND
MANDATORY: YES
ORIGIN/REF: 230_POR
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300012.ZIP file)
COREQ(S): N/A
PREREQ(S): APAR 2300008
OBJECT(S): CONSPING and CONSHELP
SOURCE(S): N/A
PROBLEM: PING command is rejected when a DTE address is entered
without IP address to override the default value set
by the CLDADDR= modifier.
DESCRIPTION: As documented, the PING command has the following
basic format (XOT PING shown):
{IPADDR=a.b.c.d(port)}
{CLDADDR=ddd...ddd}
{CLGADDR=ddd...ddd} PING {XOT}
a.b.c.d(port)
ddd...ddd
The modifiers on the left side of the PING command
set defaults for the positional arguments on the right
side of the command so that PING can be entered with no
arguments (XOT is the default protocol).
The problem occurs when you attempt to override the
default called DTE address. The HNAS documentation
says that you should enter PING , ddd...ddd to override
the CLDADDR= modifier. The comma is a place holder
for the IP address which is not being overridden.
Unfortunately, this syntax causes the PING command to
be rejected and the following message to be issued.
NASC522E INPUT DATA INVALID, REQUIRED
The problem is that the PING command fails to establish
the default protocol when the IP address argument is
omitted. Entering PING XOT , ddd...ddd eliminates the
error and allows the default called DTE address to be
overridden. However, having to specify the protocol
in this instance defeats the purpose of having default
values.
SOLUTION: The PING command decode logic has been modified to
set the default protocol to XOT when the called DTE
address argument is entered without an IP address.
In addition, the comma place holder is no longer
required but can be entered if desired. This will
allow the PING command to operate as previously
documented.
The HELP command for PING (PING ? or HELP PING) has
also been modified to reflect the corrected command
syntax as follows:
COMMAND DESCRIPTION (* => PRIVILEGED)
PING *PING REMOTE ROUTER AND/OR MCH LINK
ENTER> {IPADDR=aaa.bbb.ccc.ddd{(pppp)}}
{CLDADDR=ddd...ddd}
{CLGADDR=ddd...ddd}
{IFN=ifn} {VCN=vcn} PING {{XOT|XTP}}
{aaa.bbb.ccc.ddd{(pppp)}}
{ddd...ddd}
{ifn} {vcn}
NOTE: Right side positional arguments can be used to
override default values set by left side command
modifiers.
XOT is assumed if a protocol is not specified.
If an overriding IP address and DTE address are
both required, the IP address must be specified
first.
If an overriding IP address or DTE address is
required, either can be specified by themselves
(no comma place holder is needed).
The IFN= and VCN= modifiers are only required for
XTP routers. If overriding IFN and VCN arguments
are required without overriding IP and/or DTE
addresses, comma(s) must be used as place holders.
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).
04-01-2004 - APAR 2300011
APAR: 2300011
STATUS: CLOSED
OPEN_DATE: 03-30-2004
CLOSE_DATE: 04-01-2004
SERVICE(S): QLLC SLU UNBIND PROCESSING
MANDATORY: YES
ORIGIN/REF: 230_CP
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300011.ZIP file)
COREQ(S): N/A
PREREQ(S): N/A
OBJECT(S): MCHBFR
SOURCE(S): N/A
PROBLEM: HNAS QLLC SLU UNBIND response processing can be
prematurely terminated.
DESCRIPTION: If the QLLC SLU is already inactive when a PLU UNBIND
is received, the UNBIND response will not be returned
to the PLU and the following alarm message will be
issued:
NAS4705W LU Q1990102 CALLOUT REJECTED, RC=36
Logic introduced with the QLLC callout support
(OPTIONS=CLOTINITYP=BIND) fails to recognize a
response RH as well as a request RH when processing
a PIU build request for an SLU that is being
deactivated. The response PIU build request
is rejected even though it was for the PIU that
initiated the SLU deactivation.
SOLUTION: The PIU builder has been modified to test for a
response RH and, if detected, allow the PIU build
operation to continue without issuing the NAS4705W
message.
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).
04-19-2004 - APAR 2300010
APAR: 2300010
OPEN_DATE: 03-29-2004
CLOSE_DATE: 04-01-2004
REVISED: 04-19-2004
The original distribution of this APAR did not contain
the controls required by the DMAP APAR command. As a
result the command will not show the APAR even though
it is on the system. Distributions after the denoted
revised date contain the text string required by DMAP.
SERVICE(S): Trace Information
MANDATORY: NO, BUT RECOMMENDED ENHANCEMENT
ORIGIN/REF: 230_CP
PTF_TYPE: (SRC) HNASMACX member.
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300010.ZIP file)
COREQ(S): N/A
PREREQ(S): N/A
OBJECT(S): N/A
SOURCE(S): VTMTR
PROBLEM: The trace record created to record receipt on an
(ENHANCEMENT) expedited request from VTAM does not clearly display
the request that was received. In order to determine
the request type information on HNAS internal indexes
and exit routine bit assignments is required.
DESCRIPTION: See Problem.
SOLUTION: HNAS modified to display a trace line identifying the
the requests delivered to the expedited request
processor. The line, which starts with 'COMMAND(S)',
is only displayed when tracing of the HNAS LU is
active and TRCPRNT is set.
With this APAR on the SYSPRINT file can be searched
for strings like BIND, SDT, UNBIND, etc.
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).
03-30-2004 - APAR 2300009
APAR: 2300009
STATUS: CLOSED
OPEN_DATE: 03-30-2004
CLOSE_DATE: 03-30-2004
SERVICE(S): CONSOLE SUBSYSTEM - PFXWTO PROCESSING
MANDATORY: YES
ORIGIN/REF: 220_RBS
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300009.ZIP file)
COREQ(S): N/A
PREREQ(S): APAR 2300004, 2300005, 2300006
OBJECT(S): NASUTIL
SOURCE(S): N/A
PROBLEM: HNAS alarm messages can be truncated causing loss of
display information.
DESCRIPTION: When the PFXWTO option is in affect, HNAS alarm messages
are copied into a WTO area so that the NASNAME= operand
value can be added to the message. The WTO copy area
is 101 bytes in length (which includes space for the
NASNAME= operand value). This can cause messages that
are longer than 91 (101-10) characters in length to be
truncated.
SOLUTION: The copy WTO area has been extended to 126 bytes which
is the WTO macro limit. This will accommodate all
HNAS alarm messages. This change was made to avoid
potential message truncation that was observed in
V2R2M0 (please refer to APAR 2200081).
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).
03-30-2004 - APAR 2300008
APAR: 2300008
STATUS: CLOSED
OPEN_DATE: 03-30-2004
CLOSE_DATE: 03-30-2004
SERVICE(S): CONSOLE SUBSYSTEM - PING COMMAND
MANDATORY: YES
ORIGIN/REF: 230_SWC
PTF_TYPE: (OBJ) HNASOBJX and (SRC) HNASMACX members
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300008.ZIP file)
COREQ(S): N/A
PREREQ(S): APAR 2300002
OBJECT(S): CONSPING
SOURCE(S): NASTCP
PROBLEM: PING command problems.
DESCRIPTION: 1) The IPADDR= and CLDADDR= modifiers, when entered
on the right side of the PING command, do not
override the default values.
The PING command looks at the default (left side)
modifiers rather than the temporary (right side)
modifiers when setting the IP address and called
DTE address values. If the left side IPADDR=
and/or CLDADDR= modifiers are not set, the PING
command will be rejected and the following message
will be generated:
NASC500E DEFAULT PARAMETER OMITTED, REQUIRED
2) An 0198 ABEND can occur when a PING command is
entered. This occurs because of a change that
was made to HNAS just as the V2R3M0 release was
being finalized. A special Process Control
Element (PCE) is required to handle the PING
sequence. The PCE looks similar to the PCE
produced by the REMOTE definition statement but
is slightly different. The failure occurs
because HNAS TCP/IP fails to properly recognize
this difference and treats the PING PCE as a
bad control block.
SOLUTION: 1) PING command decode logic has been modified to
use the right side modifiers rather than the left
side modifiers. This works because the default
values for right side modifiers are set to the
left side modifiers before the PING command is
executed.
2) The PING command processor has been modified to
to treat the PING PCE the same as a REMOTE TCP/IP
PCE.
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).
03-29-2004 - APAR 2300007
APAR: 2300007
STATUS: CLOSED
OPEN_DATE: 03-15-2004
CLOSE_DATE: 03-29-2004
SERVICE(S): CONFIGURATION FASTRUN
MANDATORY: NO, BUT RECOMMENDED ENHANCEMENT
ORIGIN/REF: 220_NMP
PTF_TYPE: (OBJ) HNASOBJX and (SRC) HNASMACX members
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300007.ZIP file)
COREQ(S): N/A
PREREQ(S): APAR 2300006
OBJECT(S): CNFGAPNM and NASCNFG.
SOURCE(S): XFNASWA and XFXTRN.
PROBLEM: The name for the AMNF VBUILD statement, produced by
(ENHANCEMENT) the FASTRUN process, comes from the NASNAME= operand
instead of it's own unique operand.
DESCRIPTION: The FASTRUN process will produce the HNAS AMNF if the
//MAJNODE DD statement is present in the HNAS start
JOB. The name used for the VBUILD statement comes
from the NASNAME= operand when it should come from
its own unique BUILD definition statement operand
for improved flexibility.
SOLUTION: The HNAS configuration process has been modified to
allow the APPLNAME= operand to be coded on the BUILD
definition statement. The APPLNAME= operand will be
used to supply a name for the VBUILD statement in the
AMNF.
If APPLNAME=NONE is specified, the VBUILD statement
will be generated without a name.
If the APPLNAME= operand is omitted, the name for the
VBUILD statement will come from the NASNAME= operand.
If the NASNAME= operand is also omitted, the VBUILD
statement will be generated without a name.
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).
03-29-2004 - APAR 2300006
APAR: 2300006
STATUS: CLOSED
OPEN_DATE: 03-15-2004
CLOSE_DATE: 03-29-2004
SERVICE(S): CONSOLE SUBSYSTEM
MANDATORY: NO, BUT RECOMMENDED ENHANCEMENT
ORIGIN/REF: 230_RWG
PTF_TYPE: (OBJ) HNASOBJX and (SRC) HNASMACX members
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300006.ZIP file)
COREQ(S): N/A
PREREQ(S): APAR 2300005
OBJECT(S): CONSALRM, CONSDPRM, CONSHELP, CONSPWTO and NASUTIL.
SOURCE(S): NASMAIN and XFNASWA.
PROBLEM: Unable to prefix console output with NASNAME= operand
(ENHANCEMENT) value.
DESCRIPTION: Currently, the PFXWTO option only allows Alarm messages
to be prefixed with the NASNAME= operand value. This
makes it difficult to route and filter console command
output from NetView.
SOLUTION: HNAS logic has been modified for the new 'PFXWTO CONS'
start parameter and the PFXWTO CONS console command
so that console command output can be prefixed with
the NASNAME= operand value. This will allow NetView
to capture console output using the ASSIGN command
with the MSG= operand set equal to the NASNAME=
operand value.
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).
03-29-2004 - APAR 2300005
APAR: 2300005
STATUS: CLOSED
OPEN_DATE: 03-15-2004
CLOSE_DATE: 03-29-2004
SERVICE(S): CONSOLE SUBSYSTEM
MANDATORY: NO, BUT RECOMMENDED ENHANCEMENT
ORIGIN/REF: 230_RWG
PTF_TYPE: (OBJ) HNASOBJX and (SRC) HNASMACX members
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300005.ZIP file)
COREQ(S): N/A
PREREQ(S): APAR 2300004
OBJECT(S): CONSDMAP, CONSDPCE, CONSDPRM, CONSDSTS, CONSHELP,
CONSMON, CONSSTAT, CONSTCON, CONSTDBG, NASCONS
and NASUTIL.
SOURCE(S): NASMAIN, SYSLIN, XFBLK, XFMODMAP, XFNASWA, XFPCE
and XFXTRN.
PROBLEM: Tracing console events for diagnostic purposes is
(ENHANCEMENT) difficult.
DESCRIPTION: Currently the only way to trace console events is to
trace console PCE dispatches. This does not easily
allow console events to be isolated. There is a
need to separate console PCE dispatches from other
console related activity.
SOLUTION: HNAS logic has been modified for the new TRCCONS
start parameter and the TRCCONS {ON|OFF} console
command so that console events can be isolated from
other HNAS events.
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).
03-19-2004 - APAR 2300004
APAR: 2300004
STATUS: CLOSED
OPEN_DATE: 03-15-2004
CLOSE_DATE: 03-19-2004
SERVICE(S): CONSOLE SUBSYSTEM
MANDATORY: NO, BUT RECOMMENDED
ORIGIN/REF: 220_CP,2200079
PTF_TYPE: (OBJ) HNASOBJX and (SRC) HNASMACX members
PTF_LOC: FTP Server Directory /hnas_maint/hnas220m/apars/
(Complete FIX is contained in the 2300004.ZIP file)
COREQ(S): N/A
PREREQ(S): N/A
OBJECT(S): CONSDMAP, CONSDNAS, MCHINI, NASCONS and NASUTIL.
SOURCE(S): XFBST, XFNASWA and XFXTRN.
PROBLEM: DMAP APAR command operation and display limitations.
DESCRIPTION: The DMAP APAR command can take a long time to complete
because delays are deliberately introduced so that
other HNAS tasks have an opportunity to run while the
DMAP APAR command executes. Under V2R3M0 with current
maintenance level (2300004) applied, the DMAP APAR
command takes approximately 30 seconds to list all of
the modules containing maintenance. This delay may be
unacceptable for some customers wanting to know all
the maintenance that is on their system.
SOLUTION: HNAS logic has been changed so that the DMAP APAR
command automatically executes at initialization time
with no delays. The output of the command is logged
in the HNAS SYSPRINT so that the maintenance can be
viewed using an SDSF panel.
ADDITIONAL
ENHANCEMENT: Additionally, during the initialization pass, the
DMAP APAR command creates a table that is sorted in
APAR ID order so that it can be displayed using the
new DNAS APAR command.
Note that you can still use the DMAP APAR command
to display APARs but command output is in module name
order rather than APAR ID order. Note also that the
DMAP APAR command issued by the SYSCONS or TSO console
operator will still take approximately 30 seconds to
complete.
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).
03-16-2004 - APAR 2300003
APAR: 2300003
STATUS: CLOSED
OPEN_DATE: 03-16-2004
CLOSE_DATE: 03-16-2004
SERVICE(S): GATE Callout Support
MANDATORY: YES
ORIGIN/REF: 230_BNP
PTF_TYPE: (OBJ) HNASOBJX or ZAP (see below).
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300003.ZIP file)
COREQ(S): N/A
PREREQ(S): N/A
OBJECT(S): XOTUT1
SOURCE(S): N/A
PROBLEM: GATE call requests fail with:
NAS7720W mch-nm CALL OUT, CAN'T CALL CALLED ADDR=addr
CALLING ADDR=0000000000000000
NAS7717W LU lu-nm CALL TO DTE ADDR dte-addr VIA REMOTE
rmtnm FAILED
NAS7717W CAUSE/DIAG=000/130 (00/82) DIAGX=000D
DESCRIPTION: When DCEADDR=d...d and OPTIONS=REPDCEADDR are coded
on an MCH with GATE resources, HNAS should insert the
DCEADDR= operand as the calling DTE address when the
GATE call request packet from the CTCP has no calling
DTE address. Because of a bad test instruction,
REPDCEADDR is ignored for Fast Connect GATE MCHs.
When source (calling address) routing is used in
RTEOUT=, calls will fail because the correct calling
DTE address is not present.
SOLUTION: Incorrect test instruction modified so that the
REPDCEADDR option is properly processed.
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).
ZAP_INFO: The following ZAP will correct this problem:
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* APAR 2300003 - MARCH 16, 2004
* OPTIONS=REPDCEADDR FAILS ON GATE FAST CONNECT CALLOUT
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
NAME HNAS XOTUT1
VER 0BE6 9180,8053
REP 0BE6 9180,8056
/*
03-11-2004 - APAR 2300002
APAR: 2300002
STATUS: CLOSED
OPEN_DATE: 03-11-2004
CLOSE_DATE: 03-11-2004
SERVICE(S): TCP/IP SUPPORT
MANDATORY: YES
ORIGIN/REF: 230_CP
PTF_TYPE: (SRC) HNASMACX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300002.ZIP file)
COREQ(S): N/A
PREREQ(S): N/A
OBJECT(S): N/A
SOURCE(S): NASTCP
PROBLEM: HNAS can ABEND with 0C4 when the LOCAL socket limit
value is displayed in the NAS2601W and NAS2602I
messages.
Note: These messages are new for V2R3M0.
DESCRIPTION: The NAS2601W message is displayed when the number of
allocated TCP/IP sockets for a server reaches 80% of
the SOCLMT= operand value for a HOME LOCAL. The
NAS2601I message is displayed when the number of
allocated TCP/IP sockets for a server falls below 60%
of the SOCLMT= operand value. In both cases, the
register pointing at the SOCLMT= operand value has
been corrupted which results in the 0C4 ABEND when
the value is being formatted. The messages are not
displayed. Normally, The NAS2601W and NAS2602W
messages will be displayed as follows:
NAS2601W SERVER=ipaddr(port) PCEID=dd SOCKID=dd NAME=tt
NAS2601W SOCKET POOL DEPLETED, SOCCNT=dddd SOCLMT=dddd
NAS2602I SERVER=ipaddr(port) PCEID=dd SOCKID=dd NAME=tt
NAS2602I SOCKET POOL RESTORED, SOCCNT=dddd SOCLMT=dddd
SOLUTION: HNAS has been modified so that the register pointing
at the SOCLMT= operand value cannot be corrupted.
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).
03-09-2004 - APAR 2300001
APAR: 2300001 (PROBLEM_ID 2004055A)
STATUS: CLOSED
OPEN_DATE: 02-24-2004/03-08-2004
CLOSE_DATE: 03-09-2004
SERVICE(S): QLLC SUPPORT
MANDATORY: YES, IF QLLC SUPPORT IS REQUIRED
ORIGIN/REF: 2200077,(220_NBG,220_ITL)
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the 2300001.ZIP file)
COREQ(S): N/A
PREREQ(S): N/A
OBJECT(S): NASCNFG
SOURCE(S): N/A
PROBLEM: In 220, HNAS can ABEND with 0C4 if an SPU is defined but
is not referenced in any SVC3= operand.
DESCRIPTION: In 220, an SPU and its SLUs are initialized when HNAS
start logic interrogates all SVC3= operands on all MCHs.
If an SPU is defined in the CDF but is not referenced
in any SVC3= operand, it will not be initialized
correctly. At run time, if the un-initialized SPU is
selected via IDBLK/IDNUM matching, an 0C4 ABEND will
occur because the LU control blocks (LUBs) for the
SLUs defined in the LUNAME= operand for the SPU will
not have been resolved.
If you actually did intend to specify all SPUs in some
SVC3= operand(s) but the record containing the SPU
name was in error, the record will be ignored and the
following warning message will be generated:
NAS1041W DECODE FAILURE, RECORD FOLLOWS
In this case, the SPU identified on the invalid record
will appear undefined in the SVC3= operand and the
result will be the same, that is, the 0C4 ABEND will
occur.
SOLUTION: The HNAS fix for this SPU problem is to force the
configuration process to terminate after the entire
CDF is scanned by changing the severity code in the
NAS1041 message from 'W' to 'E' (NAS1041W -> NAS1041E).
This will allow the problem to be corrected before
an 0C4 ABEND can occur.
NOTE: In 230, all SPUs in the CDF are initialize all
regardless of whether or not they are referenced
in an SVC3= operand. This change is provided to
maintain consistency between 220 and 230
configuration error messages.
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 - July 6, 2005