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_I 240nnnn_M 240nnnn_P 240nnnn_R 240nnnn_U |
yyyy-mm-dd-> |
(blank) <Deferred> <Enhancement> <Internal> <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. Internal utility maintenance (not std fix or enhancement) 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 2400099 | <Link forward> | - | - |
HNAS V2R4M0 - 2010 MAINTENANCE SUMMARY (Link to APARs 2400099 thru 2400nnn) |
| 2009-12-14 |
Cons-Subsystem |
OBJ/SRC |
Console Subsystem Enhancements and
General Maintenance: |
|
| 2009-09-16 |
DTF (Datafono) |
OBJ |
HALT AT LOC xxxxxxxx IN MCHTMR : INV LU 3 due to an error when processing an early session end for a Datafono pseudo leased resource genned with the DATAF and RETPIU options. |
|
| 2009-09-10 |
EOMKEY EOMDATE Authorization |
OBJ/SRC |
Invocation of EOMKEY containing an already expired EOMDATE causes 45 day grace period to be ignored. |
|
|
2400095_R |
2009-08-13 |
EOMDATE Authorization Processing |
<Refresh Required> |
Changes providing the ability to extend the EOMDATE |
|
2400094_E |
2009-06-16 |
HNAS Startup PARM=
Parameter processing |
OBJ/SRC |
Enhancement to start JCL PARM= now provides a new start parameter PARMFILE=pfddname option that allows a greater number of start parameters to be specified by the user eliminating the string limit of 100 characters. |
| 2009-05-28 |
TCP/IP |
OBJ/SRC |
ABEND U198 (NASHALT) HALT AT LOC xxxxxxxx IN NASTCP : TCPIP TRANSMIT FAILURE due to an error in the HNAS close processing logic leads to a TCPXMT call with an invalid PCE address of zero. |
|
| 2009-04-30 |
HNAS end-of-day timer processing |
OBJ |
NAS0910I end-of-day rollover message not generated due to logic added by APAR 2400089. This prevents HNAS PULSE from being taken and the NAS0910I message from being generated. |
|
| 2009-04-30 |
Cons-Subsystem |
OBJ |
LLC0|5 SLU will not reconnect to VTAM application after the SVC0|5 applid is changed using the MRMT command to switch assignment to a different PLU. |
|
| 2009-03-30 |
Dataset Error Recovery Processing, including PRTSWLST and SYSPRINT switch processing. |
OBJ/SRC |
HNAS ABENDs with 0C4-10 immediately after a recoverable
B37-04 ABEND occurs for a full SYSPRINT dataset. The condition is
supposed to force a SYSPRINT switch to occur via the PRTSWLST=
configuration |
|
| 2009-03-13 |
Cons-Subsystem |
<Refresh Required> |
General maintenance for HNAS Authorization/Anniversary EOM Date
processing, Alarm logging and presentation: |
|
| 2009-02-23 |
Datafono |
OBJ |
Datafono (DTF) session
ends after alert 'NAS5724W LU |
|
| 2009-02-10 |
Datafono |
OBJ |
Leased Datafono session ending with NAS3799I (ACB closed) |
|
|
2400086_I |
2009-02-05 |
HNAS Trial Users
Authorization processing. |
<Refresh> User refresh not required. |
Internal logic changes addressing HNAS date authorization validation processing issues. |
| - | - | - | - | - |
|
2400085 thru 2400064 |
<Link back> | - | - |
HNAS V2R4M0 - 2008 MAINTENANCE SUMMARY (Link to APARs 2400064 thru 2400085) |
|
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/... Refresh |
<-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. _I - Internal Comm-Pro utility maintenance changes or improvements not directly related to standard product fixes or enhancements. Updated code included in the next HNAS Refresh edistribution. _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.
2009-12-14 - APAR 2400098
APAR: 2400098
STATUS: CLOSED
OPEN_DATE: 2009-11-18
OLDCLS_DATE: 2009-12-09
REV_DATE: 2009-12-14 - Recalled and Reissued.
CLOSE_DATE: 2009-12-14
SERVICE(S): Console command and Authorization message processing
MANDATORY: NO
ORIGIN/REF: 240_CSP,240_CPT
CPTECH: SFD
PTF_CLASS: ENHANCEMENT-APAR
PTF_TYPE: (SRC) HNASMACX and (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400098.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): Distributions with APARs 2400096, 2400094, 2400080 and
their associated APAR chains applied.
SUPERSEDES: N/A
OBJECT(S): CNFGEXEC, CONSEXEC, CONSVARY, NASCONS, NASUTIL
SOURCE(S): XFBLK
PROBLEM: This Enhancement APAR addresses the following console
improvements:
PROBLEM1: Customer indicates that the following message is
confusing because it is issued continually:
NAS9206I HNAS MAINTENANCE/USE ANNIVERSARY DATE WILL
EXPIRE IN 0ddd DAYS
PROBLEM2: Customer issues a console command list (EXEC (cmdlist))
via JCL but not all commands in list execute when one
of the commands ends in error.
PROBLEM3: Customer would like to disconnect an active PVC even
if it's SLU is inactive to force the XOT PVC to enter
PVC Setup pending state where the Router or HNAS will
send a PVC Setup request once the retry timer expires.
DESCRIPTION1: Starting with APAR 2400095, the NAS9206I message is
issued continually until the current date is within 45
days of the MAINTENANCE/USE ANNIVERSARY DATE (EOMDATE)
at which time, the message severity is changed from 'I'
to 'W' (NAS9206W). If the EOMDATE is not extended either
with a new refresh distribution or via an EOMKEY, the
EOMDATE will expire. A new EOMDATE is required to allow
HNAS to be used. Some customers do not realize the
importance of this because the NAS9206I message is
always issued and tends to be ignored.
DESCRIPTION2: Due to the way the EXEC command list is executed, an
error in any command in the list causes the subsequent
commands in the list to be purged. The rationale being
that the commands in the list could be related and all
depend on the successful completion of previous commands
in the list. Some customers specify commands that are
unrelated and expect all to be executed regardless of
errors in any single command in the list.
DESCRIPTION3: When the 'VARY sluname FORCE' command is issued to a PVC
SLU and the SLU is active, the SLU is UNBOUND and the
PVC connection is RESET (the TCP/IP socket is not
closed). However, if a PVC SLU is inactive but the PVC
connection is active, it will remain active even though
it should be closed.
SOLUTION1: HNAS has been modified to withhold the NAS9206I messages
until 60 days before the EOMDATE is to expire. This
should make the messages more significant and less
likely to be ignored. In addition, the message severity
will change from 'I' to 'W', from 'W' to 'E' and then
from 'E' to 'S' the closer the current date gets to the
EOMDATE.
SOLUTION2: HNAS has been modified to accept two new options within
an inline command list or DDNAME command list.
PURGEONERROR (the default) specifies that subsequent
commands in a command list are to be purged if an error
occurs for any command in the list.
NOPURGEONERROR specifies that subsequent commands in a
command list are to be executed even if any command ends
in error.
Example: EXEC (NOPURGEONERROR,cmd1,...,cmdn)
Notes: 1) The PURGEONERROR|NOPURGEONERROR options are
valid for the EXEC= operand on the BUILD
definition statement as well as the EXEC
console command.
2) The PURGEONERROR|NOPURGEONERROR options are
not included in the command list but are
decoded and acted upon immediately when
parsed.
3) The PURGEONERROR|NOPURGEONERROR option remains
in effect until changed by the EXEC console
command. You can display the current option
in effect by issuing EXEC LIST (no cmdlist).
SOLUTION3: The 'VARY sluname FORCE' command has been modified to
close an active PVC TCP/IP socket even when it's SLU is
inactive. Prior to this enhancement, the VARY command
would have been rejected in this situation with the
following message:
NASC015E FUNCTION ALREADY INACTIVE, VARY COMMAND ABORTED
Note that this message will still be issued if both the
PVC SLU and the PVC itself are inactive.
Note that this new logic eliminates the two step process
of first finding the PID for the PVC socket and then
issuing the VARY ID=pid FORCE command to close the PVC
socket. This new support allows customers to work with
an sluname which is useful for installations that employ
automated console command processes.
PVC Setup note: Closure of the socket causes the XOT PVC
to re-enter PVC Setup pending state which will cause the
the PVC Setup to be sent from the appropriate initiator
once the retry timer expires.
Note that while testing this enhancement it was observed
that when the VARY command was entered incorrectly, for
example, when the sluname was entered after a VARY
operand rather than immediately after the VARY command
(e.g., V OFF sluname) and no left hand modifiers were
set, the following error message was generated:
NASC100E ID= OMITTED, REQUIRED FOR V COMMAND EXECUTION
While it is true that when no resource name modifiers
are specified for a command that operates on them (e.g.,
LNM=, RNM= LUNM=) like the VARY command does, the command
reverts to the ID= modifier. If ID= is also omitted as
a left hand modifier, the NASC100E message is generated.
This can be confusing for users who are not used to using
the ID= modifier. For this reason, we have added text to
NASC100E error message that, hopefully, will further
explain why the message was issued. The new format for
the NASC100E message is as follows:
NASC100E ID= AND OTHER MODIFIERS OMITTED, REQUIRED
FOR V COMMAND EXECUTION
NASC100E ID= IS REQUIRED WHEN NO OTHER RESOURCE
IDENTIFICATION IS SPECIFIED
NASC100E IF COMMAND OPERATES ON LNM=, RNM= OR LUNM=,
ENSURE THAT RESOURCE NAME
NASC100E IS SPECIFIED BEFORE ANY COMMAND OPERANDS
(EXAMPLE: V LUNM=sluname OFF)
CIRCUMVENTION1: N/A
CIRCUMVENTION2: N/A
CIRCUMVENTION3: Use the DVC command to display the PID for the PVC
socket then issue VARY ID=pid FORCE to close the PVC
socket.
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).
2009-09-16 - APAR 2400097 (was problem 2009204A)
APAR: 2400097
STATUS: CLOSED
OPEN_DATE: 2009-07-23
CLOSE_DATE: 2009-09-16
SERVICE(S): DTF
MANDATORY: RECOMMENDED if Datafono pseudo leased resources used.
ORIGIN/REF: 240_ATC
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 2400097.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: 2009-08-13 with refresh APAR
2400095 and correction APAR 2400096 applied.
Refresh required if you are below the 2400095 APAR
level.
SUPERSEDES: N/A
OBJECT(S): MCHHL0RQ , MCHTMR
SOURCE(S): N/A
PROBLEM: HALT AT LOC xxxxxxxx IN MCHTMR : INV LU 3
DESCRIPTION: There is an error when processing an early session end for
a Datafono pseudo leased resource genned with the DATAF
and RETPIU options. The error occurs when the PLU sends
an 'M' message at the same time that the remote clears the
Datafono call. The alert "NAS5722W DATAFONO SESSION ENDED
ON LEASED LU lu-name (UNEXP'D CLR RECVD)
CAUSE/DIAG=(00/00) DIAGX=0000" is also present.
SOLUTION: End of session logic corrected.
If the PLU attempts to send data after the PIU associated
with the RETPIU Datafono option has been sent to the PLU
(this should not occur) then the VTAM session is ended
(ACB closed) and the following alert is issued:
NAS3799I LU lu-name ENDING SESSION ON MCH mch-nm HNAS
CAUSE/DIAG=000/223 (00/DF) DIAGX=0009
An enhancement part of this APAR causes HNAS to send the
following alert when the "Please Wait ..." message is sent
to a remote (EMSGE Datafono option):
NAS5726W EMSGE MESSAGE SENT TO LU lu-name (16 SEC PLU
DELAY)
This alert indicates that HNAS has been waiting 16 seconds
for a response from the PLU (the PLU is very busy). No
other action is taken (the EMSGE timer is restarted).
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).
2009-09-10 - APAR 2400096
APAR: 2400096
STATUS: CLOSED
OPEN_DATE: 2009-08-27
CLOSE_DATE: 2009-09-10
SERVICE(S): EOMKEY
MANDATORY: YES if an EOMKEY containing expired EOMDATE date is used.
ORIGIN/REF: 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 2400096.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): Distributions with APARs 2400095
their associated APAR chains applied.
SUPERSEDES: N/A
OBJECT(S): CONSMMEM, NASUTIL
SOURCE(S): NASMAIN, XFNASWA
OVERVIEW: EOMKEY correction for APAR 2400095.
PROBLEM: Invocation of EOMKEY containing an already expired
EOMDATE causes 45 day grace period to be ignored.
DESCRIPTION: If an EOMKEY is provided to extend an EOMDATE and
the new EOMDATE is itself already expired the grace
period warning alert messages (NAS9206i) operation
will be bypassed and customer specific severe alert
messages and services actions will occur immediately.
This occurs because the EOMDATE update logic fails to
initialize the ABEND grace period. This problem does
not occur when the EOMKEY contains an EOMDATE that is
not expired, that is, is beyond the current date
(TODAYSDATE).
SOLUTION: HNAS has been modified to initialize the grace period
correctly when an EOMKEY contains an already expired
EOMDATE.
General Notes for APAR 2400096:
1) The ability to set an older EOMDATE via an EOMKEY
is normally only used to simulate an EOMDATE
expiration during testing as directed by support
personnel (a parameter is available for testing).
Users with multiple EOMKEYs (saved for historical
reasons) should make sure that they are using the
current EOMKEY in their production environment.
This will ensure that you do not apply an expired
EOMKEY to a non-expired EOMDATE system.
2) Before putting a new EOMKEY in operation, you should
test it using the HNAS FASTRUN execution. This can
be done even while your production HNAS is running.
This will ensure that there are no surprises when
the EOMKEY is applied against your production HNAS.
Specify PARM='FASTRUN,EOMKEY=dd...dd'
3) Cosmetic fix.
Effective with APAR 2400095, DNAS display line 9
erroneously displays '000D' for the AUTH= value
for a permanent distribution when it should simply
display '000'. Although the '000' indicates a
permanent distribution and the trailing 'D' can be
ignored, the 'D' has been removed by this APAR thus
restoring the AUTH= display to it's previous
incarnation.
AUTH=000D SHIPID=0000000000199999 <- 2400095 display
AUTH=000 SHIPID=0000000000199999 <- 2400096 display
CIRCUMVENTION: Request an EOMKEY with an unexpired EOMDATE.
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).
2009-08-13 - APAR 2400095
APAR: 2400095_R
STATUS: CLOSED
OPEN_DATE: 2009-07-01
REV_DATE: 2009-08-13 - Recalled and Reissued.
CLOSE_DATE: 2009-08-13
SERVICE(S): EOMDATE Authorization Processing
MANDATORY: NO
ORIGIN/REF: 240_CPT
CPTECH: SFD
PTF_CLASS: STANDARD-APAR also includes enhancements
PTF_TYPE: REFRESH
PTF_LOC: Contact Support Services for Refresh E-distribution.
OVERVIEW: HNAS EOMDATE extension processing.
PROBLEM: A way is needed to extend the HNAS MAINTENANCE/USE
anniversary date (EOMDATE) without having to install
a new refresh distribution.
DESCRIPTION: Users cannot always install refresh edistributions
to extend an about to expire EOMDATE period due to
scheduling or 'no change' periods in their host
which could lead to HNAS generating warning|severe
alert messages and potential service or support
interruptions.
Prepaid Annual Maintenance/Use fees have always been
required to run the HNAS product and receive product
maintenance and support. The EOMDATE denotes the
End of Maintenance/Use date for the current prepaid
period. This date is used as follows:
- DNAS display provides the date in the following
format and is used by the user and HNAS product
support services to validate the current license
use period:
MAINTENANCE/USE ANNIVERSARY DATE IS 2009/12/31
- HNAS program will generate Information and Warning
alert messages (NAS9206I and NAS9206W) based upon
preset intervals prior to the EOMDATE expiration.
- HNAS program can generate Severe alert messages
(NAS9206S) and potential service interruptions
based upon preset intervals once the EOMDATE has
expired.
These messages are intended to provide reminders that
the HNAS MAINTENANCE/USE anniversary date is nearing
expiration or has already expired. These messages are
detailed in the HNAS Messages and Codes documentation.
It is important that the prepaid HNAS Maintenance/Use
period is renewed in a timely manner to avoid the
Sever messages or potential service interruption.
SOLUTION: HNAS has been modified to allow the EOMDATE to be
updated 'on the fly' using the new MMEM EOMKEY=dd...dd
console command and/or the new HNAS start parameter
PARM=(...,EOMKEY=dd...dd,...). The console command
is provided so that HNAS does not have to be stopped
and restarted in order to extend the EOMDATE. The
start parameter is provided so that the console
command does not have to be issued each time HNAS is
stopped and restarted. The console command is a
temporary EOMDATE update. The start parameter makes
the new EOMDATE permanent so long as the EOMKEY start
parameter is specified. The EOMDATE will revert to
it's original distribution value if the EOMKEY start
parameter is not specified or the console command is
not issued.
When a new EOMDATE is extended using an EOMKEY, the
DNAS display will reflect this using an asterisk (*)
after the date when the new EOMDATE record is written.
For example:
MAINTENANCE/USE ANNIVERSARY DATE IS 2010/12/31*
Notes: 1) The EOMKEY dd...dd string must be exactly
16 decimal digits in length.
2) The dd...dd string is an encrypted string
provided by Comm-Pro for a each user. The
EOMKEY string contains a new EOMDATE and the
CUSTID for the customer so that is unique for
each user. A special file is supplied as an
email attachment which contains the EOMKEY as
well as other identifying information. The
given EOMKEY will then have to be copied and
pasted as a MMEM console command argument or
a start parameter. The new EOMKEY file has
the following format:
EOMKEY=5962850727872317
HNAS EOMKEY CREATED AT 17:32:31 ON 2009/07/15
SHIPID=0000000000199999
CUSTID=SFD_99999
CUSTINFO=COMM-PRO ASSOCIATES
MAINTENANCE/USE ANNIVERSARY DATE IS 2011/01/31
3) If an invalid dd...dd string is specified,
HNAS will issue an error message but will
continue running.
As part of this APAR, the following new error messages
are provided:
NAS9203W HNAS EOMKEY IS INVALID, CUSTID DOES NOT
MATCH, IGNORED
NAS9203W KEYCID=99990 HNASCID=99999
NAS9203W HNAS EOMKEY IS INVALID, EOMDATE IS TOO
LOW, IGNORED
NAS9203W KEYEOM=20101130 HNASEOM=20101231
The messages above are issued if the supplied EOMKEY
contains a CUSTID value in error or an EOMDATE that
is less than the EOMDATE currently in effect (shown
in the DNAS MAINTENANCE/USE ANNIVERSARY DATE display).
Content in the NAS9206S EOMDATE expired messages was
modified to accommodate the EOMKEY logic. Please
refer to the alert messages section for additional
information.
CIRCUMVENTION: Install a product refresh distribution to extend
the EOMDATE.
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).
2009-06-16 - APAR 2400094
APAR: 2400094_E
STATUS: CLOSED
OPEN_DATE: 2009-05-01
CLOSE_DATE: 2009-06-16
SERVICE(S): Startup Parameter processing
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 2400094.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): Distributions with APARs 2400090, 2400089, 2400083 and
their associated APAR chains applied.
SUPERSEDES: N/A
OBJECT(S): CNFGEXEC, CNFGSCHD, CONSEXEC, CONSSCHD
SOURCE(S): NASMAIN, XFNASWA, XFPCE
OVERVIEW: The z/OS JCL scanner enforces a limit of 100 characters
within the PARM= operand on the EXEC statement.
PROBLEM: The EXEC start parameter string limit of 100 characters
can be too short.
DESCRIPTION: Because of the z/OS JCL limit of 100 characters for the
EXEC PARM= operand, you are limited as to how many start
parameters you can supply in the PARM= operand. For many
HNAS start parameters, there is an equivalent console
command which allows you to specify these commands in
the EXEC= (or CONCMDQ= operand) on the BUILD definition
statement so that the desired functions can be started
after the CDF is scanned instead of when HNAS processes
it's start parameters. This is a good workaround for the
100 character limit but does not address the problem when
a start parameter does not have an equivalent console
command.
SOLUTION: In order to allow ALL start parameters to be given when
HNAS is started, HNAS has been modified to accept a new
start parameter: PARMFILE=pfddname. This new parameter
is specified s follows:
PARM='...,PARMFILE=pfddname,...'
pfddname identifies a DDNAME in the HNAS start JCL that
represents a sequential file containing a list of other
start parameters.
Comments are allowed in the pfddname file and must start
with an asterisk (*) or semi-colon (;) in record column
one (1). Comments can also appear on a parameter record
but must start with a semi-colon after the parameter.
Each non-comment record in the pfddname file has the
following format:
parm ; comment
Multiple parameters can be specified on a single record
as follows:
parm1,parm2,...,parmn ; comment
Notes: 1) Leading and trailing blanks are removed from
each record before the values are processed.
2) An embedded PARMFILE= parameter in the
pfddname file will signal the end of data
in the file. Any records that follow the
embedded PARMFILE= parameter will be ignored
and the new pfddname file will be processed.
An embedded PARMFILE= parameter allows you
to chain parameter files. This can also be
done by specifying consecutive PARMFILE=
parameters in the PARM= operand as follows:
PARM='..,PARMFILE=pfddnm1,PARMFILE=pfddnm2,..'
3) When a PARMFILE= parameter is encountered in
the PARM= operand, the parameters in the
pfddname file are processed before any
subsequent parameters in the PARM= operand.
After the pfddname file is processed, HNAS
will process the remaining parameters in the
PARM= operand.
EXAMPLE: Assume the HNAS start JCL appears as follows:
//LDNAS240 JOB (),COMMPRO,MSGCLASS=X,MSGLEVEL=(1,1),NOTIFY=&SYSUID
//*ROUTE XEQ MVSESA1
//LOADNAS EXEC PGM=HNAS,REGION=0M,
// PARM='APFMEMSP=(230),PARMFILE=PFILE001,PARMFILE=PFILE002,GENNWDF'
//STEPLIB DD DSN=COMM1.V2R4M0.HNASLOAD,DISP=SHR
//VTAMLIB DD DSN=SYS1.VTAMLIB,DISP=SHR <- USSTAB
//* DD DSN=COMM1.V2R4M0.HNASLOAD,DISP=SHR <- CUSTOM USSTABS
//*NETVLIB DD DSN=NETVIEW.CNMLINK,DISP=SHR <- CNMNETV
//SYSPRINT DD SYSOUT=*
//SYSABEND DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//AUTH DD DSN=COMM1.V2R4M0.HNASMAC(NASAUTH),DISP=SHR
//PFILE001 DD DSN=COMM1.V2R4M0.HNASMAC(PFILE001),DISP=SHR
//PFILE002 DD DSN=COMM1.V2R4M0.HNASMAC(PFILE002),DISP=SHR
//NEWDEFN DD DSN=COMM1.V2R4M0.NEWCNFG(Z240NEW),DISP=OLD
//CONFIG DD DSN=COMM1.V2R4M0.OLDCNFG(Z240OLD),DISP=SHR
PFILE001 and PFILE002 identify 2 parameter files. These files are
listed below:
For PFILE001:
* PFILE001
* THIS PARMFILE CONTAINS ADDITIONAL PARMS THAT ARE ADDED
* TO THOSE IN THE EXEC PARM= OPERAND. SPECIFY AS
* PARM='...,PARMFILE=PFILENAM,...'
*
RMTCONS PRIV , TRCCONS ; CONSOLE OPTIONS
TRCSUBR ; TRACE SUBROUTINE CALLS
TRCWTO ; TRACE WTOS
SHOWCMSG ; COMPRESS WTOS
For PFILE002:
* PFILE002
* THIS PARMFILE CONTAINS ADDITIONAL PARMS THAT ARE ADDED
* TO THOSE IN THE EXEC PARM= OPERAND. SPECIFY AS
* PARM='...,PARMFILE=PFILENAM,...'
*
TRCDBK , TRCBST ; TRACE DATA BLOCK AND BINARY
STATS ON ; COLLECT STATS
TRCDISP,TRCDATA,TRCBFR,TRCIO ; TRACE PCE EVENTS
SVRSTRT ; ALLOW STACK RESTART
After processing the PARM= operand with the 2 parameter files, the
result is a PARM= parameter string that is logically equivalent to
the following:
// PARM='APFMEMSP=(230),RMTCONS PRIV,TRCCONS,TRCSUBR,TRCWTO,SHOWCMSG,TR*
// CDBK,TRCBST,STATS ON,TRCDISP,TRCDATA,TRCBFR,TRCIO,SVRSTR*
// T,GENNWDF'
The only difference is that the PARM= value above could not have been
specified in JCL because it exceeds the 100 character limit and thus
would have generated a JCL error.
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).
2009-05-28 - APAR 2400093 (was unpublished problem 2009138A)
APAR: 2400093
STATUS: CLOSED
OPEN_DATE: 2009-05-18
CLOSE_DATE: 2009-05-28
SERVICE(S): TCPIP
MANDATORY: REQUIRED to prevent potential ABEND.
ORIGIN/REF: 240_atc
CPTECH: SFD/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 2400093.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: 2009-03-13
With APARs: 2400089 applied.
SUPERSEDES: N/A
OBJECT(S): XOTXMTC
SOURCE(S): NASTCP
OVERVIEW: TCP/IP Select timeout processing.
PROBLEM: HALT AT LOC xxxxxxxx IN NASTCP : TCPIP TRANSMIT FAILURE
DESCRIPTION: The HALT is preceded by:
NAS2252E CLIENT=172.016.101.112(29421) NAME=xxxxxx SELECT
REQUEST INTERRUPT LOST, SOCKET MUST BE CLOSED
An error in HNAS close processing logic leads to a
TCPXMT call with an invalid PCE address of zero.
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).
2009-04-30 - APAR 2400092
APAR: 2400092
STATUS: CLOSED
OPEN_DATE: 2009-04-30
CLOSE_DATE: 2009-04-30
SERVICE(S): HNAS end-of-day timer processing
MANDATORY: YES
ORIGIN/REF: 240_CPT
CPTECH: SFD
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400092.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 2400089 and associated APAR chains.
SUPERSEDES: N/A
OBJECT(S): NASUTIL
SOURCE(S): N/A
OVERVIEW: HNAS end-of-day timer processing.
PROBLEM: NAS0910I end-of-day rollover message not generated.
DESCRIPTION: Due to logic added by APAR 2400089, HNAS end-of-day
processing is not executed. This prevents HNAS
PULSE from being taken and the following message
from being generated:
NAS0910I 3 BELLS AND ALL IS WELL AT 00:00:00 ON ...
SOLUTION: Error introduced by APAR 2400089 has been corrected.
CIRCUMVENTION: N/A
APPLY_INFO: See Chapter 6 (Product Maintenance Installation
section) from the HNAS Guide and Reference Manual
for instructions on how to install PTF's (Object,
Source and ZAPs) or Refresh/Upgrade maintenance.
Corrective logic included in distributions created
after CLOSE_DATE. Otherwise, apply maintenance as
directed in the APPLY_INFO (PTF).
2009-04-30 - APAR 2400091 (was problem 2009119A)
APAR: 2400091
STATUS: CLOSED
OPEN_DATE: 2009-04-29
CLOSE_DATE: 2009-04-30
SERVICE(S): MRMT applid update processing
MANDATORY: YES if you modify the SVC0|5 applid value
ORIGIN/REF: 240_NBK
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 2400091.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 2400084 and associated APAR chains.
SUPERSEDES: N/A
OBJECT(S): CONSMRMT
SOURCE(S): N/A
OVERVIEW: MRMT processing.
PROBLEM: SLU will not reconnect to VTAM application after the
SVC0|5 applid is changed using MRMT command to change
the PLU assignment.
DESCRIPTION: Due to an error in the setting of the applid field
(LUSVCAID) in the SLU control block (LUB), the SLU
status byte (LUSTAT) is overlaid making the SLU
appear offline. DLU command shows OFLN status when
it should show IDLE.
The result of this overlay is that the SLU ACB OPEN
routine will not issue an OPEN macro for the SLU thus
preventing any further communication with VTAM. The
SLU becomes unusable.
The MRMT syntax causing the problem is as follows:
MRMT SVC5=sluname/{dteaddr}I{applid}...
Specifically, the customer entered the following
command to change the applid from 0 to 5 for PAD SLU
A04TM900 to switch assignment to a different PLU.
MRMT RNM=L015 SVC5=A04TM900/I5
SOLUTION: The MRMT console command processor has been modified
to prevent the LUSTAT field from being overlaid when
an applid change takes place.
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).
2009-03-30 - APAR 2400090 (was problem 2009075A)
APAR: 2400090
STATUS: CLOSED
OPEN_DATE: 2009-03-16
CLOSE_DATE: 2009-03-30
SERVICE(S): Dataset Error Recovery Processing (including PRTSWLST
SYSPRINT switch processing).
MANDATORY: YES
ORIGIN/REF: 240_POR
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 2400090.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 2400089 and associated APAR chains.
SUPERSEDES: N/A
OBJECT(S): CNFGEXEC, CNFGPRSW, CNFGSCHD, CNFGTRTR,
CONSEXEC, CONSPRNT, CONSSCHD, CONSTRTR,
NASCNFG, NASPRNT, NASUTIL
SOURCE(S): XFBLK, XFCNFGWA
OVERVIEW: Problems related to how HNAS handles dataset (DCB)
ERP processing.
PROBLEM: HNAS ABENDs with 0C4-10 immediately after a recoverable
B37-04 ABEND occurs for a full SYSPRINT dataset.
DESCRIPTION: The recoverable B37-04 ABEND is supposed to force a
SYSPRINT switch to occur via the PRTSWLST= configuration
operand for static (DASD) datasets.
Due to an error in all HNAS DCB ABEND error processors
(not just those related to SYSPRINT datasets), HNAS
erroneously issues a CLOSE macro in the ABEND processors
which results in a 0C4-xx ABEND after the original ABEND
(normally a B37-04) occurs. ABEND exit routines are
invoked using a DCB exit list (the EXLST= operand when
the DCB is opened). The IBM Data Management Macro guide
specifically states that a DCB ABEND exit must not issue
any data management macro (for example, CLOSE) as part
of Error Recovery Processing. This piece of information
was inadvertently missed in the original DCB ABEND exit
implementation.
SOLUTION: All HNAS DCB ABEND exit routines have been modified to
NOT issue any data management macro but instead set a
flag that will be interrogated by 'mainline' logic
which will, in turn, issue the required CLOSE macro.
This will prevent the 0C4-xx ABEND from occurring
after the ABEND exit relinquishes control and mainline
code takes over. Specifically, this will allow SYSPRINT
switching within the PRTSWLST= operand to operate as
documented.
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).
2009-03-13 - APAR 2400089
APAR: 2400089
STATUS: CLOSED
OPEN_DATE: 2009-02-25
REVISE_DATE: 2009-03-12
CLOSE_DATE: 2009-03-13
SERVICE(S): General Maintenance for HNAS Authorization/Anniversary
EOM Date processing, Alarm logging and presentation.
ORIGIN/REF: 240_cpt
CPTECH: SFD
PTF_CLASS: STANDARD-APAR
PTF_TYPE: REFRESH (REQUIRED)
PTF_LOC: Contact Support Services for Refresh E-distribution.
COREQ(S): N/A
PREREQ(S): N/A
OBJECT(S): CNFGALMT, NASPRNT, NASUTIL, OSUT1
SOURCE(S): NASMAIN, NASTCP, XFNASWA, XFWTO
SUMMARY: This APAR contains a collection of changes identified
by Problem# (#=1|2|3) addressing various issues:
PROBLEM1: Logic changes to address HNAS End of Maintenance/Use
Anniversary Date (EOMDATE) validation processing.
DESCRIPTION1: See Problem.
SOULTION1: HNAS authorization check processing has been modified
to validate the End of Maintenance/Use Anniversary Date
(EOMDATE) which heretofore was displayed for information
only using the DNAS command.
MAINTENANCE/USE ANNIVERSARY DATE IS yyyy/mm/dd
For permanent users (AUTH=000 in the DNAS display),
runtime code has been modified to accommodate this
change which will now perform End of Maintenance/Use
validation as part of authorization check processing
based on EOMDATE=yyyy/mm/dd. This date reflects the
Maintenance/Use license anniversary date that was
in effect when HNAS was installed or refreshed.
EOMDATE validation is intended to provide a 'heads up'
notification as the HNAS Maintenance/Use license
approaches it's anniversary date.
HNAS will now interrogate the EOMDATE everyday at noon
and display the following messages based on how the
EOMDATE relates to the current date, that is, today's
date (TODAYSDATE).
If TODAYSDATE+45 < EOMDATE
NAS9206I HNAS MAINTENANCE/USE ANNIVERSARY DATE WILL
EXPIRE IN xxxx DAYS
If TODAYSDATE < EOMDATE <= TODAYSDATE+45
NAS9206W HNAS MAINTENANCE/USE ANNIVERSARY DATE WILL
EXPIRE IN xxxx DAYS
Note that the message severity has been changed from
I (Informational) to W (Warning) when EOMDATE is
within 45 days of TODAYSDATE.
If TODAYSDATE >= EOMDATE
NAS9206E HNAS MAINTENANCE/USE ANNIVERSARY DATE
EXPIRED xxxx DAYS AGO
In addition to the EOMDATE messages described above,
the following authorization message has been changed.
From: NAS9206I HNAS AUTHORIZATION FILE ALLOWS DATAFONO
SUPPORT
To: NAS9220I HNAS AUTHORIZATION FILE ALLOWS DATAFONO
SUPPORT
Additional information on this new authorization
processing is provided in the HNAS documentation.
CIRCUMVENTION1: Contact COMM-PRO for a refresh distribution.
PROBLEM2: Alarm logging table does not include all runtime
alarms.
DESCRIPTION2: Because the alarm logging table is allocated after
the CDF scan completes, a number of runtime alarms
(like NAS92xxs AUTH alarms) are not logged.
SOLUTION2: HNAS has been modified to allocate the alarm logging
table immediately after it starts with a default
entry limit of 512. The limit, which was previously
specified in the CDF as the ninth (last) suboperand
of the ALRMLMTS= operand, has been retired. If a
value is specified, the following configuration alert
message is generated:
NAS1101D BUILD ALRMLMTS LOGGING TABLE LIMIT PARAMETER
NAS1101D HAS BEEN RETIRED, 0512 ALWAYS USED
Note: Prior to this APAR, a user could specify a value
of zero (0) for the alarm logging table limit
which would prevent the table from being created.
Since the alarm logging table is an important
component for debugging problems, this change
means that the table will ALWAYS be generated.
CIRCUMVENTION2: N/A
PROBLEM3: Alarm logging table counts can be in error for some
alarm messages.
DESCRIPTION3: Because of an error in the processing of some multiple
line alarms (NAS2030I for example), the alarm counts
are not correct. This has to do with how the HNAS
WTO service routine (XFWTO) processes the WTO.
SOLUTION3: The XFWTO macro and it's service routine have been
fixed to process multi-line WTOs correctly so that
the alarm logging table reflects the proper alarm
count when displayed using the ALARM LOG=? command.
CIRCUMVENTION3: N/A
APPLY_INFO: N/A
2009-02-23 - APAR 2400088 (was unpublished problem 2009049B)
APAR: 2400088
STATUS: CLOSED
OPEN_DATE: 2009-02-17
CLOSE_DATE: 2009-02-23
SERVICE(S): Datafono
MANDATORY: RECOMMENDED if Datafono
ORIGIN/REF: 240_cgs
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 2400088.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.
SUPERSEDES: N/A
OBJECT(S): MCHHL0RQ
SOURCE(S): N/A
PROBLEM: Datafono (DTF) session ends after alert 'NAS5724W LU
lu-nm DID NOT RECEIVE 'M' MSG SYNC RESP FROM REMOTE'
DESCRIPTION: Customer PLU is sending a multiple element RU chain
containing a DTF 'M' message. The second (and last)
RU chain element requires a second HNAS buffer because
the size of FIC RU matched the X25 packet size.
The buffer is not allocated because HNAS is already
running the DTF M message D-- response timer (error).
Since the X25 M-bit chain does not complete, there is
no D-- response from the remote and the session fails.
SOLUTION: Logic for processing DTF FIC RU corrected so that an
RU chain for a DTF 'M' message is sent correctly.
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).
2009-02-10 - APAR 2400087 (was problem 2009300A)
APAR: 2400087
STATUS: CLOSED
OPEN_DATE: 2008-10-26
CLOSE_DATE: 2009-02-10
SERVICE(S): DATAFONO
MANDATORY: RECOMMENDED if Datafono resources
ORIGIN/REF: 240_ATC
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 2400087.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-12-12
With APAR: 2400084 applied.
SUPERSEDES: N/A
OBJECT(S): VCCLEAR
SOURCE(S): N/A
PROBLEM: Leased Datafono session ending with NAS3799I (ACB closed)
instead of NAS5721I (leased session end, ACB left open).
DESCRIPTION: This condition can occur if the remote sends a Clear to
HNAS when the LU is not in "response & disconnect" state
which indicates the clear is expected.
Customer had the RETPIU option coded which is supposed to
flush the PLU output when an unexpected clear is received.
The output was not flushed. This is because the code was
incorrectly) written to only test RETPIU if IMS was also
coded.
SOLUTION: HNAS Clear logic corrected so that RETPIU option does not
require the IMS 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).
2009-02-07 - APAR 2400086
APAR: 2400086_I
STATUS: CLOSED
OPEN_DATE: 2009-01-23
REVISE_DATE: 2009-mm-dd
CLOSE_DATE: 2009-02-05
SERVICE(S): HNAS Authorization Processing
MANDATORY: N/A
ORIGIN/REF: 240_cbs
CPTECH: SFD
PTF_CLASS: INTERNAL-APAR
PTF_TYPE: REFRESH (user refresh not required)
PTF_LOC: N/A
COREQ(S): N/A
PREREQ(S): N/A
OBJECT(S): NASUTIL
SOURCE(S): N/A
PROBLEM: Internal (non-user) logic changes to address HNAS
date authorization validation processing issues.
DESCRIPTION: See Problem.
SOLUTION: Runtime code modified to accommodate this change
which will now perform additional date validation
of the authorization files.
CIRCUMVENTION: N/A
APPLY_INFO: N/A
Last Update - December 29, 2009