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 2400106 | <Link forward> | - | - |
HNAS V2R4M0 - 2011 MAINTENANCE SUMMARY (Link to APARs 2400106 thru 2400nnn) |
| - | - | - | - | - |
|
2400105_E |
2010-11-15 |
TCPIP Debug |
OBJ/SRC |
Additional diagnostic logic is required to help solve the 'TCPIP REPLY ID FAILURE' ABEND problem which is enabled by the 'DBUG TCP' option - now a default option. |
|
2400104_R |
2010-10-29 |
Cons-Subsystem |
<Refresh Required> |
DNAS command does not show missing maintenance when there are holes in the APAR sequence due to a bug introduced by APAR 2400103. |
|
2400103_RE |
2010-09-21 |
Cons-Subsystem |
<Refresh Required> |
Enhancement providing DNAS display output regardless of the FASTRUN CC-rc and added z/OS level displays. |
|
2400102_+E |
2010-04-28 |
TCPIP Debug and General Maint. |
OBJ/SRC |
This APAR contains 1 fix and 3 enhancements for the following
conditions: |
| 2010-04-07 |
PVCs via sysplex distributor |
OBJ |
When one of 2 HNASs in a
SD (sysplex distributor) is shut |
|
|
2400100_E |
2010-04-02 |
NASAUTH |
OBJ |
HNAS has been modified to check all HNASAUTH file fields after an error is detected and report all errors before ABENDing to improve the debugging process. |
| 2010-01-15 |
DTF (Datafono) |
OBJ |
HALT AT LOC xxxxxxxx IN MCHPQ : ELEMENT NOT FOUND. |
|
| - | - | - | - | - |
|
2400098 thru 2400086 |
<Link back> | - | - |
HNAS V2R4M0 - 2009 MAINTENANCE SUMMARY (Link to APARs 2400086 thru 2400098) |
|
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.
2010-11-15 - APAR 2400105 (created to help solve problem 2009111A)
(new PMR #23825 opened for this problem)
APAR: 2400105
STATUS: CLOSED
OPEN_DATE: 2010-11-09
CLOSE_DATE: 2010-11-15
SERVICE(S): TCP/IP interface support
MANDATORY: YES, for improved debugging
ORIGIN/REF: 240_SRP
CPTECH: SFD
PTF_CLASS: STANDARD-APAR with diagnostic ENHANCEMENT
PTF_TYPE: (SRC) HNASMACX and (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400105.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) Previous distribution at APAR level 2400103 or above.
SUPERSEDES: N/A
OBJECT(S): NASUTIL
SOURCE(S): NASMAIN, NASTCP, XFBLK, XFNASWA, XFPCE
PROBLEM: Additional diagnostic logic is required to help solve
the 'TCPIP REPLY ID FAILURE' ABEND problem which is
enabled by the 'DBUG TCP' option - now a default
option.
DESCRIPTION: The 'TCPIP REPLY ID FAILURE' ABEND problem seems to be
related to the SELECT background timeout condition.
At one of our current customer sites, it appears that
that after HNAS has been running for 13 days with no
no problems, suddenly the customer starts seeing
'NAS2252E SELECT INTERRUPT LOST' messages. This seems
to occur early in the morning (2:08am) when one might
expect not much to be going on. No one at the customer
site can tell us what the system was doing during this
period. These NAS2252E messages are generated when the
SELECT background timer expires.
HNAS always runs a background timer on SELECT commands.
SELECTs are conditioned to end either when something
is received from the network (a new call for a LOCAL
or data for a REMOTE) or when a TCPIP stack timeout
occurs. The stack timeout is set for 60-seconds while
the HNAS background timer is set for 90-seconds. The
logic being that if everything is working properly
when no input is received, the stack timer will 'pop'
before the HNAS background timer does. At 2:08am at
the customer site, the stack timer does not go off to
end the SELECT so the HNAS background timer does. This
is disturbing. The stack should ALWAYS end a SELECT.
The 'TCPIP REPLY ID FAILURE' ABEND occurs, we believe,
because HNAS is receiving an ending for a new SELECT
command that really was for a previous SELECT command.
After a SELECT background timeout occurs, a new SELECT
is issued. The interrupt that HNAS receives for the new
SELECT is the one for the previous SELECT (i.e., the one
that HNAS timed out). We do not know what would cause
the stack to postpone presenting the ending for the
previous SELECT. Logic was added for APAR 2400102 that
allows HNAS to ignore the 'TCPIP REPLY ID FAILURE'
condition in order to prevent the ABEND from occurring.
This logic was enabled by specifying 'DBUG TCP' as a
start parameter (the 'DBUG TCP' start parameter was
added for APAR 2400102 and is now the default for
APAR 2400105). Instead of the ABEND, the following
alarm message will be generated:
NAS2110S INVALID TCPIP INTERRUPT REPLY ID, IGNORED
FOR cmdname
Where cmdname is the command receiving the invalid
TCPIP REPLY ID.
Note that the SELECT background timeout logic was added
many years ago for another HNAS customer. In that case
once a SELECT failed to end, it was permanent condition
unlike what appears to be happening at the current
customer site. A SELECT that never ends puts HNAS in
a 'hung' state, unable to accept new calls or user
input. IBM was involved with the original problem and
most likely made changes to the stack that now cause
the timed out SELECT to eventually end. However, we
were never informed by IBM regarding any potential
changes that they made to the stack.
SOLUTION: We now believe that it is probably necessary for HNAS
to always wait for a SELECT to end rather than trying
to CANCEL it and starting a new SELECT when the HNAS
background timer expires. This, hopefully, will
eliminate the 'TCPIP REPLY ID FAILURE' ABEND problem.
Instead of cancelling and restarting a SELECT when the
HNAS background timer expires, HNAS will now issue an
alarm message and then wait some more. Based on what
we have observed, the original SELECT should eventually
end, albeit much later than expected.
HNAS has been modified to issue the following alarm
messages when a SELECT or CANCEL background timeout
occurs. The 'DBUG TCP' start parameter must be in
effect and is set by default by this APAR.
For a LOCAL SELECT:
NAS2252E SERVER=172.029.127.220(01998) SOCKID=0000
PCEID=0009 NAME=LXOT
NAS2252E SELECT SHOULD HAVE ENDED 00nnn SECONDS AGO,
WAITING
If, after this message is issued 10 consecutive times
(840 seconds), HNAS assumes that the SELECT will not
successfully end and the following message is generated:
NAS2252E SERVER=172.029.127.220(01998) SOCKID=0000
PCEID=0009 NAME=LXOT
NAS2252E SELECT INTERRUPT LOST, RETRY WILL BE ATTEMPTED
For a REMOTE SELECT:
NAS2252E CLIENT=010.117.056.100(01128) SOCKID=0001
PCEID=000C NAME=R1CNIN
NAS2252E SELECT SHOULD HAVE ENDED 00nnn SECONDS AGO,
WAITING
If, after this message is issued 10 consecutive times
(840 seconds), HNAS assumes that the SELECT will not
successfully end and the following message is generated:
NAS2252E CLIENT=010.117.056.100(01128) SOCKID=0001
PCEID=000C NAME=R1CNIN
NAS2252E SELECT INTERRUPT LOST, SOCKET MUST BE CLOSED
For a LOCAL CANCEL:
NAS2152E SERVER=172.029.127.220(01998) SOCKID=0000
PCEID=0009 NAME=LXOT
NAS2152E SELECT SHOULD HAVE ENDED 00nnn SECONDS AGO,
WAITING FOR SELECT
If, after this message is issued 10 consecutive times
(300 seconds), HNAS assumes that the CANCEL will not
successfully end and the following message is generated:
NAS2152E SERVER=172.029.127.220(01998) SOCKID=0000
PCEID=0009 NAME=LXOT
NAS2152E CANCEL INTERRUPT LOST, NORMAL COMPLETION
ASSUMED FOR SELECT
For a REMOTE CANCEL:
NAS2252E CLIENT=010.117.056.100(01128) SOCKID=0001
PCEID=000C NAME=R1CNIN
NAS2152E SELECT SHOULD HAVE ENDED 00nnn SECONDS AGO,
WAITING FOR SELECT
If, after this message is issued 10 consecutive times
(300 seconds), HNAS assumes that the CANCEL will not
successfully end and the following message is generated:
NAS2252E CLIENT=010.117.056.100(01128) SOCKID=0001
PCEID=000C NAME=R1CNIN
NAS2152E CANCEL INTERRUPT LOST, NORMAL COMPLETION
ASSUMED FOR SELECT
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).
2010-11-03 - APAR 2400104
APAR: 2400104
STATUS: CLOSED
OPEN_DATE: 2010-10-28
CLOSE_DATE: 2010-10-29
SERVICE(S): DNAS logic to detect missing APAR(s).
MANDATORY: NO, BUT RECOMMENDED
ORIGIN/REF: 240_CPT
CPTECH: SFD
PTF_CLASS: STANDARD-APAR
PTF_TYPE: REFRESH
PTF_LOC: Contact Support Services for Refresh E-distribution.
PROBLEM: DNAS command does not show missing maintenance when
there are holes in the APAR sequence.
DESCRIPTION: Due to a bug introduced by APAR 2400103, the DNAS
command does not list missing APARs. This can only
occur if a user applies maintenance subsequent to
installing the HNAS product and there are gaps between
the highest APAR number shipped and the last APAR
number applied.
SOLUTION: HNAS has been modified to detect and display missing
APAR numbers. For example, the following is displayed
when APARs 2400002, 2400012 and 2400072 have not been
applied.
HOST NAS INFORMATION FOLLOWS
HNAS VERSION=V2R4M0 DIST=NON-SMP
HNAS PROGRAM RUNNING UNDER z/OS 01.11.00
HNAS PRODUCT INSTALLED UNDER z/OS 01.11.00
HNAS PRODUCT CREATED UNDER z/OS 01.11.00
DNAS COMMAND ENTERED AT 08:06:39 ON 2010/10/29
HNAS PROGRAM STARTED AT 18:29:32 ON 2010/10/28
HNAS PRODUCT INSTALLED AT 08:07:00 ON 2010/10/15
HNAS PRODUCT CREATED AT 07:08:18 ON 2010/09/16
HNAS PRODUCT CREATED WITH MAINTENANCE THROUGH APAR 2400000
MOST RECENT MAINTENANCE APPLIED IS APAR 2400104
AUTH=000 SHIPID=1100000011199999
CUSTID=SFD_99999
CUSTINFO=COMM-PRO ASSOCIATES
MAINTENANCE/USE ANNIVERSARY DATE IS 2010/09/31
DATAFONO SUPPORT IS INCLUDED
APARID MAINTENANCE STATUS
2400002 NOT INSTALLED
2400012 NOT INSTALLED
2400072 NOT INSTALLED
CIRCUMVENTION: Issue DNAS APAR command to see an ordered list
of all APARs on the HNAS system.
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)
2010-09-24 - APAR 2400103
APAR: 2400103
STATUS: CLOSED
OPEN_DATE: 2010-09-10
CLOSE_DATE: 2010-09-21
SERVICE(S): FASTRUN DNAS processing and DNAS z/OS display info.
MANDATORY: NO
ORIGIN/REF: 240_CNS
CPTECH: SFD
PTF_CLASS: ENHANCEMENT-APAR
PTF_TYPE: REFRESH
PTF_LOC: Contact Support Services for Refresh E-distribution.
OVERVIEW: Execution of DNAS unconditionally for FASTRUN processing
would allow quicker problem diagnosis.
PROBLEM: Customer FASTRUN fails when Datafono resources are coded
in the CDF but user expected no errors because Datafono
support was supposed to be included.
DESCRIPTION: The distribution that Comm-Pro provided to the customer
was supposed to include Datafono support but CDF errors
were generated during a FASTRUN execution when Datafono
resources were specified. Because the DNAS command was
not executed during FASTRUN, the Datafono support flag
could not be examined in the SHIPID line in the DNAS
display. When the customer specified FASTRUN CONCMDQ
as a start parameter, the DNAS command was still not
executed because of the configuration errors (RC>4
causes FASTRUN CONCMDQ to terminate without DNAS
execution). In order to verify whether or not the
Datafono support flag was set, the customer had to
remove all Datafono resources from the CDF then
re-execute HNAS with FASTRUN CONCMDQ.
SOLUTION: HNAS has been modified to force execution of the DNAS
command for FASTRUN regardless of the severity of the
configuration errors.
Note: FASTRUN is now treated the same as FASTRUN CONCMDQ
In addition, the DNAS command display has been enhanced
provide additional diagnostic information.
The following DNAS output is effective as of this APAR.
HOST NAS INFORMATION FOLLOWS
HNAS VERSION=V2R4M0 DIST=NON-SMP
HNAS PROGRAM RUNNING UNDER z/OS 01.10.00
HNAS PRODUCT INSTALLED UNDER z/OS 01.10.00 <- new line
HNAS PRODUCT CREATED UNDER z/OS 01.10.00
DNAS COMMAND ENTERED AT 07:33:27 ON 2010/09/16
HNAS PROGRAM STARTED AT 07:33:26 ON 2010/09/16 <- new line
HNAS PRODUCT INSTALLED AT 07:29:00 ON 2010/09/16
HNAS PRODUCT CREATED AT 07:08:18 ON 2010/09/16
HNAS PRODUCT CREATED WITH MAINTENANCE THROUGH APAR 240BETA
MOST RECENT MAINTENANCE APPLIED IS APAR 2400103
AUTH=000 SHIPID=1100000011199999
CUSTID=SFD_99999
CUSTINFO=COMM-PRO ASSOCIATES
MAINTENANCE/USE ANNIVERSARY DATE IS 2010/09/31
DATAFONO SUPPORT IS INCLUDED
ALL MAINTENANCE ON THROUGH MOST RECENT APAR 2400103
The following DNAS output is prior to this APAR.
HOST NAS INFORMATION FOLLOWS
HNAS VERSION=V2R4M0 DIST=NON-SMP
ASMDATE=2009/08/12 ASMHOST=ZOS <--- deleted
RUNNING UNDER z/OS 01.10.00
DNAS COMMAND ENTERED AT 12:54:50 ON 2010/09/20
HNAS PROGRAM STARTED AT 12:54:50 ON 2010/09/20
HNAS PRODUCT CREATED AT 19:35:30 ON 2009/08/12
CREATED WITH MAINTENANCE THROUGH APAR 240BETA
MOST RECENT MAINTENANCE APPLIED IS APAR 2400102
AUTH=000 SHIPID=1100000011199999
CUSTID=SFD_99999
CUSTINFO=COMM-PRO ASSOCIATES
MAINTENANCE/USE ANNIVERSARY DATE IS 2010/09/31
DATAFONO SUPPORT IS INCLUDED
ALL MAINTENANCE ON THROUGH MOST RECENT APAR 2400102
CIRCUMVENTION: Remove Datafono resources and specify FASTRUN CONCMDQ
to force DNAS execution.
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).
2010-04-28 - APAR 2400102 (created to help solve problem 2009111A)
(new PMR #23825 opened for this problem)
APAR: 2400102_+E
STATUS: CLOSED
OPEN_DATE: 2010-04-06
CLOSE_DATE: 2010-04-28
SERVICE(S): TCP/IP interface support, PULSE support
MANDATORY: NO, but recommended for improved debugging.
ORIGIN/REF: 240_FIS
CPTECH: SFD
PTF_CLASS: STANDARD-APAR with diagnostic ENHANCEMENTS
PTF_TYPE: (SRC) HNASMACX and (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400102.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) Previous distribution at APAR level 2400100 or above.
Note: Due to the large number of PREREQs, we
recommend a REFRESH distribution to pickup
this enhancement APAR.
SUPERSEDES: N/A
OBJECT(S): CNFGBFSZ, CNFGLGTB, CNFGOPTS, CNFGUSTB,
CONSDLU, CONSDMCH, CONSDVC, CONSMRMT,
CONSPING, CONSTLU, CONSTLUQ, CONSTMCH,
CONSTMCX, CONSTVC, CONSTVCQ, MCHINI,
NASCNFG, NASUTIL, QLSSCP, XTPRCV
SOURCE(S): NASMAIN, NASTCP, XFBLK, XFNASWA, XFPCE
OVERVIEW: Minor fixes are provided by this APAR as well as
additional diagnostic logic to help solve the invalid
TCPIP reply ID ABEND problem.
PROBLEM1: Specified PULSE frequency value is being erroneously
increased by one before counting down.
DESCRIPTION1: When a PULSE frequency of 60 (for example) is specified
(PULSE=(hh:mm:ss,hh:mm:ss,60)), it is actually treated
as 61. To have the PULSE message (NAS0299I) issued once
per minute, you have to specify 59 as the frequency.
SOLUTION1: HNAS has been modified to use the specified frequency
value as is rather than adding one (1) to it.
CIRCUMVENTION1: Specify a PULSE frequency value one less than the
frequency you actually want.
PROBLEM
ENHANCEMENT2: Enhancement that allows an alarm message to be issued
when CANCEL command timeout occurs.
DESCRIPTION2: Unlike the NAS2252E message that is issued when a
SELECT background timeout occurs, no equivalent message
is generated when a CANCEL background timeout occurs.
This can hide the fact that there is a problem with
the processing of the CANCEL sequence. While it is
possible to discern that a CANCEL background timeout has
occurred by looking at the TCPIP external interrupt
table, there is no record of it written in the HNAS
SYSPRINT.
SOLUTION2: HNAS has been modified to issue the following alarm
message when a CANCEL background timeout occurs:
NAS2152E CANCEL REQUEST INTERRUPT LOST, NORMAL
COMPLETION ASSUMED FOR command
Note: In addition to this new alarm message, the CANCEL
background timeout has been extended from 15 to
30 seconds.
CIRCUMVENTION2: N/A
PROBLEM
ENHANCEMENT3: Enhancement that logs diagnostic information within
each TCPIP external interrupt data record (additional
logic supplements logic added for APAR 2400042).
DESCRIPTION3: Customer has experienced a 0198 ABEND (NASHALT validity
check) after receiving the following alarm messages:
NAS2252E CLIENT=010.253.204.035(18640) SOCKID=0017
PCEID=010C NAME=XOTBNP3I
NAS2252E SELECT REQUEST INTERRUPT LOST,
SOCKET MUST BE CLOSED
These messages are followed by the following NASHALT:
HALT AT LOC 80061022 IN NASTCP : TCPIP REPLY ID FAILURE
ABEND dump contained TCPIP external interrupt table but
table did not contain enough information to determine
the cause of the NASHALT. Advised customer to run HNAS
TCPIP traces to collect additional diagnostic data.
SOLUTION3: HNAS has been modified to log additional diagnostic
data within the TCPIP external interrupt area making
the need for HNAS TCPIP traces less of a requirement.
This new logic will provide almost the same information
as standard HNAS TCPIP tracing but without the added
CPU overhead associated with event tracing. It is
expected that the new TCPIP external interrupt entry
data will show why this failure is occurring (see
problem 2009111A for more information).
Note: This enhancement allows the TCPIP request return
code plus start and end timestamps to be included
in each interrupt table entry.
CIRCUMVENTION3: Disable LU, MCH and VC traces and start global PCE
traces: TRCALL OFF TRCPCE ALLON
PROBLEM
ENHANCEMENT4: Diagnostic enhancement that allows the TCPIP REPLY ID
ABEND to be bypassed.
DESCRIPTION4: It is possible that HNAS can survive when an invalid
TCPIP reply ID is received although it is difficult
to predict what will happen after this condition is
ignored.
SOLUTION4: HNAS has been modified to ignore an invalid TCPIP reply
ID as well as a TCPIP interrupt that occurs with no
request (command) active. This new processing will
only take place if the new 'DBUG TCP' option is
specified as an HNAS start parameter.
If this new option is specified, rather than ABENDing,
the following new alarm messages are issued based on
when an invalid TCPIP interrupt occurs. HNAS continues
to run rather than terminating.
The following alarm message is issued when a TCPIP
interrupt occurs that is not expected (no command
is running which implies that no command ending
interrupt is expected). Normally, this would cause
a 'TCPIP INTERRUPT UNEXPECTED' 0198 ABEND.
NAS2109S CLIENT=010.117.056.100(04545) SOCKID=0001
PCEID=000C NAME=R1CNIN
NAS2109S UNEXPECTED TCPIP INTERRUPT, IGNORED
NAS2109S IPARM=0001850200000024001300FAD5C1E2E3F0E3E2D6
0000D740004EA808004EAB900000000000508C00
0000000001000000001348352413483533
The following alarm message is issued when a TCPIP
interrupt occurs with an invalid reply ID (does not
match the reply ID for the currently active command).
Normally, this would cause a 'TCPIP REPLY ID FAILURE'
0198 ABEND.
NAS2110S SERVER=172.029.127.220(01998) SOCKID=0000
SOCKID=0000 PCEID=0009 NAME=LXOT
NAS2110S INVALID TCPIP INTERRUPT REPLY ID, IGNORED
FOR SELECT
NAS2110S EXPECTED=0000001D PRESENTED=0000001C
NAS2110S IPARM=000185020000001C001300FAD5C1E2E3F0E3E2D6
0000D740004E8C18004E8FA000000000005187E0
00000000000000001209175512101732
Note: The IPARM value specified in both the NAS2109S
and NAS2110S messages above is the actual TCPIP
external interrupt table entry at the time of
the error, that is, the one that caused the
problem.
CIRCUMVENTION4: N/A
APPLY_INFO: See Chapter 6 (Product Maintenance Installation
section) from the HNAS Guide and Reference Manual
for instructions on how to install PTF's (Object,
Source and ZAPs) or Refresh/Upgrade maintenance.
Corrective logic included in distributions created
after CLOSE_DATE. Otherwise, apply maintenance as
directed in the APPLY_INFO (PTF).
2010-04-07 - APAR 2400101 (was problem 2009295A)
APAR: 2400101
STATUS: CLOSED
OPEN_DATE: 2009-10-22
CLOSE_DATE: 2010-04-07
SERVICE(S): PVC
MANDATORY: YES
ORIGIN/REF: 240_FIS
CPTECH: prt
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400101.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): Installations below the 2400095 level should order a
refresh distribution at the 2400101 level.
For installations at or above 2400095 the 2400097 and
2400099 APARs are PREREQs for this APAR.
SUPERSEDES: N/A
OBJECT(S): VCCLRQ , MCHHRSP , MCHTMR , XOTRCV , VCRESET , XOTXMTC
SOURCE(S): N/A
OVERVIEW: See problem
PROBLEM: When one of 2 HNASs in a SD (sysplex distributor) is shut
down some PVCs do not migrate to the working HNAS LPAR.
DESCRIPTION: The SD balances the sessions between 2 HNAS LPARS. When
one HNAS is shut down some PVC sessions do not migrate
to the working LPAR. This is caused by a timing problem.
When an XOT PVC activates (PVC Setup packet exchange)
the PLU session is activated (VTAM REQSESS operation).
The router sends a CAUSE=0F RESET to indicate that the
PVC is operational. If the PLU is first speaker and it
sends the first message while the CAUSE=0F reset is in
transit then the first message is discarded at the remote
end (which is in RESET sent state). The PLU 'hangs'
waiting for a response to the first message.
SOLUTION: HNAS will not activate the PLU until the PVC operational
RESET is received. If the reset does not arrive in 2
minutes then a CAUSE=0F RESET is sent to the remote by
HNAS and the PLU session is activated.
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).
2010-04-02 - APAR 2400100
APAR: 2400100_E
STATUS: CLOSED
OPEN_DATE: 2010-03-30
CLOSE_DATE: 2010-04-02
SERVICE(S): Authorization File (NASAUTH) message processing
MANDATORY: NO
ORIGIN/REF: 240_CBG
CPTECH: SFD
PTF_CLASS: ENHANCEMENT-APAR
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400100.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 2400098 and their
associated APAR chains applied.
SUPERSEDES: N/A
OBJECT(S): NASUTIL
SOURCE(S): N/A
PROBLEM: HNAS does not report all possible errors when a NASAUTH
file validation failure occurs.
DESCRIPTION: When HNAS detects an error in a NASAUTH authorization
file, it stops processing the file and issues an
appropriate alarm message before ABENDing with 0198.
It would be more informative if HNAS postponed the
ABEND until the entire NASAUTH file was processed.
This would report all errors in the NASAUTH file if
more than one is present. This would then provide
additional information as to whether the NASAUTH file
became corrupted or was simply the wrong file for
current distribution. The latter usually occurs
because the //AUTH DD statement points at the wrong
library.
SOLUTION: HNAS has been modified to check all NASAUTH file
fields after an error is detected and report all
errors before ABENDing.
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).
2010-01-15 - APAR 2400099 (was problem 2009352A)
APAR: 2400099
STATUS: CLOSED
OPEN_DATE: 2009-12-18
CLOSE_DATE: 2010-01-15
SERVICE(S): DATAFONO
MANDATORY: YES if DATAFONO resources.
ORIGIN/REF: 240_CAM
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 2400099.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 APARs: 2400095 through 2400098 applied.
Refresh recommended.
SUPERSEDES: N/A
OBJECT(S): MCHNRQC MCHTMR VCCLEAR VCDAT
SOURCE(S): N/A
PROBLEM: HALT AT LOC xxxxxxxx IN MCHPQ : ELEMENT NOT FOUND
DESCRIPTION: Pseudo leased LU left on a real MCH's MCHLUIQ when the
LU was moved to the system MCH (to make it available for
leased allocation).
The problem occurs under the following circumstances:
1) Pseudo leased LU configured with OPTIONS=(DATAF,EMSGE,
RETPIU).
2) EMSGE sent to remote (no PLU response to message from
the remote in 16 seconds).
3) Remote clears the call.
4) Because of the RETPIU option, HNAS waits for the PLU
to send an 'L' message. When the 'L' is received
the first message not sent to the PLU is returned to
the PLU with a leading '?' character. An error in
the RETPIU logic causes the HALT.
SOLUTION: RETPIU logic corrected.
CIRCUMVENTION: N/A
APPLY_INFO: See Chapter 6 (Product Maintenance Installation
section) from the HNAS Guide and Reference Manual
for instructions on how to install PTF's (Object,
Source and ZAPs) or Refresh/Upgrade maintenance.
Corrective logic included in distributions created
after CLOSE_DATE. Otherwise, apply maintenance as
directed in the APPLY_INFO (PTF).
Last Update - December 31, 2010