gtpm5m1zMessages (Online)

NETW

NETW0001EINVALID NAU NAME

Explanation: The ZNETW function issues this message if:

System Action: The command is rejected.

User Response: Do the following:

  1. Determine the correct NAU name.
  2. Enter the command again and specify the correct NAU name.

See TPF Operations for more information about the ZNETW commands.

NETW0002ICTC CTCNODES ACT PROCESSING BEGUN

Explanation: This is a normal response to the ZNETW ACT command when CTCNODES is specified as the ID.

System Action: Processing is continued.

User Response: None.

See TPF Operations for more information about the ZNETW ACT command.

NETW0003ISDA yyyy function PROCESSING COMPLETE

Where:

yyyy
Symbolic device address of a 37x5.

function
One of the following:

MOUNT
Normal mount.

MOUNT,F
Mount with the FORCE option.

Explanation: This is the normal response to the ZNETW MOUNT command when the SDA is mounted successfully.

System Action: The specified SDA is mounted.

User Response: None.

See TPF Operations for more information about the ZNETW MOUNT command.

NETW0004ELOGON PARAMETER IS REQUIRED WITH CDRM PARAMETER

Explanation: A ZNETW ACT command was issued with the CDRM parameter, but without the LOGON parameter. The LOGON parameter is required if you specify CDRM.

System Action: The ZNETW ACT command is rejected.

User Response: Enter the command again and specify the LOGON parameter and the CDRM parameter.

Note:
LOGON and CDRM are not valid if the resource specified on the ID parameter is a local resource.
See TPF Operations for more information about the ZNETW ACT command.

NETW0005EREJECTED, SYSTEM NOT IN OR ABOVE CRAS STATE

Explanation: The ZNETW command was issued when the TPF system was below the computer room agent set (CRAS) state.

System Action: The ZNETW command is rejected.

User Response: Do the following:

  1. Cycle the TPF system to CRAS state or above.
  2. Enter the command again.

See TPF Operations for more information about the ZNETW commands.

NETW0006ICTC CTCNODES ACT PROCESSING COMPLETED

Explanation: This is a normal response to the ZNETW ACT command when activating CTCNODES.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZNETW ACT command.

NETW0007ENETID IS REQUIRED IN ID PARAMETER

Explanation: There are multiple resources defined in the TPF system with the same node name as the one specified on the ID parameter. The name specified needs the network identifier (NETID) to be fully qualified.

System Action: None.

User Response: Enter the command again and specify the NETID on the ID parameter.

See TPF Operations for more information about the ZNETW commands.

NETW0008EREJECTED, SDA yyyy NOT FOUND IN SDAT OR NOT AVAILABLE

Where:

yyyy
The symbolic device address (SDA).

Explanation: The ZNETW MOUNT function issues this message if you specify a symbolic device address (SDA) that:

System Action: The command is rejected.

User Response: Do the following:

  1. Verify the address to be mounted or attach the SDA to the TPF system.
  2. Enter the command again with the valid SDA.

See TPF Operations for more information about the ZNETW MOUNT command. See TPF System Macros for more information about the CIOSC macro.

NETW0009EINVALID CDRM NAME

Explanation: The ZNETW command was entered with a name specified for the CDRM parameter that is not valid.

System Action: The ZNETW command is rejected.

User Response: Do the following:

  1. Determine the correct cross-domain resource manager (CDRM) name.
  2. Enter the command again and specify the correct CDRM name.

See TPF Operations for more information about the ZNETW commands.

NETW0010Etype nau func REJECTED, NETW INPUT MSG LIMIT EXCEEDED

Where:

type
The device type of the resource in the ID parameter.

nau
Name of the resource.

func
Function, for example ACT or INACT.

Explanation: The network command status table (NCST) is currently full. Therefore, no ZNETW command can be processed.

System Action: The ZNETW command is rejected.

User Response: Do the following:

  1. Enter the ZNNCS command to check the current activity in the NCST.
  2. Wait for an NCST slot to become available.
  3. Enter the ZNETW command again.

See TPF Operations for more information about the ZNETW and ZNNCS commands.

NETW0011Itype nau func PROCESSING BEGUN

Where:

type
The device type of the resource in the ID parameter.

nau
Name of the resource.

func
Function, for example the ACT or INACT parameters.

Explanation: This is the normal response to the ZNETW command.

System Action: Processing is continued.

User Response: None.

See TPF Operations for more information about the ZNETW commands.

NETW0012Etype nau ACT REJECTED, SYMBOLIC DEVICE ADDRESS NOT FOUND IN SDAT

Where:

type
The device type of the resource in the ID parameter.

nau
Name of the resource.

Explanation: The ZNETW ACT function issues this message if:

System Action: The request is rejected.

