The information in this article applies to:
Product: MIM
Version: 8.5
Platform: z/OS
Discussion
Started tasks can provide the operations team a more manageable task, improve automation control, improve availability, and enhance security. A started task leaves initiators available for the more typical short-lived work.
The MIM Component Manager spawned components are always started tasks (STC). As an STC, the MIM Component Manager allows all the MIM address spaces to be started tasks instead of a mix of JOBs and STCs. This can ease development of Workload Manager definitions and controls.
When installing MIM, first confirm the install by testing the MIM Component Manager as a JOB. Once the install has been confirmed then this procedure may be performed.
PROCEDURE
1. Select the started task name.
Do NOT use the name of an MVS subsystem.
The name should be 4 to 6 characters in length.
A maximum length of 6 characters allows the Component Manager to append a two-digit identifier to generate a unique name for each component STC.
2. Copy the JCL (XMOCPMGR) to a system procedure library using the started task name.
a. Remove the JOB statement.
b. Add a procedure end statement to the end of the member: // PEND
3. Add //procedure_name PROC as the first JCL statement in the procedure.
The value procedure_name should be replaced with the desired stored procedure name.
4. Resolve the INCLUDE using one of these three methods:
- Use a system JCL INCLUDE library and copy JCL(JCLVARS) to it, with a name associated with the procedure. Alter the include name to match the newly created JCL INCLUDE member.
OR
- Copy JCL(JCLVARS) to your procedure and place it before the EXEC statement and remove the INCLUDE statement.
OR
- Resolve all the JCL variables manually and remove the INCLUDE JCL statement. This is the least desirable as the USS pathname may be very long. Refer to the example below, entitled Example of a MIM Enterprise Server Started Task Where the INCLUDE Values Have Been Manually Resolved.
5. Copy the SYSIN control stream to a parameter library or the MIM JCL library.
The MIM parameters must be removed from the procedure.
Do not include “//” or “/*” statements. Only include MIM Component Manager statements.
Parameter file must not be line numbered.
Parameters may be in a sequential dataset or may be a member of a PDS/PDSE.
Record format VB or FB is also acceptable. A file in a USS file system is also acceptable.
Record length may be 80 – 255 bytes.
Refer to the example below, entitled Example MIM Component Manager Parameters File.
6. Update the SYSIN DD statement to point to the location of your parameters.
7. Define a security system profile for the new MIM started task procedure. Refer to the example below, entitled Example RACF Profile.
Example RACF Profile
RDEFINE STARTED Compmgr_STC_Name*.* STDATA(USER(CompmgrUserID) GROUP(STC))
Example of a MIM Enterprise Server Started Task Where the INCLUDE Values Have Been Manually Resolved
//MIMPRD PROC Add this line
//*--------------------------------------------------------------------
//*
//* Component Manager
//*
//* Copyright Metastorm Inc, All Rights Reserved, (c) 2001-2010
//*
//*--------------------------------------------------------------------
//* COMPONENT MANAGER
//*--------------------------------------------------------------------
//*
// SET ENVHLQ='SYS3.MIM.V850', Copied from
// SCSQANLE='CSQ700.SCSQANLE', JCL(JCLVARS)
// SCSQAUTH='CSQ700.SCSQAUTH',
// SCSQSNLE='CSQ700.SCSQSNLE',
// SDSNEXIT='DSN910.SDSNEXIT',
// SDSNLOAD='DSN910.SDSNLOAD',
// LQM='PROD',
// DATAPATH='/var/metastorm/mim/850'
//*
//XMOCPMGR EXEC PGM=XMOCPMGR,
// PARM='POSIX(ON)/-STDIN'
//STEPLIB DD DISP=SHR,DSN=&ENVHLQ..LOAD
// DD DISP=SHR,DSN=CSQ700.SCSQANLE * MQ
// DD DISP=SHR,DSN=CSQ700.SCSQAUTH * MQ
// DD DISP=SHR,DSN=CSQ700.SCSQSNLE * MQ
// DD DISP=SHR,DSN=DSN910.SDSNEXIT * DB2 (IF REQUIRED)
// DD DISP=SHR,DSN=DSN910.SDSNLOAD * DB2 (IF REQUIRED)
//DSNAOINI DD DISP=SHR, * DB2INI IF REQUIRED)
// DSN=SYS3.DSN910.DB2INI(DSN910)
//SYSERR DD SYSOUT=*
//SYSOUT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//SYSOUT DD SYSOUT=*
//CEEDUMP DD SYSOUT=*
//OUTPUT DD SYSOUT=*
//*--------------------------------------------------------------------
//* SHARED FILES
//*--------------------------------------------------------------------
//XMDIR DD PATH='&DATAPATH/config/client.xml'
//*
//* COMPONENT MANAGER PARAMETERS
//*
//SYSIN DD DISP=SHR,DSN=&ENVHLQ..JCL(MIMPPARM) <-- Update this statement
// PEND <-- Add this statement to denote end of procedure
Example MIM Component Manager Parameters File
EDIT SYS3.MIM.V850.JCL(MIMPARM) - 01.00 Columns 00001 00080
Command ===> Scroll ===> CSR
****** ********************************* Top of Data **********************************
=COLS> ----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8
000001 PARMDSN(SYS3.MIM.V850.CM.CNTL)
000002 #
000003 # SYMBOLIC LINK CREATION LOCATION
000004 #
000005 -compdir /var/prod
000006 #
000007 # SET TO VERBOSE MESSAGE LEVEL
000008 #
000009 -verbose
Note: There are no line numbers in columns 73 – 80. This is a requirement. Enter the edit command Unnum to confirm the member is UNNUMBERED:
EDIT SYS3.MIM.V850.JCL(MIMPARM) - 01.00 Not in number mode
Command ===> unnum Scroll ===> CSR
Refer to the MIM System Administration Guide for additional information about the MIM z/OS Component Manager.
