List of commands with similar functions for multiple resources

These tables show the IMS commands and how they affect certain resources.

Note: In the following tables, a blank indicates that the command is not applicable for the resource.

Subsections:

Telecommunication line, physical terminal, or node

The following table shows the IMS commands that affect the telecommunication line, physical terminal, or node resources. This table indicates whether each resource can perform the following functions after the command is issued:

  • Receive input
  • Send output
  • Output message queuing
Table 1. IMS commands that affect telecommunications line, physical terminal, or node resources
IMS command Receive input Send output Output message queuing
/ASSIGN Y Y Y
/LOCK N N Y
/MONITOR Y N Y
/PSTOP N N Y
/PURGE N Y Y
/RSTART Y Y Y
/START Y Y Y
/STOP N N Y
/UNLOCK Y   Y
Note: /MONITOR, /PSTOP, /PURGE, and /RSTART refer to the telecommunication line or physical terminal, not to the node.

Logical terminal

The following table shows the IMS commands that affect logical terminal resources. This table indicates whether these resources can perform the following functions after the command is issued:

  • Receive input
  • Send output
  • Queuing from other terminals
Table 2. IMS commands that affect logical terminal resources
IMS command Receive input Send output Queuing from other terminals
/ASSIGN Y Y Y
/LOCK N N N
/PSTOP N N Y
/PURGE N Y N
/RSTART      
/START Y Y Y
/STOP N N N
/UNLOCK   Y Y

MSC logical link (MSLINK) commands

Several commands are used to control logical links to other systems (MSLINKs). Logical link definitions are defined with the MSLINK macro or the CREATE MSLINK command, which enable you to name the link, to associate the logical link with a logical link defined in a partner system, and to define the type of physical link the logical link can be used with.

The following table describes the effect of each of the commands that you can use to control logical link definitions.

Table 3. Commands used to control MSC logical links definitions
MSC use and effect Type-1 command Type-2 command
Set or reset the ASR. /CHANGE LINKlink ASR ON|OFF UPDATE MSLINK SET(ASR(ON|OFF))
Change the session resynchronization option. /CHANGE LINK link

FORCSESS|SYNCSESS|
COLDSESS

 UPDATE MSLINK SET (SYNCOPT(FORCSESS|SYNCSESS| COLSDESS))
