template

When Procman/HOS needs to submit a job on the host then it first reads an appropriate template (skele-ton of the JOB) and makes substitution of special variables (they are surrounded with ##). A result of this substitution is a real valid job that is subsequently copied to temporarily allocated dataset and sub-mitted. There are many templates in Procman/HOS which are used in many scripts. There are templates for JCL analysis and generation, for checking JCL after is has been edited, for copying to the host and much more. In PHP scripts names of templates are used instead of member names in order to allow to set member names freely. The mapping of template names to member names must be correctly defined by template option. The example below is not complete, it only shows the syntax. A list of standard tem-plates is listed below the sample.

'template' => array (
    'jck_job_new'          => 'PRXJNEW',
    'jck_job_change'       => 'PRXJCHA',
    'jck_job_editchk1'     => 'HOSJEDT',
    'jck_job_editchk1_tws' => 'HOSJEDT1',
    'jck_job_approve'      => 'HOSJEDTB',
    'jck_job_tws_approve'  => 'HOSJJCKT',
    'jck_job_reft'         => 'HOSJREFT',
    'jck_job_ref'          => 'HOSJREF',
    'jck_job_final'        => 'HOSJEDTF',
    'jck_job_fast'         => 'HOSJEDTF',
    'jck_proc_new'         => 'HOSPCHKN',
    'jck_proc_change'      => 'HOSPCHKC',
    ...
)

Standard templates:

• jck_job_new JCL analysis in JCL NEW processes (m_jcl_analyse_1 module).

• jck_job_change JCL analysis in JCL CHANGE processes (m_jcl_analyse_1 module).

• jck_job_editchk1 JCL check of jobs in the request activity (m_jcl_change, m_jcl_change_objects, m_jcl_generate modules and in the preview started from m_jcl_fillforms module).

• jck_job_editchk1_tws JCL check of jobs with IWS variable substitution in the request activity (m_jcl_change, m_jcl_change_objects, m_jcl_generate modules and in the preview started from m_jcl_fillforms module).

• jck_job_ref JCL generator in JCL processes (m_jcl_analyse_2 module).

• jck_job_approve JCL check of jobs started from m_jcl_approve module.

• jck_job_tws_approve JCL check of jobs with TWS variable substitution started from m_jcl_approve module.

• jck_job_final final JCL check of jobs executed after members have been copied to the target libraries (m_jcl_final_check module).

• jck_job_fast fast JCL check of jobs (from target libraries, members are not copied to temporary dataset), available in m_hos_jcl_approve module.

• approve_regenerate_job JCL generator started from m_jcl_approve module (uses selected jobs as the input).

• jck_proc_new JCL analysis in PROC NEW processes (m_jcl_analyse_1 module).

• jck_proc_change JCL analysis in PROC CHANGE processes (m_jcl_analyse_1 module).

• jck_proc_editchk1 JCL check of procedures in the request activity (m_jcl_change, m_jcl_change_objects, m_jcl_generate modules and in the preview started from m_jcl_fillforms module).

• jck_proc_editchk1_tws JCL check of procedures with IWS variable substitution in the request activity (m_jcl_change, m_jcl_change_objects, m_jcl_generate modules and in the preview started from m_jcl_fillforms module).

• jck_proc_ref JCL generator in PROC processes (m_jcl_analyse_2 module).

• jck_proc_approve JCL check of procedures started from m_jcl_approve module.

• jck_proc_tws_approve JCL check of procedures with TWS variable substitution started from m_jcl_approve module.

• jck_proc_final final JCL check of procedures executed after members have been copied to the target libraries (m_jcl_final_check module).

• jck_proc_fast fast JCL check of procedures (from target libraries, members are not copied to temporary dataset), available in m_hos_jcl_approve module.

• approve_regenerate_proc JCL generator started from m_jcl_approve module (uses selected procedures as the input).

• change_by_parm_jobname1 analysis of selected JCL/PROC members in 'Change by parameters' function in m_jcl_fillforms module.

• change_by_parm_jobname2 generation of new JCL/PROC members that performs required changes in 'Change by parameters' function in m_jcl_fillforms module.

• change_cc when control cards are processed in JCL processes then a special job with variables that are substituted is analyzed instead of the selected member (because valid JCL is required by the analyzer). The member that is analyzed (by subsequent m_jcl_analyse_1 module) is specified by this template.

• copy copying of members to target libraries by m_jcl_copy module (members are first copied to temporary library and then the copy job is submitted).

• fast_copy copying of members to target libraries by m_jcl_fast_copy module (assumes the members already exist on the host, which is typically a case of INIT processes).

• delete deletion of members from target libraries by m_jcl_delete module.

• gdg_change_limit changing GDG limit in DSN processes by m_dsn_gdg_submit module.

• dsn_append_tape appending (merging) datasets into the target dataset (newly created) in DSN_APPEND processes (m_dsn_append_submit mudule) in case of TAPE device type.

• dsn_append_volume appending (merging) datasets into the target dataset (newly created) in DSN_APPEND processes (m_dsn_append_submit mudule) in case of VOLUME device type.

• dsn_rename renaming datasets in DSN_RENAME processes by m_dsn_rename_submit module.

• dsn_copy copying datasets in DSN_COPY processes by m_dsn_copy_submit module.

• idcams an alternative template used instead of gdg_change_limit. When this template is defined then it has a higher priority (by default it calls IDCAMS utility).

• dsn_gtyp finds current GDG limits of selected datasets in DSN processes by m_dsn_gdg_enter module.

• dsn_parm finds parameters of selected datasets in DSN processes by m_dsn_append_enter module.

• split members that are checked by JCL checker or members where IWS variables should be substituted have to be copied to the host into a temporary dataset. This copying takes a while when members are copied one by one. If more members are copied then Procman/HOS can use a fast method of saving members to the host. All files are concatenated in one single PS dataset and split to members by IEBUPDTE utility. To enable this fast method the split template must be defined. Even when the template is defined Procman/HOS can decide to use the standard one by one method if the number of analyzed files is small.

• universal job that is submitted in UNIVERSAL processes by m_universal_submit module.

• members_download job submitted when members are downloaded by the the fast method when Import button is pressed in m_jcl_edit and m_jcl_approve modules. The fast method is used when it is enabled by ps_transfer option.

• members_upload job submitted when members are uploaded by the the fast method when Export button is pressed in m_jcl_edit and m_jcl_approve modules. The fast method is used when it is enabled by ps_transfer option.

There can be other user-defined templates as well. They are used in interfaces of process configuration in cases when the template name is configurable by the user. Names of such templates are fully under control of the administrator who prepares your process definition. A typical example of such a template is (extracted from process configuration):

array (
    'name'     => 't0500',
    'type'     => 'task',
    'module'   => 'm_jcl_final_jck_auto',
    'input'    => array (
        'i_goto'          => '',
        'i_environment'   => '',
        'i_jcl_approve'   => '',
        'i_log'           => '',
        'i_jcl_final_jck' => 'template_index_jcl="jck_job_final", ' .
                             'template_index_proc="jck_proc_final", ' .
                             'skip_in_manual_mode=true',
    ),
    'output'   => array (
        'i_log'         => '',
        'i_jcl_approve' => '',
        'i_goto'        => '',
        'i_environment' => ''
    )
)