Skip to main contentIBM ZLPN Documentation

IMS™ DB/DC and IMS Connect for z/OS®

IMS DB/DC is an optional product available upon request for the z/OS remote access environment. Please contact the IBM Innovation Center, Dallas if you wish to add IMS DB/DC to your guest z/OS system.

Table of contents

  1. IMS™ DB/DC and IMS Connect for z/OS®

  2. 1 IMS DB/DC Installation and Configuration

    2.1. Dataset Information

    2.2. Special Instructions for doing STAGE1 Gen

  3. 2 Instructions to start/stop the IMS subsystem

    3.1. Starting IMS

    3.2. Stop IMS

  4. 3 IMS terminals in full screen APPLication mode

  5. Appendix A. IMS Connect

    A.1. IMS Connect PROCS and PARMS

    A.2. Implementation

    A.3. Start IMS and IMS Connect Tasks

    A.4. Stop IMS and IMS Connect Tasks

1 IMS DB/DC Installation and Configuration

When requested to be connected to the guest z/OS system, IMS DB/DC will be installed and configured as documented in the IMS DB/DC program directory and installation guide, with some minor modifications to conform to IBM Innovation Center, Dallas installation guidelines.

In this environment, only one IMS subsystem can run at a time because two SVCs are required for IMS and only one pair of SVCs is defined. A separate pair of SVCs would be needed for each version of IMS to run multiple versions simultaneously.

IMS Connect is also configured on the system, but it is not activated. Please follow instructions found in Appendix A. IMS Connect to activate it.

1.1 Dataset Information

IMS DB/DC datasets will have the following format and contain information as described below:

1.2 Special Instructions for doing STAGE1 Gen

All of these instructions must be performed with IMS NOT running.

  1. Run [hlq].IMSGEN.CNTL(STAGE1). This uses member STG1MACS as input and generates a jobstream that is STAGE2.

  2. Modify the STAGE2 job to have the output go to [hlq].USER.SDFSRESL. You can perform this modification using a clist.

  3. To execute the clist, go to TSO option 6 and enter the following command (with correct HLQ):

    EX '[hlq].SVSC.CLIST(STAGE2U)' '[hlq].IMSGEN.CNTL'

    This will take STAGE2, apply the needed modifications, and create STAGE2U. Run all the steps or jobs of STAGE2U.

  4. Then run SECURITY, DEFLTAGN, OLCUTL.

In Summary:

  1. PREPROC – checks names (not currently used)
  2. STAGE1 – uses STG1MACS as input
    • [hlq].IMSGEN.CNTL(STAGE1)
  3. STAGE2 – output created by STAGE1
    • Go to TSO option 6, copy step 4, press ENTER
  4. This REXX exec stores the updated STAGE2 in STAGE2U member:
    • EX '[hlq].SVSC.CLIST(STAGE2U)' '[hlq].IMSGEN.CNTL'
  5. STAGE2U – STAGE2U clist creates this job:
    • [hlq].IMSGEN.CNTL(STAGE2U)
  6. SECURITY – turns off security on these systems
    • [hlq].IMSGEN.CNTL(SECURITY)
  7. DEFLTAGN – replaces Resource Access Security module DFSISIS0
    • [hlq].IMSGEN.CNTL(DEFLTAGN)
  8. OLCUTL – Online Change Utility - makes the changed objects available.
    • [hlq].IMSGEN.CNTL(OLCUTL)

The same process exists for IMS1210, DFSD10, and DFSE10. Only the dataset HLQ changes.

2 Instructions to start/stop the IMS subsystem

Depending on when IMS was requested for the system, the IMS started tasks are found in either SVTSC.PROCLIB or VENDOR.PROCLIB and follow a naming standard of IMSnn*, where nn is 12, 13, or 14 representing the IMS version.

The following commands can be issued from the LOG display in SDSF. From the TSO Primary Option Menu, type SD.LOG and press ENTER. In the following examples, IMS V9 is being started. To start IMS V13, substitute 13 for 12 in the commands below. To start IMS V14, substitute 14 for 12 in the commands below.

2.1 Starting IMS

In order to start IMS, the IRLM task must be started first. To start IRLM for IMS V9 issue the following command from SDSF command line:

/S IMS12RL1

This will start the task for the IRLM associated with IMS V12. The two digits in the task name refer to the version.

Next you will start the control region for IMS V12. Issue command:

