Changing network and communications settings *MODIFY,NJE
Function
Use the *MODIFY,NJE command to:
- Reset the lines connecting your node to a specific remote node when your node has abnormally ended communication on the line.
- Place jobs that are scheduled for transmission to a specific remote node in operator hold status.
- Release a remote node from hold status.
- Dynamically add a directly-connected node to your network at your home node.
- Dynamically add an indirectly-connected node to your network.
- Dynamically add an alias of your home node to your network.
- Dynamically delete a node or alias from your network.
- Change the way jobs are routed between your node and any remote node in your network.
- Change the type of networking protocol you are using between your node and a remote node.
- Change the job password control option for first job card passwords sent to a remote node.
- Change the default print, TSO, external writer, or punch classes of an alias or the home node.
- Change the option for processing inbound SYSOUT data in NETDATA format on the home node.
Syntax
Print Class
Parameters
- ADD=nodename
- Specifies the name of the new node you want to add to the network.
- PATH=nodename1
- When the PATH=nodename1 parameter is used with the ADD=nodename parameter, it specifies the path value nodename1 for the indirectly connected node that you are adding. When it is used with the NAME=nodename parameter, it changes the node to an indirectly connected path node with a path value of nodename1.
- TYPE=BSC or SNA or TCPIP
- Indicates the BSC/NJE, the SNA/NJE, or the TCP/IP/NJE networking protocol that you want between
your node and the node you specify on the NAME= parameter. Note: Any jobs scheduled using the previous protocol need to be rerouted. You can use NJEROUT DSP to reroute the jobs by specifying the PATH and TO parameters for the modified node.
- DEL=nodename
- Specifies the name of the node or alias you want to delete from the network.
- NAME=nodename
- Specifies the name of a node to modify. JES3 changes the communication protocol being used to transmit data to this node based on what you select in the TYPE= keyword.
- FORCE
- Resets the lines connecting your node with the specified remote node. You can use this parameter only for BSC/NJE networks.
- HOLD
- Places jobs scheduled for transmission to the node in operator hold status at this node. Use the HOLD parameter only for directly connected nodes.
- NOHOLD
- Restarts networking activity between your node and the specified node. Use the NOHOLD parameter only for directly connected nodes.
- NETHOLD=NO or YES
- Specifies the option for processing inbound SYSOUT data in NETDATA format. NETHOLD=NO indicates that the output is placed on the writer queue for processing by JES3 writers if the destination is defined as a device or remote workstation. NETHOLD=YES indicates that the SYSOUT is always placed on the hold queue for processing by TSO RECEIVE.
- PATH=nodename1
- Specifies the name of the remote node to which JES3 will send all future transmissions destined for the node specified in the NAME= parameter.
- JT=
- Specifies the number of job transmitters defined for the node. This keyword is valid only for nodes that have a type of TCPIP.
- JR=
- Specifies the number of job receivers defined for the node. This keyword is valid only for nodes that have a type of TCPIP.
- OT=
- Specifies the number of output transmitters defined for the node. This keyword is valid only for nodes that have a type of TCPIP.
- OR=
- Specifies the number of output receivers defined for the node. This keyword is valid only for nodes that have a type of TCPIP.
- SS=NO or YES
- Specifies that a secure signon protocol is used that uses an encryption key stored in the security product. This keyword is valid only for nodes that have a type of TCPIP.
- TLS=NO or YES
- Indicates whether the Transport Layer Secure facility is to be used by all sockets that are used by this node. This keyword is valid only for nodes that have a type of TCPIP.
- TYPE=BSC or SNA or TCPIP
- Indicates one of the BSC/NJE, the SNA/NJE and the TCP/IP/NJE networking protocols that you want between your node and the node you selected on the NAME= keyword.
- PWCNTL= or PC=
- Specifies that the job password control option for passwords sent to the designated node for processing is to be set to one of the following: send jobs with passwords encrypted (SENDENC), send jobs with passwords in clear text (SENDCLR), or send jobs after passwords are verified at the local node (LOCALCHK).
- R= or RETRYCT=
- Specifies the number of retries (from 1 to 300) to attempt before ending the BSC NJE line.
- ADDAL=aliasnam or AA=aliasnam
- Specifies the name of a new alias of the home node to be added.
- PRECHECK=YES or NO
- Specifies the option for whether an NJE job undergoes revalidation before execution on the home node. PRECHECK=YES specifies that an NJE job marked dubious undergoes additional validation on the home node. PRECHECK=NO specifies that JES3 is not to perform path verification process for certain inbound NJE jobs.
- PRTDEF=class
- Specifies the default print class for output being received under the home node or alias. The default is A.
- PRTTSO=class
- Specifies the default TSO class for output being received under the home node or alias. The default is the PRTDEF value specified (or assigned by default).
- PRTXWTR=class
- Specifies the default external writer class for output being received under the home node or alias. The default is the PRTDEF value specified (or assigned by default).
- PUNDEF=class
- Specifies the default punch class for output being received under the home node or alias. The default is B.
- SP=
- Specifies the name of the spool partition. JES3 writes spool data for all jobs from that node to this partition.
- VFYPATH=YES or NO
- Displays the option for whether path verification processing is performed for NJE jobs claiming to originate on the named node. VFYPATH=YES specifies that JES3 is to perform path verification processing for inbound NJE jobs. NJE jobs might be marked dubious as a result. VFYPATH=NO specifies that JES3 does not perform path verification processing for inbound NJE jobs.
Rules
- You cannot dynamically add your installation (the home node) to the network.
- Be careful when using the *MODIFY,NJE command to change the type of protocol from SNA or TCP/IP to BSC. In particular, a device with DTYPE of NJELINE must be available for this BSC node to use. If such a device does not exist, it must be added with a hot start with refresh before you can use the modified BSC node.
- You cannot dynamically delete your installation (the home node) from the network.
- You cannot delete an active adjacent BSC node from your installation. An active node is a node currently transmitting or receiving data.
- You should not delete an active SNA node from your installation.
- You cannot delete an active adjacent TCP/IP node from your installation. An active TCP/IP node is a node that has signed on to another node with at least one socket.
- A TCP/IP node cannot be modified to another protocol if it has socket definitions referencing it, regardless of whether the node is active.
- Use the NETHOLD= parameter only for the home node.
- Use the R and FORCE parameters only for BSC/NJE networking.
- Use the FORCE parameter only when all other attempts to clear or restart the line have failed.
- If you are using multiple concurrent lines between this node and the specified node, you must end those connections before using the FORCE or DEL parameter.
- You can use the PRTDEF, PRTTSO, PRTXWTR, or PUNDEF parameter only when adding a new alias, modifying an existing alias, or modifying the home node.
- The path specified on the PATH parameter must not be the home node or an alias.
- Spool partition can be added or modified to a node with modify command.
- Spool partition cannot be deleted from a node with modify command.
- Spool partition cannot be added to an alias or home node.
- A node cannot be defined with more than one protocol at a time.
- You can modify a node that uses BSC protocol to use SNA or TCP/IP protocol.
- When you modify the protocol for a node, any parameters that depend on the old protocol are cleared out and defaults are used if the protocol for the node is modified back. Therefore, you might need more than one modify command to restore the protocol-dependent settings to the ones that you need.
- You can modify a node between using SNA protocols and using TCP/IP protocols with little impact to your complex, if both BDT and TCP/IP are capable of understanding how to connect the node.
- Additions, deletions, and modifications to TYPE=TCPIP nodes are remembered over a JES3 hot start. Additions, deletions, and modifications to BSC and SNA nodes are not remembered over a JES3 hot start.
- Modifying a node from TYPE=TCPIP to BSC or SNA is treated as a simultaneous deletion of the
TCP/IP node and addition of a BSC or SNA node with the same name. Therefore, the node is not
remembered over a JES3 restart. Likewise, modifying a node from TYPE=BSC or SNA to TCPIP is treated
as a simultaneous deletion of the BSC or SNA node and addition of a TCP/IP node with the same name.
Therefore, the node is remembered as TYPE=TCPIP over a JES3 restart.
During a hot start with refresh, all nodes will be defined according to their parameters in the initialization stream except that active nodes will retain the definitions that they have at the time JES3 is brought down. If you modify node types, you can ensure that the nodes you are working remain defined and retain their protocol across a restart if you define all nodes in the initialization stream and perform a hot start with refresh.
- The value specified for the JT, JR, OT, or OR keyword must not be less than 1 or greater than 7.
- The JT, JR, OT, and OR keywords must not be specified in such a way that the sum of the values for JT and OT, or the sum of the values for JR and OR would become greater than 8. For example, if the JT value for the node being modified is currently 4 and OT is being modified, the value of OT cannot be greater than 4.
Examples
Reset the BSC/NJE lines to node BOS:
*F,NJE,N=BOS,FORCE
- JES3 allows any current transmissions to the specified node to complete.
- JES3 then places the specified node in hold status. However, you can still receive network jobs from the node and both nodes can still transmit and receive messages and commands.
- Any new jobs that are routed to the specified node after the command is entered are placed in operator hold status.
- Any jobs that are routed to the specified node that were in specialized rescheduling at the time the command was entered will remain in specialized rescheduling; they will be placed in operator hold status when they have been rescheduled.
IAT8460 NJERMT UPDATE COMPLETE. REQUEST HONORED.Hold all jobs scheduled for transmission to the remote node CHI:
*F,NJE,NAME=CHI,HOLD
IAT8460 NJERMT UPDATE COMPLETE. REQUEST HONORED.Issue the *F,NJE command to release node CHI from hold status:
*F,NJE,NAME=CHI,NOHOLDJES3 releases the specified node from hold status but
does not release any jobs that are routed to the node that were placed in operator hold
status before you entered this command. Follow the steps below to release all jobs that are routed
to CHI that are in operator hold status: - Issue the *I,Q,H command to determine which networking jobs are in hold status:
*I,Q,H - Issue the *F,J=,R command including the job number for each job in hold status to release the
jobs from operator hold status:
The resulting display (IAT8674) indicates that jobs 1234 and 2345 were either being prepared for transmission or were waiting for transmission (dspname = NJESND) when they were put in operator hold status.*F,J=(1234,2345),R
IAT8460 NJERMT UPDATE COMPLETE. REQUEST HONORED.Issue the *F,NJE command to assign spool partition PART1 to NODE1.
*F,NJE,NAME=NODE1,SP=PART1JES3 modifies the spool partition for NODE1 to
PART1. IAT8460 NJERMT UPDATE COMPLETE. REQUEST HONORED.