User Response: Enter the command again and specify a valid SDA.

See TPF Operations for more information about the ZNETW ACT command.

NETW0013ISDA yyyy function PROCESSING BEGUN

Where:

yyyy
Symbolic device address of a 37x5.

function
One of the following:

MOUNT
Normal mount.

MOUNT,F
Mount with the FORCE option.

Explanation: This is the initial response to the ZNETW MOUNT command.

System Action: Processing is continued.

User Response: None.

See TPF Operations for more information about the ZNETW MOUNT command.

NETW0014Etype nau ACT REJECTED, DUPLICATED SDA ASSIGNED

Where:

type
The device type of the resource in the ID parameter.

nau
Name of the resource.

Explanation: The symbolic device address (SDA) specified on the SDA parameter is assigned to another Network Control Program/Adjacent Link Station (NCP/ALS/CTC).

System Action: The request is rejected.

User Response: Enter the command again and specify a valid SDA that is not in use.

See TPF Operations for more information about the ZNETW commands.

NETW0019Etype nau ACT REJECTED, CIOSC MOUNT SDA ERROR

Where:

type
The device type of the resource in the ID parameter.

nau
Name of the resource.

Explanation: An error was detected by the CIOSC while trying to mount the Network Control Program (NCP) indicated by the SDA parameter.

System Action: The ZNETW command is rejected.

User Response: Do the following:

  1. Ensure that the NCP is available.
  2. Enter the command again.

See TPF Operations for more information about the ZNETW commands.

NETW0020Etype nau ACT REJECTED, NCP/CTC NOT POLLING

Where:

type
The device type of the resource in the ID parameter.

nau
Name of the resource.

Explanation: A ZNETW ACT or INACT command was issued for a cross-domain resource and the adjacent link station (ALS), Network Control Program (NCP) or channel-to-channel (CTC) of the owning cross-domain resource manager (CDRM) was not polling. The check is based on the CDRM parameter of the ZNETW ACT command or the CCW index field of the resource's RVT.

System Action: The ZNETW command is rejected.

User Response: Do the following:

  1. Verify that the request was issued for the correct resource.
  2. Check the status of NCP/ALS/CTC of the owning CDRM.
  3. Enter the command again.

See TPF Operations for more information about the ZNETW commands.

NETW0021Etype nau ACT REJECTED, SESSION LIMIT EXCEEDED

Where:

type
The device type of the resource in the ID parameter.

nau
Name of the resource.

Explanation: The Network Control Program (NCP) activation request cannot be processed because the maximum number adjacent link stations (ALSs) defined in the Systems Network Architecture (SNA) keypoint (CTK2) is zero or all the CCW areas have been used.

System Action: The ZNETW command is rejected.

User Response: Do the following:

  1. Define additional ALSs with the MAXALS parameter on the SNAKEY macro.
  2. Load new CTK2.
  3. IPL
  4. Enter the command again.

See TPF Operations for more information about the ZNETW commands. See TPF ACF/SNA Network Generation for more information about the SNAKEY macro.

NETW0022Etype nau ACT REJECTED, ACT OF CD-LU REQUIRES LOGON PARAMETER

Where:

type
The device type of the resource in the ID parameter.

nau
Name of the resource.

Explanation: The activation of a cross-domain logical unit (LU) was requested without indicating the local application program that it should be logged to. The activation of a CD-LU by the TPF system requires the use of the LOGON parameter.

System Action: The request is rejected.

User Response: Enter the command again and specify the LOGON parameter.

See TPF Operations for more information about the ZNETW ACT command.

NETW0023Etype nau ACT REJECTED, ACT OF NCP REQUIRES SDA PARAMETER

Where:

type
The device type of the resource in the ID parameter.

nau
Name of the resource.

Explanation: The activation of a local Network Control Program (NCP) was requested without indicating its symbolic device address (SDA). The activation of an NCP requires the use of the SDA parameter.

System Action: The request is rejected.

User Response: Enter the command again and specify the SDA parameter.

See TPF Operations for more information about the ZNETW ACT command.

NETW0024Etype nau func REJECTED, NO PATH FOUND

Where:

type
The device type of the resource in the ID parameter.

nau
Name of the resource.

func
Function, for example ACT or INACT.

Explanation: The activation or deactivation of a cross domain NAU was rejected, because its owning subarea is not known, therefore a path to the NAU cannot be found.

System Action: The ZNETW command is rejected.

User Response: If the ZNETW ZCT command was entered, do the following:

  1. Determine the owning subarea of the NAU and insure that the CDRM and NCP to that CDRM are active.
  2. Enter the command again.

If the ZNETW INACT command was entered, no action is necessary.

See TPF Operations for more information about the ZNETW INACT command.

