CRM Administration

The CRM establishes and monitors communication links between the WebLogic JAM Gateway and mainframe systems, such as CICS, IMS, and batch. The CRM also provides support for the coordination of transactional resources using the two-phase commit protocol. For more information about how the CRM functions within WebLogic JAM, see WebLogic JAM Architecture.

With WebLogic JAM, you may administer and run the CRM in two environments: an environment or a z/OS or OS/390 Unix environment. This section provides information and steps for administering the CRM in both environments.

This section provides information on the following subjects:

• Starting the CRM

• Stopping the CRM

• Activating and De-Activating CRM Links

• CRM Console Commands

 

---

Starting the CRM

The CRM command launches the Communications Resource Manager. You can start the CRM from either a z/OS or OS/390 MVS or z/OS or OS/390 Unix platform. The CRM may be started from the command line or from a shell script. You can enter the CRM command from a Unix command line or you may also use JCL on a z/OS or OS/390 MVS platform to run the CRM. Sample JCL is included with your WebLogic JAM installation.

To start the CRM:

1. Determine the required arguments for the CRM command as shown in Table  7-1.

   Table 7-1 Arguments for the CRM command

   Keyword	Default	Optional/ Required	Description
   <hostname>: <port>	None	Required	The machine name or dotted-IP address and port number (//hostname:port) of the machine where the CRM is running.
   <crm name>	None	Required	The name of the CRM configured in the WebLogic JAM configuration.
   -t [0|1|2|3]	0	Optional	Sets the level of tracing. 0=No tracing. Setting this level effectively disables CRM tracing. 1=Minimum tracing. At this level, the CRM traces only major events and is sufficient only to determine the sequence of application conversations. 2=Medium tracing. At this level, the CRM also traces all APPC verbs and the communication between the WebLogic JAM Gateway and the CRM. 3=Maximum tracing. At this level, the CRM also traces all I/O buffers.
   -s	disabled (if not present)	Optional	Turns on APPC Stack API traces.
   -p <nbr>	100 threads	Optional	Turns on the performance option and indicates the number of threads used to service requests. This value should correspond to the load of SNA requests that will be made concurrently across a CRM and all of its links. If the number of requests exceeds the number of threads, the request is still executed; however, the completion time could be affected. Do not exceed 200 threads. The CRM is tuned for a maximum of 200 threads. Lower the threads value if you have a restriction on the number of threads that can be active in your system.

   
    

2. Follow the instructions for either:

• Starting the CRM in an MVS Environment

or

• Starting CRM in z/OS or OS/390 Unix Environment

Setting CRM Trace Level at CRM Startup

The CRM trace option can be enabled by using the -t option. For example, for full tracing:

CRM -t3 //myhost:7011 CRMB

The list in Table  7-1describes the three levels of tracing that can be set, and the functionality corresponding to each level.

On z/OS or OS/390 Unix systems, traces are written to a file in the directory in which the CRM was started. If the environment variable SNACRMWORKDIR is set, the trace is written to the directory it specifies. The file name is specified as:

CRM.<pid>.trace.<seq>

Where <pid> is the process ID of the CRM process, and <seq> is the sequence number of the trace file, which is always 0.

On MVS systems, traces are written to the file identified by DD:TRACE.

Note: Trace options for the CRM may also be set from the WebLogic Administration Console. See Modifying CRM Trace Level Settings for more information about setting trace options from the WebLogic Administration Console.

Setting APPC API Tracing at Startup

You can capture the VTAM APPC API by enabling the APPC API tracing. The API trace shows the parameters and values passed and returned to the VTAM APPC stack. The API trace is captured to the GTF tracing facility. The GTF tracing facility must be active in the mainframe region to capture the API traces.

The CRM APPC API trace option can be enabled by using the -s option. For example:

CRM -s //myhost:7011 CRMB

After capturing the traces, you must format the print using GTF formatting procedures such as IPCS. The APPC API trace is written to GTF as user ID 2EA. You may use this ID to filter the GTF print to include only the APPC API traces.

Note: Trace options for the CRM may also be set from the WebLogic Administration Console. See Setting APPC API Tracing in the WebLogic Administration Console for more information about setting trace options from the WebLogic Administration Console.

Starting the CRM in an MVS Environment

To start the CRM in an MVS environment, you use JCL. A JCL sample is included with your WebLogic JAM installation in member CRMSTART.

To start the CRM, follow these steps:

1. Set the following environment variable in the environment where the CRM is started. For each running CRM, you must have a unique APPDIR set. For MVS, the APPDIR is the high-level qualifier for the data sets created by the CRM. A sample ENV file is delivered in the DATA library. For each concurrently running CRM, you must have a unique ENV file.

   APPDIR=<High level qualifier for data sets to be created in APPDIR>

2. Use the set commands shown in Table  7-2 to customize the sample JCL.

   Table 7-2 JCL set Commands for the Sample CRMSTART

   Command Name	Description
   SET STARTCMD	Sets the CRM command line parameters. For example: '-t3 "//<hostname>:<port>" <crm name>'
   SET OBJLIB	Indicates the name of the PDSE library where the CRM executable is installed.
   SET DATA	Indicates the data set containing the ENVFILE.
   SET ENVFILE	Indicates the name of the PDS member that contains the environment variables for the CRM. A sample member, ENV, is delivered with your product.
   SET SIZE	Defines the region size for the running CRM task. The recommended setting for this option is 0M to allow the CRM to start up and level out to the size it requires.
   SET ENV	Indicates the ENVFILE DD name. This value is pre-set.
   SET RUNOPTS	Specifies the optional runtime operands for the Language Environment (LE). This is usually used for debugging. See your system administrator for more information if this option is used.
   SET CEE	Specifies the high-level qualifier for the LE runtime library. Language Environment is required to run the CRM. Note: Uncomment the SET CEE line and tailor the STEPLIB concatenation if these libraries are not in your system link library concatenation.
   SET CBC	Specifies the high-level qualifier for the C/C++ runtime library. Note: Uncomment the SET CBC line and tailor the STEPLIB concatenation if these libraries are not in your system link library concatenation.

   
    

3. Run a crmstart job using JCL written for your system. Listing  7-1 shows a JCL for the crmstart command.

Listing 7-1 Sample JCL for the CRM Command

//***************************************************************
//* THIS JOB IS USED TO RUN THE CRM PROCESS.                     *
//*                                                               *
//* @(#)$Id: crmstart.jcl,v 1.3 2001/05/07 23:41:27 jsmith Exp $
//* Copyright (c)2000 BEA Systems, Inc., all rights reserved.     *
//***************************************************************
//*  YOU MUST SET THE ENVIRONMENT VARIABLES NEEDED BY CRM         *
//***************************************************************
//***************************************************************
//*  USE THE SET STATEMENTS TO SET THE APPROPRIATE VALUES         *
//*  STARTCMD IS THE CRM COMMAND LINE                             *
//*  OBJLIB IS THE LOAD LIBRARY CONTAINING THE PROGRAM EXECUTABLES*
//*  DATA IS THE DATASET THAT CONTAINS THE ENVIRONMENT VARIABLES  *
//*  ENVFILE NAMES THE MEMBER THAT CONTAINS THE ENVIRONMENT VARS  *
//*  RUNOPTS SETS ANY DESIRED LE RUNTIME OPTIONS (OPTIONAL)       *
//*  SIZE SETS THE REGION SIZE FOR THE CRM PROCESS. 0M SETS NO   *
//*       LIMITS ON THE REGION SIZE                               *
//*  TAILOR YOUR JCL FOR THE BELOW IF THESE LIBRARIES ARE NOT     *
//*  IN YOUR SYSTEM LINK LOAD LIBRARY CONCATENATION               *
//*  CEE IS THE HLQ FOR THE LE RUNTIME LIBRARY                    *
//*  CBC IS THE HLQ FOR THE C/C++ RUNTIME LIBRARY                 *
//***************************************************************
//  SET STARTCMD='"//<hostname>:<port>" <crm name>'
//  SET OBJLIB=
//  SET DATA=
//  SET ENVFILE=ENV
//  SET RUNOPTS=
//  SET SIZE=0M
//  SET ENV='ENVAR("_CEE_ENVFILE=DD:ENV")'
//* SET CEE=CEE,CBC=CBC
//CRM      EXEC  PGM=CRM,REGION=&SIZE,
//  PARM='POSIX(ON) &ENV &RUNOPTS/&STARTCMD'
//STEPLIB  DD  DSN=&OBJLIB,DISP=SHR
//*        DD  DSN=&CEE..SCEERUN,DISP=SHR
//*        DD  DSN=&CBC..SCLBDLL,DISP=SHR
//MSGFILE  DD  SYSOUT=*
//TRACE    DD  SYSOUT=*
//SYSPRINT DD  SYSOUT=*
//ENV      DD  DSN=&DATA(&ENVFILE),DISP=SHR
//                                           

Starting CRM in z/OS or OS/390 Unix Environment

You may start the CRM in either console mode or as a background task. In console mode you may interact with the console to perform or monitor different tasks. In background mode, you must use the CRMDOWN command to stop the CRM. This task is described in Stopping the CRM in a z/OS or OS/390 Unix Environment. You must also disable the interactive dialog from STDIN.

When you start the CRM in z/OS or OS/390 Unix environment, the CRM command line console prompt displays. You may choose to start the CRM in background mode, in which case, no console prompt displays.

To start the CRM in z/OS or OS/390 Unix:

1. Set the following environment variables in the environment where the CRM is started.

   • PATH - the PATH variable must be modified to include the bin subdirectory of your CRM installation directory.

   • LIBPATH - the LIBPATH variable must be modified to include the lib subdirectory of your CRM installation directory.

   • APPDIR must be set to the application directory. For Unix, the APPDIR indicates the directory for the files created by the CRM.

   A sample file, uss.env, is delivered with the installation of WebLogic JAM.

   For example, if you installed the CRM into the directory /work/bea/crm, the following commands will set your PATH and LIBPATH variables appropriately:

   export PATH=$PATH: /work/bea/crm/bin
   export LIBPATH=$PATH:	/work/bea/crm/lib
   export APPDIR=/home/bea/jam

2. Enter the CRM command with your required option arguments on the command line. The CRM command and optional arguments follows:

CRM [ -t 0|1|2|3 ]  [-s] [-p <nbr>] <hostname>:<port> <crm name>

For example: To start the CRM running on the machine myhost listening on port 5587 with the CRM name of MYCRM, enter the following on the command line. This example disables standard input, pipes the std.out and std.err to files, and runs in background mode rather than console mode. The STDIN capability is disabled by piping from the /dev/null directory.

$ CRM //myhost:5587 MYCRM </dev/null >std.out 2>std.err &

 

---

Stopping the CRM

The crmdown command shuts down a CRM. You must explicitly shut down the CRM if the WebLogic JAM Gateway is stopped and the CRM needs to be stopped. You can stop the CRM in a z/OS or OS/390 MVS environment or in a z/OS or OS/390 Unix environment.

To stop the CRM:

1. Determine the required arguments for the crmdown command as shown in Table  7-3.

   Table 7-3 Command Line Options for crmdown

   Keyword	Default	Optional/ Required	Description
   -n<hostname>: <port>	None	Required	The machine name or dotted-IP address and port number (//hostname:port) of the machine where the CRM is running.
   -v	Off	Optional	Specifies verbose. Normally the command will not produce extraneous messages, facilitating use in a script.
   -i	Off	Optional	Ignores errors.

   
    

2. Follow the instructions for either:

• Stopping the CRM in an MVS Environment

or

• Stopping the CRM in a z/OS or OS/390 Unix Environment

Stopping the CRM in an MVS Environment

To stop the CRM in an MVS environment, you use JCL. A JCL sample, CRMDOWN, is included with your WebLogic JAM installation.

1. Use the set commands shown in Table  7-4 to customize the sample JCL.

   Table 7-4 JCL set Commands for the Sample CRMDOWN

   Command Name	Description
   SET STOPCMD	Sets the crmdown command line parameters.
   SET OBJLIB	Indicates the name of the PDSE library where the crmdown executable is installed.
   SET DATA	Indicates the data set containing the ENVFILE.
   SET ENVFILE	Indicates the name of the PDS member that contains the environment variables for the crmdown. A sample member, ENV, is delivered with your product.
   SET SIZE	Defines the region size for the running crmdown task.
   SET RUNOPTS	Specifies the optional runtime operands for the Language Environment (LE). This is usually used for debugging. See your system administrator for more information to use these options.
   SET ENV	Indicates the ENVFILE DD name.
   SET CEE	Specifies the high-level qualifier for the LE runtime library. Language Environment is required to run the CRM. Note: Uncomment the SET CEE line and tailor the STEPLIB concatenation if these libraries are not in your system link library concatenation.
   SET CBC	Specifies the high-level qualifier for the C/C++ runtime library. Note: Uncomment the SET CBC line and tailor the STEPLIB concatenation if these libraries are not in your system link library concatenation.

   
    

2. Shut down the CRM using JCL written for your system. Listing  7-2 shows a JCL for the crmdown command.

Listing 7-2 Sample JCL for crmdown Command

//***************************************************************
//*  THIS JOB IS USED FOR THE STAND-ALONE COMMAND USED            *
//*  TO SHUTDOWN THE CRM PROCESS.                                *
//*                                                               *
//* @(#)$Id: crmdown.jcl,v 1.5 2001/05/07 23:41:27 crount Exp $
//* Copyright (c)2000 BEA Systems, Inc., all rights reserved.     *
//***************************************************************
//*  YOU MUST SET THE ENVIRONMENT VARIABLES NEEDED BY CRMDOWN     *
//***************************************************************
//*****************************************************************
//*  STOPCMD INDICATES THE COMMAND LINE FOR CRMDOWN               *
//*  OBJLIB IS THE LOAD LIBRARY CONTAINING THE PROGRAM EXECUTABLES*
//*  RUNOPTS SETS ANY DESIRED LE RUNTIME OPTIONS (OPTIONAL)       *
//*  DATA IS THE DATASET THAT CONTAINS THE ENVIRONMENT VARIABLES  *
//*  ENVFILE NAMES THE MEMBER THAT CONTAINS THE ENVIRONMENT VARS  *
//*  SIZE SETS THE REGION SIZE FOR THE CRM PROCESS                *
//*                                                               *
//*  TAILOR YOUR JCL FOR THE BELOW IF THESE LIBRARIES ARE NOT     *
//*  IN YOUR SYSTEM LINK LOAD LIBRARY CONCATENATION               *
//*  CEE IS THE HLQ FOR THE LE RUNTIME LIBRARY                    *
//*  CBC IS THE HLQ FOR THE C/C++ RUNTIME LIBRARY                 *
//***************************************************************
//  SET STOPCMD='-n<host name>:<port>'
//  SET OBJLIB=
//  SET RUNOPTS=
//  SET DATA=
//  SET ENVFILE=ENV
//  SET SIZE=1M
//  SET ENV='ENVAR("_CEE_ENVFILE=DD:ENV")'
//* SET CEE=CEE,CBC=CBC
//CRMDOWN  EXEC  PGM=CRMDOWN,REGION=&SIZE,
//  PARM='POSIX(ON) &ENV &RUNOPTS/&STOPCMD'
//STEPLIB  DD  DSN=&OBJLIB,DISP=SHR
//*        DD  DSN=&CEE..SCEERUN,DISP=SHR
//*        DD  DSN=&CBC..SCLBDLL,DISP=SHR
//ENV      DD  DSN=&DATA(&ENVFILE),DISP=SHR
//MSGFILE  DD  SYSOUT=*
//SYSPRINT DD  SYSOUT=*
//

Stopping the CRM in a z/OS or OS/390 Unix Environment

You can stop the CRM in a z/OS or OS/390 Unix environment by running crmdown from a command line. If the command could not be successfully sent to the CRM, crmdown prints an error message and exits with error code 1. Upon successful completion, crmdown exits with exit code 0.

To stop the CRM from a command line:

1. Enter the crmdown command with your required option arguments on the command line.

For example: To stop the CRM running on mach1 at port 5000:

crmdown -n mach1:5000

 

---

Activating and De-Activating CRM Links

The crmlkon and crmlkoff commands are used to activate or de-activate CRM links. You can activate and de-activate links from either a z/OS or OS/390 MVS or z/OS or OS/390 Unix platform

Note: You can also start and stop a CRM link from the WebLogic Administration Console. For instructions, see Modifying CRM Link Definitions.

This section provides information on the following subjects:

• Activating CRM Links

• De-Activating CRM Links

Activating CRM Links

The crmlkon command is responsible for activating CRM links. You can activate CRM links in the z/OS or OS/390 MVS environment or the z/OS or OS/390 Unix environment. This is useful if one or more individual links needs to be restarted after the CRM is connected.

To activate CRM links in any environment:

1. Determine the required arguments for the crmlkon command as shown in Table  7-5.

   Table 7-5 Command Line Options for crmlkon

   Keyword	Default	Optional/ Required	Description
   -n<hostname>: <port>	None	Required	The machine name or dotted-IP address and port number (//hostname:port) of the machine where the CRM is running.
   <linkname>	None	Required	Names the link or links to be started. Use a space to separate multiple link names.
   -v	Off	Optional	Specifies verbose. Normally the command will not produce extraneous messages, facilitating use in a script.
   -i	Off	Optional	Ignores errors. When specifying multiple links, any error encountered when issuing CRM commands causes crmlkon to stop processing links and return. This allows errors to be ignored for individual links and processing continues with the next named link.

   
    

2. Follow the instructions for either:

• Activating CRM Links in an MVS Environment

or

• Activating CRM Links from a z/OS or OS/390Unix Environment

Activating CRM Links in an MVS Environment

To activate CRM links in an MVS environment, you use JCL. A JCL sample, crmlkon, is included with your WebLogic JAM installation. Refer to your system administrator for more information about your particular setup.

To activate CRM links in an MVS environment, follow these steps:

1. Use the set commands shown in Table  7-6 to customize the sample JCL.

   Table 7-6 JCL set Commands for the Sample CRMLKON

   Command Name	Description
   SET LINKCMD	Sets the crmlkon command line parameters.
   SET OBJLIB	Indicates the name of the PDSE library where the crmlkon executable is installed.
   SET DATA	Indicates the data set containing the ENVFILE.
   SET ENVFILE	Indicates the name of the PDS member that contains the environment variables for the CRMLKON. A member, ENV, is delivered with your product.
   SET SIZE	Defines the region size for the running crmlkon task.
   SET ENV	Indicates the ENVFILE DD name. This value is pre-set.
   SET RUNOPTS	Specifies the optional runtime operands for the Language Environment (LE). This is usually used for debugging. See your system administrator for more information.
   SET CEE	Specifies the high-level qualifier for the LE runtime library. Language Environment is required to run the CRM. Note: Uncomment the SET CEE line and tailor the STEPLIB concatenation if these libraries are not in your system link library concatenation.
   SET CBC	Specifies the high-level qualifier for the C/C++ run-time library. Note: Uncomment the SET CBC line and tailor the STEPLIB concatenation if these libraries are not in your system link library concatenation.

   
    

2. Run a crmlkon job using JCL written explicitly for your system. Listing  7-3 shows a JCL for the crmlkon command.

Listing 7-3 Sample JCL for crmlkon Command

//*****************************************************************
//*  THIS JOB IS USED FOR THE STAND-ALONE LINK COMMAND            *
//*  TO ACTIVATE A REMOTE LINK.                                  *
//*                                                               *
//* @(#)$Id: crmlkon.jcl,v 1.10 2001/05/07 23:41:27 crount Exp $
//* Copyright (c)2000 BEA Systems, Inc., all rights reserved.     *
//***************************************************************
//*  YOU MUST SET THE ENVIRONMENT VARIABLES NEEDED BY CRMLKON     *
//***************************************************************
//***************************************************************
//*  LINKCMD INDICATES THE DISTRIBUTED CRM ADDRESS AND LINKNAME   *
//*  OBJLIB IS THE LOAD LIBRARY CONTAINING THE EAM PROGRAM OBJECTS*
//*  RUNOPTS SETS ANY DESIRED LE RUNTIME OPTIONS                  *
//*  DATA IS THE DATASET THAT CONTAINS THE ENVIRONMENT VARIABLES  *
//*  ENVFILE NAMES THE MEMBER THAT CONTAINS THE ENVIRONMENT VARS  *
//*  SIZE SETS THE REGION SIZE FOR THE CRM PROCESS                *
//*  TAILOR YOUR JCL FOR THE BELOW IF THESE LIBRARIES ARE NOT     *
//*  IN YOUR SYSTEM LINK LOAD LIBRARY CONCATENATION               *
//*  CEE IS THE HLQ FOR THE LE RUNTIME LIBRARY                    *
//*  CBC IS THE HLQ FOR THE C/C++ RUNTIME LIBRARY                 *
//***************************************************************
//  SET LINKCMD='-n<host name>:<port> <linkname>'
//  SET OBJLIB=
//  SET RUNOPTS=
//  SET DATA=
//  SET ENVFILE=ENV
//  SET SIZE=1M
//  SET ENV='ENVAR("_CEE_ENVFILE=DD:ENV")'
//* SET CEE=CEE,CBC=CBC
//CRMLKON  EXEC  PGM=CRMLKON,REGION=&SIZE,
//  PARM='POSIX(ON) &ENV &RUNOPTS/&LINKCMD'
//STEPLIB  DD  DSN=&OBJLIB,DISP=SHR
//*        DD  DSN=&CEE..SCEERUN,DISP=SHR
//*        DD  DSN=&CBC..SCLBDLL,DISP=SHR
//ENV      DD  DSN=&DATA(&ENVFILE),DISP=SHR
//MSGFILE  DD  SYSOUT=*
//SYSPRINT DD  SYSOUT=*

//

Activating CRM Links from a z/OS or OS/390Unix Environment

The crmlkon command starts all of the CRM links named on the command line. If the command could not be successfully sent to the CRM, crmlkon prints an error message and exits with error code 1. Upon successful completion, crmlkon exits with exit code 0.

To activate CRM links from a Unix command line:

1. Enter the crmlkon command with your required option arguments.

For example, to start links, link2 and cicstest, owned by the CRM running on mach1 at port 5000:

crmlkon -n mach1:5000 link2 cicstest

De-Activating CRM Links

The crmlkoff command is responsible for de-activating CRM links. You can de-activate CRM links in the z/OS or OS/390 MVS environment or the z/OS or OS/390 Unix environment. This is useful if one or more individual links needs to be stopped after the CRM is connected.

To de-activate CRM links in any environment:

1. Determine the required arguments for the crmlkoff command as shown in Table  7-7.

   Table 7-7 Command Line Options for crmlkoff

   Keyword	Default	Optional/ Required	Description
   -n<hostname>: <port>	None	Required	The machine name or dotted-IP address and port number (//hostname:port) of the machine where the CRM is running.
   <linkname>	None	Required	Names the link or links to be started. Use a space to separate multiple link names.
   -v	Off	Optional	Specifies verbose. Normally the command will not produce extraneous messages, facilitating use in a script.
   -i	Off	Optional	Ignores errors. When specifying multiple links, any error encountered when issuing CRM commands causes crmlkon to stop processing links and return. Errors can be ignored for individual links and processing continues with the next named link

   
    

2. Follow the instructions for either:

• De-Activating a CRM Link in an MVS Environment

or

• De-Activating a CRM Link in a z/OS or OS/390 Unix Environment

De-Activating a CRM Link in an MVS Environment

To de-activate CRM links in an MVS environment, you use JCL. A JCL sample, crmlkoff, is included with your WebLogic JAM installation.

1. Use the set commands shown in Table  7-8 to customize the sample JCL.

   Table 7-8 JCL set Commands for the Sample CRMLKOFF

   Command Name	Description
   SET LINKCMD	Sets the crmlkoff command line parameters.
   SET OBJLIB	Indicates the name of the PDSE library where the crmlkoff executable is installed.
   SET RUNOPTS	Specifies the optional runtime operands for the Language Environment (LE). This is usually used for debugging. See your system administrator for more information if using these options.
   SET DATA	Indicates the data set containing the ENVFILE.
   SET ENVFILE	Indicates the name of the PDS member that contains the environment variables for the crmlkoff. A member, ENV, is delivered with your product.
   SET SIZE	Defines the region size for the running crmlkoff task.
   SET ENV	Indicates the ENVFILE DD name.This value is pre-set.
   SET CEE	Specifies the high-level qualifier for the LE runtime library. Language Environment is required to run the CRM. Note: Uncomment the SET CEE line and tailor the STEPLIB concatenation if these libraries are not in your system link library concatenation.
   SET CBC	Specifies the high-level qualifier for the C/C++ run-time library. Note: Uncomment the SET CBC line and tailor the STEPLIB concatenation if these libraries are not in your system link library concatenation.

   
    

2. De-activate a CRM link using JCL written explicitly for your system. Listing  7-4 shows a sample JCL for the crmlkoff command.

Listing 7-4 Sample JCL for crmlkoff Command

//***************************************************************//*  THIS JOB IS USED FOR THE STAND-ALONE LINK COMMAND            *
//*  TO DEACTIVATE A REMOTE LINK.                                *
//*                                                               *
//* @(#)$Id: crmlkoff.jcl,v 1.10 2001/05/07 23:41:27 crount Exp $
//* Copyright (c)2000 BEA Systems, Inc., all rights reserved.     *
//***************************************************************//*  YOU MUST SET THE ENVIRONMENT VARIABLES NEEDED BY CRMLKOFF    *
//***************************************************************//***************************************************************//*  LINKCMD INDICATES THE DISTRIBUTED CRM ADDRESS AND LINKNAME   *
//*  OBJLIB IS THE LOAD LIBRARY CONTAINING THE EAM PROGRAM OBJECTS*
//*  RUNOPTS SETS ANY DESIRED LE RUNTIME OPTIONS                  *
//*  DATA IS THE DATASET THAT CONTAINS THE ENVIRONMENT VARIABLES  *
//*  ENVFILE NAMES THE MEMBER THAT CONTAINS THE ENVIRONMENT VARS  *
//*  SIZE SETS THE REGION SIZE FOR THE CRM PROCESS                *
//*  TAILOR YOUR JCL FOR THE BELOW IF THESE LIBRARIES ARE NOT     *
//*  IN YOUR SYSTEM LINK LOAD LIBRARY CONCATENATION               *
//*  CEE IS THE HLQ FOR THE LE RUNTIME LIBRARY                    *
//*  CBC IS THE HLQ FOR THE C/C++ RUNTIME LIBRARY                 *
//***************************************************************//  SET LINKCMD='-n<host name>:<port> <linkname>'
//  SET OBJLIB=
//  SET RUNOPTS=
//  SET DATA=
//  SET ENVFILE=ENV
//  SET SIZE=1M
//  SET ENV='ENVAR("_CEE_ENVFILE=DD:ENV")'
//* SET CEE=CEE,CBC=CBC
//CRMLKOFF EXEC  PGM=CRMLKOFF,REGION=&SIZE,
//  PARM='POSIX(ON) &ENV &RUNOPTS/&LINKCMD'
//STEPLIB  DD  DSN=&OBJLIB,DISP=SHR
//*        DD  DSN=&CEE..SCEERUN,DISP=SHR
//*        DD  DSN=&CBC..SCLBDLL,DISP=SHR
//ENV      DD  DSN=&DATA(&ENVFILE),DISP=SHR
//MSGFILE  DD  SYSOUT=*
//SYSPRINT DD  SYSOUT=*
//

De-Activating a CRM Link in a z/OS or OS/390 Unix Environment

The crmlkoff command stops all of the CRM links named on the command line. If the command could not be successfully sent to the CRM, crmlkoff prints an error message and exits with error code 1. Upon successful completion, crmlkoff exits with exit code 0.

To de-activate CRM links from a Unix command line:

1. Enter the crmlkoff command with your required option arguments.

For example: To stop links link1 and cicstest owned by the CRM running on mach at port 5000:

crmlkoff -n mach:5000 link1 cicstest

 

---

CRM Console Commands

When you run the CRM from the z/OS or OS/390 Unix command line, you are presented with a CRM prompt. Table  7-9 lists the commands the you can enter at the CRM prompt and the tasks to perform. Some of the functionality for these commands is also available from the WebLogic Administration Console. For these cases, the corresponding location in the WebLogic Administration Console is provided.

Table 7-9 CRM Commands and Corresponding WebLogic Administration Console Functions

CRM Console Commands	CRM Task	WebLogic Administration Console Location
DA	Display All Tasks	None
DL	Display Link Status	JAM —>CRM —><CRM Name > —>CRM Links
DS	Display Link Statistics	JAM —>CRM —><CRM Name > —>CRM Links —> <CRM Link Name>
DT	Display Trace Status	JAM —>CRM —><CRM Name > —>Administration Tab —> Diagnostics Tab
LS	Stop Link(s)	JAM —>CRM —><CRM Name > —>Administration Tab —> Start/Stop Tab
SL	Start Link(s)	JAM —>CRM —><CRM Name > —>Administration Tab —> Start/Stop Tab
ST	Start All Links	JAM —>CRM —><CRM Name > —>Administration Tab —> Start/Stop Tab
SH	Shutdown (normal)	None
SI	Shutdown Immediate	None
DC	Disconnect	None
DF	Display Flags	JAM —>CRM —><CRM Name > —>Administration Tab —> Start/Stop Tab
AY	Enable APPC Trace	JAM —>CRM —><CRM Name > —>Administration Tab —> Diagnostics Tab
AN	Disable APPC Trace	JAM —>CRM —><CRM Name > —>Administration Tab —> Diagnostics Tab
T0	Set Trace Level to 0	JAM —>CRM —><CRM Name > —>Administration Tab —> Diagnostics Tab
T1	Set Trace Level to 1	JAM —>CRM —><CRM Name > —>Administration Tab —> Diagnostics Tab
T2	Set Trace Level to 2	JAM —>CRM —><CRM Name > —>Administration Tab —> Diagnostics Tab
T3	Set Trace Level to 3	JAM —>CRM —><CRM Name > —>Administration Tab —> Diagnostics Tab
L0	Stop Link	JAM —>CRM —><CRM Name > —>Administration Tab —> Start/Stop Tab
L1	Start Link	JAM —>CRM —><CRM Name > —>Administration Tab —> Start/Stop Tab
NLS	Named Link Stop	JAM —>CRM —><CRM Name > —>Administration Tab —> Start/Stop Tab
SNL	Start Named Link	JAM —>CRM —><CRM Name > —>Administration Tab —> Start/Stop Tab