Change the default modetable name. /CHANGE LINK link MODE name UPDATE MSLINK SET(MODETBL(name)
Assign to a new physical link. /MSASSIGN LINK link MSPLINK name UPDATE MSLINK SET(MSPLINK(name)
Stop the current link and sending and receiving of messages. /PSTOP LINK link UPDATE MSLINK STOP(COMM)
Force the stoppage of a link. /PSTOP LINK link PURGE|FORCE UPDATE MSLINK STOP(COMM) OPTION(FORCE)
Start a previously stopped MSLINK and start the queuing of or sending of messages to logical links on another system. /RSTART LINK link UPDATE MSLINK START(COMM)
Start a previously stopped MSLINK and start the queuing of or sending of messages to logical links on another system, but use modetable for this session only. /RSTART LINK link MODE name UPDATE MSLINK START(COMM) SET(MODETBL(name))
Start or stop an internal trace. /TRACE SET ON|OFF LINK link UPDATE MSLINK START(TRACE) or UPDATE MSLINK STOP(TRACE)
Start or stop an XRF takeover trace. /TRACE SET ON|OFF LINK link TAKEOVER UPDATE MSLINK START(TKOTRC) or UPDATE MSLINK STOP(TKOTRC)
Start or stop the bandwidth mode. Not applicable UPDATE MSLINK SET(BANDWIDTH(ON|OFF))
Change the send/receive buffer size. Not applicable UPDATE MSLINK SET(BUFSIZE(size))
Change the logical link name. Not applicable UPDATE MSLINK SET(MSLINK(name))
Change the partner id. Not applicable UPDATE MSLINK SET(PARTNER(id))

MSC physical link (MSPLINK) commands

Several commands are used to control physical links (MSPLINKs). The MSPLINK macro or the type-2 CREATE MSPLINK command can define the following types of connections between two systems:

  • Channel-to-channel (CTC)
  • Memory-to-memory (MTM)
  • TCP/IP
  • VTAM®

The following table describes the effect of each of the commands that you can use with to control physical link paths to IMS systems.

Table 4. Commands used to control MSC physical links
MSC use and effect Type-1 command Type-2 command
Disable logons to this physical link. /PSTOP MSPLINK UPDATE MSPLINK STOP(LOGON)
Enable logons to this physical link. /RSTART MSPLINK UPDATE MSPLINK START(LOGON)
Change the address of the channel-to-channel adapter. Not applicable UPDATE MSPLINK SET(ADDR(addr))
Set or reset ASR for all assigned logical links. Not applicable UPDATE MSPLINK SET(ASR(ON|OFF))
Change the order in which IMS restarts TCP/IP and VTAM links after an XRF takeover. Not applicable UPDATE MSPLINK SET(BACKUP(n|NO))
Change the input and output buffer sizes for each logical link that is assigned to a physical link. Not applicable UPDATE MSPLINK SET(BUFSIZE(size))
Change the default modetable name for all assigned logical links. Not applicable UPDATE MSPLINK SET(MODETBL(name))
Change the physical link name. Not applicable UPDATE MSPLINK SET(MSPLINK(name))
Change the VTAM node name. Not applicable UPDATE MSPLINK SET(NODE(name))
Change the number of parallel sessions that can be active for TCP/IP and VTAM physical link types. Not applicable UPDATE MSPLINK SET(SESSION(n))

MSC logical link path (MSNAME) commands

Several commands are used to control logical link paths (MSNAMEs). Logical link paths are defined by system identifier (SYSID) pairs that identify sending and destination systems. Logical link paths are named by the MSNAME macro or by the CREATE MSNAME command.

The following table describes the effect of each of the commands that you can use to control logical link paths resources.
Table 5. Commands used to control MSC logical link paths
MSC use and effect Type-1 command Type-2 command
Change the local system identification SIDs. Not applicable UPDATE MSNAME SET(SIDL(id)
Change the remote system identification SIDs. Not applicable UPDATE MSNAME SET(SIDR(id)
Assign a new logical link path to a logical link. /MSASSIGN MSNAME UPDATE MSNAME SET(MSLINK(name))

Halt the queuing of primary requests for all remote terminals and programs represented by the MSNAME.

Continued conversations and secondary requests are handled. Primary requests entered through an input terminal receive message DFS065. Requests from other systems that require use of the logical link path for a response are not accepted but remain queued in the sending system.

 /PURGE MSNAME UPDATE \MSNAME STOP(Q) START(SEND)
Start a previously stopped MSNAME and start the queuing of or sending of messages to logical link paths. /START MSNAME UPDATE MSNAME START(Q,SEND)
Stop the sending and receiving of primary request messages associated with the logical link path.

When an MSNAME is stopped by an input system, primary requests for remote programs or terminals associated with the stopped logical link path are canceled, and message DFS065 is returned to the input terminal. Conversations in progress are allowed to continue.

When an MSNAME is stopped by a destination system, messages received from other systems over a stopped logical link path cause a logical link path to be stopped in the sending system (input or intermediate), and MTOs of the sending and receiving systems to be notified by messages DFS2140 and DFS2142, respectively. The message remains queued in the sending system until the logical link is subsequently started in both systems.

 /STOP MSNAME UPDATE MSNAME STOP(Q,SEND)

Transaction

The following table shows the IMS commands that affect transaction resources. This table indicates whether these resources can perform the following functions after the command is issued:

  • Message scheduling by transaction
  • Message queuing by transaction
Table 6. IMS commands that affect transaction resources
IMS command Message scheduling by transaction Message queuing by transaction
/ASSIGN

or

UPDATE TRAN SET		 Y Y
/LOCK

or

UPDATE TRAN SET(LOCK|ON|OFF)		 N Y
/MSASSIGN

or

UPDATE TRAN SET(MSNAME)		 Y Y
/PSTOP

or

UPDATE TRAN STOP(SCHD) START(Q)		 N Y
/PURGE

or

UPDATE TRAN START(SCHD) STOP(Q)		 Y N
/START

or

UPDATE TRAN START(Q,SCHD)		 Y Y
/STOP

or

UPDATE TRAN STOP(Q,SCHD)		 N N
/UNLOCK

or

UPDATE TRAN SET(LOCK|ON|OFF)		 Y Y

Transaction class

The following table shows the IMS commands that affect transaction class resources. This table indicates whether these resources can perform transaction scheduling by class after the command is issued.

Table 7. IMS commands that affect transaction class resources
IMS command Transaction scheduling by class
/ASSIGN Y
/MSASSIGN Y
/START Y
/STOP N
UPDATE TRAN Y or N1
UPDATE TRAN SET Y
UPDATE TRAN START (Q) Y
UPDATE TRAN STOP (Q) N
1 Whether the transaction class can perform transaction scheduling by class after the UPDATE command is issued depends on the parameters and keywords specified in this command.

Program

The following table shows the IMS commands that affect program resources. This table indicates whether the program can be started after the command is issued.

Table 8. IMS commands that affect program resources
IMS command Can the program be started?
/ASSIGN Y
/LOCK N
/START Y
/STOP N
/UNLOCK Y
UPDATE PGM SET(LOCK(ON)) N
UPDATE PGM SET(LOCK(OFF) Y
UPDATE PGM START(SCHD) Y
UPDATE PGM STOP(SCHD) N

Database

The following table shows the IMS commands that affect database resources. This table indicates whether the database can be accessed after the command is issued.

Table 9. IMS commands that affect database resources
IMS command Can the database be accessed?
/DBDUMP N
/DBRECOVERY N
/LOCK N
/START Y
/STOP N
/UNLOCK Y
UPDATE Y or N1
UPDATE DB START(ACCESS) Y
UPDATE DB STOP(ACCESS) N
UPDATED DB STOP(UPDATES) Y
UPDATE DB STOP(SCHD) N
UPDATE DB SET(LOCK(ON)) N
UPDATE DB SET (LOCK(OFF)) N
1 Whether the database can be used after the UPDATE command is issued depends on the parameters and keywords specified in this command.

Area

The following table shows the IMS commands that affect area resources. This table indicates whether the area can be accessed after the command is issued.

Table 10. IMS commands that affect area resources
IMS command Can the area be accessed?
/DBRECOVERY N
/START Y
/STOP N
UPDATE Y or N1
UPDATE AREA START(ACCESS) Y
UPDATE AREA STOP(ACCESS) N
UPDATE AREA STOP(SCHD) N
1Whether the database can be used after the UPDATE command is issued depends on the parameters and keywords specified in this command.

Subsystem

The following table shows the IMS commands that affect subsystem resources. This table indicates whether the subsystem can be attached after the command is issued.

Table 11. IMS commands that affect subsystem resources
IMS command Can the subsystem be attached?
/START Y
/STOP Y
/CHANGE N

User

The following table shows the IMS commands that affect user resources. This table indicates whether the user resource can perform the following functions after the command is issued:

  • Receive input
  • Send output
  • Output message queuing
Table 12. IMS commands that affect user resources
IMS command Receive input Send output Output message queuing
/ASSIGN Y Y Y
/RSTART Y Y Y
/START Y Y Y
/STOP N N Y