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 2400018 | <Link forward> | - | - |
HNAS V2R4M0 - 2007 MAINTENANCE SUMMARY (Link to APARs 2400018 thru 2400nnn) |
| - | - | - | - | - |
|
2400017_E |
2006-12-28 |
Cons-Subsystem |
OBJ/SRC |
This Enhancement APAR addresses the following console |
| 2006-12-13 |
Cons-Subsystem |
OBJ |
Minor bug and cosmetic fixes for APAR 2400014:
|
|
|
2400015_R |
2006-12-05 |
Cons-Subsystem |
<Refresh |
1) A System 0C4 ABEND in MCHSOL with R1=X'40404040' can occur
due to a bug in the MRMT logic. |
|
2400014_RE |
2006-12-05 |
Cons-Subsystem |
<Refresh |
This Enhancement APAR addresses the following console improvements: |
| 2006-11-24 |
SYSPRINT trace logging support |
SRC |
A System 0C4-10 ABEND can occur while trace entries are being logged to SYSPRINT and ALARM messages are being generated for a remote console session. |
|
| 2006-11-21 |
Cons-Subsystem |
OBJ |
SHUTDOWN hangs when QUIT command is issued if TCPIP server component(s) fail to complete initialization. |
|
|
2400011_R |
2006-11-16 |
Datafono |
<Refresh |
Customer would like to use custom translate table for Datafono sessions. |
|
2400010_ER |
2006-11-14 |
Cons-Subsystem |
<Refresh |
Enhancement allowing TYPE=XOT REMOTE IP Address and/or Port to be altered via the console subsystem. Remote must be in IDLE state before addresses can be changed. |
|
2006-10-23 see rev_date |
1) GATE FC |
OBJ |
1) NAS3799I LU lu-nm ENDING SESSION ON MCH mch-nm HNAS CAUSE/DIAG=000/217 (00/D7) DIAGX=0007
condition. |
|
| 2006-10-06 |
1) MRMT LUNAME=* |
OBJ/SRC |
1) Improvement allowing the asterisk to be removed from or added to the
GATE pluname suboperand of the LUNAME= operand for a TYPE=MCH|XTP REMOTE definition statement to be modified using the MRMT console command. |
|
| 2006-10-02 |
PVC VTAM/Resets |
OBJ/SRC |
1) IMS to IMS PVC connection receives NAS5705W reset CAUSE/DIAG=000/219. |
|
| 2006-09-19 |
Cons-Subsystem |
OBJ |
An 0C1 ABEND can occur when the remote console output reaches the scroll line limit which is controlled by the LNCT= modifier (defaults to 23 lines). |
|
|
2006-09-08 see rev_date |
GATE |
OBJ |
1) REQSESS operations for GATE control and Fast
Connect (FC) data sessions are not retried when the PLU is not active. |
|
| 2006-09-07 |
TCPIP |
SRC |
NAS2211W CLOSE REQUEST FAILED error message erroneously generated due to bad socket number being passed to the socket CLOSE processor condition can lead to depletion of sockets. |
|
|
2400003_ER |
2006-08-30 |
SVC0|5= Callout |
<Refresh |
Enhancement to associate a
separate TYPE=MXT|SVC REMOTE |
|
2400002_R |
2006-08-21 |
CNFG BFRSIZ= processing |
<Refresh |
HNAS buffer header size was increased by 16 bytes which requires a change to the BFRSIZE= value. |
|
2400001_ER |
2006-08-10 |
SYSPRINT |
<Refresh |
Enhancement to dynamically allocate SYSPRINT log files now provided. |
| 2400000 | 2006-07-31 | ALL | N/A | Service_Notice-Begin_Maintenance/APAR_Cycle |
| 240eshp | 2006-06-01 | ALL | N/A | Early Ship product release. |
| 240beta | 2006-05-01 | ALL | N/A | Beta product testing. |
| - | - | - | - | - |
| 240nnnn_i | yyyy-mm-dd |
GATE/LLCn/ PVC/QLLC/... |
ZAP/SRC/ OBJ/DOC/ CNFG/... |
<-Brief Problem 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.
2006-12-28 - APAR 2400017 (were problems 2004301A, 2006055A (DNWD)
2006334C and 2006342C)
APAR: 2400017_E
STATUS: CLOSED
OPEN_DATE: 2006-12-21
REVISE_DATE: N/A
CLOSE_DATE: 2006-12-28
SERVICE(S): Console modifier/display and debug enhancements
MANDATORY: NO
ORIGIN/REF: 230|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 2400017.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): 2400016 and associated APAR chains.
SUPERSEDES: N/A
OBJECT(S): CONSALRM, CONSDNWD, CONSEXEC, CONSPRNT, CONSQUIT,
CONSSHOW, CONSTPRT, NASCNFG, NASUTIL
SOURCE(S): NASMAIN, XFBLK, XFCNFGWA, XFGBLS
OVERVIEW: This Enhancement APAR addresses the following console
and debugging improvements:
PROBLEM1: HNASXEQ changes for DNWDF command which was deferred
from APAR 2400014 is now provided.
PROBLEM2: PRNT ON|OFF console command does not write command
action alarm message to SYSCONS which can cause
confusion if command is entered from a remote
console.
PROBLEM3: SHOW ON|OFF console command does not write command
action alarm message to SYSCONS which can cause
confusion if command is entered from a remote
console.
PROBLEM4: Enhancement allowing console command '# comments' to
be displayed in SYSPRINT HNASCMD-> output.
DESCRIPTION1: See problem.
DESCRIPTION2: See problem.
DESCRIPTION3: See problem.
DESCRIPTION4: There are 3 ways to write single line # comments
to SYSPRINT:
1 - via the modify interface:
/f jobname,# comments
2 - via the BUILD CONCMDQ=(# comments',...)
HNASCMD-> # comments
3 - via CMDLISTs (EXEC cmdlist)
'hlq.HNASCNTL(PINGIT)'
# PINGIT command list start
PING PINGRTR1
PAUSE
PING PINGRTR2
PAUSE
# router 3 is currently offline, ping will timeout.
PING PINGRTR3
# PINGIT command list end
In either case the SYSPRINT log will display:
HNASCMD-> # comments
Command list will also generate this message:
HNASCMD-> # router 3 is offline, ping will timeout.
SOLUTION1: DNWDF command has been modified to echo it's execution
parameters like all other commands.
SOLUTION2: PRNT command processor has been modified to issue the
following alarm messages when PRNT ON|OFF is issued:
For ON:
NAS0210I SYSPRINT LOGGING ENABLED BY consname
For OFF:
NAS0211W SYSPRINT LOGGING DISABLED BY consname
Note: PRNT ON is forced when HNAS SHUTDOWN is requested
via the QUIT command so that JOB ending console
command output will be logged in SYSPRINT.
Starting with this APAR, the DNAS and ALARM LOG=?
commands will both be executed during SHUTDOWN
processing. Prior to this APAR, only ALARM LOG=?
was executed at SHUTDOWN. This is done to provide
needed information for Comm-Pro problem diagnosis
should it become necessary.
SOLUTION3: SHOW command processor has been modified to issue the
following alarm messages when PRNT ON|OFF|ERR is issued:
For ON:
NAS0110I SYSCONS ERROR AND INFO ALARM OUTPUT
ENABLED BY consname
For OFF:
NAS0111W SYSCONS NON-FORCED ALARM OUTPUT
DISABLED BY consname
For ERR:
NAS0112I SYSCONS ERROR ALARM OUTPUT
ENABLED BY consname
SOLUTION4: The console command decoder has been modified to look
for a # character in record column 1 and treat it and
what follows as a comment record. The comment record
will be displayed in the HNASCMD-> command display.
CIRCUMVENTION1: N/A
CIRCUMVENTION2: N/A
CIRCUMVENTION3: N/A
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).
2006-12-13 - APAR 2400016 (was problem 2006341A)
APAR: 2400016
STATUS: CLOSED
OPEN_DATE: 2006-12-07
REVISE_DATE: N/A
CLOSE_DATE: 2006-12-13
SERVICE(S): Console Command Processing (under APAR 2400014)
MANDATORY: YES
ORIGIN/REF: 240_CPT
CP_TECH: SFD
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400016.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): 2400014 and associated APAR chains.
SUPERSEDES: N/A
OBJECT(S): CONSDLU, CONSDMCH, CONSDPCE, CONSDVC, CONSEXEC,
CONSMMEM, NASCONS, NASUTIL
SOURCE(S): N/A
OVERVIEW: Enhancement APAR 2400014 introduced a number of
new and useful features into the HNAS console
subsystem, chief among which was the echoing
of command execution parameters and modifiers
(HNASXEQ->) In spite of exhaustive testing, some
anomalies and problems were also introduced.
This APAR remedies these issues.
PROBLEM1: NASC054E EXEC cmdlist FILE EXCEEDS QUEUED COMMAND
LIMIT, COMMAND LIST IGNORED message generated.
PROBLEM2: MMEM echo message suppressed when ECHOXEQ NO is in
effect can cause confusion with ENTER YES or NO
message.
PROBLEM3: Some default parameters are not echoed for the
DLU, DMCH, DPCE and DVC commands.
DESCRIPTION1: See problem.
Logic changes introduced in APAR 2400014 causes the
multi-element command list to terminate.
While this doesn't affect the operation of HNAS it
can cause some user defined command lists to end
prematurely.
This bug only affects EXEC command lists and does
not affect multiple console commands on a single
command line.
Bug occurs because the command queue is not being
re-initialized when a new command list is processed.
This results in the new command list being appended
to the end of the command queue which will eventually
result in the NASC054E message.
DESCRIPTION2: The following message was pulled when the HNASXEQ
logic was added because it duplicated the HNASXEQ
message.
NASCONS MMEM ADDRESS=dddddddd DATA=xx...xx
However, when ECHOXEQ NO is in effect no data is
displayed before the following message:
ENTER: N=ABORT, Y=APPLY
This can cause confusion.
DESCRIPTION3: The problem is caused by the fact that parameters are
displayed only if their associated flag is set ON. For
some parameters, flag OFF is also a valid state. That
is, the same flag is used for two actions or parameters.
For example, for the SHOWNAME|SHOWADDR parameter, flag
ON=>SHOWADDR and OFF=>SHOWNAME. Since the echo logic
only displays parameters when its associated flag is
ON, SHOWNAME will not be displayed.
SOLUTION1: The EXEC command list processor has been modified to
re-initialize the command queue area prior to
populating it with the new command list.
SOLUTION2: The original question message has been restored which
will only be issued when ECHOXEQ NO is in effect.
SOLUTION3: The DLU, DMCH, DPCE and DVC command echo logic has
been changed to allow parameters with OFF state flags
to be displayed.
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-12-13 - APAR 2400015 (was unpublished problem 2006344A)
APAR: 2400015
STATUS: CLOSED
OPEN_DATE: 2006-11-30
PRVCHG_DATE: 2006-12-05
REVISE_DATE: 2006-12-13
CLOSE_DATE: 2006-12-05
SERVICE(S): Console MRMT Processing
MANDATORY: YES
ORIGIN/REF: 230_SDD
CPTECH: SFD
PTF_CLASS: STANDARD-APAR
PTF_TYPE: REFRESH
PTF_LOC: Contact Support Services for Refresh E-distribution.
PROBLEM1: S0C4 ABEND in MCHSOL with R1=X'40404040' can occur due
to a bug in the MRMT logic.
PROBLEM2: The MRMT command can be rejected with a NASC313E
message when an MXT name is being added to an SVC0=
or SVC5= entry.
DESCRIPTION1: LLC0 LU HAS X'40404040' LUMXT field. The ABEND results
when this value is used as an address. The SVC0=
string for the resource (addressed via LUCNFGPT) has
the X'40404040' value at the SVC0MXT offset.
Problem caused by the use of the MRMT command to add a
new LU to the SVC0= operand list. No MXT was specified
with the new LU name so the MXT name (SVC0MXT) was set
to blanks. When the new LU was selected at session
setup time, MCHSOL was called to process application
selection. The invalid SVC0MXT field was used because
it was not zero which is required when an MXT is not
associated with an SVC0= LU entry.
Note: This problem also exists for the SVC5= operand.
DESCRIPTION2: Due to a bad test on the REMOTE type, the MXT that is
named in an SVC0= or SVC5= update request is rejected
even though it really is an MXT. The wrong base
register was being used to perform the REMOTE type
test. The MRMT command is rejected and the following
error message is issued:
NASC313E REMOTE MXT1 IS NOT TYPE=MXT, REQUIRED
SOLUTION1: The MRMT console command processor has been modified
to set SVCiMXT=0 when a new LU is added to the SVCi=
operand. If an MXT name is specified either at the
same time or at a later time, the SVC0MXT field will
be set to the correct MXT address.
SOLUTION2: The MRMT console command processor has been modified
to use the correct base register when testing the
REMOTE type.
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-12-05 - APAR 2400014 (was problem 2005277B, 2006055A and 2006118B)
APAR: 2400014_ER
STATUS: CLOSED
OPEN_DATE: 2005-10-04 for 2005277B
2006-02-24 for 2006055A
2006-04-29 for 2006118B
PRVCHG_DATE: 2006-12-04
REVISE_DATE: 2006-12-05 (ECHOXEQ=MIN Default)
CLOSE_DATE: 2006-12-05
SERVICE(S): Console modifier processing and display enhancements
MANDATORY: NO
ORIGIN/REF: 230_SDD,230_SIK,230|240_CPT
CPTECH: SFD
PTF_CLASS: ENHANCEMENT-APAR
PTF_TYPE: REFRESH
PTF_LOC: Contact Support Services for Refresh E-distribution.
PROBLEM: This Enhancement APAR addresses the following console
improvements:
PROBLEM1: Customer indicates that it is difficult to remember
the left side modifiers in effect which can cause
confusion when issuing commands that use modifiers.
PROBLEM2: Currently, there is no command line history of what
modifiers and default operands are in effect when a
command is executed other than the optional right
side temporary modifiers that are echoed when the
command is entered.
PROBLEM3: DLU, DMCH and DVC displays are currently set up to
display header information for XTP resources (IBM
routers) when most customers use XOT resources
(Cisco routers).
PROBLEM4: DPCE command displays OFLN for a LOCAL or REMOTE
resource that is defined with INIT=IDLE or after
VARY INACT|OFF is entered.
PROBLEM5: No error message is generated for commands like ALARM
and EXEC when no command parameters are specified.
DESCRIPTION1: Due to the large number of resources in the customer's
configuration, using left side modifiers can cause
confusion when issuing some console command. Customer
has a hard time remembering which modifiers are set.
Left side modifiers as well as active filter settings
(previously entered standalone or previous entered as
left side modifiers) filter can sometimes get in the
way causing confusion.
DESCRIPTION2: See PROBLEM2.
DESCRIPTION3: DLU, DMCH and DVC header displays can be confusing for
Cisco router environments even though Console Subsystem
documentation clearly identifies what XOT information
is displayed in an XTP column.
DESCRIPTION4: The DPCE command displays OFLN (for OFFLINE) when
INIT=IDLE is specified or VARY INACT|OFF is entered
but configuration does not allow INIT=OFFLINE to be
specified in the CDF.
DESCRIPTION5: When ALARM or EXEC is entered with no parameters,
the commands essentially NOP and the console prompt
is issued. An error message is more appropriate in
this instance to indicate that a command argument is
required for these commands. For other commands that
are entered without arguments, a default parameter is
set which allows the command to be executed. For
example, TRCPRNT entered by itself is treated as
TRCPRNT ON as indicated by the HNASXEQ response.
HNASCMD-> TRCPRNT
HNASXEQ-> TRCPRNT ON
SOLUTION1: For console commands that utilize remembered modifier,
a new option operand (BPM - bypass permanent modifiers)
has been added so that all remembered modifiers will
be ignored when the command is executed. With this
new option, the user will not have to display the
current parameters using the DPARM command to see
what values are enabled. The console operator can
simply specify the right hand modifiers that are
appropriate for the specific command.
For example, if RNM=MCH1 and LUNM=MCH10001 are
specified as remembered modifiers and the operator
wants to display all LUs on MCH2, he would enter:
DLU BPM MCH2
Prior to this enhancement, the operator would have
to enter:
DLU RNM=MCH2 LUNM=
In addition, the HELP command now displays common
command parameters after the HELP header message.
For example, when HELP ? is entered the following
following is displayed:
HNASCMD-> HELP ?
HNASXEQ-> HELP HELP
COMMAND DESCRIPTION (* => PRIVILEGED)
COMMON PARAMETERS FOR ALL COMMANDS: cmdnm parm
parm=? to display help for cmdnm.
BPM to bypass permanent modifiers for cmdnm.
HELP DISPLAY CONSOLE COMMAND HELP INFORMATION
ENTER> HELP {SHOWALL|command}
General notes for the HELP command:
1) HELP with no arguments will display a one line
description for each command.
2) HELP command will display a verbose description
for the given command.
3) HELP SHOWALL will display a verbose description
for all commands.
SOLUTION2: HNAS has been modified to display the command modifiers
and parameters (HNASXEQ-> response) that will be used
when the command is executed immediately before command
execution so that the user can see what global filters
are in effect when the command was executed.
All valid HNAS commands will yield a HNASCMD-> and
HNASXEQ-> response. HNAS modifiers entered either as
standalone or prefixing a command (left side) won't
generate a HNASXEQ-> response because modifiers aren't
commands.
Note: The DNWDF command was not included in the HNASXEQ
change. HNASXEQ support for the DNWDF command
will be added at a future time.
Under this new logic, the customer does not have to
enter 'DPARM MODIFIERS' and look in the DOC to see
what was set and how it relates to the given command.
command.
In addition to the HNASXEQ echo logic, the new ECHOXEQ
command was added to control how much data is echoed
when a command is entered:
ECHOXEQ MAX causes all applicable command modifiers
and parameters to be echoed on multiple lines (if
necessary) with the HNASXEQ-> prefix for each line.
Data at the end of one line is continued on the next
with an ellipsis (...) suffix as an indication that
more information exists.
ECHOXEQ MIN causes all applicable command modifiers
and parameters to be echoed on a single line. If
more information exists than can be displayed on
one line, an ellipsis (...) will terminate the line.
ECHOXEQ MIN is the default that is established when
the console session is started.
ECHOXEQ NO causes the echoing of command modifiers
and parameters to be inhibited.
For example: when DRMT MCH1 is entered, the following
is echoed back (note that ECHOXEQ MIN is the default).
HNASCMD-> DRMT MCH1
HNASXEQ-> DRMT RNM=MCH1 APPLNAME CONNECT CTCP CUD CUD0 DCEADDR DF...
RMTNAME OPERAND TYPE
MCH1 00831EAC MCH
APPLNAME=MCHSOL (000)
:
If you wish to display all modifiers and parameters
for each command, enter ECHOXEQ MAX. For the
DRMT MCH1 example above:
HNASCMD-> ECHOXEQ MAX
HNASXEQ-> ECHOXEQ MAX
HNASCMD-> DRMT MCH1
HNASXEQ-> DRMT RNM=MCH1 APPLNAME CONNECT CTCP CUD CUD0 DCEADDR DF...
HNASXEQ-> LNAME DFXNAME DTEADDR FAC GATE HOME IDBLK IDNUM ID...
HNASXEQ-> LETO IFNUM INIT IPADDR LLC0 LLC3 LLC4 LLC5 LOGTAB ...
HNASXEQ-> LUNAME MAXDATA MBITCHN OPTIONS PACE PAD PADPARM PK...
HNASXEQ-> TSIZ PORT PROTOCOL PVC PWPROT SUBADDR SUBD SVC0 SV...
HNASXEQ-> C3 SVC4 SVC5 SYSL TAP TRAN TYPE USSTAB VCLMT
RMTNAME OPERAND TYPE
MCH1 00831EAC MCH
APPLNAME=MCHSOL (000)
:
The ECHOXEQ option will stay in effect until changed
or until the console session is ended.
SOLUTION3: The DLU, DMCH and DVC commands have been modified to
display header information for both XTP and XOT
resources. For example, the header for the DLU
command was changed
From:
PID IFN CID VCN RTRNAME LUOPT STAT TYPE SLUNAME PLUNAME
001E 00000000 L N IDLE PCNE MCH10001
To:
IFN|
MPID RPID CID VCN RTRNAME LUOPT STAT TYPE SLUNAME PLUNAME
001E 00000000 L N IDLE PCNE MCH10001
The new MPID column displays the PID for the MCH PCE
that owns the displayed SLUNAME. The IFN|RPID column
identifies either the XTP MCH interface number (REMOTE
TYPE=XTP,IFNUM=xx,...) or the PID for the XOT router
PCE (REMOTE TYPE=XOT) over which the SLU is connected.
SOLUTION4: The configuration process has been modified to accept
INIT=ONLINE as an alternate for INIT=ACTIVE and
INIT=OFFLINE as an alternate for INIT=IDLE. This was
done to provide consistency with V2R4 console displays.
SOLUTION5: The following new console error message will be
generated for commands that require parameters
which are not specified:
NASC531E PARAMETER DATA OMITTED, REQUIRED
In addition, when parameters are specified but are
invalid for the given command, the following new
message is generated:
NASC532E PARAMETER DATA INVALID, REQUIRED
The NASC532E message above replaces the following
message which has been retired:
NASC522E INPUT DATA INVALID, REQUIRED
CIRCUMVENTION1: Use DPARM command to display remembered modifiers.
Never use left side modifiers so that permanent
values are not set. Use right side modifiers only
to set temporary values for each command as needed.
CIRCUMVENTION2: Use right side modifier overrides to reset permanent
left side (or standalone) modifiers.
CIRCUMVENTION3: Consult Console documentation for description of
column data.
CIRCUMVENTION4: N/A
CIRCUMVENTION5: 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-11-24 - APAR 2400013
APAR: 2400013
STATUS: CLOSED
OPEN_DATE: 2006-11-20
CLOSE_DATE: 2006-11-24
SERVICE(S): SYSPRINT trace logging support
MANDATORY: YES
ORIGIN/REF: 240_CPT
CP_TECH: SFD
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (SRC) HNASMACX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400013.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): NASMAIN, XFNASWA
PROBLEM: A System 0C4-10 ABEND can occur while trace entries
are being logged to SYSPRINT and ALARM messages are
generated for a remote console session.
DESCRIPTION: The ABEND can occur if the following combination of
conditions are met:
1) ALL traces are active (TRCBST, TRCSUBR, etc) and
TRCPRNT is active.
2) A remote console is connected and is conditioned
to receive alarm messages.
3) The SYSPRINT log increases in size due to the trace
entries being logged which forces the following
alarm message to be generated for the local SYSCONS
and RMTCONS:
NAS0200W xxxx SYSPRINT LOG RECORDS WRITTEN
The ABEND occurs because the HNAS savearea chain
reaches it's end while processing all this SYSPRINT
activity. This is not an illegal loop scenario.
It is a legitimate sequence, albeit an unusual set
of conditions.
SOLUTION: HNAS has been modified to increase the number of
pre-allocated saveareas in order to handle the
sequence of events described above.
CIRCUMVENTION: Reduce the number of traces that are active and/or
do not use the remote console in alarm mode.
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-11-21 - APAR 2400012
APAR: 2400012
STATUS: CLOSED
OPEN_DATE: 2006-11-21
CLOSE_DATE: 2006-11-21
SERVICE(S): Console Subsystem SHUTDOWN processing
MANDATORY: YES
ORIGIN/REF: 240_OVR
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 2400012.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): 2400010
SUPERSEDES: N/A
OBJECT(S): NASCONS
SOURCE(S): N/A
PROBLEM: SHUTDOWN hangs when QUIT command is issued if TCPIP
server component(s) fail to complete initialization.
DESCRIPTION: If an invalid IP address is specified for a LOCAL
definition statement and INIT=ACTIVE is in effect,
the LOCAL will not be bound to the stack. This
prevents the server initialization from completing.
If /P HNAS or /F HNAS,Qx is entered to shutdown HNAS,
SHUTDOWN will hang because of a bad test in the
console shutdown completion logic.
The following error message can be generated if
HNAS successfully connects to the stack but cannot
complete the BIND because of the bad IP address:
NAS2231W SERVER=010.117.056.218(01998)
SOCKID=0000 PCEID=0007 NAME=LXOT
NAS2231W BIND REQUEST FAILED, RC=FFFFFFFF 00000031
Note that this message is not generated if HNAS has
not connected to the stack. The indication that
HNAS has connected to the stack is signaled by the
following message:
NAS2050I SERVER=010.117.056.218(01998)
SOCKID=0000 PCEID=0007 NAME=LXOT
NAS2050I API CONNECTION TO TCPIP HAS BEEN ESTABLISHED
SOLUTION: The console processor has been modified to detect
when the SHUTDOWN process is hung due to the failed
server initialization so the SHUTDOWN will complete.
CIRCUMVENTION: Cancel HNAS via the SDSF DA or ST menu with 'C' in
the NP column as follows:
NP JOBNAME JobID Owner Prty Queue C Pos SAff ASys ...
C LDNAS240 JOB01644 SFD 9 EXECUTION A SYS1
:
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-11-16 - APAR 2400011 (was unpublished problem 2006283A)
APAR: 2400011_R
STATUS: CLOSED
OPEN_DATE: 2006-11-09
CLOSE_DATE: 2006-11-16
SERVICE(S): DATAFONO
MANDATORY: NO but recommended if Datafono resources used.
ORIGIN/REF: 240_CCS
CPTECH: PRT
PTF_CLASS: STANDARD-APAR
PTF_TYPE: REFRESH
PTF_LOC: Contact Support Services for Refresh E-distribution.
PROBLEM: Customer would like to use custom translate table
for Datafono sessions.
DESCRIPTION: The Datafono translate table (which was provided by
IBM Spain) is in CSECT XAICDTFT which is in
hlq.HNASOBJ(MCHUT2). MCHUT2 contains more that the
XAICDTFT CSECT.
SOLUTION: This APAR facilitates replacement of the XAICDTFT CSECT
by placing it in a separate hlq.HNASOBJ member named
XAICDTFT. A custom Datafono table is installed as
follows:
Non-SMP/E installations:
Copy your version of XAICDTFT to hlq.HNASOBJX(XAICDTFT)
and then run the HNASMNT job to rebuild the HNAS load
module in hlq.HNASLOAD. To remove the custom translate
table delete the hlq.HNASOBJX XAICDTFT member and rerun
HNASMNT (the Comm-Pro version of XAICDTFT will still be
in hlq.HNASOBJ).
SMP/E installations:
After the TSORECV job has been run the rrrr.LNS0240.F4
relfile PDS has the HNAS object members used to build
HNAS. Preserve the LNSCDTFT member and then install
your custom XAICDTFT as member LNSCDTFT in
rrrr.LNS0240.F4 (relfile member names must start with
the LNS prefix (assigned to Comm-Pro by IBM)). Your
custom XAICDTFT can also be installed as a USERMOD.
If this is done the MCS ++MOD statement must use the
LNSCDTFT 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).
2006-11-14 - APAR 2400010 (was unpublished problem 2006297A)
APAR: 2400010_ER
STATUS: CLOSED
OPEN_DATE: 2006-10-24
CLOSE_DATE: 2006-11-14
SERVICE(S): MRMT console command enhancement
MANDATORY: NO, but recommended
ORIGIN/REF: 240_CPA
CPTECH: SFD
PTF_CLASS: ENHANCEMENT-APAR
PTF_TYPE: REFRESH
PTF_LOC: Contact Support Services for Refresh E-distribution.
PROBLEM: Enhancement to allow IPADDR= and PORT= values for a
TYPE=XOT REMOTE to be modified dynamically using
the MRMT console command.
DESCRIPTION: Prior to this enhancement, the IPADDR= and PORT=
values could only be changed dynamically for
TYPE=DMY REMOTEs. For TYPE=XOT REMOTEs, the
IPADDR= and PORT= values could only be changed by
stopping HNAS, updating the CDF then restarting
HNAS.
SOLUTION: The MRMT console command processor has been modified
to allow the IPADDR= and/or the PORT= values to be
changed dynamically without having to stop HNAS.
In order to allow this change, the target TYPE=XOT
REMOTE must be in the offline state. This can be
done in the CDF by specifying INIT=IDLE or during
execution using the VARY FORCE command.
For example, assume that the TYPE=XOT REMOTE named
R1CNIN was configured with IPADDR=10.117.56.100 and
INIT=ACTIVE. To change the IP address from its
current value of 10.117.56.100 to 10.117.56.201,
for example, the following command sequence would
have to be entered:
RNM=R1CNIN <- set remembered RMT name
VARY FORCE NOPR <- vary R1CNIN offline
MRMT IPADDR=10.117.56.201 <- change IP address
VARY ON NOPR <- vary R1CNIN back online
Notes: 1) The commands above could have been entered
with a temporary REMOTE name as a right side
modifier, e.g., VARY R1CNIN FORCE NOPR
2) If the MRMT command above is issued while
the REMOTE is online, the command will be
rejected and the following message issued:
NASC022W RESOURCE ONLINE,
MUST BE OFFLINE (USE VARY)
3) If the MRMT command attempts to change a
dynamic IP address (IPADDR=DYNAMIC), the
command will be rejected and the following
message issued:
NASC312E RNM=rmtname CONFIG INVALID, REQUIRED
CIRCUMVENTION: Stop HNAS, change IPADDR= in CDF for respective
TYPE=XOT REMOTE (R1CNIN in this case) then restart
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).
2007-01-19 - APAR 2400009 (was problem 2006254A (2300203)
and APAR 2300181 & 2300189)
APAR: 2400009
STATUS: CLOSED
OPEN_DATE: 2006-09-11
REV_DATE: 2007-01-19 - ZIP file retired, refresh required.
Do not use 2006-10-23 *.zip file.
CLOSE_DATE: 2006-10-23 - edistribution correct as of this date.
SERVICE(S): GATE FC, USSTAB, USSMSG (MCHSOL)
MANDATORY: YES
ORIGIN/REF: 240_ZAG,230_BMO,230_ATO
CPTECH: CPT,PRT
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400009.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: 2006-10-02
With APAR: 2400007 applied.
SUPERSEDES: N/A
OBJECT(S): MCHHL4RQ , MCHSOL
SOURCE(S): N/A
PROBLEM 1: NAS3799I LU lu-nm ENDING SESSION ON MCH mch-nm
HNAS CAUSE/DIAG=000/217 (00/D7) DIAGX=0007
DESCRIPTION 1: The above session end can result when fields in a
GATE Fast Connect data session LU are not properly
refreshed after the PLU UNBINDs the session.
SOLUTION 1: HNAS UNBIND logic corrected.
PROBLEM 2: USSMSG 3 (EXTRANEOUS PARAMETER) message issued when
keyword parameter from remote not in any USSPARM
entry following the selected USSCMD entry.
DESCRIPTION 2: For details please see APAR 2300181 memo.
SOLUTION 2: Logic for APAR 2300181 incorporated into V2R4M0.
PROBLEM 3: HNAS erroneously sends USSMSG when SUPP=ALWAYS is
specified.
DESCRIPTION 3: See PROBLEM 3.
SOLUTION 3: Logic for APAR 2300189 incorporated into V2R4M0.
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-10-10 - APAR 2400008 (was problem 2005018A)
APAR: 2400008
STATUS: CLOSED
OPEN_DATE: 2005-01-18
CLOSE_DATE: 2006-10-06
SERVICE(S): 1) GATE (LLC4) MRMT LUNAME=* modify support
2) PVC NEWDEFN interface service
MANDATORY: NO but recommend
ORIGIN/REF: 230_BNP,240_CPT
CPTECH: SFD
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (SRC) HNASMACX and (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400008.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 2400007 and associated APAR chains.
SUPERSEDES: N/A
OBJECT(S): CNFGPVC, CONSMRMT, NASCNFG
SOURCE(S): XFNASWA
PROBLEM1: Customer reports that they are unable to dynamically
remove the asterisk that follows pluname suboperand
of the LUNAME= operand for an MCH.
PROBLEM2: PVC= entry in NEWDEFN CDF contains invalid character
for the MCH interface name.
DESCRIPTION1: Customer specified a GATEFC MCH with the LUNAME=
operand coded as follows:
LUNAME=(V115A/GTMW4000*/R115/0/5)
Since an asterisk (*) is specified after the pluname,
HNAS will issue a REQSESS to force a BIND from the
CTCP. If the CTCP is not active, the REQSESS will
fail and the following message will be issued:
NAS3702W REQSESS FROM SLU V115A TO PLU GTMW4000
FAILED R15=xx R0=xx FDB2=xx SENSE=xxxxxxxx
The customer does not want to activate the CTCP to
eliminate this message and prefers to remove the
asterisk 'on the fly' to prevent HNAS from issuing
the REQSESS. He wants HNAS to wait for the CTCP
to come active and BIND the SLU when it does.
The customer attempted to remove the asterisk by
entering the following console command:
RNM=V115 MRMT LUNAME=V115A/GTMW4000
Unfortunately, this generated the following error
message because LUNAME= modification is only allowed
for TYPE=SPU REMOTE definition statements:
NASC311E RNM=V115 TYPE=MCH INVALID, REQUIRED
DESCRIPTION2: The MCH interface name in a PVC= operand entry can
contain a hyphen (-) as a proxy for the forward slash
(/) character that is normally present in an interface
name. The hyphen proxy is required because the CDF
treats a forward slash as a suboperand separator for
an operand that supports multiple suboperands. When
the PVC entry is processed, the hyphen is replaced
with the forward slash before it is saved in the
NEWDEFN CDF. The result is that if the NEWDEFN CDF
is used as the //CONFIG CDF in a subsequent HNAS
run, an error will occur when the PVC= operand is
processed because of the forward slash that replaced
the original hyphen (it is treated as a separator).
This bug was found during testing of the MRMT LUNAME=
enhancement for a GATE MCH that also had PVCs defined.
SOLUTION1: HNAS has been modified to allow the asterisk to be
removed from or added to the pluname suboperand
of the LUNAME= operand for a TYPE=MCH|XTP REMOTE
definition statement to be modified using the MRMT
console command.
To remove, enter: MRMT {RNM=}V115 LUNAME=V115A/GTMW4000
To add, enter: MRMT {RNM=}V115 LUNAME=V115A/GTMW4000*
Note that you can also use this command to change
the pluname.
SOLUTION2: HNAS has been modified to save the NEWDEFN CDF record
for PVC= operand entries before the hyphen substitution
takes place so that the NEWDEFN CDF contains the exact
same PVC= statement as the original CDF.
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-10-02 - APAR 2400007 (was problem was problem 2006215A and 2006115A)
APAR: 2400007
STATUS: CLOSED
OPEN_DATE: 2006-08-03
CLOSE_DATE: 2006-10-02
SERVICE(S): PVC
MANDATORY: YES
ORIGIN/REF: 230_FIS/230_CSP
CPTECH: PRT/SFD
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (SRC) HNASMACX and (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400007.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 2400006, 2400003, 2400001
and their associated APAR chains.
SUPERSEDES: N/A
OBJECT(S): FOR PROBLEM 1 & 2: VCRESET, XOTBXM
FOR PROBLEM 3: CNFGCNCT, CNFGLGTB, CNFGOPTS, CNFGPRSW,
CNFGRTIN, CNFGRTOT, CNFGSVC0, CNFGSVC3,
CNFGSVC4, CNFGSVC5, CNFGTRTR, CNFGTYPE,
CNFGUSTB, CONSEXEC, CONSMRMT, CONSPRNT,
CONSTRTR, NASCNFG, NASNETV, NASUTIL
SOURCE(S): FOR PROBLEM 3: NASMAIN, XFCNFGWA, XFNASWA
PROBLEM 1: IMS to IMS PVC connection receives reset:
NAS5705W RESET SCHEDULED ON MCH mch-nm VC vc-addr
lu-name LU lu-addr CAUSE/DIAG=000/219 (00/DB) DIAGX=0000
PROBLEM 2: When HNAS is restarted (HNAS-TO-HNAS environment) the
first outbound PLU FMD PIU is not sent by HNAS.
PROBLEM 3: NAS1201W LOCAL RTEIN|RTEOUT OMITTED, REQUIRED
message is being generated when only PVCs are
specified in the CDF.
DESCRIPTION1: When HNAS receives a -RSP to a PIU sent to the PLU the
following actions occur:
If the sense is 10xx the NAS3711I alert is issued and
the negative response is ignored (APAR 2300198).
For other sense values:
If the session is not a PVC the VTAM session is ended.
If there is an X25 session it is cleared (DIAG=219/DB).
If the session is a PVC then a RESET DIAG=129 is sent
to inform the remote of the -RSP. The VTAM session is
ended (ACB closed, PLU receives NOTIFY). When the sense
is 0826 (request not supported) there is no reason to
end the VTAM session because the PLU knows that the data
was discarded (this can happen if a data base has been
taken down).
DESCRIPTION2: After APAR 2300107 the VC upper window edge is not set
when a PVC SETUP packet is built. This makes the VC's
X25 transmit window appear closed. Host data must be
deferred until the window is opened.
Most installations will not see this because in most
cases the router sends a RESET DIAG=015 following it's
response to the HNAS PVC SETUP. This reset opens the
X25 window.
DESCRIPTION3: PVCs do not require RTEIN= for inbound connections
or RTEOUT= for outbound connections because all the
information necessary to establish PVC connections
is provided in the PVC= operand on an MCH. However,
for SVCs, RTEIN= and RTEOUT= are required to provide
routing information for inbound and outbound calls,
respectively. When no SVCs are configured, there is
no need to specify RTEIN= and/or RTEOUT=. Therefore
the NAS1201W message shown above should be withheld.
SOLUTION 1: HNAS logic modified to not end the VTAM session when
a -RSP SENSE=0826 is received from the PLU on a PVC
session.
SOLUTION 2: HNAS logic modified to properly set the upper window
edge.
SOLUTION 3: HNAS has been modified to detect the absence of SVC
definitions (CONNECT=NO, SVC0=NONE, SVC3=NONE,
SVC4=NONE and SVC5=NONE is in effect for all MCHs
in the CDF). If this is the case, the NAS1201W
LOCAL RTEIN/RTEOUT OMITTED messages will not be
generated. Note that in this case, the PVC= operand
on all MCHs must specify valid PVC information.
An MCH with no PVC or SVC definitions will cause
HNAS to terminate after the CDF is scanned.
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-09-19 - APAR 2400006
APAR: 2400006
STATUS: CLOSED
OPEN_DATE: 2006-09-18
CLOSE_DATE: 2006-09-19
SERVICE(S): Console Subsystem, Remote Console SIMATTN Support
MANDATORY: YES
ORIGIN/REF: 230_CPT
CP_TECH: SFD
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (OBJ) HNASOBJX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400006.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): NASUTIL
SOURCE(S): N/A
PROBLEM: An 0C1 ABEND can occur when the remote console output
reaches the scroll line limit which is controlled by
the LNCT= modifier (defaults to 23 lines).
DESCRIPTION: When the LNCT= value is reached during console command
output, a simulated attention (SIMATTN) condition is
set. The SIMATTN input processor will abort output if
the console operator enters an 'A' character. It will
resume output if any other data is entered (normally
a null line). The 0C1 ABEND occurs because of a blown
base register in the SIMATTN processor.
CIRCUMVENTION: N/A
SOLUTION: HNAS has been modified to correct the blown register
that is passed to SIMATTN processor.
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).
2007-01-19 - APAR 2400005 (was unpublished problem 2006250A)
APAR: 2400005
STATUS: CLOSED
OPEN_DATE: 2006-09-07
REV_DATE: 2007-01-19 - ZIP file retired, refresh required.
Do not use 2006-09-08 *.zip file.
CLOSE_DATE: 2006-09-08 - edistribution correct as of this date.
SERVICE(S): GATE
MANDATORY: RECOMMENDED
ORIGIN/REF: 230_ZAG (2300201)
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 2400005.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): MCHHRQ, MCHNRQC
SOURCE(S): N/A
PROBLEM 1: REQSESS operations for GATE control and Fast Connect
(FC) data sessions are not retried when the PLU is not
active.
PROBLEM 2: Enhancement to provide a NASxxxxI alert message to
indicate that a GATE control session has been bound.
DESCRIPTION1: The HNAS LUs for GATE control sessions and GATE FC
data sessions should always be in session with the PLU
if the PLU name is defined in the HNAS CDF. In order
to establish these sessions HNAS uses a VTAM REQSESS
macro to ask the PLU for a bind. If the PLU is not
active the REQSESS fails. A NAS3702W alert is issued
with SENSE=0857xxxx. HNAS should retry the REQSESS
based on the MCHTMR value (default=60 seconds).
Because of an error in the REQSESS completion routine
the REQSESS is not retried.
SOLUTION 1: REQSESS completion routine corrected so that REQSESS
is retried.
SOLUTION 2: NAS3797I LU lu-nm RECEIVED BIND FROM PLU plu-nm
The above alert message will be issued when a GATE
control session is bound. Previously this alert
was only used for BINDs received for PVC LUs.
This will eliminate the requirement to view the HNAS
DLU command display output to confirm that the GATE
control session is active.
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-09-07 - APAR 2400004
APAR: 2400004
STATUS: CLOSED
OPEN_DATE: 2006-09-05
CLOSE_DATE: 2006-09-07
SERVICE(S): TCP/IP interface support
MANDATORY: YES
ORIGIN/REF: 230_NBK (2300200)
CP_TECH: SFD
PTF_CLASS: STANDARD-APAR
PTF_TYPE: (SRC) HNASMACX
PTF_LOC: FTP Server Directory /hnas_maint/hnas240m/apars/
(Complete FIX is contained in the 2400004.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): NASTCP
PROBLEM: NAS2211W CLOSE REQUEST FAILED error message erroneously
generated due to bad socket number being passed to the
socket CLOSE processor condition can lead to depletion
of sockets.
The following messages are generated when an inbound
socket connection is received from a non-configured
router:
NAS2261W SERVER=010.117.056.170(01998) SOCKID=0000
PCEID=0007 NAME=XOTSRVR
NAS2261W ACCEPT REQUEST FAILED, RC=EEEEEEEE FFFFFFFF
NAS2211W SERVER=010.117.056.170(01998) SOCKID=0000
PCEID=0007 NAME=XOTSRVR
NAS2211W CLOSE REQUEST FAILED, RC=FFFFFFFF 00000403
NAS2262W SERVER=010.117.056.170(01998) SOCKID=0000
PCEID=0007 NAME=XOTSRVR
NAS2262W REMOTE=010.117.056.100(51973) NOT CONFIGURED,
CONNECTION REJECTED
DESCRIPTION: The NAS2261W and NAS2262W messages are correctly issued
when an inbound socket connection is received for a
non-configured router but the NAS2211W message is not.
This message is being generated due to a bad socket
number being passed the the socket CLOSE processor
(TCPCLS).
In addition to the erroneous NAS2211W message, the
allocated socket remains allocated because the CLOSE
request failed. This means that a new connection will
not reuse the same socket but will allocate a new one.
If the problem persists, it is theoretically possible
to run out of sockets which can only be corrected by
stopping and restarting HNAS.
CIRCUMVENTION: Add a TYPE=XOT|XTP REMOTE definition statement with
the IPADDR= operand set to the value displayed in
in the NAS2262W message or set IPADDR=DYNAMIC.
SOLUTION: HNAS has been modified to correct the blown register
that is passed to TCPCLS.
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-08-30 - APAR 2400003 (was problem 2006054A)
APAR: 2400003_ER
STATUS: CLOSED
OPEN_DATE: 2006-02-23
CLOSE_DATE: 2006-08-30
SERVICE(S): LLC0/5 callout & callin (SVC0|5=)
MANDATORY: NO, but recommended
ORIGIN/REF: 230_CCS
CPTECH: SFD/PRT
PTF_CLASS: ENHANCEMENT-APAR
PTF_TYPE: REFRESH
PTF_LOC: Contact Support Services for Refresh E-distribution.
PROBLEM: Enhancement to associate a separate TYPE=MXT REMOTE
with each callout and callin DTE address.
DESCRIPTION: Prior to this enhancement, an LLC0 callout resource
with multiple destination addresses was specified
as follows:
REMOTE TYPE=MCH|XTP
SVC0=(n,
sluname/dteaddr1-dteaddr2-dteaddr3{O|T}
/mxtname/cud,
:
When the SLU is bound by a PLU, a Call Request packet
is generated using dteaddr1 as the called DTE address.
If this call fails (Clear received or no response to
Call Request packet), a call is then placed to dteaddr2
and, if necessary, to dteaddr3.
When a dteaddri value is specified, the MXT identified
by mxtname above becomes the REMOTE that is associated
with the SLU for the entire LU/VC session. The dteaddri
value is used as the called DTE address while the named
MXT supplies the calling DTE address (DCEADDR= operand),
facilities data (FAC= operand), call user data (CUD=
operand) and for PAD calls, PAD parameters (PADPARM=
operand). When multiple dteaddri values are coded,
all outbound Call Request packets will carry the same
calling DTE address, facilities data and call user
data because there is only one MXT pointer.
SOLUTION: HNAS has been modified to allow the name of an MXT
(short for a TYPE=MXT REMOTE) or the new SVC (short
for a TYPE=SVC REMOTE) to be specified in place of
the dteaddri suboperands.
When an MXT or SVC is specified as a rmtname in place
of a dteaddri value, it becomes the REMOTE that is
associated with the SLU for the duration of the LU/VC
session. In this case, it will be the REMOTE that
provides the called DTE address (DTEADDR= operand),
calling DTE address (DCEADDR= operand), facilities
data (FAC= operand) and call user data (CUD= operand).
These four operands provide all the information
necessary to create a unique Call Request packet.
For PAD calls that require PADPARM= values to override
those on the root MCH, an MXT rather than an SVC should
be used in place of a dteaddri value. This is because
the SVC REMOTE does not support the PADPARM= operand.
If PADPARM= values are not required, we recommend using
an SVC rather than an MXT for call processing. The SVC
control block uses less memory than the MXT. The SVC
control block is X'178' (376) bytes in length while the
MXT control block is X'480' (1152) bytes in length.
Note that when an MXT or SVC is specified in place
of a dteaddri value, the MXT identified by mxtname
will be ignored for the duration of the LU/VC session.
However, if specified, this MXT will be used to supply
VTAM parameters for the SLU during AMNF generation via
the FASTRUN process. If this MXT is not specified,
VTAM parameters come from the root MCH.
If the direction indicator at the end of the dteaddri
list is a 'T' instead of an 'O' (twoway support) and a
dteaddri list entry is a rmtname instead of a dteaddri,
the named REMOTE will be used for inbound as well as
outbound connections. If the direction indicator is
an 'I' and a dteaddri list entry is a rmtname instead
of a dteaddri, the named REMOTE will be used for inbound
connections only. For inbound calls, the DTEADDR=
value is used like a dteaddri value from dteaddri list.
If the calling DTE address from the inbound Call Request
packet matches the DTEADDR= operand value, the SLU will
be allocated for the inbound call.
The new syntax for the REMOTE SVC0= and SVC5= operands
is as follows:
REMOTE TYPE=MCH|XTP
SVCx=(n,
sluname/dteid1-dteid2-dteid3{T|O|I}
/mxtname/cud,
:
The new syntax for the MRMT SVC0= and SVC5= parameters
is as follows:
MRMT mchname
SVCx=sluname/dteid1-dteid2-dteid3{T|O|I}
/mxtname/cud
Where: dteidi = dteaddri (dd...dd) (for T|O|I)
= Xidnumi (Xdd...dd) (for T|I)
= <rmtnamei> (for T|O|I)
x = 0 for SVC0 or 5 for SVC5
CDF example to specify a dteaddr, Xidnum and <rmtname>
value for the same SLU:
MCH1 REMOTE TYPE=MCH
SVC0=(20,
MCH10011/1234-X1234-<SVC1>T01/MXT0,
:
SVC1 REMOTE TYPE=SVC
DTEADDR=10981000,DCEADDR=20351000
FAC=420909430707,CUD=C0000000
MXT0 REMOTE TYPE=MXT
DTEADDR=10991000,DCEADDR=20361000
FAC=420707430303,CUD=C0000000
MXT1 REMOTE TYPE=MXT
DTEADDR=10991001,DCEADDR=20361001
FAC=420808430303,CUD=C0000000
MRMT example to modify the Xidnum and <rmtname> value
while leaving the dteaddr value alone:
MRMT MCH1 SVC0=MCH10011/-X6789-<MTX1>
Note that when a hyphen is entered without a preceding
value, it acts as a place holder preserving the value
of the skipped dteidi list entry (1234 in this case).
DRMT example to review MRMT change:
DRMT MCH1 SVC0=MCH10011
RMTNAME OPERAND TYPE
MCH1 0084F4E8 MCH
SVC0=0020
MCH10011/1234-X6789-<MXT1>T01/MXT0
Notes: 1) Up to 3 dteidi values may be specified for
any direction identifier (T|O|I). Xidnumi
values are only used for inbound connections
while dteaddri and <rmtnamei> values can be
be used for inbound and outbound connections.
For inbound connections, the SLU is allocated
if a match occurs for any dteidi value in the
list.
2) The rmtnamei in the dteidi list must be
enclosed in non-equivalence symbols <>.
The MXT|SVC addressed by an <rmtnamei>
operand is used for the duration of the
call. That is, an MXT coded after the
dteidi list (/mxtname) is not used when
a dteidi <rmtnamei> entry is used.
3) A dd...dd value prefixed with an 'X' is
used as an IDNUM value to be matched against
IDNUM value that is carried in the CUD field
of an inbound Call Request packet. If a
match occurs, the SLU is allocated to the
inbound call. The Xdd...dd value can
contain up to 14 paired hex digits.
4) A dd...dd value without the 'X' represents
a DTE address that is used as the called
DTE address in an outbound Call Request
packet OR is matched against the calling
DTE address from an inbound Call Request
packet. If a match occurs, the SLU is
allocated to the inbound call. The dd...dd
value can contain up to 15 decimal digits.
5) Multiple dteidi values may also be specified
when the direction identifier is I. In this
case, inbound dteaddri or Xidnumi matching
will look at up to 3 values. If <rmtnamei>
is specified as a dteidi value, the dteaddri
will come from the DTEADDR= operand on the
named MXT|SVC.
6) Xidnum values are not supported in the
DTEADDR= operand on a TYPE=MXT REMOTE.
An Xidnum value may only be specified as a
dteidi value.
CIRCUMVENTION: N/A
APPLY_INFO: See Chapter 6 (Product Maintenance Installation
section) from the HNAS Guide and Reference Manual
for instructions on how to install PTF's (Object,
Source and ZAPs) or Refresh/Upgrade maintenance.
Corrective logic included in distributions created
after CLOSE_DATE. Otherwise, apply maintenance as
directed in the APPLY_INFO (PTF).
2006-08-21 - APAR 2400002
APAR: 2400002_R
STATUS: CLOSED
OPEN_DATE: 2006-08-18
CLOSE_DATE: 2006-08-21
SERVICE(S): Configuration BFRSIZ= processing
MANDATORY: NO
ORIGIN/REF: 240_CPT
CPTECH: SFD
PTF_CLASS: STANDARD-APAR
PTF_TYPE: REFRESH
PTF_LOC: Contact Support Services for Refresh E-distribution.
PROBLEM: HNAS buffer header size was increased by 16 bytes which
requires a change to the BFRSIZ= value.
DESCRIPTION: Starting with the V2R4M0 release of HNAS, the buffer
header was increase from 52 to 68 bytes which means if
you specified a value that used to allow one full packet
to fit into a single buffer, it will now require two (2)
buffers. This means that the value specified for BFRLMT=
might now be too small which can cause buffer slowdown
mode to be entered.
SOLUTION: HNAS has been modified to detect whether the new buffer
header size is being used when the BFRSIZ= operand is
processed. If not, HNAS will automatically increase
the BFRSIZ= value by 16 bytes and the following message
will be issued:
NAS1121D BUILD BFRSIZ=dddd AUTOMATICALLY INCREASED TO
dddd, DEBUG FIELD ADDED
The BFRSIZ= value will not be increased by 16 bytes
and this message will be withheld if the value you
code for BFRSIZ= already accounts for the new 68 byte
packet header, that is, it is one of the following
values:
196 = 68 + 128
324 = 68 + 256
580 = 68 + 512
1092 = 68 + 1024
2116 = 68 + 2048
4164 = 68 + 4096
9362 = TCPIP transfer limit
Note that the X.25 packet size is always given as a
power of 2 via facility code 42 therefore intervening
values do not have to be tested.
CIRCUMVENTION: Increase the value specified for BFRSIZ= by 16 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).
2006-08-10 - APAR 2400001 (was unpublished problem 2006194B)
APAR: 2400001_ER
STATUS: CLOSED
OPEN_DATE: 2006-07-07
CLOSE_DATE: 2006-08-10
SERVICE(S): SYSPRINT log management
MANDATORY: NO
ORIGIN/REF: 240_NBG
CPTECH: SFD
PTF_CLASS: ENHANCEMENT-APAR
PTF_TYPE: REFRESH
PTF_LOC: Contact Support Services for Refresh E-distribution.
PROBLEM
ENHANCEMENT: Ability to dynamically allocate SYSPRINT log files
now provided.
DESCRIPTION: Starting with the V2R4M0 release of HNAS, you can
statically allocate in JCL and define in the CDF
multiple SYSPRINT log files using the PRTSWLST=
operand on the BUILD definition statement which
employs the following syntax:
PRTSWLST=({LOOP|STOP},SWITCHAFTERINIT,SWITCHATtime,
ddname1,...,ddnamen)
With this definition, HNAS will switch from ddnamei
to ddnamej (j=i+1) when an action event occurs
(e.g., SWITCHAFTERINIT or SWITCHATMIDNIGHT), when the
current ddnamei dataset becomes full, when the PRTLMT=
value is reached or when manually requested using
the PRNT NEXTPRSW console command. DDNAME switching
in the PRTSWLST= list will stop when the last DDNAME
(ddnamen) is used unless LOOP is specified, in which
case, the first DDNAME (ddname1) will be reused.
For some users, statically allocated DDNAMEs is
limiting because datasets can be reused and because
it requires pre-defining DDNAME statements that may
or may not actually get used. To eliminate or
supplement the need for static DDNAMEs, dynamic
dataset allocation is required.
SOLUTION: HNAS has been modified to allow SYSPRINT log files
to be dynamically allocated in addition to being
statically allocated. The syntax of the PRTSWLST=
operand has been changed as follows:
PRTSWLST=({LOOP|STOP},SWITCHAFTERINIT,SWITCHATtime,
{ddname1|DYNAMIC=ocls},...
...,{ddnamen|DYNAMIC=ocls})
PRTSWLST= now specifies a list of static (ddnamei)
or dynamic (DYNAMIC=outclass) DDNAMEs that will be
used when a SYSPRINT switch occurs for any of the
reasons outlined above. You may specify static
DDNAMEs and/or request DYNAMIC DDNAME allocation
in any combination.
If you specify DYNAMIC= (no output class) or
DYNAMIC (no equal sign), class A is assumed.
Dynamic SYSPRINT log files are assigned DDNAMEs
of the form DYN#xxxx where xxxx=0001, 0002 and
so on. xxxx is incremented by 1 with each new
dynamic allocation. These generated DDNAMEs are
reserved and must not be defined statically in
the HNAS start JCL.
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-07-22 - APAR 2400000 - Notice
APAR: 2400000
STATUS: SERVICE_NOTICE-<BEGIN_MAINTENANCE/APAR_CYCLE>
OPEN_DATE: 2006-07-31
CLOSE_DATE: 2007-07-31
SERVICE(S): ALL_V2R4M0
MANDATORY: N/A (PLEASE_READ_THIS_NOTICE)
ORIGIN/REF: N/A
PTF_TYPE: N/A
PREREQ(S): N/A
MACRO(S): N/A
OBJECT(S): N/A
SOURCE(S): N/A
NOTICE: HNAS V2M4M0 release is now available.
DESCRIPTION: Standard maintenance/APARs are now provided for
this distribution level.
SOLUTION: N/A
APPLY_INFO: N/A
2006-05-01 - APAR 240beta - Notice
APAR: 230beta
STATUS: TESTING
OPEN_DATE: 2005-11-01
CLOSE_DATE: 2006-05-01
SERVICE(S): ALL_V2R4M0
DESCRIPTION: Beta product testing underway (including Datafono).
Please refer to the 240 New Features list for details.
Last Update - January 19, 2007