NETW0025Etype nau ACT REJECTED, NCP/CTC ALREADY HAS SDA ASSIGNED

Where:

type
The device type of the resource in the ID parameter.

nau
Name of the resource.

Explanation: The ZNETW ACT command was entered but the Network Control Program (NCP) resource specified is already active.

System Action: The ZNETW ACT command is rejected.

User Response: If the symbolic device address (SDA) the one needed for the NCP, do the following:

  1. Deactivate the resource.
  2. Enter the ZNETW ACT command again and specify the new SDA.

See TPF Operations for more information about the ZNETW ACT and ZNKEY commands.

NETW0027Etype nau ACT REJECTED, SDA NOT VALID FOR THIS DEVICE TYPE

Where:

type
The device type of the resource in the ID parameter.

nau
Name of the resource.

Explanation: The ZNETW ACT command with the SDA parameter specified was entered but the device type of the symbolic device address (SDA) specified does not match the device type of the resource specified on the ID parameter.

For example, if you specify an Network Control Program (NCP) resource on the ID parameter and a channel-to-channel (CTC) resource on the SDA parameter, the function enters this message.

System Action: The ZNETW ACT command is rejected.

User Response: Enter the command again and specify the same device type on both the ID and SDA parameters.

See TPF Operations for more information about the ZNETW ACT command.

NETW0028Etype nau ACT REJECTED, PRIMARY LU luname NOT ACTIVE

Where:

type
The device type of the resource in the ID parameter.

nau
Name of the resource.

Explanation: The ZNETW ACT command was entered for a secondary logical unit (SLU) thread but the thread's owning PLU is not active.

System Action: The ZNETW ACT command is rejected.

User Response: Do the following:

  1. Enter the ZNETW ACT command to activate the PLU.
  2. Enter the command again.

See TPF Operations for more information about the ZNETW ACT command.

NETW0029WCDRM nau INACT I SAVESESS REMOTE CDRM DOES NOT SUPPORT DACTCDRM TYPE 4 ESCALATED TO FORCED, SESSION OUTAGE NOTIFICATION

Where:

nau
The 1 to 8 character CDRM name.

Explanation: The requested remote CDRM does not support nondisruptive CDRM inactivation. The CDRM is inactivated by using session outage notification (SON), DACTCDRM type 3.

System Action: For the TPF system to perform SON, the immediate inactivation is automatically escalated to a forced inactivation.

User Response: None.

See TPF Operations for more information about the ZNETW INACT command.

NETW0030Etype nau INACT REJECTED, I AND F PARAMETERS ARE MUTUALLY EXCLUSIVE

Where:

type
The device type of the resource in the ID parameter.

nau
Name of the resource.

Explanation: The ZNETW INACT command issues this message if you specify both the I (immediate) and F (forced) inactivation parameters. You can specify one of these parameters, but not both.

System Action: The request is rejected.

User Response: Enter the command again and specify either the I or the F parameter.

See TPF Operations for more information about the ZNETW INACT command.

NETW0031EREJECTED, SDA yyyy NOT MOUNTED SUCCESSFULLY

Where:

yyyy
The symbolic device address (SDA) of a 37x5.

Explanation: The ZNETW MOUNT command was entered but the symbolic device address (SDA) specified was found in the symbolic device address table (SDAT) but was unable to be mounted by using the CIOSC MOUNT macro.

System Action: The SDA is not mounted.

User Response: Do the following:

  1. Verify that the SDA is attached and online to the TPF system.
  2. Verify that the SDA is not in an error state.
  3. Enter the command again.

See TPF Operations for more information about the ZNETW MOUNT command. See TPF System Macros for more information about the CIOSC MOUNT macro.

NETW0032EREJECTED, SDA yyyy ALREADY MOUNTED. FORCE OPTION REQUIRED

Where:

yyyy
The symbolic device address (SDA) of a 37x5.

Explanation: The ZNETW MOUNT command was entered but the symbolic device address (SDA) specified was already mounted to the TPF system.

If you want to override the message and remount (that is, dismount and remount) the SDA, you must specify the FORCE option.

Note:
Dismounting the SDA of the link station can disrupt communications.

System Action: The SDA is not mounted.

User Response: Do the following:

  1. Determine whether you want to use the SDA that is already mounted or if you want to remount that SDA.
  2. If you want to remount the SDA, enter the ZNETW MOUNT command again with the FORCE parameter specified.

See TPF Operations for more information about the ZNETW MOUNT command.

NETW0033Itype nau func PROCESSING COMPLETE

Where:

type
The device type of the resource in the ID parameter.

nau
Name of the resource.

func
Function, for example the ACT or INACT parameters.

Explanation: This is the normal response to the ZNETW command when processing is complete.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZNETW commands.

