IMS Version 9

/PSTOP

Format

Read syntax diagramSkip visual syntax diagram>>-+-/PSTOP-+--------------------------------------------------->
   '-/PST---'

             .-------.
             V       |
>--+-LINE--+---line#-+--------------------+--------------+-----><
   |       |                 .--------.   |              |
   |       |                 V        |   |              |
   |       +-line#--PTERM--+---pterm#-+-+-+              |
   |       |               '-ALL--------' |              |
   |       '-ALL--------------------------'              |
   +-LINK--+-link  #------+------------------------------+
   |       +-ALL----------+                              |
   |       +-link #-PURGE-+                              |
   |       '-link #-FORCE-'                              |
   |          .----------------.                         |
   |          V                |                         |
   +-LTERM--+---+-ltermname--+-+-+-----------------------+
   |        |   '-ltermname*-'   |                       |
   |        '-ALL----------------'                       |
   |            .-------------.                          |
   |            V             |                          |
   +-MSPLINK--+---msplinkname-+-+------------------------+
   |          '-ALL-------------'                        |
   +-REGION--+-reg#--+-AOITOKEN--aoitokenname-+--------+-+
   |         |       '-TRANSACTION--tranname--'        | |
   |         '-JOBNAME--jobname--TRANSACTION--tranname-' |
   |         .---------------.                           |
   |         V               |                           |
   '-TRAN--+---+-tranname--+-+------------+--------------'
           |   '-tranname*-'              |
           '-ALL--+---------------------+-'
                  |          .------.   |
                  |          V      |   |
                  '-CLASS--+---cls#-+-+-'
                           '-ALL------'

Environments and Keywords

Table 86 lists the environments (DB/DC, DBCTL, and DCCTL) from which the command and keywords can be issued.

Table 86. Valid Environments for the /PSTOP Command and Keywords
Command / Keywords DB/DC DBCTL DCCTL
/PSTOP X X X
AOITOKEN X X X
CLASS X X
FORCE X X
JOBNAME X X X
LINE X X
LINK X X
PURGE X X
LTERM X X
MSPLINK X X
PTERM X X
REGION X X X
TRAN X X

Usage

/PSTOP accomplishes the following:

If an error is detected on parameters that are independent of one another, only the invalid parameters are indicated as being in error and the /PSTOP command processes the rest of the parameters.

/PSTOP can be used to reset conditions previously established with the /START, /RSTART, /PURGE, or /MONITOR command.

In a single IMS system, or in the local system in a multiple system configuration, IMS system messages such as broadcast text and terminal status messages (DFS059 TERMINAL STARTED) are not affected by /PSTOP. In a multiple system configuration, broadcast messages are queued but not sent across process stopped links. potential transactions.

LINE
Specifies the communication line that IMS will stop sending messages to and receiving messages from.
LINK
Specifies the link to be stopped; the partner link in another IMS system stops itself and notifies that system's master terminal operator.

/PSTOP LINK resets continuous mode for a BISYNC link. See the /RSTART LINK CONTINUOUS command in /RSTART for an explanation of continuous mode.

PURGE
PURGE can only be used for one logical link whose physical link is channel-to-channel. PURGE must be used when the partner link is in a system that has failed and the link will not go idle although it has been stopped.
FORCE
The FORCE keyword is for VTAM links and is intended for use when an MSC VTAM link will not clean up and idle during normal PSTOP processing, even though VTAM has terminated the session. It can be used, in conjunction with some VTAM commands to idle and clean up the VTAM link within IMS, so that an /RSTART LINK can be issued to restart the link.

The operation of the command first determines if the link has begun PSTOP processing. (If so, the link will display as PSTOPPED NOTIDLE). Next it will test if the hang condition is due to an outstanding VTAM request that has not completed. If so, it will issue an inquire request to VTAM to determine if the session is inactive. In that case, IMS will simulate completion of the VTAM request and allow the link to complete PSTOP processing.

To determine if the session is still active to VTAM, issue a DISPLAY NET,SESSIONS,LU1=applid1,LU2=applid2,SCOPE=ALL,LIST=ALL, and note the SID of the session if it is active.

If the session is not active, and it has a PSTOPPED NOTIDLE status to IMS, then /PSTOP LINK x FORCE can be issued. If the session is still active to VTAM, then VARY NET,TERM,SID=x,NOTIFY=YES,SCOPE=ALL,TYPE=FORCE can be issued to VTAM to terminate the session.

Under normal conditions, the VTAM VARY NET,TERM command should terminate the session in VTAM and cause IMS to PSTOP and IDLE the link associated with the VTAM session. If the VTAM VARY command does terminate the VTAM session but does not PSTOP and IDLE the link, then the IMS /PSTOP LINK FORCE command can be used to complete the PSTOP and cleanup processing within IMS.

