The individual APAR hyperlink *.ZIP files provide all of the necessary SRC (source) and OBJ (object) updates for the respective PTF. Most APARs have PREREQ(S) as designated in the APAR memos (multiple APAR PTF's may be required to install a particular APAR PTF). If a product refresh or upgrade is required you will need to contact your HNAS support representative to order the appropriate edistribution. HNAS product edistributions are provided via our ftp server and build as requested (e-mail attachment can also be provided upon special request). We suggest that you contact your HNAS support representative to request that an FTP userid account be set-up for your organization if you haven't already done so.
| APAR# | CLOSE_DATE | SERVICE |
PTF_TYPE |
PROBLEM |
|---|---|---|---|---|
|
240nnnn 240nnnn_D 240nnnn_E 240nnnn_M 240nnnn_P 240nnnn_R 240nnnn_U |
yyyy-mm-dd-> |
(blank) Deferred Enhancement Circumvention Pending Refresh Upgrade |
-> -> -> -> -> -> -> |
Denotes a Standard APAR. Fix or Enhancement deferred to a later (future) release. A new function has been added by this APAR. Circumvention is available, see APAR memo. APAR type pending assignment. Refresh up to/above this APAR number has to be installed. Upgrade to denoted HNAS VnRnMn has to be installed. |
| - | - | - | - | - |
| 2400nnn thru 2400086 | <Link forward> | - | - |
HNAS V2R4M0 - 2009 MAINTENANCE SUMMARY (Link to APARs 2400086 thru 2400nnn) |
|
2400085_R |
2008-12-20 |
HNAS Trial Users |
<Refresh, new trial product distributions optionally> |
This Comm-Pro internal APAR was implemented so that the HNAS Trial edistribution could optionally be generated to stop HNAS when the expiration date occurs rather then continue running and not permitting the product to restart once the expiration date occurs. |
|
2400084_E |
2008-12-12 |
Configuration |
OBJ/SRC |
SVC0= and SVC5= decode modified to allow the specification of a GENERIC name in addition to the HNAS APPL SLU name for VTAM (SETLOGON OPTCD=GNAMEADD) support for callout sessions (IMS in this case). |
| 2008-11-26 |
Configuration and Console parameter processing
for |
OBJ/SRC |
This APAR contains fixes for the following conditions: |
|
| 2008-07-07 |
Configuration FASTRUN |
OBJ/SRC |
Customer encounters 0C4-10 ABEND during HNAS FASTRUN processing after upgrading to HNAS maintenance level 2400080. |
|
|
2400081_E |
2008-06-27 |
Configuration |
OBJ/SRC |
New OPTIONS=RESETINO enhancement provides the ability to optionally Clear or terminate the host session when reset packets are received by HNAS from the network/router. |
|
2400080_E |
2008-06-18 |
Cons-Subsystem |
OBJ/SRC |
This APAR contains 3 enhancements and 1 fix for the following
conditions: |
| 2008-05-30 |
Cons-Subsystem |
OBJ |
This APAR contains fixes for the following conditions: |
|
|
2400078_E |
2008-05-20 |
Cons-Subsystem |
OBJ |
This APAR contains a fix for the console DVC VCST field and an
enhancement for the DVC|DLU command output (VCTO): |
| 2008-05-14 |
Configuration |
OBJ |
0198 (NASHALT) ABEND during HNAS start-up initialization due to a configuration resource calculation error when processing SOCLMT=602 and the sum of TYPE=XOT REMOTE VCLMT= values plus the TAP sockets equals 602. |
|
| 2008-05-05 |
GATE |
OBJ |
NAS4709W REMOTE alert message issued due to an unusual sequence where HNAS does not clear the LU input queue when the CTCP sends a Clear packet during an m-bit sequence. |
|
|
2400075_RE |
2008-05-05 |
Cons-Subsystem |
<Refresh |
This APAR contains console enhancements and a fix to the console command
line decode: |
|
2400074_E |
2008-04-23 |
Datafono IDTST=, |
OBJ/SRC |
This APAR contains a collection of enhancements and general maintenance: |
| 2008-04-10 |
QLLC |
OBJ/SRC |
QLLC X25 session terminated when the PLU sends a CLEAR PIU to HNAS. |
|
| 2008-03-18 |
PVC, |
OBJ |
HALT AT LOC 800637E6 IN NASTCP : TCPIP TRANSMIT FAILURE |
|
| 2008-03-13 |
Configuration and Console parameter processing |
OBJ |
Error in Datafono OPTIONS=DATAFAM|DATAF decode causes DATAFM typo to be processed as DATAF while it should generate an error. Note that the decode problem is not limited to the DATAF argument but also affects other operands. |
|
|
2400070_RE |
2008-02-29 |
Cons-Subsystem |
<Refresh |
Enhancement provides improved console command argument input error decoding. |
|
2400069_E |
2008-02-26 |
CALLOUT T21= X25 Level 3
Timer |
OBJ/SRC |
New OPTIONS=SVCCALLTMR=nn|T21=nn enhancement provides the ability to increase the previously fixed (30 second) X25 Level 3 Clear timer preventing potential outbound call request timeout conditions. |
|
2400068_E |
2008-02-12 |
Cons-Subsystem |
OBJ/SRC |
New
OPTIONS=ALRMSGTXT=SHORT|LONG enhancement provides ability to reduce
Trace and Alert message lengths as follows: |
| 2008-02-02 |
Cons-Subsystem |
OBJ |
Remote console password prompt is not displayed until input is entered. Related to APAR 2400066. |
|
| 2008-01-31 |
Cons-Subsystem |
OBJ |
Remote console session connect processing bug can cause HNAS to loop preventing other HNAS tasks from operating. Introduction of APAR 2400064 caused this problem. |
|
| 2008-01-17 |
Cons-Subsystem |
OBJ |
HNAS 0C4 ABEND when starting a remote console session using MCHSOL and USSMSG 0 ("Command Accepted") is specified. |
|
|
2400064_RE |
2008-01-17 |
Cons-Subsystem |
<Refresh |
Enhancement providing ability to schedule console commands that can be
executed automatically at specific times via
|
| - | - | - | - | - |
|
2400063 thru 2400018 |
<Link back> | - | - |
HNAS V2R4M0 - 2007 MAINTENANCE SUMMARY (Link to APARs 2400018 thru 2400063) |
| 2400017 thru 2400000 | <Link back> | - | - |
HNAS V2R4M0 - 2006 MAINTENANCE SUMMARY (Link to APARs 2400000 thru 2400017) |
| - | - | - | - | - |
| 240nnnn_i | yyyy-mm-dd |
GATE/LLCn/ PVC/QLLC/... |
ZAP/SRC/ OBJ/DOC/ CNFG/... |
<-Brief Problem\Enhancement Description-> 240nnnn_i= APAR Type - (blank) Denotes as a Standard APAR. _D - Deferred to a later release. Memo only, no PTF (fix) issued. Corrective logic or support will be provided in a future release. _E - Enhancement-APAR assignment. Denotes enhancement introduced after initial product release date. A new function has been added by this APAR. _M - Circumvention available (C reserved for custom identification). _P - Pending assignment. _R - Refresh edistribution required. To benefit from this APAR, a refresh release, up to this APAR number or most recent, has to be installed. _U - Upgrade required to the designated release. Memo only, no PTF (fix) issued. See link vrmnnnn_i table for an expanded description. |
| - | <Deferred> |
- |
<-> |
Denotes that problem resolution was deferred to a latter release although an apar memo is present describing the problem/reference. |
|
- |
- | <Enhancement> |
<-> |
Depicts an enhancement, not a problem fix. |
Please refer to the X.25 HostNAS (HNAS) Product Notices web page
section HNAS V2R4M0 - Release Status for additional information.
2008-12-23 - APAR 2400085 (was unpublished problem 2008343A)
APAR: 2400085_R
STATUS: CLOSED
OPEN_DATE: 2008-12-08
REVISE_DATE: 2008-12-23 SHIPJOB change, does not affect distribution.
CLOSE_DATE: 2008-12-20
SERVICE(S): HNAS Trial Period Expiration Shutdown Processing
MANDATORY: N/A
ORIGIN/REF: 240_CPT
CPTECH: SFD
PTF_CLASS: UTILITY-APAR
PTF_TYPE: REFRESH
PTF_LOC: N/A - Does not affect existing customers.
COREQ(S): N/A
PREREQ(S): N/A
OBJECT(S): NASUTIL
SOURCE(S): NASMAIN, XFNASWA
PROBLEM: HNAS continues to run after trial period expires as
long as the product isn't restarted.
DESCRIPTION: Effective with APAR 2400085 for trail distributions only,
when the DNAS command output shows a 16-digit SHIPID=
field that starts with a 1 (1xxxxxxxxxxxxxxx) and a
non-zero AUTH=value, it indicates that HNAS will ABEND
when the trial NASAUTH file expires. Conversely, if the
SHIPID= field is not 16 digits in length, HNAS will
continue to run when the trial NASAUTH file expires but
will not be allowed to restart if it is shutdown.
The HNAS trial product was initially designed to not
allow the product to be restarted or activated after the
trial expiration date. There are now some organizations
that require the product to shutdown when the trial
expires.
SOLUTION: SHIPJOB and runtime code modified to provide new option.
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).
2008-12-12 - APAR 2400084 (was problem 2008241A)
APAR: 2400084_E
STATUS: CLOSED
OPEN_DATE: 2008-08-28
CLOSE_DATE: 2008-12-12
SERVICE(S): CNFG/VTAM
MANDATORY: YES (if GENERIC resources used)
ORIGIN/REF: 240_BA2
CPTECH: SFD/prt
PTF_CLASS: ENHANCEMENT-APAR
PTF_TYPE: (OBJ) HNASOBJX and (SRC) HNASMACX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400084.ZIP file)
SMP/E PTFs are provided via user request because the
Comm-Pro supplied MCS is unique to each customer.
COREQ(S): N/A
PREREQ(S): Distribution dated after: 2008-11-26
with APAR: 2400083 applied.
SUPERSEDES: N/A
OBJECT(S): CNFGSVC0 , CNFGSVC5 , CONSDRMT , CONSMRMT , MCHNRQC ,
MCHSVCI , NASCNFG , VCCLEAR , XOTBXM , XOTRCV ,
XOTXMTC
SOURCE(S): VTMSND1 , VTMUT1 , XFNASWA
DESCRIPTION: See PROBLEM
PROBLEM: Customer would like HNAS APPL LUs to be associated
with generic VTAM resource names so the PLU can use
a generic name when acquiring an HNAS LU (to trigger
an X25 callout).
SOLUTION: SVC0= and SVC5= string processors have been modified
to allow the specification of a GENERIC name in
addition to the HNAS APPL SLU name:
e.g. SVC0=(..,LU001+GENNM/...)
The optional generic name (GENNM above) will be sent
to VTAM via (SETLOGON OPTCD=GNAMEADD) after the ACB
associated with the HNAS APPL LU LU001 is opened.
This allows VTAM to acquire the LU001 using the
GENNM generic name.
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).
2008-11-26 - APAR 2400083 (was unpublished problem 2008323B)
APAR: 2400083
STATUS: CLOSED
OPEN_DATE: 2008-11-18
CLOSE_DATE: 2008-11-26
SERVICE(S): TCPIP stack deactivation and SVRSTRT processing.
MANDATORY: YES
ORIGIN/REF: 240_csp, 240_cpt
CPTECH: SFD
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (OBJ) HNASOBJX and (SRC) HNASMACX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400083.ZIP file)
SMP/E PTFs are provided via user request because the
Comm-Pro supplied MCS is unique to each customer.
COREQ(S): N/A
PREREQ(S) APAR 2400081 and associated APAR chains.
SUPERSEDES: N/A
OBJECT(S): CNFGTPNM, NASCNFG, NASUTIL
SOURCE(S): NASTCP, XFBLK, XFNASWA, XFPCE, XFXTRN
OVERVIEW: Problems related to how HNAS handles the SVRSTRT
start parameter when the TCPIP stack is deactivated.
PROBLEM1: The following message can be generated when the
TCPIP stack is deactivated:
NAS7720W BRN1 CALL OUT, CAN'T CALL CALLED
ADDR=F311022081263127 CALLING ADDR=C311022081040000
DESCRIPTION1: The above alert indicates that unmapable addresses were
used or that a PCE could not be found for a callout
operation.
When the SVRSTRT option is not in effect (the default),
HNAS remains active after the stack is taken down when
it should have been shutdown. The message is generated
because HNAS will not reconnect with the stack even
though VTAM sessions are still allowed to come active.
The following TCPIP alerts are also present:
NAS2401W CLIENT=169.165.250.144(01656) SOCKID=0001
PCEID=0009 NAME=BR1XOT
NAS2401W RECEIVE REQUEST FAILED, RC=FFFFFFFF 00000005
(00005)
**** RECEIVE ended with I/O errors.
NAS2401W CLIENT=169.165.250.144(01657) SOCKID=0002
PCEID=000A NAME=BR1XOT
NAS2401W RECEIVE REQUEST FAILED, RC=FFFFFFFF 0000040C
(01036)
**** RECEIVE ended because stack was down.
NAS2102E TCPIP SEVER INDICATED, PATHID=0001
TCPNAME=RCCTCP11
**** Stack down.
Note: Inbound calls will also fail (calls cleared)
under this scenario because the HNAS HOME
server component remains down.
SOLUTION1: When the SVRSTRT option is not specified and the stack
is taken down, HNAS has been modified to shutdown as
the documentation specifies. This will require HNAS
to be restarted when the stack is restarted.
CIRCUMVENTION1: Specify the SVRSTRT option so that HNAS will monitor
the stack for reactivation which will prevent the
callouts and callins from failing.
PROBLEM2: When the SVRSTRT option is omitted and multiple stacks
are defined to HNAS, connections to an active stack can
hang if one stack is stopped.
DESCRIPTION2: When SVRSTRT is omitted and only one stack is defined
to HNAS, HNAS should shutdown (see problem 1). Due to
a logic error, HNAS remains active but will not allow
the stopped stack to restart. In addition, the SVRSTRT
logic erroneously prevents other stacks from continuing
operation. This causes the hang condition.
SOLUTION2: HNAS has been modified to force the SVRSTRT option
when multiple stacks are specified. This will ensure
that an active stack will continue to communicate with
HNAS if another stack is taken down. In addition, it
will allow the deactivated stack to come active again.
The following new configuration message is generated
in this case.
NAS1211D MULTIPLE TCPNAME VALUES SPECIFIED,
SVRSTRT OPTION FORCED
CIRCUMVENTION2: N/A
Note: These 2 problems were introduced into HNAS when
multiple server support was added in February of
2002. During our testing of the multiple server
support, the SVRSTRT option was active and so HNAS
recovered as it was supposed to when one stack
was taken down. Apparently, the same tests were
not performed with the SVRSTRT option omitted nor
did any user report a problem with this option
until November 18, 2008.
We believe that this problem is unusual because
many customers run with the SVRSTRT option or
manually shutdown HNAS whenever the stack is
taken down which will avoid the problem.
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).
2008-07-07 - APAR 2400082 (was unpublished problem 2008188A)
APAR: 2400082
STATUS: CLOSED
OPEN_DATE: 2008-07-05
CLOSE_DATE: 2008-07-07
SERVICE(S): Configuration processing
MANDATORY: YES if FASTRUN is used
ORIGIN/REF: 240_NBK
CPTECH: SFD
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (OBJ) HNASOBJX and (SRC) HNASMACX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400082.ZIP file)
SMP/E PTFs are provided via user request because the
Comm-Pro supplied MCS is unique to each customer.
COREQ(S): N/A
PREREQ(S) APAR 2400080 and associated APAR chains.
SUPERSEDES: N/A
OBJECT(S): CONSDNWD, NASCNFG
SOURCE(S): XFCNFGWA
PROBLEM: Customer encounters 0C4-10 ABEND during HNAS FASTRUN
processing after upgrading to HNAS maintenance level
2400080.
DESCRIPTION: Due to an error introduced by APAR 2400080, FASTRUN
processing ABENDs when the NAS1391I MXT override
messages are being generated. This occurs because the
wrong internal operand indices were assembled for APAR
2400080 which are different than those assembled in
the MXT override modules.
SOLUTION: HNAS configuration processing has been modified so that
the correct internal operand indices are assembled to
match those in the MXT override modules.
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).
2008-06-27 - APAR 2400081 (was unpublished problem 2008156A)
APAR: 2400081_E
STATUS: CLOSED
OPEN_DATE: 2008-06-04
CLOSE_DATE: 2008-06-27
SERVICE(S): RESET, RESETINO Option
MANDATORY: NO
ORIGIN/REF: 240_CSP
CPTECH: PRT
PTF_CLASS: ENHANCEMENT-APAR
PTF_TYPE: (OBJ) HNASOBJX and (SRC) HNASMACX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400081.ZIP file)
SMP/E PTFs are provided via user request because the
Comm-Pro supplied MCS is unique to each customer.
COREQ(S): N/A
PREREQ(S): Distribution dated after: 2008-04-23
With APAR: 2400074 applied.
Refresh recommended if you are below the 2400075 level.
SUPERSEDES: N/A
OBJECT(S): CNFGOPTS CONSDRMT CONSMRMT VCRESET
SOURCE(S): XFNASWA
PROBLEM
ENHANCEMENT: OPTIONS=RESETINO may be specified on a TYPE=MCH REMOTE
to specify processing to occur when HNAS receives a
RESET packet from the remote.
DESCRIPTION: This option causes HNAS to end the PLU session with a
NOTIFY (generated when the LU's. ACB is closed). The
NAS3799I session end message will show "HNAS CAUSE/
DIAG=000/211".
The X25 session that initiated the RESET is also ended
with a CLEAR CAUSE/DIAG=000/211.
This option can be manipulated with console commands:
MRMT mch-name OPTIONS=RESETINO ; set option.
MRMT mch-name OPTIONS=NORESETINO ; resets option.
When RESETINO is in effect:
LLC0 and LLC5 SVCs:
Any inbound RESET terminates the PLU session and ends
the X25 session with CLEAR C/D=000/211.
LLC0 and LLC5 PVCs:
Inbound RESETs with C/D=000/015 or 000/000 are ignored
(these are used by the router to report PVC operational
status). Any other inbound RESET terminates the PLU
session with a NOTIFY. The X25 PVC session remains
active.
LLC3 sessions:
Because an inbound RESET can potentially affect many
PLU sessions HNAS has always terminated all associated
PLU sessions when a reset is received (as above,
C/D=000/015 and 000/015 are excepted for PVC QLLC
sessions).
LLC4 sessions:
An inbound RESET is passed to the GATE PLU where the
processing decision is made.
When HNAS generates a RESET (Outbound) the PLU session
is always taken down (APAR 2300140).
This enhancement was recently requested by a customer
who needed to force a disconnect when their remote
end user equipment generated a reset (mismatch window
size) that caused the session transaction to hang.
This enhancement is based upon the NPSI RESETINO=YES|NO
option that up to this point was not required by the
NAS/HNAS user base. The NPSI RESETINO=(ccdd,ccdd,...)
option providing RESET cc=Cause and dd=Diagnostic code
filtering is not included in this enhancement.
SOLUTION: N/A
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).
2008-06-18 - APAR 2400080
APAR: 2400080_E
STATUS: CLOSED
OPEN_DATE: 2008-06-12
CLOSE_DATE: 2008-06-18
SERVICE(S): Configuration and Console, enhancements and fix.
MANDATORY: NO
ORIGIN/REF: 240_CPT
CPTECH: SFD
PTF_CLASS: ENHANCEMENT-APAR
PTF_TYPE: (OBJ) HNASOBJX and (SRC) HNASMACX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400080.ZIP file)
SMP/E PTFs are provided via user request because the
Comm-Pro supplied MCS is unique to each customer.
COREQ(S): N/A
PREREQ(S): With APAR 2400079 and associated APAR chains.
SUPERSEDES: N/A
OBJECT(S): CNFGCNCM, CNFGEXEC, CNFGSCHD, CONSDMAP, CONSDNWD,
CONSHELP, CONSSNAP, NASCNFG, NASCONS
SOURCE(S): SYSLIN, XFBLK, XFCNFGWA, XFMODMAP, XFXTRN
SUMMARY: This APAR contains 4 PROBLEM#s (#=1-4) issues, 3
enhancements and 1 fix for the configuration and
console subsystem.
PROBLEM1
ENHANCEMENT1: The configuration operand counterpart for the EXEC
console command is CONCMDQ= instead of EXEC=.
DESCRIPTION1: There is a lack of name symmetry for the EXEC console
command and the CONCMDQ= configuration operand unlike
the SCHEDULE command and the SCHEDULE= operand.
SOLUTION1: The HNAS configuration process was modified to accept
EXEC= as an alias for the CONCMDQ= operand.
PROBLEM2
ENHANCEMENT2: The CONCMDQ=|EXEC= operand does not allow a DDNAME to
be specified in addition to a command list.
DESCRIPTION2: See problem description.
SOLUTION2: The HNAS configuration process was modified to accept
CONCMDQ=ddname or EXEC=ddname as a value where ddname
identifies a command list file. This is similar to
what is now done for the SCHEDULE=ddname operand.
PROBLEM3
ENHANCEMENT3: There is no current way to request a SNAP dump of
individual HNAS storage areas.
DESCRIPTION3: Currently, the TRCTRAP SNAP is the only way to solicit
a SNAP dump of HNAS storage areas but this command dumps
ALL HNAS storage areas. There is no way to take a SNAP
dump of individual HNAS storage areas.
SOLUTION3: HNAS has been modified to accept the new SNAP console
command which accepts a list of individual HNAS storage
area names as arguments. The SNAP command syntax is
as follows:
SNAP {ALL|trgtlist}
trgtlist={ALOG|ALARMLOG} <- alarm log
{BFR|BFRSTOR} <- buffer pool
{CNFG|CONFIG} <- configuration area
{CVT} <- communications vector table
{DNAS|CONSDNAS} <- DNAS module (NASIDENT)
{MCH|MCHSTOR} <- MCH area (MCH,VCB,LUB)
{MLOG|MAINTLOG} <- maintenance log
{PCE|PCESTOR} <- dynamic PCE area
{TINT|TCPINTBL} <- TCPIP interrupt table
{TRC|TRACE} <- internal trace table
{VINT|VTAMINTBL} <- VTAM interrupt table
{WA|XFNASWA} <- workarea
{WAX} <- workarea extension
PROBLEM4: The SCHEDULE= operand does not restrict command text
to 63-bytes.
DESCRIPTION4: Effective with APAR 2400075, the command text provided
for the CONCMDQ= operand, EXEC and SCHEDULE console
commands was set to 63-bytes maximum to allow 2-bits in
the command string length byte to be reserved for flags.
This was done to support the overlay of the HNASCMD->
with EXECCMD->, SCHDCMD->, PRXYCMD-> and TRAPCMD->, as
appropriate. This change was erroneously missed for
the SCHEDULE= operand.
SOLUTION4: The HNAS configuration process was modified to limit
the length of queued command text for the SCHEDULE=
operand to 63-bytes.
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).
2008-05-31 - APAR 2400079 (was unpublished problem 2008128A and 2008144A)
APAR: 2400079
STATUS: CLOSED
OPEN_DATE: 2008-05-27
CLOSE_DATE: 2008-05-30
SERVICE(S): SYSPRINT, Alert and Configuration messages
MANDATORY: NO, RECOMMENDED
ORIGIN/REF: 240_SMB,240_CPT
CPTECH: SFD
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400079.ZIP file)
SMP/E PTFs are provided via user request because the
Comm-Pro supplied MCS is unique to each customer.
COREQ(S): N/A
PREREQ(S): Distribution dated after 2008-04-30 or an earlier
distribution with APAR 2400075 and associated APAR
chains applied
SUPERSEDES: N/A
OBJECT(S): CNFGIPAD, CNFGSVC3, NASCNFG, NASPRNT
SOURCE(S): N/A
SUMMARY: This APAR contains 3 PROBLEM#s (#=1|2|3) issues,
relating to Configuration and Alert messages.
PROBLEM1: NAS1321W REMOTE IPADDR TCPIP Alert Messages generates
a CC=4 Warning message for a configuration option that
is permissible.
DESCRIPTION1: The NAS1321W message was created to identify potential
run time problems when an IPADDR/PORT combination is
not unique. It turns out that these messages are
actually more for information rather than as a warning.
The following messages are affected:
NAS1321W REMOTE IPADDR WAS ALSO SPECIFIED FOR LOCAL
NAMED LXOT
NAS1321W VALID ONLY IN HNAS-TO-HNAS ENVIRONMENT USING
THE SAME TCPIP STACK
NAS1321W REMOTE IPADDR AND PORT WERE ALSO SPECIFIED FOR
REMOTE NAMED R2CNOT1
NAS1321W THE SOCKETS FROM BOTH REMOTES WILL BE COMBINED
IN A COMMON POOL
SOLUTION1: The NAS1321W message severity was changed from
Warning (CC=4) to Informational (CC=0) to eliminate
non-zero condition codes for valid (although unusual)
configuration options. Message NAS1321I will now be
used for these configuration messages.
PROBLEM2: NAS1391I messages generate too much SYSPRINT output
during HNAS initialization.
DESCRIPTION2: The NAS1391I message was created to show which MXT
operands override their MCH counterparts when an MXT
is associated with an SLU within the SVC0=, SVC3=,
SVC5= or PVC= operand. Since most customers use MXTs
to override root MCH operands, the number of NAS1391I
messages can become extensive leading to NAS0200W
messages which sets CC=4.
SOLUTION2: The HNAS configuration process has been changed to
only issue the NAS1391I messages during a FASTRUN
execution. These messages will not be seen in a
normal HNAS run. If you need to see the effect
of MXT operand overrides, you will need to run a
FASTRUN execution of HNAS prior to a normal run.
PROBLEM3: FASTRUN processing ends with CC=04 after addition of
MCH definitions.
DESCRIPTION3: The additional MCH statements added a number of LUs.
This caused 20,000 additional NAS1391I messages to
be generated which resulted in the following alert
to be issued:
NAS0200W 16384 SYSPRINT LOG RECORDS WRITTEN
The 'W' severity code causes the FASTRUN process to
end with a CC=4 completion.
SOLUTION3: The NAS0200W message severity was changed from
Warning (CC=4) to Informational (CC=0) to eliminate
non-zero condition codes for this valid informational
alert message.
CIRCUMVENTION: {optional, when appropriate}
APPLY_INFO: See Chapter 6 (Product Maintenance Installation
section) from the HNAS Guide and Reference Manual
for instructions on how to install PTF's (Object,
Source and ZAPs) or Refresh/Upgrade maintenance.
Corrective logic included in distributions created
after CLOSE_DATE. Otherwise, apply maintenance as
directed in the APPLY_INFO (PTF).
2008-05-20 - APAR 2400078 (was unpublished problem 2008112A)
APAR: 2400078_E
STATUS: CLOSED
OPEN_DATE: 2008-02-04
CLOSE_DATE: 2008-05-20
SERVICE(S): Console, DVC/DLU Display Fix and VCTO|LUTO Enhancement
MANDATORY: NO, but recommended.
ORIGIN/REF: 240_CPT
CPTECH: PRT/SFD
PTF_CLASS: ENHANCEMENT-APAR
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400078.ZIP file)
SMP/E PTFs are provided via user request because the
Comm-Pro supplied MCS is unique to each customer.
COREQ(S): N/A
PREREQ(S): Distribution dated after: 2008-02-28
With APAR 2400059, 2400070 and associated APAR chains.
SUPERSEDES: N/A
OBJECT(S): CONSDLU, CONSDVC, MCHPVCI
SOURCE(S): N/A
SUMMARY: This APAR contains 2 PROBLEM#s (#=1|2) issues, 1
problem and 1 enhancement for the console subsystem
DVC and DLU display output.
PROBLEM1: Uninitialized PVC DVC VCST field depicts DATA state
when IDLE should be depicted.
DESCRIPTION1: The DVC VCST field should depict a state of IDLE (P1)
prior to PVC Setup initialization. Once the PVC Setup
is successful the state should depict DATA (P4D1)
state.
This condition did not affect the actual operation of
the PVC although the status was incorrectly displayed.
SOLUTION1: Logic corrected to initialize PVC into VC state P1
instead of P4D1 before PVC Setup exchanges.
PROBLEM2
ENHANCEMENT2: Enhancement providing the ability to determine if a
PVC is in timer recovery state.
DESCRIPTION2: The DVC and DLU commands do not indicate if a VC or LU
timer, respectively, is running. In particular, for a
PVC, prior to PVC Setup initialization.
In viewing the PVC connect status DVC VCST or DLU STAT,
it doesn't reveal that the setup PVC LU is in timer
reconnect mode (PVCRECONTMR=).
SOLUTION2: The DVC and DLU commands have been modified to provide
a new column. For DVC, the VCTO column will now display
the current VC timer in effect if one is active. For
DLU, the LUTO column will now display the current LU
timer in effect if one is active. Note also that the
the DLU STAT column has been renamed LUST. The data
listed in this column remains the same.
For DVC, the VCTO column can contain the following:
CALL - SVC Call Request sent to DTE, response expected.
RQSE - REQSESS sent to VTAM, BIND expected.
RCWT - PVC reconnect wait state (PVCRECONTMR=), REQSESS
issued on timer expiration.
RQSD - REQSHUT sent to VTAM, SHUTDOWN expected.
STUP - PVC Setup sent to DTE, response expected.
CLR - SVC Clear Request sent to DTE, response expected.
STLG - REQSESS wait state (REQSESSDELAY=), REQSESS
issued on timer expiration.
EMSG - Datafono EMSGE sent to DTE, response expected.
SUWT - PVC Setup wait state (PVCSETUPTMR=), Setup
issued on timer expiration.
MSYN - Datafono MULTISYNC sent to DTE, response expected.
STMD - QLLC QSM sent to SPU, response expected.
DISC - QLLC QDISC sent to SPU, response expected.
XID - QLLC QXID sent to SPU, response expected.
TEST - QLLC QTEST sent to SPU, response expected.
REXP - QLLC PIU sent to SPU, response expected.
ICOL - QLLC SPU input collection in progress.
OMTR - QLLC SPU output metering in progress.
CLSD - QLLC SPU close wait state, open performed
on timer expiration.
For DLU, the LUTO column can contain the following:
DLAY - QLLC DACTLU/ACTLU wait state, ACTLU issued
on timer expiration.
REXP - QLLC PIU sent to SLU, response expected.
RQSE - REQSESS sent to VTAM, BIND expected.
RQSD - REQSHUT sent to VTAM, SHUTDOWN expected.
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).
2008-05-14 - APAR 2400077 (was unpublished problem 2008126A)
APAR: 2400077
STATUS: CLOSED
OPEN_DATE: 2008-05-05
CLOSE_DATE: 2008-05-14
SERVICE(S): Configuration processing
MANDATORY: YES if SOCLMT= value is specified
ORIGIN/REF: 240_SMB
CPTECH: SFD
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400077.ZIP file)
SMP/E PTFs are provided via user request because the
Comm-Pro supplied MCS is unique to each customer.
COREQ(S): N/A
PREREQ(S) APAR 2400032 and associated APAR chains.
SUPERSEDES: N/A
OBJECT(S): CNFGHOME, CNFGSCLM
SOURCE(S): N/A
PROBLEM: Customer gets 0198 (NASHALT) ABEND when they specify
SOCLMT=602 and the sum of TYPE=XOT REMOTE VCLMT= values
plus the TAP sockets equals 602. Two REMOTEs with
different IPADDR= values were specified which means
that two TAP sockets are required. VCLMT=300 was
specified for each REMOTE for a total of 602 sockets.
DESCRIPTION: ABEND occurs because SOCLMT= value includes the TAP
socket for a router but it does not also include the
temporary socket value. The temporary socket value was
introduced with APAR 2100011 but was not accounted for
in the total socket count calculation. Configuration
processing should detect this error but does not. The
result is that the NASHALT occurs during initialization
because SOCLMT=604 should have been specified instead
of SOCLMT=602.
SOLUTION: The HNAS configuration processing has been modified to
detect when the SOCLMT= value is too low and then issue
the following error message before terminating. This
will prevent HNAS from starting and thus eliminate the
NASHALT.
NAS1311S REMOTE XOTCNOT2 HOME XOTSRVR LIMIT REACHED
SOCCNT=00303 SOCLMT=00602 NEEDED=00301
CIRCUMVENTION: Omit the SOCLMT= operand to allow it to default to
2000.
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).
2008-05-05 - APAR 2400076 (was unpublished problem 2008050A)
APAR: 2400076
STATUS: CLOSED
OPEN_DATE: 2008-02-19
CLOSE_DATE: 2008-05-05
SERVICE(S): GATE
MANDATORY: YES
ORIGIN/REF: 240_NBG
CPTECH: prt
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400076.ZIP file)
SMP/E PTFs are provided via user request because the
Comm-Pro supplied MCS is unique to each customer.
COREQ(S): N/A
PREREQ(S): Distribution dated after: 2007-01-13
with APAR: 2400018 applied.
Refresh recommended if you are below the 2400070 level.
SUPERSEDES: N/A
OBJECT(S): XOTFCDC , XOTGTDC
SOURCE(S): N/A
PROBLEM: NAS4709W REMOTE rmt-nm lu-nm LU lu-addr LUIQ TIMEOUT,
LUIQ BFR CT=xxxx alert issued.
DESCRIPTION: This alert indicates the buffer at the head of the LU
input queue has been there for 5 minutes. The alert
indicates that data from the remote is not being
delivered to the PLU.
The LU involved is a GATE data session LU. The input
queue is 'stuck' because there is an incomplete M-bit
chain being received from the remote. The incomplete
M-bit chain is followed by a Clear confirm packet.
The queue is not serviced because of the incomplete
packet at the queue head. The Clear confirm packet is
a result of a Clear sent to HNAS by the GATE PLU.
This situation occurs rarely.
The problem arises because HNAS does not clear the LU
input queue when the CTCP sends a Clear packet.
SOLUTION: HNAS modified to clear the LU input queue when a GATE
Clear packet is received from the CTCP.
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).
2008-05-05 - APAR 2400075 (was unpublished problem 2008034A)
APAR: 2400075_RE
STATUS: CLOSED
OPEN_DATE: 2008-02-04
CLOSE_DATE: 2008-05-05
SERVICE(S): Console Enhancements & Multiple Commands Line Fix
MANDATORY: NO, but recommended for improved flexibility.
ORIGIN/REF: 240_CPT
CPTECH: SFD
PTF_CLASS: ENHANCEMENT-APAR
PTF_TYPE: REFRESH
PTF_LOC: Contact Support Services for Refresh E-distribution.
COREQ(S): N/A
PREREQ(S) N/A
SUMMARY: This APAR contains 3 PROBLEM# (#=1|2|3) issues, 2
enhancements and 1 fix for the console subsystem.
PROBLEM1
ENHANCEMENT1: Need the ability to schedule LOCAL console commands
from a REMOTE console and vice versa.
DESCRIPTION1: Currently, commands entered from any console (LOCAL
or REMOTE) are executed for that console only. There
is no way to schedule commands or modify queues and
workareas for one console from another.
SOLUTION1: HNAS has been modified to accept a console PCE name
as the first argument for certain commands so that
the command will affect the named console rather than
the requesting console. The following commands have
been modified for this support.
********************************************************
ALARM {LCLCONS|rconname} {action}
action = {ON|OFF} {TEST='text'}
{FILTER={?|*|
({A|P|S},id1({A|P|S|FC|FU}),...
...,idn({A|P|S|FC|FU}))}}
{LIMITS={?|*|@|
(tsec,ict,dct,act,wct,ect,sct,uct)}}
{LOG={?|CLEAR|RESET}}
{MSGTXT={?|SHORT|LONG}}
{PULSE={?|*|(hh:mm:ss,hh:mm:ss,seconds)}}
{SHOW}
********************************************************
EXEC {LCLCONS|rconname} {action}
action = (cmd1,...,cmdn) <- Execute inline command list
ddname <- Execute dataset command list
LIST ddname <- List dataset command list
STOP <- Stop command list execution
********************************************************
SCHEDULE {LCLCONS|rconname} {action}
action = (time1,cmd1,..) <- Append inline schedule list
to active schedule list
ddname <- Append dataset schedule list
to active schedule list
LIST ddname <- List dataset schedule list
LIST <- List active schedule list
SUSP <- Suspend active schedule list
RSME <- Resume active schedule list
PRG <- Purge active schedule list
********************************************************
{ID=lo{-hi}} SMSG 'text'
-OR-
SMSG {LCLCONS|rconname} 'text'
********************************************************
TRCCONS {ALLON|ALLOFF} <- global control
-OR-
{ID=lo{-hi}} TRCCONS {ON|OFF}
-OR-
TRCCONS {LCLCONS|rconname} {ON|OFF}
********************************************************
Notes: 1) When the LCLCONS argument is specified, it
directs command processing to the local
console. When LCLCONS and rconname are
omitted for the local console, LCLCONS is
assumed.
2) When the rconname argument is specified, it
directs command processing to the named
remote console. When LCLCONS and rconname
are omitted for a remote console, rconname
is forced to the name of the remote console.
3) Console names can be provided by issuing the
DPCE TYPE=CONS command. Only consoles that
are in the active state can be targeted by
the rconname parameter.
4) The LCLCONS and rconname arguments are valid
for privilege consoles only when specified
for the EXEC or SCHEDULE command. These
commands are normally non-privileged while
the ALARM command and all trace commands are
privileged.
5) When a command is executed, the normal console
command echo prefix is HNASCMD->. This prefix
is changed when the command is the result of
an EXEC command, SCHEDULE command, comes from
another console or is the result of a TRAP.
In these cases, the HNASCMD-> echo prefix is
replaced with EXECCMD->, SCHDCMD->, PRXYCMD->
or TRAPCMD->, respectively, so that these
commands can be identified in the SYSPRINT
log file.
*** MIGRATION ISSUE ***
In order to implement the HNASCMD-> overlay
logic, it was necessary to set the maximum
queued command size to 63 bytes. Prior to
this APAR, the maximum queued command size was
80 bytes. This does not affect the CONCMDQ
queue size itself which remains at 512 bytes.
PROBLEM2
ENHANCEMENT2: Need the ability to specify a PCE name for commands
that operate on PCEs.
DESCRIPTION2: For those commands that use a PCE as an argument via
ID= or RNM= modifiers, there is no way to specify a
PCE name when the PCE is not associated with a LOCAL
or REMOTE definition statement.
SOLUTION2: HNAS has been modified to accept a PCE name as the first
argument for certain commands so that the command will
affect the named PCE rather than the PCEs identified by
RNM= or ID= modifier. The following commands have
been modified for this support.
********************************************************
{ID=lo{-hi}} DPCE {rmtname} {parmlist}
-OR-
{RNM=rmtname} DPCE {rmtname} {parmlist}
-OR-
DPCE {pcestatic|pcename} {parmlist}
parmlist = {FMT1|FMT2}
{SHOWNAME|SHOWADDR}
{ALLID}
{TYPE={TMR|CONS|NETV|UTIL|TCP|XTP|XOT}}
{PROT={XTP|XOT}}
{STATE={IDLE|ACTIVE}}
{TRACE={ON|OFF}}
********************************************************
cmdnm {ALLON|ALLOFF} {types} <- global
-OR-
{ID=lo{-hi}} cmdnm {rmtname} {ON|OFF} {types}
-OR-
{RNM=rmtname} cmdnm {rmtname} {ON|OFF} {types}
-OR-
cmdnm {pcestatic|pcename} {ON|OFF} {types}
cmdnm = {STATS|TRCBFR|TRCDATA|TRCDISP|TRCIO|TRCPCE}
types = {ALLTYPES|NOTYPES} or
{CONS|NETV|TCP|TMR|UTIL|XOT|XTP}
********************************************************
Notes: 1) pcestatic = TIMER|LCLCONS|NETVIEW|NASUTIL|
XTPUTIL|XOTUTIL|PING
Alternative names for the pcestatic argument
are as follows:
WATMRPCE = TIMER
WACONPCE = LCLCONS
WANTVPCE = NETVIEW
WANASPCE = NASUTIL
XTPUTIL = XTPUTIL
XOTUTIL = XOTUTIL
WAPNGPCE = PING
2) When the pcestatic argument is specified, it
directs command processing to named static
PCE.
3) When the pcename argument is specified, it
directs command processing to the named PCE.
4) When pcestatic and pcename are omitted, the
command operates off of the RNM= or ID=
modifier. When the RNM= modifier is used,
command processing is directed at the named
REMOTE. When the ID= modifier is used, command
processing is directed at the identified PCEs.
5) PCE names can be provided by issuing the DPCE
command.
PROBLEM3: Unable to enter multiple SCHEDULE commands via the
HNAS console.
DESCRIPTION3: HNAS, erroneously, does not allow multiple SCHEDULE
or EXEC commands to be entered on the same line. For
example, SCHEDULE ddname SCHEDULE LIST is rejected
and the following error message is issued:
NASC512E PARAMETERS DUPLICATED, SCHEDULE COMMAND ABORTED
This occurs because the second SCHEDULE command is
treated as another DDNAME. This command string is
supposed to append the ddname schedule list to the
resident schedule list and then LIST the new resident
schedule list.
Similarly, EXEC ddname1 EXEC ddname2 is also rejected
with the same error because the second EXEC command is
also treated as another DDNAME. In fact, for SCHEDULE
or EXEC, any command that follows the first SCHEDULE
or EXEC command is also treated as a second DDNAME.
For example, EXEC ddname DNAS will be rejected with
the NASC512E message when it should be accepted.
SOLUTION3: HNAS has been corrected to allow multiple SCHEDULE
or EXEC commands to be entered on the same input line
and to allow other commands to follow these commands.
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).
2008-04-23 - APAR 2400074 (was problem 2008045A, 2008045B, 2008063A)
APAR: 2400074_E
STATUS: CLOSED
OPEN_DATE: 2008-02-14
REV_DATE: 2008-04-23 - Recalled and Reissued.
CLOSE_DATE: 2008-04-23
SERVICE(S): Miscellaneous Enhancements & DATAF Fix
MANDATORY: RECOMMENDED
ORIGIN/REF: 240_cpt,240_atc
CPTECH: SFD,PRT
PTF_CLASS: ENHANCEMENT-APAR
PTF_TYPE: (OBJ) HNASOBJX and (SRC) HNASMACX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400074.ZIP file)
SMP/E PTFs are provided via user request because the
Comm-Pro supplied MCS is unique to each customer.
COREQ(S): N/A
PREREQ(S): Distribution dated after: 2008-04-08
With APAR: 2400073 applied.
Refresh recommended if you are not at the 2400070 level.
SUPERSEDES: N/A
OBJECT(S): CNFGOPTS , CONSDRMT , CONSMRMT , MCHHL0RQ , MCHTMR
MCHUT2 , VCDAT , XOTRCV , XOTTR
SOURCE(S): LUD , VCDD , VTMRCV1 , VTMUT1 , XFNASWA
PROBLEM1: HNAS Datafono support does not include the IDTST=YES/NO
option.
SOLUTION1: Logic added to allow IDTST to be specified as in the
OPTIONS= list of a TYPE=DFX REMOTE.
Sample:
rmt-name REMOTE TYPE=DFX
OPTIONS=(DATAFAM,EMSGE,IDTST,XID=STD,IMS);
When IDTST is in effect HNAS looks for the X'5F' and
X'60' ID delimiter characters in inbound R(3) messages
from the remote. If an ID is present it is remembered
in the HNAS LU control block for the session.
The ID string in PLU output messages is tested against
the ID in the LU. If there is a match the 11 characters
following the Datafono message type byte are removed
before data is sent to the remote.
If the IDs do not match the PLU's message is discarded
and the following alert is issued:
NAS5725W LU lu-name DISCARDING MSG W BAD ID FROM
PLU plu-name
Special Cases:
When IDTST is coded and the inbound R(3) message does
not have an ID (no 5F/60 delimiter characters) then
outbound messages are not checked for an ID string.
When IDTST is coded and the PLU sends a message that
is less that 12 bytes long the message is sent without
modification.
If multiple inbound R(3) messages arrive each is
processed for an ID string.
If the R(3) ID string length is greater that 11 bytes
then ID string is ignored and the following alert is
issued:
NAS5723W DATAFONO IDTST LU lu-name REC'D ID STRING W
LENGTH > 11
PROBLEM2: When Datafono option DATAF coded and the PLU sends
a series of M messages HNAS does not wait for a D(8)
response that must be sent by the remote for each M
message (as required by the Datafono specification).
SOLUTION2: HNAS corrected to wait for the D(8) ('D--') response
after transmission of an M message. If the required
response is not received in 40 seconds the following
alerts are issued:
NAS5724W LU lu-nm DID NOT RECEIVE 'M' MSG SYNC RESP
FROM REMOTE
NAS3799I LU lu-nm ENDING SESSION ON MCH mch-nm HNAS
CAUSE/DIAG=000/223 (000/223 (00/DF) DIAGX=0008
PROBLEM3: HNAS does not provide a way for CUD0 to participate
in the selection of the HNAS SLU name for an inbound
session.
SOLUTION3: A new option (OPTIONS=CUD0SELECTSLU) allows the SVCi=
'X' processing code to start the hex compare at CUD0
(instead of CUD1).
Sample statement for a TYPE=MCH REMOTE:
OPTIONS=CUD0SELECTSLU
CUD0=(A2,A3,A4)
CTCP=(80,80,80)
SVC0=(7,LU1/XA2,LU2/XA2,
LU3/XA3,LU4/XA3,
LU5/XA4,LU6/XA4,LU7/XA4)
The CUD0= and CTCP= parameters identify the CUD0 values
that create LLC0 calls that will be assigned LUs from
the SVC0= string. The CUD0SELECTSLU option causes the
LU allocation routine to select the LU if the hex value
following the X character matches the CUD0 value in the
call request packet. In the above, LU1 & LU2 will be
used for CUD0=A2 calls, LU3 & LU4 will be used for
CUD0=A3 calls and LU5, LU6 & LU7 will be used for
CUD0=A4 calls. Up to 511 SVC0= entries may be coded.
Any number of LUs may be associated with a particular
CUD0 value.
PROBLEM4: The NAS7708W alert (displays PVC SETUP packet data
when there is a SETUP problem) does not identify
the LU name associated with the PVC session.
SOLUTION4: LU: lu-name field added to the alert message. If
the LU name is not available (for example, when
there is no MCH name in HNAS matching the responder
field in a SETUP from the remote) then '********'
is displayed in the LU name area.
PROBLEM5: The NAS7718T trace (displays PVC SETUP packet connect
activity) does not identify the LU name associated
with the PVC session.
SOLUTION5: LU: lu-name field added to the trace message. If
the LU name is not available (for example, when
there is no MCH name in HNAS matching the responder
field in a SETUP from the remote) then '********'
is displayed in the LU name area.
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).
2008-04-10 - APAR 2400073 (was problem 2004274A)
APAR: 2400073
STATUS: CLOSED
OPEN_DATE: 2004-10-01
CLOSE_DATE: 2008-04-10
SERVICE(S): QLLC
MANDATORY: RECOMMENDED if QLLC in use.
ORIGIN/REF: 230|240_NBG
CPTECH: PRT
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (OBJ) HNASOBJX and (SRC) HNASMACX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400073.ZIP file)
SMP/E PTFs are provided via user request because the
Comm-Pro supplied MCS is unique to each customer.
COREQ(S): N/A
PREREQ(S): N/A
SUPERSEDES: N/A
OBJECT(S): MCHHL3RQ
SOURCE(S): VTMRCV1
PROBLEM: QLLC X25 session terminated when the PLU sends a
CLEAR PIU to HNAS.
DESCRIPTION: Because of a logic error an X25 CLEAR is generated
when the PLU sends a CLEAR PIU to a QLLC LU. The
CLEAR PIU from the PLU is not delivered to the
remote because of the X25 clear.
SOLUTION: Logic corrected.
This problem was originally reported on Oct 1, 2004.
It was inadvertently omitted from a previous V2R3M0
APAR. This problem has only been seen at one HNAS
installation.
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).
2008-03-18 - APAR 2400072 (was problem 2008074A)
APAR: 2400072
STATUS: CLOSED
OPEN_DATE: 2008-03-14
CLOSE_DATE: 2008-03-18
SERVICE(S): PVC
MANDATORY: YES if PVCs used.
ORIGIN/REF: 240_FIS
CPTECH: PRT
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400072.ZIP file)
SMP/E PTFs are provided via user request because the
Comm-Pro supplied MCS is unique to each customer.
COREQ(S): N/A
PREREQ(S): Distribution dated after: 2008-02-28
with REFRESH APAR: 2400070 applied.
If you are not at the above level a refresh is
recommended.
SUPERSEDES: N/A
OBJECT(S): VCCLRQ
SOURCE(S): N/A
PROBLEM: HALT AT LOC 800637E6 IN NASTCP : TCPIP TRANSMIT FAILURE
DESCRIPTION: Halt resulted because BFRPCEPT was 0 when a buffer was
passed to TCPXMT. The LU was a PVC LLC0 LU with a VTAM
session that was forced by a VARY ON command. This HNAS
console command should not open the ACB for a PVC with
no session.
SOLUTION: The PVC VTAM session start routine was modified to not
open a PVC LU's ACB if there is no PVC session (PVC
SETUPs have not been exchanged with the router).
The customer used the VARY lu OFF/ON sequence because
the LU associated with the PVC was not active. When a
PVC LU's ACB is not open it indicates that the PVC
session has not been established with PVC SETUP packets.
Until the SETUP sequence completes the LU can't be used
by the PLU because there is no remote to receive PLU
data.
The status of a PVC LU can be displayed with the HNAS
console DLU command or a VTAM D NET,ID= command.
CIRCUMVENTION: Do not issue VARY lu-name OFF/ON sequence for a PVC
LU that has no session with 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).
2008-03-18 - APAR 2400071 (was unpublished problem 2008028A)
APAR: 2400071
STATUS: CLOSED
OPEN_DATE: 2008-03-02
REV_DATE: 2008-03-18 - Memo updated.
CLOSE_DATE: 2008-03-13
SERVICE(S): Configuration and Console parameter processing
MANDATORY: NO, but highly recommended
ORIGIN/REF: 240_ATC
CPTECH: SFD
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400071.ZIP file)
SMP/E PTFs are provided via user request because the
Comm-Pro supplied MCS is unique to each customer.
COREQ(S): N/A
PREREQ(S) APAR 2400070 and associated APAR chains.
SUPERSEDES: N/A
OBJECT(S): CNFGOPTS, CONSDRMT, CONSMLCL, CONSMRMT
SOURCE(S): N/A
PROBLEM: Error in parameter decode processing can cause one
parameter to be processed as another.
DESCRIPTION: Customer specified OPTIONS=DATAFM for a TYPE=DFX
REMOTE when he meant to specify OPTIONS=DATAFAM but
because the parameter decode processing accepts DATAF
or DATAFAM, DATAFM was treated as DATAF. This occurs
because the decode tests for a text match but not
also a text length match.
Note that the decode problem is not limited to the
DATAF argument but also affects other operands. For
example CUD=NONExxx is treated as CUD=NONE instead
of being rejected.
SOLUTION: The configuration and console command parsers have been
modified to not only test for a parameter text match
but also a text length match. This will ensure that,
for example, DATAFM will be rejected rather than being
treated as DATAF.
CIRCUMVENTION: Specify the correct parameter exactly as intended.
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).
2008-02-29 - APAR 2400070
APAR: 2400070_RE
STATUS: CLOSED
OPEN_DATE: 2008-02-06
REVISE_DATE: N/A
CLOSE_DATE: 2008-02-29
SERVICE(S): Console input error message processing
MANDATORY: NO
ORIGIN/REF: 240_CPT
CPTECH: SFD
PTF_CLASS: ENHANCEMENT-APAR
PTF_TYPE: REFRESH
PTF_LOC: Contact Support Services for Refresh E-distribution.
COREQ(S): N/A
PREREQ(S): N/A
OVERVIEW: This Enhancement APAR addresses the following console
and debugging improvement.
PROBLEM
ENHANCEMENT: Sometimes it is difficult to determine which console
command argument is in error when the NASC532E error
message is issued.
DESCRIPTION: When a console command is entered and one of the command
arguments is in error, the command is rejected and the
following messaged is issued:
NASC532E PARAMETER DATA INVALID, cmdname COMMAND ABORTED
This message tells you that there was a problem with
the command parameter data but it does not tell you
which parameter is in error.
SOLUTION: The console command error processor has been modified
to display up to 8 bytes before and after the parameter
data that is in error. The new format for the NASC532E
message is as follows:
NASC532E PARAMETER DATA INVALID: baddata...,
cmdname COMMAND ABORTED
The new format of the error message should help you
resolve input errors more quickly than in the past.
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).
2008-02-26 - APAR 2400069 (was unpublished problem 2008045C)
APAR: 2400069_E
STATUS: CLOSED
OPEN_DATE: 2008-02-14
CLOSE_DATE: 2008-02-26
SERVICE(S): CALLOUT T21= X25 Level 3 Timer
MANDATORY: NO
ORIGIN/REF: 240_smb
CPTECH: prt/sfd
PTF_CLASS: ENHANCEMENT-APAR
PTF_TYPE: (OBJ) HNASOBJX and (SRC) HNASMACX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400069.ZIP file)
SMP/E PTFs are provided via user request because the
Comm-Pro supplied MCS is unique to each customer.
COREQ(S): N/A
PREREQ(S): With APAR 2400068 and associated APAR chains.
If you are not at the 2400064 level a refresh is
recommended.
SUPERSEDES: N/A
OBJECT(S): CNFGOPTS, CONSDRMT, CONSMRMT, XOTXMTC
SOURCE(S): XFNASWA
PROBLEM
ENHANCEMENT: Customer requires the ability to increase the Call
Request timer from the 30 second fixed value.
DESCRIPTION: HNAS CALLOUT operation can prematurely timeout because
a Call Accept from the remote is taking longer than the
existing fixed 30 second timer permits. An internal
Clear DIAG=C5 is generated and the socket is closed
when this condition is encountered.
The X.25 Level 3 Call Request response timer (T21=) was
implemented to control this condition.
SOLUTION: HNAS has been modified to accept OPTIONS=SVCCALLTMR=nn|
T21=nn on the TYPE=MCH and TYPE=MXT REMOTE statements.
This allows users to specify the call accept timeout
intervals. The OPTION on MXT REMOTEs only applies to
LLC0/LLC5 calls that use the MXT.
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).
2008-03-21 - APAR 2400068 (was unpublished problem 2008037A and
2007318A)
APAR: 2400068_E
STATUS: CLOSED
OPEN_DATE: 2008-02-06
REV_DATE: 2008-03-21 - Memo description updated (problem ref)
CLOSE_DATE: 2008-02-12
SERVICE(S): Alarm message control
MANDATORY: RECOMMENDED
ORIGIN/REF: 240_NBG/RWG
CPTECH: prt
PTF_CLASS: ENHANCEMENT-APAR
PTF_TYPE: (OBJ) HNASOBJX and (SRC) HNASMACX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400068.ZIP file)
SMP/E PTFs are provided via user request because the
Comm-Pro supplied MCS is unique to each customer.
COREQ(S): N/A
PREREQ(S): Distribution dated after: 2008-01-17
with APAR: 2400064 applied.
Refresh recommended for installation below 2400064.
SUPERSEDES: N/A
OBJECT(S): CNFGOPTS, CONSALRM, XOTTR
SOURCE(S): NASTCP, XFBLK, XFNASWA
ENHANCEMENT: Customer needs control of Call Request packet trace
message size and system console routing as well as
control of selected alert message sizes.
DESCRIPTION: See problem.
SOLUTION: HNAS has been modified to accept the following BUILD
statement OPTIONS= parameter:
OPTIONS=ALRMSGTXT=SHORT|LONG
The main reason for this change is to provide call
activity information in the job log for use by programs
that process the log and to force various alarm messages
to fit on a single line.
EFFECT1: When used in conjunction with TRCMCH ICR OCR the new
option changes the way that inbound and outbound calls
are traced.
LONG, the default, coded with TRCMCH ICR ON / OCR ON
results in the following records being sent to SYSPRINT:
NAS7718T followed by 3 NAS7798T messages giving the call
request packet content. These are the 'normal' pre-
APAR ICR trace records.
NAS7719T followed by 3 NAS7798T messages giving the call
request packet content. These are the 'normal' pre-
APAR OCR trace records.
SHORT coded the with TRCMCH ICR ON results in the
following being sent to SYSPRINT and to the operator's
console:
NAS7730I ED:eeeeeeeeeeeeeee ING:ggggggggggggggg
CUD:cccccccc FAC:llffffffffffff MCH:mch-name
IP:a.b.c.d
e...e: called address (up to 15 decimal digits).
g...g: calling address (up to 15 decimal digits).
c...c: call user data (up to 4 bytes displayed).
ll : facilities length byte.
f...f: facility data (up to 6 bytes displayed).
mch-name: name of
thall.
a.b.c.d: ip address that sent the call request to HNAS.
SHORT coded the with TRCMCH OCR ON results in the
following being sent to SYSPRINT and to the operator's
console:
NAS7731I ED:eeeeeeeeeeeeeee ING:ggggggggggggggg
CUD:cccccccc FAC:llffffffffffff RMT:remote-nm
LU:lu-name
The content of the ED:, ING:, CUD: and FAC: fields is
described above.
remote-nm: name of the TYPE=XOT REMOTE used for the call.
lu-name : name of the HNAS LU that triggered the call.
EFFECT2: When a GATE CTCP clears an inbound call request HNAS
issues a 2 line NAS7716W alert. With ALRMSGTXT=SHORT
the following single line alert is generated:
NAS7716W a.b.c.d TO mch-name FAILED, CTCP CLEAR
VIA LU lu-name CAUSE/DIAG=ccc/ddd (xx/yy) DIAGX=xxxx
a.b.c.d: IP address that sent the call request.
mch-name: name of the HNAS MCH that received the call.
lu-name: name of the HNAS LU the CTCP sent clear to.
ccc/ddd: cause and diagnostic from the CTCP.
xx/yy: hex versions of ccc/ddd.
xxxx: diagnostic extension (currently not used).
EFFECT3: When an callout fails (remote returns clear or does
not respond to the HNAS call request) HNAS issues a 2
line NAS7717W alert. With ALRMSGTXT=SHORT the following
single line alert is issued:
NAS7717W LU lu-name CALL TO called-addr|desc-text
RMT rmt-name FAILED CAUSE/DIAG=ccc/ddd (xx/yy) DIAGX=xxxx
lu-name: name of LU that generated the call.
called-addr: called DTE address in the call request pkt.
desc-text: descriptive text from the RTEOUT= slot
for the call. If coded, this text replaces
the called-address field.
rmt-name: name of the TYPE=XOT REMOTE used for the call.
ccc/ddd: cause and diagnostic from the CTCP.
xx/yy: hex versions of ccc/ddd.
xxxx: diagnostic extension (currently not used).
EFFECT4: For example, when ALRMSGTXT=LONG (the default) is in
effect, the NAS2200I message is displayed as follows:
NAS2200I SERVER=010.117.056.171(01998)
SOCKID=0000 PCEID=0009 NAME=LXOT
NAS2200I SOCKET ASSIGNED BY SERVER,
SOCCNT=00001 SOCLMT=02000
When ALRMSGTXT=SHORT is in effect, this same message
is displayed as follows:
NAS2200I SERVER=010.117.056.171(01998) NAME=LXOT
SOCKET ASSIGNED BY SERVER, SOCCNT=00001 SOCLMT=02000
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).
2008-02-02 - APAR 2400067 (no problem number assigned)
APAR: 2400067
STATUS: CLOSED
OPEN_DATE: 2008-02-01
CLOSE_DATE: 2008-02-02
SERVICE(S): Console Subsystem - Remote Console
MANDATORY: YES, if remote console access is used and APAR 2400066
has been applied.
ORIGIN/REF: 240_CPT
CPTECH: SFD
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400067.ZIP file)
SMP/E PTFs are provided via user request because the
Comm-Pro supplied MCS is unique to each customer.
COREQ(S): N/A
PREREQ(S) APAR 2400066 and associated APAR chains.
SUPERSEDES: N/A
OBJECT(S): NASCONS
SOURCE(S): N/A
PROBLEM: Remote console password prompt is not displayed until
input is entered.
DESCRIPTION: Logic changes introduced with APAR 2400066 can cause
the remote console password prompt to be inhibited
until input is entered. The standard input prompt
from the CONPRMT= operand is displayed instead. This
makes it appear as though no password is required.
SOLUTION: The logic introduced with APAR 2400066 has been
corrected so that the password prompt appears as it
normally should.
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).
2008-01-31 - APAR 2400066 (was unpublished problem 2008028A)
APAR: 2400066
STATUS: CLOSED
OPEN_DATE: 2008-01-28
CLOSE_DATE: 2008-01-31
SERVICE(S): Console Subsystem - Remote Console
MANDATORY: YES, if remote console access is used and APAR 2400064
has been applied.
ORIGIN/REF: 240_CPT
CPTECH: SFD
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400066.ZIP file)
SMP/E PTFs are provided via user request because the
Comm-Pro supplied MCS is unique to each customer.
COREQ(S): N/A
PREREQ(S) APAR 2400064 and associated APAR chains.
SUPERSEDES: N/A
OBJECT(S): NASCONS, NASUTIL
SOURCE(S): N/A
PROBLEM: Remote console session connect processing bug can
cause HNAS to loop preventing other HNAS tasks from
operating.
DESCRIPTION: Logic changes introduced with Enhancement APAR 2400064
can cause HNAS to loop when a remote console session
connection is attempted. The problem occurs because of
a branch instruction that should have been but was not
modified when APAR 2400064 logic was added. The bad
branch is not always executed due to a timing problem
which means that this failure can be intermittent but
should nevertheless be corrected.
SOLUTION: The branch instruction has been corrected.
CIRCUMVENTION: Do not use remote console access, restrict use to
local (/F modify) access.
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).
2008-01-17 - APAR 2400065 (no problem number assigned)
APAR: 2400065
STATUS: CLOSED
OPEN_DATE: 2008-01-14
CLOSE_DATE: 2008-01-17
SERVICE(S): VTAM USSMSG - MCHSOL
MANDATORY: YES
ORIGIN/REF: 240_cpt
CPTECH: PRT
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400065.ZIP file)
SMP/E PTFs are provided via user request because the
Comm-Pro supplied MCS is unique to each customer.
COREQ(S): N/A
PREREQ(S): Distribution dated after: 2007-06-06
With APARs: 2400040 applied.
SUPERSEDES: N/A
OBJECT(S): MCHSOL
SOURCE(S): N/A
PROBLEM: 0C4 ABEND when starting a remote console session
using MCHSOL and USSMSG 0 ("Command Accepted") is
specified.
DESCRIPTION: APAR 2400032 (USSTAB reload) introduced logic that
causes a S0C4 abend when USSMSG 0 is defined and a
console session is started using MCHSOL. The error
is due to 0 being used as a control block address.
SOLUTION: Logic corrected.
CIRCUMVENTION: Don't use MCHSOL for console access.
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).
2008-01-17 - APAR 2400064 (was unpublished problem 2007022A and
2007339A)
APAR: 2400064_RE
STATUS: CLOSED
OPEN_DATE: 2007-01-22
CLOSE_DATE: 2008-01-17
SERVICE(S): Scheduled console command processing
MANDATORY: NO, but recommended for improved diagnostics.
ORIGIN/REF: 240_CPT
CPTECH: SFD
PTF_CLASS: ENHANCEMENT-APAR
PTF_TYPE: REFRESH
PTF_LOC: Contact Support Services for Refresh E-distribution.
COREQ(S): N/A
PREREQ(S) N/A
ENHANCEMENT: Need the ability to schedule console commands that
can be executed automatically at specific times.
DESCRIPTION: As an aid to problem diagnosis, sometimes it is
necessary to start/stop traces as well as issue
display commands at specific times. Prior to this
enhancement this action could only be done manually
via operator intervention.
SOLUTION: HNAS has been modified to accept the new SCHEDULE=
operand and SCHEDULE console command that allows
commands to be scheduled for automatic execution.
Syntax for SCHEDULE= operand is as follows:
SCHEDULE=ddname|(hh:mm:ss,cmd,...,hh:mm:ss,cmd)
Syntax for SCHEDULE console command is as follows:
SCHEDULE ddname|(hh:mm:ss,cmd,...,hh:mm:ss,cmd)
SCHEDULE LIST {ddname}
SCHEDULE SUSPEND|SUSP
SCHEDULE RESUME|RSME
SCHEDULE PURGE|PRG
Where: (hh:mm:ss,cmd,...,hh:mm:ss,cmd) is an inline
schedule list. Inline times and commands are
added to the end of an existing schedule list
if one is active.
ddname identifies a file that contains a list
of times and commands. A ddname schedule list
can contain the following:
Comments are allowed and start with an asterisk
(*) or semi-colon (;) in record column 1.
Comments can also appear on a command line but
must start with a semi-colon after the command.
A single time and command can be specified on
a single record as follows:
hh:mm:ss , cmd ; comment
Although we recommend enclosing the strings in
parentheses () as follows:
(hh:mm:ss , cmd) ; comment
Multiple times and commands can be specified on
a single record as follows:
(hh:mm:ss , cmd , ... , hh:mm:ss , cmd) ; comment
LIST will display the current schedule list in
effect. If ddname is not specified, the active
(current) schedule list is displayed. If ddname
is specified, the identified schedule list is
displayed but the active schedule list remains
unaffected.
SUSPEND causes the active schedule list to be
suspended so that no commands will be scheduled.
The list itself is maintained.
RESUME causes the active schedule list that was
suspended to be resumed so that commands will be
scheduled again.
PURGE causes the current schedule list to be
cleared. No commands are left to be scheduled
and the SUSPEND state is cleared.
Notes: 1) In order to provide symmetry between SCHEDULE
and EXEC command processing, the EXEC command
was also modified to allow multiple commands
to be specified on a single record within a
command list file as follows:
(cmd , ... , cmd) ; comment
A single command can still be specified on a
single record as follows:
cmd ; comment
2) For both the EXEC and SCHEDULE commands, you
may enclose a cmd within single or double
quotes (e.g., cmd, 'cmd' or "cmd" are valid).
If single quotes are part of a cmd, it can be
enclosed in double quotes (e.g., smsg 'test'
or "smsg 'test'" are valid). The enveloping
single or double quotes are removed from each
cmd before the values are saved.
3) For both the EXEC and SCHEDULE commands,
leading and trailing blanks are removed from
each cmd (and time for the SCHEDULE command)
before the values are saved.
4) For both the EXEC and SCHEDULE commands, an
END command will signal the end of data in a
file. In addition, for EXEC, an embedded
EXEC command and for SCHEDULE, an embedded
SCHEDULE command will also signal the end of
data in a file. Any records that follow
these statements will be ignored.
5) For both the EXEC and SCHEDULE commands, the
CONCMDQ queue is used to save commands. For
the EXEC command, cmd values are enqueued
to CONCMDQ in a first in, first out (FIFO)
manner. For the SCHEDULE command, cmd values
are enqueued to CONCMDQ in a last in, first out
(LIFO) manner. LIFO enqueue is used because
scheduled commands must be executed at the
specified time rather than after any other
queued commands.
WARNING: If a command is currently running
when a scheduled command is enqueued, the
current command is aborted in favor of the
scheduled command (the same action takes
place when a command is entered by a console
operator). If a command list is running,
the list is interrupted while the scheduled
command executes. The command list is then
restarted with the next queued command after
the scheduled command executes.
6) Multiple commands can be scheduled for
execution at the same time. For example:
(12:00:00,ALARM LOG=?,12:00:00,DNAS)
WARNING: Because scheduled commands are
enqueued to CONCMDQ in a LIFO manner, commands
with the same schedule time are executed in the
reverse order from how they are listed in the
schedule list. In the list above, DNAS will be
executed before ALARM LOG=? at approximately
noon each day. You should consider this when
listing commands in a schedule list.
A simple solution to ensure processing order
(avoiding reverse coding) is to sequentially
list the commands and step by 1 second as
depicted in the following sample:
(12:00:00,ALARM LOG=?,12:00:01,DNAS)
7) Wildcards (*) may be specified for any time
digit. When a wildcard character is supplied
for a time digit (hh:mm:ss), it will be
replaced with the corresponding digit from
the current time then the resulting time
will be tested against the current time.
Examples:
If (**:**:00,ALARM LOG=?) is a scheduled
command, the ** will be replaced by the
current hours and minutes values so that
ALARM LOG=? will be executed every 60
seconds.
If (**:30:00,ALARM LOG=?) is a scheduled
command, the ** will be replaced by the
current hours value so that ALARM LOG=? will
be executed at half past every hour.
If (1*:00:00,ALARM LOG=?) is a scheduled
command, the * will be replaced by the low
order hours digit so that ALARM LOG=? will
be executed on the hour between 10:00 and
and 19:00 each day.
If (12:**:00,ALARM LOG=?) is a scheduled
command, the ** will be replaced by the
current minutes value so that ALARM LOG=?
will be executed once per minute between
12:00 and 12:59 each day.
You can specify a wildcard for any time except
the low order second digit (hh:mm:s*) because
a scheduled command would be executed every
second which could impact HNAS performance.
8) For the SCHEDULE command when an inline list
or ddname list is given, entries are added to
the end of the active SCHEDULE list in effect.
If the active schedule list contains another
SCHEDULE command, the specified schedule list
will replace the active (RESIDENT) list. This
allows you to chain schedule lists (see Item 9
examples).
9) For the EXEC command, an embedded EXEC command
allows you to chain command lists. For the
SCHEDULE command, an embedded SCHEDULE command
allows you to chain schedule lists.
For example, if you want to run a different
schedule list each day, you could structure
them as follows (assume HNAS is started on
Monday):
BUILD SCHEDULE=DD4MON
//DD4MON DD DSN=hlq.HNASMAC(DD4MON),DISP=SHR
//DD4TUE DD DSN=hlq.HNASMAC(DD4TUE),DISP=SHR
//DD4WED DD DSN=hlq.HNASMAC(DD4WED),DISP=SHR
//DD4THU DD DSN=hlq.HNASMAC(DD4THU),DISP=SHR
//DD4FRI DD DSN=hlq.HNASMAC(DD4FRI),DISP=SHR
//DD4SAT DD DSN=hlq.HNASMAC(DD4SAT),DISP=SHR
//DD4SUN DD DSN=hlq.HNASMAC(DD4SUN),DISP=SHR
Each schedule list file will end with a
SCHEDULE command that points at the next
file which will take effect at midnight.
The DD4MON file will end with the following
statement: (00:00:00,SCHEDULE DD4TUE)
The DD4TUE file will end with the following
statement: (00:00:00,SCHEDULE DD4WED)
:
The DD4SUN file will end with the following
statement: (00:00:00,SCHEDULE DD4MON)
In this way, you can operate with a different
set of scheduled commands each day and because
DISP=SHR is specified for each ddname, you can
make changes to any of the inactive list files
while HNAS is running. Note also that you can
alter the normal schedule list flow by simply
entering a new SCHEDULE command from the
operator console.
As another example, suppose you want to run
different schedule lists during the day and
night, you could structure them as follows
(assume HNAS is started during the day):
BUILD SCHEDULE=DD4DAY
//DD4DAY DD DSN=hlq.HNASMAC(DD4DAY),DISP=SHR
//DD4NIT DD DSN=hlq.HNASMAC(DD4NIT),DISP=SHR
As before, each schedule list file will end
with a SCHEDULE command that points at the
other file which will take effect at the
specified time.
The DD4DAY file will end with the following
statement: (00:00:00,SCHEDULE DD4NIT)
The DD4NIT file will end with the following
statement: (06:00:00,SCHEDULE DD4DAY)
10) When a scheduled command is executed, the
normal console command echo prefix is changed
from HNASCMD-> to SCHDCMD-> so that scheduled
commands can be identified in the SYSPRINT
log file.
11) When SCHEDULE=schdlist is decoded during HNAS
activation, scheduled commands are suspended
until after the NAS0001I INITIALIZATION
COMPLETE message is issued and after first
CONCMDQ=cmdlist 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).
Last Update - December 24, 2008