NETW0034Etype nau ACT ACTIVATION OF APPC SESSIONS NOT ALLOWED WITH ZNETW

Where:

type
The device type of the resource in the ID parameter.

nau
Name of the resource

Explanation: The ZNETW ACT function issues this message if you specify a local TPF/APPC LU on the LOGON parameter. Sessions with this LU cannot be activated with the ZNETW command.

System Action: The request is rejected.

User Response: Do one of the following:

See TPF Operations for more information about the ZNETW ACT and ZNCNS commands.

NETW0035Etype nau INACT REJECTED, SAVESESS ONLY VALID FOR INACT I OR F ON A REMOTE CDRM

Where:

type
The device type of the resource in the ID parameter.

nau
Name of the resource.

Explanation: The ZNETW INACT command was entered with the following specified:

System Action: The ZNETW INACT command is rejected.

User Response: Do the following:

  1. Check the NAU type and the type of inactivation required.
  2. Enter the appropriate command again.

See TPF Operations for more information about the ZNETW INACT command.

NETW0036Etype nau ACT REJECTED, CDRM NOT ACTIVE

Where:

type
The device type of the resource in the ID parameter.

nau
Name of the resource.

Explanation: The ZNETW ACT command was entered but the the owning CDRM is not active and bound or is in data flow reset state.

System Action: The ZNETW ACT command is rejected.

User Response: Do the following:

  1. Activate the CDRM.
  2. Enter the command again.

See TPF Operations for more information about the ZNETW ACT command.

NETW0037Etype nau ACT REJECTED, REQUESTED RESOURCE ALREADY ACTIVE AND BOUND

Where:

type
The device type of the resource in the ID parameter.

nau
Name of the resource.

Explanation: The ZNETW ACT command was entered but the resource specified for activation is already active and bound.

System Action: The ZNETW ACT command is rejected.

User Response: Do one of the following:

See TPF Operations for more information about the ZNETW ACT command.

NETW0038Etype nau ACT REJECTED, ACTIVATION OF ALS IS INVALID

Where:

type
The device type of the resource in the ID parameter.

nau
Name of the resource.

Explanation: The ZNETW ACT command was entered but the adjacent link station (ALS) specified on the ID parameter. An ALS cannot be activated from the TPF system.

System Action: The ZNETW ACT command is rejected.

User Response: Do the following:

  1. Verify the resource you want to activate.
  2. If the resource an ALS, activate the ALS from the communications management configuration (CMC)
  3. If the resource is not an ALS, enter the command again with the correct ID.

See TPF Operations for more information about the ZNETW ACT command.

NETW0039Etype nau ACT REJECTED, NO SLU THREADS EXIST

Where:

type
The device type of the resource in the ID parameter.

nau
Name of the resource.

Explanation: The ZNETW function issues this message if you specify a primary LU (PLU) for the ID and LOGON parameters, but the local PLU specified on the LOGON parameter does not have any secondary LU (SLU) threads.

System Action: The request is rejected.

User Response: Do one of the following:

See TPF Operations for more information about the ZNETW ACT command.

NETW0040Etype nau ACT REJECTED, NCP NOT ACTIVE

Where:

type
The device type of the resource in the ID parameter.

nau
Name of the resource.

Explanation: The ZNETW ACT command was entered and an error occurred because cross-domain resource and the adjacent link station (ALS), channel-to-channel (CTC) or Network Control Program (NCP) of the owning cross-domain resource manager (CDRM) is not active.

System Action: The ZNETW ACT command is rejected.

User Response: Do the following:

  1. Verify that the request was entered for the correct resource.
  2. Check the status ALS, NCP, CTC of the owning CDRM and be sure that it is active.
  3. Enter the command again.

See TPF Operations for more information about the ZNETW ACT command.

NETW0041Etype nau ACT REJECTED, APPL-APPL SESSION ALREADY EXISTS

Where:

type
The device type of the resource in the ID parameter.

nau
Name of the resource.

Explanation: The ZNETW ACT function issues this message if:

System Action: The request is rejected.

User Response: None.

See TPF Operations for more information about the ZNETW ACT command.

NETW0043Etype nau ACT REJECTED, LOGON NAME NOT A LOCAL APPL

Where:

type
The device type of the resource in the ID parameter.

nau
Name of the resource.

Explanation: The ZNETW ACT function issues this message if a functional management message routing (FMMR) resource was specified on the ID parameter, but the resource specified on the LOGON parameter was not an FMMR.

System Action: The request is rejected.

User Response: Enter the command again and specify a valid, local application on the LOGON parameter.

See TPF Operations for more information about the ZNETW ACT command.

NETW0045Etype nau ACT REJECTED, INVALID REMOTE PLU OWNING SUBAREA

Where:

type
The device type of the resource in the ID parameter.