After PSTOP processing is completed on one side of the line, the other side should be displayed. If the other side is not in a PSTOP IDLE state, the operation should be repeated for the other IMS. When both sides are in the PSTOP IDLE state, the /RSTART LINK command can be issued.

IMS replies with DFS058 /PSTOP LINK COMPLETED EXCEPT LINK x, if the /PSTOP LINK x FORCE command cannot be executed because:

  • The session is still active to VTAM.
  • Normal PSTOP processing has not begun (issue /PSTOP without the FORCE keyword in this case).
  • PSTOP processing is not completing due to some reason other than an incomplete VTAM request.
LTERM
Specifies the logical terminal that is to be stopped from sending and receiving messages.

The /PSTOP LTERM command has no effect on an LTERM that is in QLOCK state, or is a remote logical terminal. The LTERM parameter can be generic, where the generic parameter specifies LTERMs that already exist.

The /PSTOP LTERM command is valid only for LTERMs that belong to nodes that are logged on.

MSPLINK
Applies to MSC VTAM links only; it stops logons to the physical link and enables the operator to reassign (/MSASSIGN) logical links to the physical link. The /MSASSIGN command does not affect links in sessions that have not been stopped by the /PSTOP command. When logical link assignments are complete, the /RSTART command should be issued to permit logons to the physical link.
REGION
If the TRANSACTION keyword is specified, the message region is not stopped. A QC status (no more messages) is returned to the application program currently active in the specified region. The scheduler will continue to schedule available transactions in the referenced region.

The /PSTOP REGION command is ignored unless both of the following occur:

If the AOITOKEN keyword is specified, the AO application in wait AOI token state is posted and receives AIB return code X'00000004' and reason code X'0000004C'.

