Defining and controlling CAS cross-system communication

This section describes how you can use the CASACT, CASDEF, and CASDEFD views to define and control the VTAM® cross-system communication between CASs. The CAS in the MVS™ system to which you are connected is considered the local CAS. A CAS in another MVS system with which the local CAS communicates is a remote CAS.

CASACT (CAS cross-system activity)

The CASACT view can help you manage the activity of your VTAM cross-system communication links. The action commands you can use from the CASACT view affect only the running CAS; they do not affect the CAS definition in the parameter repository.

To display information about current CAS cross-system communication activity, you can:

Figure 14 is an example of the CASACT view.

Figure 14. The CASACT view
 27FEB2005  10:37:40 ------------------------- INFORMATION DISPLAY ----   
 COMMAND  ===>                                                                        
 CURR WIN ===> 1        ALT WIN ===>                                                  
  W1 =CASACT============MV26=====*========15FEB2005==10:37:40====PLEXMGR======   
 CMD System   Cur Description                          SPCF XCF  VTAM VTAMAppl        
 --- -------- Sys -----------                          Act  Conv Act  --------        
     ASATACAS No  AR Saturn CAS on MVS29.              No   No   No                   
     BASETEC1 No  basetec testing at inc49 - JON       No   No   No   BASETEC1        
     BASETEC2 No  basetech tesing at inc49 - JON       No   No   No   BASETEC2        
     MV26     Yes Use CasDef to update..               No   No   Yes                  
     MV27     No  Use CasDef to update                 No   No   No                   
     MV28     No  Use CasDef to update..               No   No   No                   
     MV29     No  Use CasDef to update..               No   No   No                   
     QSATACAS No  AR Saturn CAS on MVS26.              No   No   No                   
     RSATACAS No  AR Saturn CAS on MVS27.              No   No   No                   
     SSATACAS No  AR Saturn CAS on MVS28.              No   No   No                   

 

Action commands

Table 7 summarizes the action commands you can use with the CASACT view.

Table 7. CASACT view action commands
Primary command Line command Description
HALt system HAL Halts VTAM communication between the local CAS and a remote CAS.

All communication sessions between the local CAS and the specified CAS are terminated immediately, regardless of any outstanding requests for information. Once communication is halted, you cannot access the remote CAS again until you restart communication using the START action command.

QUIEsce system QUI Quiesces communication between the local CAS and a remote CAS.

Communication sessions between the local CAS and the specified CAS are terminated only after all information requests between the sessions are complete. Once communication is quiesced, you cannot access the remote CAS again until you restart communication using the START action command.

STart system S Starts communication between the local CAS and a remote CAS that is newly defined or one that was previously quiesced or halted.

The START command is not valid for a remote CAS with which communication is currently active.

Note:
These action commands are not valid for the local CAS, which is identified by a value of YES in the Cur Sys field.

Hyperlink fields

There are no hyperlink fields in the CASACT view.

CASDEF (Multiple CAS definitions)

Each CAS must be defined to the MVS system on which it resides. In addition, for a CAS to communicate with other CASs through VTAM or join an XCF group, the CAS must be defined to other MVS systems. The CASDEF view allows you to create and maintain these local and cross-system CAS definitions.

A CAS definition includes:

To display information about your CAS definitions, you can:

Figure 15 is an example of the CASDEF view.

Figure 15. The CASDEF view
27FEB2005 10:42:14 -------------- INFORMATION DISPLAY --------  
COMMAND  ===>                                                                 
CURR WIN ===> 1        ALT WIN ===>                                           
 W1 =CASDEF============MV26=====*========(00 BROWSE)====PLEXMGR=============  
