Command Line STA and STO Commands

You can start or stop databases from the command line of the COPE main screen by using the following commands:

For Fast-Path DEDB databases, substitute the word "AREA" for "DB".

COPE provides these commands mainly so that you can issue them via PF keys or batch programs. This is described in the BMC-COPE-Administration-Guide.

You start and stop transactions using the same set of screens as databases.

Enter COPE SS from a cleared screen, or just SS from the COPE screen, to get the selection screen (see the following figure).

COPE Online - Start/Stop Selection Screen (TR side)

Enter TR for TRansaction, against the DB/TR, and blank out the SYSTEM name to get a scrollable list of Lsys' (COPE Online - Database List Screen).

COPE Online - Start/Stop System List Screen (TR side)

Select an IMS system with an X, and press <Enter>. The following screen then appears (see the following figure).

COPE Online - Transaction List screen

Entering S or P against a Trancode starts or stops that transaction and its associated program. In the above example, transaction INVTRAN1 was previously stopped by an S0C7 abend. The S on the left-hand side is a command to start the transaction again, to make it available to all users. Note that the Description field of the stopped transaction contains the module name, PMAP offset, and abend code, for the abend which caused the transaction to stop.

COPE programs have the same status as the Trancode. When there are multiple Trancodes for one program, the program is started for started Trancodes and stopped for stopped ones.

The difference from Databases is that transactions will almost always be stopped by MPP abends, rather than by a user. Users start the transaction when they know the program has been fixed. Sometimes you will want to stop a transaction and leave an explanation. This is achieved in the same way as for databases. Use the 30-character User Name field on the first Start/Stop selection screen.

If your transaction is stopped by an MPP abend, normally the next thing you want to do (after fixing the application program) is to start the transaction. You can use SS screens to start it, or you can use the "Quick-Start" command:

This will start the transaction and program. Note there is no slash (/) and no TRAN keyword above.

Sometimes after issuing a STA Trancode, when you run the transaction, it is still stopped. This happens in situations where your abend was in a DLI call, and you are using dedicated (by Lsys) message regions. If this happens, just issue "STA Trancode" again, and after the second time you will find that the transaction is started. However, issuing STA trancode twice, without testing whether the Trancode was started between, will not protect you from this problem. The reason is that the intervening test transaction is needed by COPE to resynchronize the status. In other words, "if it is stopped, start it".

As with databases, groups of transactions may be pre-defined, for mass starting and stopping.

You can start or stop all transactions in an Lsys at once, from either the list of Lsys's, or from the initial selection screen (with the NAME field blank). This is referred to as "Start/Stop of a System, TR Side" and is further described in "System Start/Stop.<XREF>". You start or stop a system on the TR Side, if you need to either:

• Make the system unavailable, but do not want to deallocate all the databases.
• Deallocate the system's program load libraries.