If JOBNAME keyword is specified, the job name for the dependent region must be 1-8 alphanumeric or national ($,#,@) characters. The first character of the job name must be either alphabetic or national.

TRANSACTION
Stops the scheduling of transactions; however, the transactions will continue to be processed until the limit count is reached. If the limit count is large, the processing interval will be long. The /DISPLAY command ascertains the status of the transaction; the /ASSIGN command alters the status of the transaction.

If a region is scheduled against a process stopped transaction and there are no more messages available for that transaction, the region does not wait for the next message (wait-for-input-mode). Instead, a QC status (no more messages) is returned to the application. If the region is scheduled and waiting for the next message when the command is entered, the region is notified and a QC status is returned to the application.

A batch message processing region (BMP) scheduled against wait-for-input (WFI) transactions returns a QC status code (no more messages) for /PSTOP REGION, /DBD, /DBR, or /STA commands only.

/PSTOP cannot stop the scheduling of Fast Path exclusive transactions but can be used to stop Fast Path potential transactions.

/PSTOP TRANSACTION cannot be used for Fast Path exclusive transactions or CPI Communications driven transaction programs.

The TRANSACTION parameter can be generic where the generic parameter specifies transactions that already exist.

Examples

Example 1 for /PSTOP Command

Entry ET:

  /PSTOP LINE 4 PTERM 1

Response ET:

  DFS058I  PSTOP COMMAND COMPLETED

Response RT:

  DFS059I  TERMINAL PSTOPPED

Explanation: LINE 4 PTERM 1 is not sent application program or message switch output and is not allowed to send input. Output messages for the terminal continue to be queued.

Example 2 for /PSTOP Command

Entry ET:

  /PSTOP LINE 4 6 200

Response ET:

  DFS058I  PSTOP COMMAND COMPLETED EXCEPT LINE 200

Explanation: LINE 4 and LINE 6 are not allowed to send or receive messages. Message queuing continues. Line 200 is an invalid line number.

Example 3 for /PSTOP Command

Entry ET:

  /PSTOP LINK 2 3 4

Response ET:

  DFS058I  PSTOP COMMAND COMPLETED

Response ET:

  DFS2169I  DISCONNECTION COMPLETED ON LINK 2

Explanation: Logical link 2 is disconnected. This message is received for each logical link that is disconnected.

Response Remote MT:

  DFS2161I  LINK 2 STOPPED BY PARTNER
  DFS2161I  LINK 3 STOPPED BY PARTNER
  DFS2161I  LINK 4 STOPPED BY PARTNER

Explanation: Logical links 2, 3, and 4 stop processing messages. Output queuing continues.

Response ET:

  DFS2169I  DISCONNECTION COMPLETED ON LINK 3

Explanation: Logical link 3 is disconnected. This message is also received when logical link 4 disconnects.

Example 4 for /PSTOP Command

Entry ET:

  /PSTOP LINK ALL

Response ET:

  DFS058I  PSTOP COMMAND COMPLETED

Response Remote MT:

  A DFS2161 LINK n STOPPED BY PARTNER message
  is received for each logical link that was
  operational when /PSTOP was entered.

Explanation: Output to all logical links stops. Output queuing continues. Input is not allowed.

Response ET:

  DFS2169I  DISCONNECTION COMPLETED ON LINK XXX

Explanation: As each logical link is disconnected, this message is received.

Example 5 for /PSTOP Command

Entry ET:

  /PSTOP LINK 1 2 3 PURGE

Response ET:

  DFS2272I PURGE KEYWORD INVALID, ONLY ONE
  CTC LINK ALLOWED

Explanation: Only one link can be specified with the PURGE keyword.

Example 6 for /PSTOP Command

Entry ET:

  /PSTOP LINK 2 PURGE

Response ET:

  DFS2273I PURGE KEYWORD REJECTED, CURRENT STATUS
  OF LINK IS NORMAL

Explanation: The partner system has not failed and the link appears to be working.

Example 7 for /PSTOP Command

Entry ET:

  /PSTOP LTERM APPLE, TREE

Response ET:

  DFS058I  PSTOP COMMAND COMPLETED

Response RT:

  DFS059I  TERMINAL PSTOPPED

Explanation: The physical terminals associated with logical terminals APPLE and TREE are not sent output that is destined for logical terminals APPLE or TREE, or allowed to enter input. Output queuing continues.

Example 8 for /PSTOP Command

Entry ET:

  /PSTOP MSPLINK ALL

Response ET:

  DFS058I  COMMAND COMPLETED

Explanation: All the VTAM physical links are stopped from receiving logons. Any links in session are not affected.

Example 9 for /PSTOP Command

Entry ET:

  /PSTOP TRANSACTION SEED

Response ET:

  DFS058I  PSTOP COMMAND COMPLETED

Explanation: Transaction code SEED can no longer be scheduled. Queuing of the transaction continues.

Example 10 for /PSTOP Command

Entry ET:

  /PSTOP TRANSACTION ALL CLASS 3

Response ET:

  DFS058I  PSTOP COMMAND COMPLETED

Explanation: All transactions associated with class 3 can no longer be scheduled. Queuing of the transactions continues.

Example 11 for /PSTOP Command

Entry ET:

  /PSTOP REGION 1 TRANSACTION XYZ

Response ET:

  DFS058I  PSTOP COMMAND IN PROGRESS

Response ET:

  DFS0569I PSTOP COMPLETE FOR REGION 1 TRAN XYZ
  DFS0566I PSTOP NOT VALID FOR TRAN XYZ

Explanation: If the DFS0569I message prints, processing of the transaction type, xyz, is stopped in message region 1. If the DFS0566I message prints, the command was ignored because the two required conditions were not satisfied.

Example 12 for /PSTOP Command

Entry ET:

  /PSTOP REGION 2 AOITOKEN AOITOK2

Response ET:

  DFS058I PSTOP COMMAND IN PROGRESS

Response MT:

  DFS0569I PSTOP OR STOP COMPLETE FOR REGION 2 AOIT AOITOK2.

Explanation: If the DFS0569I message prints, the AO application in region 2 waiting for a message for AOI token AOITOK2 is posted; the application receives AIB return code X'00000004' and reason code X'0000004C'.

Example 13 for /PSTOP Command

Entry ET:

  /PSTOP REGION 2 AOITOKEN  AOITOK2

Response ET:

   DFS058I PSTOP COMMAND IN PROGRESS

Response MTO:

   DFS1190I REGION 2 NOT WAITING ON AOITOKEN AOITOK2

Explanation: If the DFS1190I message prints, the command is ignored because region 2 was not waiting on AOI token AOITOK2.

Example 14 for /PSTOP Command

Entry ET:

  /DIS ACTIVE REG

Response ET:

  REGID JOBNAME   TYPE  TRAN/STEP PROGRAM  STATUS         CLASS
      1 MPP610C   TP    NQF1      PMVAPZ12 ACTIVE           1,  2,  3,  4
        BATCHREG  BMP   NONE
        FPRGN     FP    NONE
        DBTRGN    DBT   NONE
        DBRECTA9  DBRC
        DLIECTA9  DLS
        *96081/150611*
 

Explanation: Message processing program PMVAPZ12 is processing transaction NQF1. The job name of the region is MPP610C

Entry ET:

  /PSTOP REGION JOBNAME MPP610C TRAN NQF1

Response ET:

  DFS058I PSTOP COMMAND IN PROGRESS
  DFS0569I PSTOP OR STOP COMPLETE FOR REGION 00001 TRAN NQF1

Response ET:

  DFS058I PSTOP COMMAND IN PROGRESS
  DFS0566I PSTOP NOT VALID FOR TRAN NQF1

Explanation: If the DFS0569I message is displayed, processing if the transaction type, NQF1, is stopped in message region 1. If the DFS0566I message is displayed, the command was ignored because the two required conditions were not satisfied.

Go to the previous page Go to the next page

IBM Confidential

Downloads | Library | Support | Support Policy | Terms of use | Feedback
Copyright: IBM Corporation 1974, 2004 Copyright IBM Corporation 1974, 2004  timestamp Last updated: March, 2004