CMD CAS      Cur Description                          Status        VTAM     Del     
--- Name---- Sys -----------                          ------------- ApplName ---     
    ASATACAS No  AR Saturn CAS on MVS29.              Installed     *NONE*   No      
    BASETEC1 No  basetec testing at inc49 - JON       Installed     BASETEC1 No      
    BASETEC2 No  basetech tesing at inc49 - JON       Installed     BASETEC2 No      
    MV26     Yes Use CasDef to update..               Installed     *NONE*   No      
    MV27     No  Use CasDef to update                 Installed     *NONE*   No      
    MV28     No  Use CasDef to update..               Installed     *NONE*   No      
    MV29     No  Use CasDef to update..               Installed     *NONE*   No      
    QSATACAS No  AR Saturn CAS on MVS26.              Installed     *NONE*   No      
    RSATACAS No  AR Saturn CAS on MVS27.              Installed     *NONE*   No      
    SSATACAS No  AR Saturn CAS on MVS28.              Installed     *NONE*   No      
 

Notes:
  1. Scroll to the right to see the Del field, which indicates whether a CAS definition has been marked for deletion.
  2. The CASDEF view in Figure 15 is shown in browse mode, which means no editing actions can be performed. For a description of the CASDEF edit and browse modes, see Editing CAS definitions.

The first time you display the CASDEF view (that is, before you have added any CAS definitions), information for a default definition is displayed. The VTAM ApplName field contains a value of *NONE*, and the Description field contains the words Use CASDEF to update.

Action commands

Table 8 summarizes the action commands you can use with the CASDEF view.

Note that the CASDEF view can be displayed in two modes, browse and edit. By default, CASDEF appears in browse mode, which allows you to review CAS definitions, but not modify them. Most of the CASDEF action commands require you to be in edit mode, as noted in Table 8. For a description of the CASDEF browse and edit modes, see Editing CAS definitions.

Table 8. CASDEF view action commands
Primary command Line command Description
ADD system A Displays the ADD CAS SYSTEM DEFINITION input panel, which lets you create a CAS definition, as described in topic Adding a CAS definition.

Before you can add a CAS definition, you must issue the EDIT action command to obtain access to the parameter repository.

CANCEL n/a Cancels CAS definition changes you are currently making or returns from edit mode to browse mode.
CHANGE system C Displays the CHANGE CAS SYSTEM DEFINITION input panel, which lets you change an existing CAS definition.

The format of this panel is similar to that shown in Figure 16. You can modify any field in the panel except CAS System Name.

Before you can change a CAS definition, you must issue the EDIT action command to obtain access to the parameter repository.

DELete system DEL Marks a CAS definition for deletion from the parameter repository, as described in topic Deleting a CAS definition.

Before you can mark a CAS definition for deletion, you must issue the EDIT action command to obtain access to the parameter repository.

EDIT n/a Provides editing access to CAS definitions in the parameter repository, as described in topic Editing CAS definitions.
INStall system INS Immediately updates a running CAS with new or changed CAS definitions, as described in topic Installing CAS definition changes.
SAVE n/a Saves in the parameter repository any CAS definition changes you have made while in edit mode.
UNDelete system UND Reinstates a CAS definition that was marked for deletion but not saved, as described in topic Deleting a CAS definition.

Before you can mark a CAS definition for deletion, you must issue the EDIT action command to obtain access to the parameter repository.

Hyperlink fields

Table 9 shows the hyperlink field on the CASDEF view.

Table 9. CASDEF view hyperlink field
Hyperlink field View displayed Description
CAS Name CASDEFD Displays detailed information about a specific CAS definition.

Editing CAS definitions

Before you can add, change, or delete CAS definitions, you must obtain editing access to the parameter repository. You cannot issue any action command that affects a CAS definition in the parameter repository until you have issued the EDIT command.

To edit a CAS definition in the parameter repository, do the following:

  1. Display the CASDEF view.
  2. Issue the EDIT primary action command to obtain editing access to the CAS parameter repository.

    The edit mode status field on the window information line changes from (00 BROWSE ) to (00 EDIT ) to indicate that edit mode is active.

  3. Issue any of these action commands: As you modify CAS definitions, the edit mode status field on the window information line changes from (00 EDIT   ) to (00 EDIT MOD   ). This means you have made changes that have not yet been saved in the CAS parameter repository.
  4. When you are ready to save your changes, issue the SAVE primary action command.

    The edit mode status field on the window information line changes from (00 EDIT MOD ) to (00 EDIT ) to indicate that edit mode is still active, but all outstanding modifications have been saved.