nau
Name of the resource.

Explanation: The ZNETW ACT function issues this message if the CDRM parameter was not specified and the owning subarea of the remote primary LU (PLU) is zero.

System Action: The request is rejected.

User Response: Enter the command again and specify a valid CDRM resource on the CDRM parameter.

See TPF Operations for more information about the ZNETW ACT command.

NETW0046Etype nau ACT REJECTED, LOGON ONLY ALLOWED WITH CD TPF APPL

Where:

type
The device type of the resource in the ID parameter.

nau
Name of the resource.

Explanation: The ZNETW ACT function issues this message if you specify the LOGON parameter and do not specify a cross-domain application program on the ID parameter. The LOGON parameter is only permitted when initiating sessions between local and cross domain application programs.

System Action: The request is rejected.

User Response: Do one of the following:

See TPF Operations for more information about the ZNETW ACT command.

NETW0047Etype nau ACT REJECTED, LOGON NOT ALLOWED WITH SDA

Where:

type
The device type of the resource in the ID parameter.

nau
Name of the resource.

Explanation: The ZNETW ACT function issues this message if you specify both the LOGON parameter and the SDA parameter. You can specify one of these parameters, but not both.

System Action: The request is rejected.

User Response: Enter the command again and specify either the LOGON or the SDA parameter.

See TPF Operations for more information about the ZNETW ACT command.

NETW0049Etype nau ACT REJECTED, SDA VALID ONLY FOR ACTIVATION OF NCP/CTC

Where:

type
The device type of the resource in the ID parameter.

nau
Name of the resource.

Explanation: The ZNETW ACT function issues this message if you specify the SDA parameter but the resource specified is not a Network Control Program (NCP) or channel-to-channel (CTC) resource. The SDA parameter is valid only for initiating an NCP or CTC session.

System Action: The request is rejected.

User Response: Do one of the following:

See TPF Operations for more information about the ZNETW ACT command.

NETW0050IROUTE INFORMATION STATUS FOR NCP name

Where:

NCP name
The NCP name.

Explanation: This is a normal response to the ZNETW ROUTE command. This message is followed by a display of the routing information for the specified Network Control Program (NCP) or CTC.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZNETW ROUTE command.

NETW0052ESPECIFIED NAU IS NOT AN NCP OR CTC

Explanation: The network addressable unit (NAU) specified in the ZNETW ROUTE command is not a Network Control Program (NCP) or a CTC. Requests for routing information are only valid with NCPs or CTCs.

System Action: None.

User Response: Verify that the NAU specified is an NCP or CTC.

See TPF Operations for more information about the ZNETW ROUTE command.

NETW0053IINACT CTCNODES PROCESSING COMPLETE

Explanation: This is a normal response to the ZNETW ACT command when inactivating CTCNODES.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZNETW ACT command.

NETW0054ICTC CTCNODES INACT PROCESSING BEGUN

Explanation: This is the normal response to the ZNETW INACT command with CTCNODES specified for the ID parameter.

System Action: Processing is continued.

User Response: None.

See TPF Operations for more information about the ZNETW INACT command.

NETW0055EREJECTED, type func IN PROGRESS FOR nau

Where:

type
One of the following:

LOCAL

REMOTE

func
One of the following:

ACT

INACT

INACT,I

INACT,F

nau
The name of the resource with the conflicting action.

Explanation: The ZNETW function issues this message when there is a conflicting entry in the network command status table (NSCT) for the specified resource.

System Action: The request is rejected.

User Response: Wait until processing is completed on the conflicting resource as enter the command again, if necessary.

See TPF Operations for more information about the ZNETW commands.

NETW0056Etype nau ACT REJECTED, LOGON PARAMETER RESOURCE NOT ACTIVE

Where:

type
The device type of the resource in the ID parameter.

nau
Name of the resource.

Explanation: The ZNETW ACT command was entered with the LOGON parameter specified. An error occurred because the resource specified on the LOGON parameter is not active.

System Action: The ZNETW ACT command is rejected.

User Response: Do the following:

  1. Enter the ZNETW ACT command and specify the resource on the ID parameter to activate that local resource (that is, the resource on the LOGON parameter).
  2. Enter the original ZNETW ACT command again and specify that resource on the LOGON parameter.

See TPF Operations for more information about the ZNETW ACT command.

NETW0057Etype nau ACT REJECTED, LOGON PARAMETER RESOURCE NOT LOCAL

Where:

type
The device type of the resource in the ID parameter.

nau
Name of the resource.

Explanation: The ZNETW ACT function issues this message if you specify a resource on the LOGON parameter that is not local.

System Action: The request is rejected.

User Response: Enter the command again and specify a valid, local resource on the LOGON parameter.

See TPF Operations for more information about the ZNETW ACT command.

