Commands that help control resources in an MSC environment

Uses and effects of Multiple System Coupling (MSC) commands are described so that you can assess their effects in your MSC environment.

If an MSC error occurs when the MSC trace is not operational, check the log for X'67' records, because some error information is logged even when the link trace is not set on.

When you suspect link problems, you can use either of the following two commands to start a trace:

Type-1 command /TRA SET ON LINK X LEVEL 3 MODULE ALL.
Type-2 command UPDATE MSLINK NAME(mslinkname) START(TRACE). This command uses the same level and module settings that were used the last time the /TRACE SET (ON) LINK command was issued. If a /TRACE SET (ON) LINK command has not been issued since the last cold start, this command defaults to MODULE=ALL and LEVEL=4.

Table 1. MSC environment commands
Command	MSC use and effect
`/ASSIGN`	Change transaction priorities.
`/BROADCAST`	Use of the `LTERM` keyword value `ALL` sends the broadcast message to all terminals of the local system only. No general broadcast capability exists for remote MSC terminals. Their LTERMs must be defined in the broadcasting system and specified in the command. Broadcasts to MTOs of remote MSC systems are possible even when the MTO terminals are not defined in the broadcasting system; use the keyword `MASTER`. The system must have defined the SYSIDs of such remote systems by using MSNAME macros or by using the type-2 CREATE MSNAME command.
`/CHANGE`	Change link mode table and session restart.
`/PSTOP`	Queue for remote processing, but do not send.
`/PURGE`	Reject subsequent primary requests for remote processing. Accept secondary or continued conversational requests. Continue sending those requests that are allowed to queue.
`/STOP`	If remote program or terminal stopped in input system: Return DFS065 to input terminal if a primary request. Queue but do not send secondary requests. If local program or terminal accessed by remote MSC systems: Queue secondary requests. Return message DFS065 to input terminal in input system for primary requests. Message DFS065 identifies, by SYSID, the MSC processing system that rejected the message. Message is logged, but canceled.
`/START`	Reset previous `/START` and `/PSTOP` effects.
`/TRACE`	Using the `LINK` keyword, you can invoke a trace of MSC operation. Trace data is recorded within type X'67' records on the IMS system log.
`UPDATE MSLINK`	Using the `UPDATE MSLINK` command, you can set or change various logical link attributes, including starting and stopping the logical link and starting and stopping traces of the logical link. The command requires the Operations Manager (OM) API. The command syntax for this command is defined in XML and is available to automation programs that communicate with OM. Using the `UPDATE` command, you can also modify MSLINK parameter values BUFSIZE=, MODETBL=, PARTNER (ID)=, and the MSLINK name (MSLINK label field).
`UPDATE MSNAME`	Using the `UPDATE MSNAME` command, you can set or change various logical link path attributes, including starting and stopping the queuing or sending of messages to logical link path. The command requires the Operations Manager (OM) API. The command syntax for this command is defined in XML and is available to automation programs that communicate with OM. Using the `UPDATE` command, you can also modify the MSNAME parameter value SYSID=.
`UPDATE MSPLINK`	Using the `UPDATE MSPLINK` command, you can set or change various physical link attributes, including preventing or allowing logons to the physical link. The command requires the Operations Manager (OM) API. The command syntax for this command is defined in XML and is available to automation programs that communicate with OM. Using the `UPDATE` command, you can also modify MSPLINK parameter values such as ADDR=, BACKUP=, BUFSIZE=, MODETBL=, SESSION=, and the physical link name (MSPLINK label field).