At any time while you are editing CAS definitions, you can issue the CANCEL primary action command to cancel your changes or exit edit mode and return to browse mode:

Adding a CAS definition

To add a CAS definition to the parameter repository, do the following:

  1. Display the CASDEF view.
  2. Issue the EDIT primary action command to obtain editing access to the CAS parameter repository.
  3. Issue the add primary (ADD) or line (A) action command from the CASDEF view.

    The ADD CAS SYSTEM DEFINITION input panel appears, as shown in Figure 16.

    Figure 16. Adding a CAS definition
    --------------------- ADD CAS SYSTEM DEFINITION -------------------------------
    COMMAND ===>
     
    CAS System Name    ===> EYUA     (Recommended same as MVS System Name)
      Description      ===>
     
    System Identification Information:
      MVS System Name  ===> EYUA          SMF ID          ===> *
      SysPlex Name     ===> *             Subsystem ID    ===> *
     
    System Communication Information:
      VTAM Appl Name   ===> EYUCAS0A
      XCF Group Name   ===> EYUGR310
     
     
     
    Enter END to add the CAS System Definition.
    Enter CANCEL to leave without adding.
  4. Provide the following information, as appropriate:
    CAS System Name
    Specify a unique 1- to 8-character name for the CAS.

    Since there is generally only one CAS per MVS image, you should make this name the same as the MVS system name. The only exception would be if you are defining a test CAS on a system where a production CAS already exists.

    Description
    Specify a 1- to 40-character description of the CAS definition.
    System Identification Information
    Use the fields in this section of the panel to uniquely identify the CAS.
    MVS System Name
    Specify the name of the MVS system in which the CAS resides.
    Sysplex Name
    Specify the name of the sysplex to which the MVS system belongs. (Every MVS system has a sysplex name, even if it is not part of a formal sysplex configuration.) You can code * (asterisk) if the MVS System Name uniquely identifies the system.
    SMF ID
    Specify the name of the MVS system as it appears in the active SMFPRMxx member of SYS1.PARMLIB. You can code * (asterisk) if the MVS System Name uniquely identifies the system.
    Subsystem ID
    Specify the SSID= value used in the CAS startup procedure. You can code * (asterisk) if the MVS System Name uniquely identifies the system.
    System Communication Information
    Use the fields in this section of the panel to specify the CAS cross-system communication parameters.
    VTAM Application Name
    Specify the name you used in the APPL statement when defining a VTAM major node for this CAS (see the CICS® Transaction Server for z/OS® Installation Guide manual). This name is unique for each CAS across multiple MVS systems; it is the name that VTAM uses to identify a CAS.
    XCF Group Name
    Start of changeUse the default value of EYUGR310, even if you do not use XCF communication links at your enterprise.End of change
  5. Issue the END command to return to the CASDEF view.
  6. Issue the SAVE action command to save the CAS definition in the parameter repository.
    Note:
    If you decide not to add this CAS definition to the parameter repository, you can use the CANCEL action command at any time before you issue SAVE.
  7. Repeat this procedure for each CAS with which you want the local CAS to communicate.

The definitions on the local CAS are now complete. However, the remote CASs that were defined to this CAS still need information about themselves and the other CASs with which they will communicate.

For example, suppose your environment consists of three CASs, named EYUCAS01, EYUCAS02, and EYUCAS03 respectively, and you are currently connected to the system in which EYUCAS01 resides.

If each CAS has a separate parameter repository that it does not share with any other CAS, then you must establish a connection to each CAS in turn and define them to each other, as follows:

  1. After adding definitions for EYUCAS01, EYUCAS02, and EYUCAS03 to the parameter repository for EYUCAS01, exit PlexManager.
  2. Log on to the MVS system in which the CAS executes and change the CAS identified in your CICSPlex SM profile to EYUCAS02.
  3. Return to PlexManager and display the CASDEF view.
  4. Add definitions of EYUCAS01, EYUCAS02, and EYUCAS03 to the parameter repository for EYUCAS02.
  5. Repeat steps 1 through 4 to add definitions of EYUCAS01, EYUCAS02, and EYUCAS03 to the parameter repository for EYUCAS03.

