•
•
•
•
•
• CRM [ -t 0|1|2|3 ] [-p<nbr>] [-s] [-n <type>:#:#] [-u <keyfile>] [-V] <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.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.
• 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.//host:port groupAPPDIR must be set to the application directory.Refer to the Oracle 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:When you start CRM from the UNIX command line, the following CRM Command Line Console appears:To launch CRM with the console running in the background:To launch CRM with detailed tracing and APPC Stack API tracing turned on from the command line using the host/port address, type: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:CRM name (default CRM)CRMLOGS exits with a return code of 0 upon successful completion.To display the RSTRTLOG log file for group2, type:To display the BLOBLOG log file for group1, type: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.Names the machine and port running the CRM server; indicates that the parameters immediately following are the hostname and port of the machine running the CRM where the linkname is located.Specifies verbose. Normally the command will not produce any messages, facilitating use in a script.Names the link to be started. This is the DM_SNALINKS entry in the DMCONFIG that defines this link. Multiple link names can be specified.Specifies the IP host name and port of the machine running the CRM where the linkname is located.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.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.Names the machine and port running the CRM server; indicates that the parameters immediately following are the hostname and port of the machine running the CRM where the linkname is located. This is required.Specifies verbose. Normally the command will not produce any messages, facilitating use in a script.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.Mandatory. Specifies the IP host name and port for the machine running the CRM. This is the value that was used on the CRM command line. For example, myhostmachine:5000.Optional. Specifies a key file containing the authentication name to be used with the CRM. For example, /secure/secret.key.To change the trace level to 2 (set medium CRM trace) by the CRM running on mach1 at port 5000, use the following command:crmchtr only checks the syntax of the command. If the command could not be successfully sent to the CRM, crmchtr prints an error message and exits with error code 1. Upon successful completion, crmchtr exits with exit code 0.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.Specifies verbose. Normally the command will not produce any messages, facilitating use in a script.To stop the CRM running on mach1 at port 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.