|
|
This section provides information about the commands an administrator uses to perform activities with the Communications Resource Manager (CRM) to maintain BEA Tuxedo Mainframe Adapter for SNA applications. These commands work using JCL on z/OS MVS.
This section discusses the following commands:
Launches the Communications Resource Manager.
CRM [ -t 0|1|2|3 ] [-p<nbr>] [-s] [-n <type>:#:#] [-u <keyfile>] <addr> <group>When you start CRM from the command line, the CRM Command Line Console puts its prompt in the window and, if exited, shuts down all of the active links.
You must configure one CRM for each Tuxedo Mainframe Adapter for SNA Gateway, as well as configure one stack for each CRM definition. Each stack can manage one or more SNA links.
CRM has two types of log files stored in $APPDIR, RSTRTLOG, and BLOBLOG. RSTRTLOG is the transaction state log used during the recovery process, while the BLOBLOG log stores session and link information. Deleting the log files requires a cold start for each link involved. You can use the CRMLOGS command to display the contents and state of the CRM log files.
When initiating the CRM from the UNIX command line, you can specify any of the following CRM trace levels using the -t option:
0 = No tracing. Setting this level effectively disables CRM tracing and closes the trace file, if there is one. If tracing is subsequently restarted, a new file is created with an incremented numerical suffix.1 = Minimum tracing. At this level, CRM traces only major events and is sufficient only to determine the sequence of application conversations.2 = Medium tracing. At this level, CRM also traces all I/O buffers.3 = Maximum tracing. At this level, CRM also traces all APPC verbs.
The APPC Stack API trace is either enabled or disabled using the -s option of the CRM command (refer to “General Options”). If enabled, it generally shows the parameters and results of all API calls. Depending on the stack being used, other options (such as vendor-specified environment variables) may have to be activated for CRM to enable the trace.
| Note: | The time tag information in the CRM trace should reflect the current system time. In order to make use of the correct time zone information on UNIX and MVS systems, it is important that the TZ environment variable be set correctly. If this variable is not set correctly on your system, refer to your system documentation for further information. |
Establishes that process authentication is in effect for communications between the CRM and a client process.
Is the location of a file containing a hash key known to both the CRM and the client process. The file contains a single line specifying a unique hash key (limited to eight characters). The file should be protected.
Establishes that encryption is in effect for this process.
Is the encryption type. Currently, the only valid entry is GPE (for general purpose encryption).
Designates the minimum number of bits to be used for encryption. These levels are used during the negotiation between the CRM and client process. Any number is acceptable, but the negotiated values resolve to 0, 56, or 128.
Designates the maximum number of bits to be used for encryption. These levels are used during the negotiation between the CRM and client process. Any number is acceptable, but the negotiated values resolve to 0, 56, or 128
The following parameters apply to this command:
-s
addr
You must set the following environment variables before starting the CRM:
Refer to the BEA Tuxedo Mainframe Adapter for SNA Release Notes for a list of operating systems and stacks that can communicate with the CRM.
CRM exits with a return code of 0 upon successful completion.
Following is an example of the CRM command:
CRM -t 0 //myhost:5587 GROUP2 /dev/null>std.out 2>std.err &
When you start CRM from the UNIX command line, the following CRM Command Line Console appears:
$ CRM -t 0 //myhost:5587 GROUP2
BEA Tuxedo Mainframe Adapter for SNA Resource Manager started Thu Dec 11
18:40:49.098 1997
[CRM]
Console active. Enter commands
?>
da => Display active tasks
dl => Display remote links
ds => Display link statistics
dt => Display trace status
st => Start all links
sh => Stop all links and terminate
si => Terminate immediately (no quiesce)
To launch CRM with the console running in the background:
$ CRM -t 0 //myhost:5587 GROUP2 <dev/null>std.out 2>std.err &
To launch CRM with detailed tracing and APPC Stack API tracing turned on from the command line using the host/port address, type:
CRM -t 2 -s //myhost:5587
Displays the content and state of the BEA Tuxedo Mainframe Adapter for SNA Communications Resource Manager (CRM) log files in the current directory.
CRMLOGS <group> [<crm name>]
Use the CRMLOGS command to display the contents and state of the two CRM log files. RSTRTLOG is the transaction state log used during the recovery process and the BLOBLOG log stores session and link information. Deleting the log files requires a cold start for each link involved.
CRMLOGS requires the following parameters:
CRMLOGS exits with a return code of 0 upon successful completion.
To display the RSTRTLOG log file for group2, type:
CRMLOGS GROUP2 CRM.GROUP2.RSTRTLOG
To display the BLOBLOG log file for group1, type:
CRMLOGS GROUP1 CRM.GROUP1.BLOBLOG
Start one or more named CRM links.
crmlkon -n<hostname:port> [-v -i -h -u<keyfile>] <linkname> ...
crmlkon starts all of the CRM links named on the command line. This command is useful if one or more individual links failed to start when the CRM server booted. Use this command from any machine located on the same TCP/IP network as the machine running the CRM server. When used in a script, crmlkon will return 0 if the command could be sent to the target CRM. It will return 1 if the command could not be sent to the target CRM.
-n
hostname and port of the machine running the CRM where the linkname is located.
-v
-i
-u
<keyfile>
<linkname>
DMCONFIG that defines this link. Multiple link names can be specified.
<hostname:port>
h
To start links link2 and cicstest owned by the CRM running on mach1 at port 5000:
crmlkon -n mach1:5000 link2 cicstest
crmlkon only checks the syntax of the command. Separate facilities, either jsnacrm or mainframe-based facilities must be used to determine if the link actually became active. If the command could not be successfully sent to the CRM, crmlkon prints an error message if in verbose mode and exits with error code 1. Upon successful completion, crmlkon exits with exit code 0.
Stop one or more named CRM links.
crmlkoff -n<hostname:port> [-v -i -h -u<keyfile>] <linkname> ...
crmlkoff stops all of the CRM links named on the command line. This is useful if one or more individual links need to be stopped after the CRM server booted. It can be used from any machine located on the same TCP/IP network as the machine running the CRM server. It can be used in a script and will return 0 if the command could be sent to the target CRM. It will return 1 if the command could not be sent to the target CRM.
-n
hostname and port of the machine running the CRM where the linkname is located. This is required.
-v
-i
-u
<keyfile>
<linkname>
h
To stop links link1 and cicstest owned by the CRM running on mach at port 5000:
crmlkoff -n mach:5000 link1 cicstest
crmlkoff only checks the syntax of the command. Separate facilities, either jsnacrm or mainframe based facilities, must be used to determine if the link actually became inactive. If the command could not be successfully sent to the CRM, crmlkoff prints an error message if in verbose mode and exits with error code 1. Upon successful completion, crmlkoff exits with exit code 0.
crmdown -n<hostname:port> [-v -i -h -u<keyfile>]
crmdown shuts down the CRM specified on the command line. It can be used from any machine located on the same TCP/IP network as the machine running the CRM server. It can be used in a script and will return 0 if the command could be sent to the target CRM. It will return 1 if the command could not be sent to the target CRM.
-n
-v
-i
-u
<keyfile>
To stop the CRM running on mach1 at port 5000:
crmdown -n mach1:5000
crmdown only checks the syntax of the command. If the command could not be successfully sent to the CRM, crmdown prints an error message if in verbose mode and exits with error code 1. Upon successful completion, crmdown exits with exit code 0.
|