NETW0058Etype nau ACT REJECTED, LOGON PARAMETER RESOURCE NOT STARTED

Where:

type
The device type of the resource in the ID parameter.

nau
Name of the resource.

Explanation: The ZNETW ACT command was entered with the LOGON parameter specified. An error occurred because you specified a resource on the LOGON parameter that:

System Action: The ZNETW ACT command is rejected.

User Response: Do the following:

  1. Enter a ZROUT START command for the application name in the ZNETW ACT command when specifying the LOGON parameter.
  2. Enter the ZNETW ACT command again.

See TPF Operations for more information about the ZROUT START and ZNETW ACT commands.

NETW0059Etype nau ACT REJECTED, UNABLE TO ASSIGN A CLU NETWORK ADDRESS

Where:

type
The device type of the resource in the ID parameter.

nau
Name of the resource.

Explanation: A ZNETW command was entered to activate a control LU-control LU (CLU-CLU) session over a channel-to-channel (CTC) link but the network address could not be assigned.

System Action: The ZNETW command is rejected.

User Response: Check the local element table or the network address table to determine why these tables are full.

See TPF Operations for more information about the ZNETW commands.

NETW0060ISUBAREA DISPLAY NAU  TYPE  STATUS  IN-PROG

Explanation: This is the normal response to the ZNETW DISPLAY command. This message is followed by a display of the status of the network subareas.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZNETW DISPLAY command.

NETW0061Inau func PROCESSING count SESSIONS PENDING

Where:

nau
Name of the resource being inactivated.

func
Function in process, which can be one of the following:

INACT

INACT,I

count
The count of sessions pending inactivation.

Explanation: The ZNETW INACT command was entered. The TPF system monitors the inactivation request on a time initiated basis. This message is issued to report the status of the inactivation request.

System Action: The event is restarted to await completion of the ZNETW INACT command.

User Response: Do the following:

  1. Enter the ZNDLU command with the PROCEDURE-UNBIND parameter specified to identify the pending sessions.
  2. Enter a more powerful ZNETW INACT command for these LUs to force the inactivation of these sessions.

See TPF Operations for more information about the ZNETW INACT and ZNDLU commands.

NETW0062IALSNODES PROCESSING BEGUN

Explanation: The ZNETW ACT command was entered with ALSNODES specified for the ID parameter.

System Action: Processing continues.

User Response: None.

See TPF Operations for more information about the ZNETW ACT command.

NETW0063IALSNODES ACT PROCESSING COMPLETED

Explanation: The processing of a ZNETW ACT ID-ALSNODES message has completed.

System Action: Exit the ECB.

User Response: None.

See TPF Operations for more information about the ZNETW ACT command.

NETW0064IALSNODES ACT PROCESSING BEGUN

Explanation: The ZNETW INACT command was entered with ALSNODES specified for the ID parameter.

System Action: Processing continues.

User Response: None.

See TPF Operations for more information about the ZNETW INACT command.

NETW0065IALSNODES INACT PROCESSING COMPLETED

Explanation: The ZNETW INACT command was entered with ALSNODES specified for the ID parameter.

System Action: Processing completed successfully. The entry control block exits.

User Response: None.

See TPF Operations for more information about the ZNETW INACT command.

NETW0066EINCORRECT CNT VALUE, SPECIFY 1 TO 255

Explanation: The ZNETW ACT command was entered with the CNT parameter specified. An error occurred because the value specified is not correct.

System Action: The ZNETW ACT command is rejected.

User Response: Enter the ZNETW ACT command again specifying a valid value for the CNT parameter.

See TPF Operations for more information about the ZNETW ACT command.

NETW0067Ix SLU SESSIONS REQUESTED, y INITIATED

Where:

x
The number of secondary logical unit (SLU) sessions requested.

y
The number of SLU sessions initiated.

Explanation: This is the normal response to the ZNETW ACT command with the CNT parameter specified.

System Action: Session activation continues.

User Response: Enter the ZNDLU command if you want to display the active SLU sessions.

See TPF Operations for more information about the ZNETW ACT and ZNDLU commands.

NETW0069Ifunc nau REQUEST OVERRIDDEN BY A MORE POWERFUL COMMAND

Where:

func
One of the following:

ACT

INACT

INACT,I

nau
Name of the resource.

Explanation: A ZNETW command was entered. This message displays when:

System Action: The following happens:

  1. The less powerful command is purged from the NCST.
  2. A message is sent to both the originator of the message in the NCST and the originator of the current ZNETW command request to notify each about the purge. (If the requests were made from the same device, then only one message is sent.)

User Response: Do the following:

  1. Wait for processing to complete for the more powerful resource.
  2. Enter the command again, if necessary.

