This HNAS Problem Summary documentation area provides
information Datafono problem activity for the HNAS product 230.c product level.
This section is provided
to assist customers in their identification of problems for troubleshooting
and fault isolation by identifying problems currently under review or analysis,
and identifying non APAR problems or anomalies.
Please contact your HNAS first level
technical support representative or access their problem reporting system for
specific problem tracking; or refer to the respective APAR Maintenance Summary
sections for APAR activity. Problem summary entries are in the same format
as our APAR memo's for ease of viewing and eventual conversion to actual APARs, as
required. APAR entries provide standard corrective logic (PTF)
maintenance, instructions on circumventing various problems (configuration changes,
etc.) and may defer correction to a later HNAS VnRnMn release. Some problem log
entries may contain circumventions in lieu of APAR assignment pending resolution in a later
release.
| Problem # | Open_Date | Close_Date | Service | Origin/Ref Type |
Status Resolved in HNAS VRM |
|---|---|---|---|---|---|
| - | - | - | - | - | - |
| Note | Date-> | 2006-09-18 |
- |
- | We no longer provide standard maintenance for the 230.c product. We advise all 230.c Datafono users to upgrade to the 240 product. Emergency maintenance support is still provided for 230.c as required by the end user although corrective action may require an upgrade to 240. |
| Note | Date-> | 2006-08-01 |
- |
- | We recommend that Datafono users upgrade from the interim 230.c release to 240 now that the release is available. |
| 2006131A | 2006-05-11 | 2006-05-11 | <Datafono> | CPT_230 |
P6131A Corrective logic included in distributions created as of: 2006-05-11
- <A configuration loop will result if the names of 2 MCHs in the CDF are the same in the first 4 character positions.> |
| 2006093A | 2006-04-03 | 2006-04-03 | <Datafono> | CCS_230 |
P6093A Corrective logic included in distributions created as of: 2006-04-03
19:00 pst.- <PING (XOT) causes Abend in Datafono 230.c systems.> |
| 2006079A | 2006-03-20 | 2006-04-05 |
LLC-0/LLC-5 Callout (CICS) Appl. in Spain. <non-Datafono |
CCS_230 (230.c) & 240 |
P6079A
corrective logic is now included in 230.c & 240 distributions created as of: 2006-04-04) - <Customer would like +RSP to BIND that triggers a callout to be sent when call accept received. CICS would show 'being ACQUIRED' as the resource status.> Standard support in 240 (not provided in 230) |
| 2006075A | 2006-03-16 | 2006-mm-dd | <Datafono> | CGS_230 |
OnHold, Pending Additional User Input - <NAS5728E and NAS3799I Alert messages encountered.> |
| 2006011A | 2006-01-11 | 2006-01-31 | pseudo-leased <Datafono> |
CGS_230 |
DTFB04
corrective logic included in distributions created as of: 2006-01-11). Problem: HALT AT LOC xxxxxx IN VTMLURL : INV LU followed by U198 ABEND. Description: This problem results from incorrect logic which occurs when HNAS sends an UNBIND to the PLU in response to a SHUTDOWN request from the PLU. After the UNBIND is delivered the completion routine calls the LU release routine without checking for a Datafono leased resource (which is always active and never released).> |
| Note | - | 2006-01-11 |
- |
- | Date formats changed from mm-dd-yyyy to yyyy-mm-dd in this document. |
| 2005329B | 2005-11-25 | 2005-12-19 | pseudo-leased <Datafono> |
CGS_230 | DTFB03 - corrective logic included in distributions created as of: 2005-12-19). < USER 198 ABEND with "HALT AT LOC xxxx IN VTMLURL: INV LU" when CICS brought down. When CICS is terminated it UNBINDs its active LUs. The processing for pseudo-leased Datafono LUs (which are always active) has a logic error that results in the above HALT.> |
| 2005329A | 2005-11-25 | 2006-03-16 | <Datafono> | CGS_230 |
DTFB05 -
corrective logic included in distributions created as of:2006-03-10
- <Customer receiving NAS5722E RECEIVING INVALID D(9) MSG FROM RMT rmt-nm FOR LU lu-nm ON MCH mch-nm RECV ST=R(3) SEND ST=R(4). The message indicates that HNAS thinks the D(9) message (used by the remote to ask the PLU for the next M message segment) is out of sequence. It appears that it is but a trace is required so we can see what is going on.> |
| 2005328A | 2005-11-24 | 2005-11-29 |
Console Ping xot <Datafono> |
CCS_230 |
DTFB02 -
corrective logic included in distributions created as of: 2005-11-29). <HNAS U198 ABEND when Ping to an IP DCE address is attempted via the console> |
| 2005321A | 2005-11-17 | 2005-12-21 |
TCP/IP Interface Support <Datafono> |
CCS_230 |
APAR_2300170
<NASHALT U198 ABEND when HNAS is running and the TCP/IP Stack is forced down. INITAPI is being rejected with erno= 1036 and a subsequent NASHALT results after successful GETIPBOPT request indicates that stack is up.> |
| 2005277D | 2005-10-04 | 2005-10-04 |
GATE <Datafono> |
GCS_230 |
DTFB01 -
corrective logic included in distributions created as of: 2005-10-05). <HALT AT LOC xxxxxx IN MCHTMR : INV VCCLOCK As a result of timer modifications made for Datafono, HNAS terminates when the REQSESS delay timer expires for a GATE (LLC4) session. The problem only occurs if GATE resources are defined and the REQSESS delay timer is used.> |
| 2004341A | 2004-12-04 |
2004-12-31 UFO |
CONSOLE SUBSYSTEM (DNAS, first cmd execution) <Datafono> |
CPT_230 |
see Circumvention. <DMAP APAR command causes 0C1 ABEND when HNAS is started because it is loaded on a double word (DW) rather than a quadruple word (QW) boundary.> |
| 2005313A | 2005-11-09 | 2006-02-17 |
CDF Resources <Datafono> <Deferred 240> |
DTF_230 |
Improvements incorporated in the upcoming HNAS 240 release. <CDF Scanner improvements requested for some DataFono configuration options will be provided in the 240 release.> |
| - | - | - | - | - | - |
| - | - | - | - | - |
Under_Analysis/Testing - Fix Under development - |
|
IBM PMR# |
Open_Date |
Close_Date |
Service |
Type |
HNAS VRM References |
|---|---|---|---|---|---|
|
- |
- |
- > |
-> |
-> |
HNAS APAR# N/A Problem# N/A |
|
- |
- |
- |
- |
- |
- |
2006-mm-dd - PROBLEM 2006nnnA
PROBLEM_ID: 2006nnnA
STATUS: PENDING
OPEN_DATE: 2006-mm-dd
REVISE_DATE: N/A
CLOSE_DATE: 2006-mm-dd
SERVICE(S): DATAFONO
Additional information will be provided as available.
2006-05-17 - PROBLEM 2006131A
PROBLEM_ID: 20061231A
APAR: N/A (corrected via 230.c problem id)
STATUS: CLOSED
OPEN_DATE: 2006-05-11
CLOSE_DATE: 2006-05-11
SERVICE(S): Configuration processing in V2R3M0C (Datafono only)
MANDATORY: NO, but recommended
ORIGIN/REF: 230_CPT
CP_TECH: SFD
PUBLISH: OVERVIEW
PTF_CLASS: TBD
PTF_TYPE: TBD
PTF_LOC: TBD
COREQ(S): N/A
PREREQ(S): 2300190
OBJECT(S): TBD
SOURCE(S): NASCNFG
PROBLEM: A configuration loop will result if the names of 2
MCHs in the CDF are the same in the first 4 character
positions.
DESCRIPTION: For V2R3M0C Datafono distributions only, a configuration
loop can occur (see problem). Due to a label name that
was changed by APAR 2300190 in the NASCNFG module which
was subsequently missed when the Datafono changes to
NASCNFG were applied, name validation logic branched to
the wrong label which caused the loop. Normally, this
error would simply generate the following error message
and HNAS would terminate after the CDF was completely
scanned.
NAS1321E REMOTE NAME mchname1 CONFLICTS WITH REMOTE
NAME mchname2, REQUIRED
CIRCUMVENTION: Ensure that all MCH names are unique in the first 4
character positions.
SOLUTION: The branch to the wrong label has been corrected as of
the problem CLOSE_DATE.
2006-04-04 - PROBLEM 2006093A
PROBLEM_ID: 2006093A
APAR: N/A (corrected via 230.c problem id)
STATUS: CLOSED
OPEN_DATE: 2006-04-03
CLOSE_DATE: 2006-04-03
SERVICE(S): Distribution Job -- Datafono Systems Only
MANDATORY: YES
ORIGIN/REF: 230C_CCS
CPTECH: PRT
PTF_CLASS: N/A
PTF_TYPE: (SRC) HNASMACX
PTF_LOC: FTP Server Directory /hnas_maint/hnasproblem/
(Complete FIX is contained in the P06093A.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): N/A
SOURCE(S): XFPCE
PROBLEM: HALT AT LOC xxxx IN NASTCP : INVALID TCPIP INTERRUPT
REQUEST
when PING command entered.
DESCRIPTION: The distribution job fails to incorporate the XFPCE
macro which has changes required for proper operation
of the PING command.
SOLUTION: Install Datafono version of XFPCE macro in the
qqqq|hlq.HNASMACX data set and run the HNASMNT job.
CIRCUMVENTION: Do not issue the HNAS PING command.
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).
2006-04-01 - PROBLEM 2006075A
PROBLEM_ID: 2006075A
STATUS: OPEN, OnHold, Pending User Input
OPEN_DATE: 2006-03-16
REVISE_DATE: 2006-04-01
CLOSE_DATE: 2006-mm-dd
SERVICE(S): Datafono
MANDATORY: TO-BE-DETERMINED (TBD)
ORIGIN/REF: 230C_CGS
CP_TECH: PRT
PUBLISH: YES_OVERVIEW
PTF_INFO: TO-BE-DETERMINED
PTF_CLASS: TO-BE-DETERMINED
--------
OVERVIEW: See problem.
PROBLEM: NAS5728E RECEIVED INV MSG FROM RMT rmt-nm FOR LU lu-nm
on MCH mch-nm DATA=data
DESCRIPTION: The above alert indicates that an HNAS Datafono session
received a message that did not start with a valid
Datafono protocol character. DATA= displays the first
8 characters of the message (translated from ASCII to
EBCDIC). The customer received messages starting with
TPV60086, S3811279, and blanks (which may indicate non-
printable ASCII).
After the alert message the call is cleared with a
CAUSE/DIAG=000/223 (00/DF) -- HNAS cleared Datafono
session.
DISCUSSION: ISARX25 does not check the validity of the Datafono
protocol characters. HNAS is more restrictive in this
area. The reason was to prevent non-Datafono devices
from trying to start sessions. In this case this was
the desired action (customer reported that the TPV...
and S.... messages were not for valid Datafono
sessions).
SOLUTION: For the time being this problem is on hold pending
further developments. Possible actions are:
1) Remove the HNAS checking of Datafono protocol
characters.
2) Send the alert to SYSPRINT only (the NAS3799I
session end message with CAUSE/DIAG=000/223
indicates that a problem occurred).
CIRCUMVENTION: N/A
APPLY_INFO: N/A
2005-12-20 - PROBLEM 2005329B
PROBLEM_ID: 2005329B
STATUS: CLOSED
OPEN_DATE: 2005-11-25
REVISE_DATE: 2005-mm-dd
CLOSE_DATE: 2005-12-19
SERVICE(S): DATAFONO, pseudo-leased
MANDATORY: YES
ORIGIN/REF: 230.C_CGS
CP_TECH: PRT
PUBLISH: OVERVIEW
OBJECT(S): MCHHL0RQ
SOURCE(S): N/A
PTF_INFO: N/A
--------
OVERVIEW: See problem.
PROBLEM: USER 198 ABEND - "HALT AT LOC xxxx IN VTMLURL: INV LU"
when CICS is brought down.
DESCRIPTION: When CICS is terminated it UNBINDs its active LUs.
The processing for pseudo-leased Datafono LUs (which
are always active) has a logic error that results in
the above HALT.
SOLUTION: UNBIND processing for pseudo-leased LUs 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).
2006-03-16 - PROBLEM 2005329A (DTFB05)
PROBLEM_ID: 2005329A
STATUS: CLOSED
OPEN_DATE: 2005-11-25
REVISE_DATE: 2006-03-09
CLOSE_DATE: 2006-03-16
SERVICE(S): DATAFONO
MANDATORY: YES
ORIGIN/REF: 230.C_CGS
CP_TECH: PRT
PUBLISH: OVERVIEW (see problem summary)
PTF_INFO: TO-BE-DETERMINED
--------
Problem 1: Customer receiving: NAS5721E RECEIVED INV MSG FROM
RMT rmt-nm FOR LU lu-nm ON MCH mch-nm DATA=xx
Problem 2: Customer receiving: NAS5722E RECEIVING INVALID D(9)
MSG FROM RMT rmt-nm FOR LU lu-nm ON MCH mch-nm
RECV ST=R(3) SEND ST=R(4)
Note: Because of HNAS numbering conflicts NAS5721E is now
NAS5728E and NAS5722E is now NAS5729E.
DESCRIPTION1: NAS5721E indicates that a message was received that
did not start with a valid datafono character. A
trace showed that the message was an EOT character
(X'04') that was received in last message sent clear
expected state ('L'-sent). ISARX25 discards inbound
messages in this state.
DESCRIPTION2: NAS5722E indicates that HNAS has received a D(9)
message (used by the remote to ask the PLU for the
next M message segment) when the send state in not
M message sequence active. A trace showed that the
state was not required by HNAS. ISARX25 treats the
D(9) message as a normal data message when this
happens.
SOLUTION: HNAS logic modified to correctly emulate ISARX25 logic.
CIRCUMVENTION: N/A
APPLY_INFO: TO-BE-DETERMINED
2006-01-11 - PROBLEM 2005328A (DTFB02)
PROBLEM_ID: 2005328A
STATUS: CLOSED
OPEN_DATE: 2005-11-24
CLOSE_DATE: 2005-11-29
NOTE_DATE: 2006-01-11 - Successfully tested by customer.
- - - - - - - - - - - -
2005-11-29 - Datafono Beta test: Problem DTFB02
PROBLEM_ID: DTFB02 (2005328A)
STATUS: CLOSED
OPEN_DATE: 2005-11-27
CLOSE_DATE: 2005-11-29
SERVICE(S): Console subsystem PING command
MANDATORY: YES
PUBLISH: YES
ORIGIN/REF: 230.C_CCS (CEC)
CP_TECH: SFD
PTF_CLASS: DATAFONO-APAR.
PTF_TYPE: (SRC) HNASMACX
PTF_LOC: FTP Server Directory /hnas_maint/hnas230m/apars/
(Complete FIX is contained in the DTFB02.ZIP file)
Additional information will be provided as available.
COREQ(S): N/A
PREREQ(S): N/A
OBJECT(S): N/A
SOURCE(S): NASMAIN, XFPCE
PROBLEM: HALT AT LOC xxxxxx IN NASTCP : INVALID TCPIP INTERRUPT
DESCRIPTION: Missing update to XFPCE macro causes the PING PCE
to be incorrectly created. This causes a validity
error that results in a NASHALT 0198 ABEND.
SOLUTION: The XFPCE macro has been modified to produce the PING
PCE correctly in a Datafono environment. The XFPCE
macro is assembled during the NASMAIN assembly.
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).
2005-12-21 - PROBLEM 2005321A
PROBLEM_ID: 2005321A
STATUS: CLOSED, see APAR 2300170.
OPEN_DATE: 2005-11-17
PRVCHG_DATE: 2005-11-21
CLOSE_DATE: 2005-12-21 - fix successfully tested by customer.
SERVICE(S): TCP/IP interface support
MANDATORY: N/A
ORIGIN/REF: 230_CCS - CID changed from CGS to CCS (CEC)
CP_TECH: SFD
PUBLISH: YES
PTF_CLASS: TBD
PTF_TYPE: (SRC) HNASMACX
PTF_LOC: TBD
COREQ(S): N/A
PREREQ(S): 2300162 and all associated APAR PreReq chains
OBJECT(S): TBD
SOURCE(S): NASTCP
PROBLEM: NASHALT U198 ABEND when HNAS is running and the TCP/IP
Stack is forced down.
DESCRIPTION: INITAPI is being rejected with erno=1036 and a subsequent
NASHALT results after successful GETIPBOPT request that
indicates that stack is up.
The INITAPI erno=1036 says 'TCP/IP is not installed'.
INITAPI will not be executed unless GETIBMOPT shows that
named stack is installed and active. Since the GETIBMOPT
in this case showed the stack to be acive, the INITAPI
failure should not have occurred. The NASHALT results
because the successful GETIBMOPT and the failed INITAPI
are mutually exclusive. Normally, if the stack is down,
the GETIBMOPT will show this and will be retried after a
1-minute forced delay. This will continue indefinitely
until the stack comes up so that the INITAPI can then
be attempted.
CIRCUMVENTION: N/A
SOLUTION: HNAS modified to treat the INITAPI failure with
erno=1036 like a GETIBMOPT that shows that the stack
is down to prevent the ABEND. However, a real fix
would be to determine why the GETIBMOPT showed that
the stack was up when, in fact, it appears to be down
due to the INITAPI failure.
2004-12-31 - PROBLEM 2004341A (affects Datafono support only)
PROBLEM_ID: 2004341A
STATUS: CLOSED
OPEN_DATE: 2004-12-06
REVISE_DATE: 2004-mm-dd
CLOSE_DATE: 2004-12-31
SERVICE(S): CONSOLE SUBSYSTEM, HNAS INSTALLATION LINK EDIT
MANDATORY: TO-BE-DETERMINED
(YES WHEN HNAS IS NOT LOADED ON A QUAD WORD BOUNDARY)
ORIGIN/REF: 230_CPT (DATAFONO support)
CP_TECH: SFD
PUBLISH: YES, WIP
PTF_INFO: TO-BE-DETERMINED
PTF_CLASS: TO-BE-DETERMINED
PTF_TYPE: (SRC) HNASMACX
PTF_LOC: FTP Server Directory /hnas_maint/hnasproblem/
(Complete FIX is contained in the 2004341A.ZIP file)
COREQ(S): N/A
PREREQ(S): N/A
SUPERSEDES: N/A
OBJECT(S): N/A
SOURCE(S): SYSLIN
PROBLEM: DMAP APAR command causes 0C1 ABEND when HNAS is
started because it is loaded on a double word (DW)
rather than a quadruple word (QW) boundary.
DESCRIPTION: The console subsystem assumes that all command
processors are aligned on a quadruple word boundary
because it uses the low order 4-bits of each console
command processor address as flags. The size of all
HNAS modules is forced to a multiple of 16-bytes.
Thus, when HNAS is loaded on a DW boundary, all
modules have DW rather than QW alignment. This
misalignment causes the 0C1 ABEND.
SOLUTION: The link edit SYSLIN has been modified by adding
a PAGE NASMAIN statement so that HNAS is forced
to a page boundary when loaded. This will ensure
that all modules are on a QW boundary and prevent
the 0C1 ABEND.
CIRCUMVENTION: Short term solution until problem is closed and
APAR is issued:
Add PAGE NASMAIN statement immediately before
INCLUDE HNASOBJ(NASMAIN) statement in the SYSLIN
member of the HNASMAC library. This forces the
link edited HNAS load module to be loaded on a
page boundary when it is invoked as PGM=HNAS.
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 - September 18, 2006