If the CASs operate in a shared DASD, shared parameter repository environment, then you can do the following:

  1. After adding definitions for EYUCAS01, EYUCAS02, and EYUCAS03 to the parameter repository for EYUCAS01, exit PlexManager.
  2. Log on to the MVS system in which the CAS executes and change the CAS identified in your CICSPlex SM profile to EYUCAS02.
  3. Return to PlexManager and display the CASDEF view.
  4. Issue the INSTALL * action command to dynamically update the cross-system communication parameters for the local CAS.
  5. Repeat steps 1 through 4 to update the definitions for EYUCAS03.
Note:
For a complete description of the CICSPlex SM profile where you specify a CAS name, see the CICSPlex System Manager User Interface Guide.

Deleting a CAS definition

To delete a CAS definition from the parameter repository, do the following:

  1. Display the CASDEF view.
  2. Issue the EDIT primary action command to obtain editing access to the CAS parameter repository.
  3. Issue the delete primary (DELete) or line (DEL) action command from the CASDEF view.

    The CAS definition is marked for deletion and is removed from the CASDEF view. However, the definition is not yet removed from the parameter repository.

  4. To complete the deletion process, issue the SAVE action command. The definition is removed from the repository.

If you change your mind, you can use the UNDELETE action command to reinstate a deleted CAS definition. Note, however, that you must issue UNDELETE before using the SAVE action command. Once a delete request is saved, the definition cannot be reinstated.

If you know the name of the CAS definition you want to reinstate, you can issue the primary action command as follows:

   UNDelete casname

where casname is the name of the deleted CAS definition that you want to reinstate.

If you do not remember the name of the deleted CAS definition, first issue this command:

   PARMS DELETED(*)

CAS definitions that have been marked for deletion since the last time you issued the SAVE command are redisplayed in the CASDEF view. The deleted definitions have a value of YES in the Del field.

Once you have identified the CAS definition you want to reinstate, you can:

Installing CAS definition changes

To update a running CAS with new or changed CAS definitions, you can install the changes using the INStall action command. This allows the changes to take effect immediately, without waiting until the CAS is restarted or the MVS system is IPLed.

After you have added or changed CAS definitions, issue the install primary (INStall) or line (INS) action command from the CASDEF view. You can issues the INSTALL action command while the CASDEF view is in either edit or browse mode.

Note:
The INSTALL action command does not save the CAS definition changes in the parameter repository. If you have not already saved the changes, use the SAVE action command, as described in Editing CAS definitions. Otherwise, the changes that you installed in the running CAS are lost the next time the CAS is restarted.

CASDEFD (A specific CAS definition)

The CASDEFD view provides detailed information about a specific CAS definition in the parameter repository. You can use the same action commands to maintain CAS definitions from the CASDEFD view as you can from the CASDEF view.

To display information about a specific CAS definition:

Figure 17 is an example of the CASDEFD view.

Figure 17. The CASDEFD view
 27FEB2005  14:53:48 ----------- INFORMATION DISPLAY --------------------------
 COMMAND  ===>                                                 SCROLL ==> PAGE
 CURR WIN ===> 1        ALT WIN ===>
 >W1 =CASDEF===CASDEFD==EYUA=====*========(00 BROWSE        )=PLEXMGR======1===
     Cas Name........ EYUA      Description... System A CAS
      Current System. Yes       Status........ Installed
     Identification--
      MVS Sysname.... EYUA      SMF ID........ *
      Sysplex........ *         Subsys Name... *
     Communication---
      VTAM Appl...... EYUCAS1A  XCF Group..... EYUGROUP
      VTAM Mode...... *NONE*
 
 
 
     Update Info-----
      UpdSystem...... EYUA      UpdTime....... 09:05:00
      UpdUser........ LGS181    UpdDate....... 23FEB1995
      Deleted?....... No
 
 
 

Action commands

The action commands you can use with the CASDEFD view are the same as those for the CASDEF view, as shown in Table 8.

Hyperlink fields

There are no hyperlink fields in the CASDEFD view.

[[ Contents Previous Page | Next Page Index ]]