See TPF Operations for more information about the ZNETW commands.

NETW0100ICPCP ACT PROCESSING BEGUN

Explanation: This is the normal response to the ZNETW ACT command with CPCP specified for the ID parameter.

System Action: Processing continues.

User Response: None.

See TPF Operations for more information about the ZNETW ACT command.

NETW0101ICPCP ACT PROCESSING COMPLETE, CP cpname SELECTED

Where:

cpname
The name of the remote CP with which the TPF system now has CP-CP sessions.

Explanation: This is the normal response to the:

System Action: None.

User Response: None.

See TPF Operations for more information about the ZNETW ACT command.

NETW0103ELINK alsname IS QUIESCED

Where:

alsname
The name of the adjacent link station (ALS) specified for the LINK parameter on the ZNETW ACT command.

Explanation: The ZNETW ACT command was entered, but the ALS specified for the LINK parameter is quiesced. A quiesced link cannot be used to start any new sessions.

System Action: The ZNETW ACT request is rejected.

User Response: Enter the command and specify an ALS for the LINK parameter that is not quiesced.

See TPF Operations for more information about the ZNETW ACT command.

NETW0104ECP-CP SESSIONS ALREADY EXIST ON PROCESSOR x

Where:

x
The CPU ID of the TPF processor with the CP-CP sessions.

Explanation: The ZNETW ACT command was entered with the CPCP option for the ID parameter, but the TPF system already has active CP-CP sessions. Only 1 TPF processor in the loosely coupled complex is allowed to have CP-CP sessions at any given time.

System Action: The ZNETW ACT request is rejected.

User Response: None.

See TPF Operations for more information about the ZNETW ACT command.

NETW0105ECANNOT ACTIVATE CP-CP SESSIONS, LINK alsname NOT ACTIVE

Where:

alsname
The name of the adjacent link station (ALS) specified for the LINK parameter on the ZNETW ACT command.

Explanation: The ZNETW ACT command was entered, but the ALS specified for the LINK parameter is not active.

System Action: The ZNETW ACT request is rejected.

User Response: Do one of the following:

See TPF Operations for more information about the ZNETW ACT command.

NETW0106ELINK alsname NOT CONNECTED TO REMOTE CP cpname

Where:

alsname
The name of the adjacent link station (ALS) specified for the LINK parameter on the ZNETW ACT command.

cpname
The name of the remote CP specified for the ID parameter on the ZNETW ACT command.

Explanation: The ZNETW ACT command was entered, but the ALS specified for the LINK parameter is not connected to the remote CP specified for the ID parameter.

System Action: The ZNETW ACT request is rejected.

User Response: Do one of the following:

See TPF Operations for more information about the ZNETW ACT command.

NETW0107ELINK alsname DOES NOT SUPPORT CP-CP SESSIONS

Where:

alsname
The name of the adjacent link station (ALS) specified for the LINK parameter on the ZNETW ACT command.

Explanation: The ZNETW ACT command was entered, but the ALS specified for the LINK parameter does not support CP-CP sessions.

System Action: The ZNETW ACT request is rejected.

User Response: Do one of the following:

See TPF Operations for more information about the ZNETW ACT command.

NETW0108ENO LINKS ACTIVE THAT SUPPORT CP-CP SESSIONS

Explanation: The ZNETW ACT command was entered without the LINK parameter specified and CPCP was specified for the ID parameter. One of the following errors occurred:

System Action: The ZNETW ACT command is rejected.

User Response: Do the following:

  1. Activate a link that supports CP-CP sessions.
  2. Enter the ZNETW ACT command again.

See TPF Operations for more information about the ZNETW ACT command.

NETW0109ELINK alsname DOES NOT EXIST

Where:

alsname
The name of the adjacent link station (ALS) specified for the LINK parameter on the ZNETW ACT command.

Explanation: The ZNETW ACT command was entered but, the resource specified for the LINK parameter does not exist or is not an ALS.

System Action: The ZNETW ACT request is rejected.

User Response: Enter the ZNETW ACT command again and specify a valid ALS name for the LINK parameter.

See TPF Operations for more information about the ZNETW ACT command.

NETW0110EREJECTED, NO CP-CP SESSIONS TO PROCESS LOGON REQUEST

Explanation: The ZNETW ACT command was entered with the LOGON parameter specified but there were no active CP-CP sessions to process the session activation request.

System Action: The ZNETW ACT command is rejected.

User Response: Do the following:

  1. Activate CP-CP sessions.
  2. Enter the ZNETW ACT command again.

See TPF Operations for more information about the ZNETW ACT command.

NETW0111EREJECTED, TPF NOT RUNNING IN APPN MODE

Explanation: The ZNETW ACT command was entered to start CP-CP sessions but the TPF system is not running in APPN mode.