/S IMS12CR1

As IMS starts running it will issue a write to operator with reply (WTOR). For a normal restart, you must reply with a command like:

/R 03,/NRE CHKPT 0 FORMAT ALL

In this example the 03 matches the reply number in the IMS response. This will cold start IMS.

2.2 Stop IMS

To stop IMS, issue the following commands from SDSF:

/R 04,/CHE SNAPQ
/R 05,/CHE FREEZE

These commands will close the checkpoint dataset and bring down the control region. You will still need to stop the IRLM with the following command:

/P IMS12RL1

3 IMS terminals in full screen APPLication mode

In order to connect to IMS, the IMS version you want to connect must be started and the VTAM APPL must be activated. The current highest level of IMS supported on the system will be the active VTAM APPL. i.e IMS14APL You can display which VTAM APPLs are active by issuing the following command:

/D NET,APPLS

To display the specifics about the IMS VTAM APPL that is active, issue the following command:

/D NET,ID=IMS14APL,E

If you want to activate a different IMS, you must first stop the current VTAM APPL and start the new VTAM APPL. For instance, to stop the IMS V14 APPL and start the IMS V13 APPL, issue the following commands:

/V NET,INACT,ID=IMS14APL
/V NET,ACT,ID=IMS13APL

Note: Since we only include one set of SVC's defined for IMS, you can run only one version of IMS at a time.

In the default STAGE1 for each version of IMS, there are predefined terminals named for LF02, LF03, LF04 which correspond to the F02, F03, F04 terminal attribute used on the DIAL command. To be connected as one of those predefined terminal names, use the DIAL command and specify one of the terminal IDs (either F02, F03, or F04). Following is an example of this command:

D ETPGyyy F02

To see the definitions for the terminals refer to the STAGE1 input found in the IMSGEN.CNTL library. i.e. IMS1010.IMSGEN.CNTL(STG1MACS).

When you specify IMS on your "WELCOME TO THE SOFTWARE VENDOR SYSTEMS CENTER" , you may see differences in the screen you are presented based on which terminal id you selected.

If you connect without one of these Terminal IDs, a signon screen will appear.If you get the sign on screen, you must specify a user ID but no password is needed. Neither the user ID nor the password are checked.

Note: To drop the VTAM terminal session to the IMS application, issue the following command from any terminal connected to IMS:

/RCL

Appendix A. IMS Connect

This appendix provides instructions for solution developers to implement IMS Connect with IMSPlex support, on their remote development system. These instructions assume that the guest z/OS system is active and that the solution developer is logged on to TSO to perform the tasks.

Additional information can be found in the IMS V9 Connect Users Guide and Reference here: http://www.elink.ibmlink.ibm.com/publications/servlet/pbi.wss?CTY=US&FNC=SRX&PBL=SC18-9287-02

A.1 IMS Connect PROCS and PARMS

There are several additional started task procs and parm members required for IMS Connect with IMSPlex support (used to access Operations Manager). These members are in addition to the normal IMS control and dependent region procs/parms. You will find these members located in [hlq].PROCLIB (hlq represents the high level qualifier of your version of IMS). Please verify that you have these members on your system, if not, please contact the IBM Innovation Center, Dallas support team:

A.2 Implementation

Copy member IMSxxCR1 from SVTSC.PROCLIB into VENDOR.PROCLIB. Change the RGSUF parm to RGSUF=IV2. This is all the cusomization you should need to do, provided all of the above members exist on your system.

A.3 Start IMS and IMS Connect Tasks

Once IMS connect is implemented, you must start the IMS tasks in the following order. Below are commands to complete this task:

S IMSxxRL1
S IMSxxSCI
S IMSxxRM1
S IMSxxOM1

Start IMS Control Region:

S IMSxxCR1

(Follow normal IMS start procedure in 2.1 Starting IMS)

S IMSxxHWS

A.4 Stop IMS and IMS Connect Tasks

Use the following order and commands to stop the IMS tasks – please wait for each shutdown to complete before continuing on to the next one:

  1. Look in SYSLOG for the outstanding reply number for DTSCHWS. Respond with xx,CLOSEHWS QUIESCE

  2. Shut IMS control and dependent regions down using normal shutdown commands (see 2.2 Stop IMS).

  3. P IMSxxOM1

  4. P IMSxxRM1

  5. P IMSxxSCI

  6. P IMSxxRL1