System Action: The ZNETW ACT command is rejected.

User Response: Do the following:

  1. Enter the ZNAPN command to switch the TPF system to APPN mode.
  2. Enter the ZNETW ACT command again.

See TPF Operations for more information about the ZNETW ACT and ZNAPN commands.

NETW0112EREJECTED, LOCAL CP cpname NOT ACTIVE

Where:

cpname
The name of the local APPN CP in the TPF system.

Explanation: The ZNETW ACT command was entered to start CP-CP sessions but the local CP is not active.

System Action: The ZNETW ACT command is rejected.

User Response: Do the following:

  1. Enter the ZNETW ACT and ZROUT START commands to start the local CP.
  2. Enter the original ZNETW ACT command again.

See TPF Operations for more information about the ZNETW ACT and ZROUT START commands.

NETW0113EINSUFFICIENT RESOURCES TO START CP-CP SESSIONS

Explanation: The ZNETW ACT command was entered to start CP-CP sessions, but the necessary resources are not available. This could be because there are no session control blocks (SCBs) defined, SCBs are defined but all in use, or the selected ALS is already at its maximum session limit.

System Action: The ZNETW ACT request is rejected.

User Response: Enter the ZNKEY command and specify the MAXSCB parameter to determine if SCBs are defined and do one of the following:

See TPF Operations for more information about the ZNETW ACT, ZNKEY, and ZNMON commands.

NETW0114EREJECTED, CANNOT ACCESS APPN TAPST RECORD

Explanation: The ZNETW ACT command was entered to start CP-CP sessions, but the APPN TAPST record on file could not be examined.

System Action: The ZNETW ACT request is rejected.

User Response: None.

See TPF Operations for more information about the ZNETW ACT command.

NETW0115EREJECTED, NO CP-CP SESSIONS EXIST

Explanation: The ZNETW INACT command was entered with the CPCP option specified for the ID parameter, but there were no CP-CP sessions active.

System Action: The ZNETW INACT request is rejected.

User Response: None.

See TPF Operations for more information about the ZNETW INACT command.

NETW0116EREJECTED, CP-CP SESSIONS EXIST ON PROCESSOR x

Where:

x
The CPU ID of the TPF processor that owns the CP-CP sessions.

Explanation: The ZNETW INACT command was entered with the CPCP option specified for the ID parameter, but this TPF processor does not own the CP-CP sessions. If the FORCE parameter was specified, the TPF processor that owns the CP-CP sessions is still active. Therefore, this processor cannot deactivate those CP-CP sessions.

System Action: The ZNETW INACT request is rejected.

User Response: Enter the ZNETW INACT command from the TPF processor that owns the CP-CP sessions.

See TPF Operations for more information about the ZNETW INACT command.

NETW0117WCOMPLETED, PROCESSOR x NO LONGER OWNS CP-CP SESSIONS

Where:

x
The CPU ID of the TPF processor that owned the CP-CP sessions.

Explanation: The ZNETW INACT command was entered with the FORCE parameter and the CPCP option for the ID parameter. The TPF processor that owns the CP-CP sessions was found to be inactive.

System Action: The APPN structures in the TPF system are updated to indicate that CP-CP sessions no longer exist in the loosely coupled complex.

User Response: While the APPN structures in the TPF system are cleaned up, it may be necessary to deactivate the CP-CP sessions from the remote CP.

See TPF Operations for more information about the ZNETW INACT command.

NETW0118ECP-CP SESSION ACTIVATION WITH CP cpname HAS FAILED

Where:

cpname
The name of the remote CP with which the TPF system tried to start CP-CP sessions.

Explanation: The ZNETW ACT command was entered to start CP-CP sessions but the activation failed.

System Action: The ZNETW ACT request is rejected.

User Response: Review the path information unit (PIU) trace to determine why the CP-CP sessions could not be activated.

See TPF Operations for more information about the ZNETW ACT command.

NETW0119EREJECTED, CP-CP ACTIVATION VALID ONLY IN NORM STATE

Explanation: The ZNETW ACT command was entered to start APPN CP-CP sessions while the TPF system was below NORM state.

System Action: The ZNETW ACT command is rejected.

User Response: Do the following:

  1. Cycle the TPF system to NORM state.
  2. Enter the ZNETW ACT command again.

See TPF Operations for more information about the ZNETW ACT command.

NETW0120EREJECTED, NO ACTIVE APPN LINKS ON THIS HOST

Explanation: The ZNETW ACT command was entered but no APPN links are active on the TPF processor.

System Action: The ZNETW ACT command is rejected.

User Response: Do the following:

  1. Activate an APPN link on that TPF processor.
  2. Enter the ZNETW ACT command again.

See TPF Operations for more information about the ZNETW ACT command.