HOS IWS adhoc processes can insert IWS applications to the current plan of IWS z/OS scheduler.
IWS adhoc simple process select one or more application from IWS and puts it to current plan. All IWS applications are updated to host in one transaction.
IWS adhoc on demand process select one or more application from IWS, provide dialog for change and then puts it to current plan. Each IWS application is updated to host separately,
IWS adhoc on time process loads set of JCL scripts. These JCL scripts are grouped together to one IWS application and updated to host.
.
The user can change and check the JCL source code for operations inside the IWS application in dialog.
The IWS AD application data can be changed in dialog or at the background using IWS rules.
Multiple applications are updated with independent separate transactions to the host.
User cannot set manual hold, priority and group definition for the updated IWS occurrence.
ADHOC ON DEMAND process creates record with DB state ON_DEMAND, this record is AD record with additional Current plan fields – input arrival, deadline, variable table. ON_DEMAND record is after successful update to Z/OS converted to record with DB state HISTORY and the process is finished.
The IWS ADHOC simple process can process multiple IWS AD records and updates the to the IWS plan.
The user cannot alter the JCL source code in operations or the AD record data.
All AD records in one process share the same parameters for the plan – input arrival, deadline.
User can set additional parameters manual hold, priority and group definition for the updated IWS occurrence.
It etc/app_sec these three fields must be enabled for the dialog in the module m_tws_adhoc_save_many
Example app_sec setting for module m_tws_adhoc_save_many
ADHOC SIMPLE process first creates record with DB state ON_DEMAND, this record is AD record with additional Current plan fields – input arrival, deadline, variable table.
By default after successful update to Z/OS the ON_DEMAND record is converted to DB state HISTORY, this record is AD record with additional Current plan fields – input arrival, deadline, variable table.
If settings result_dbstat in interface i_tws_adhoc_simple is set to to IN_PLAN , after successful update to z/OS process creates record with DB state IN_PLAN. IN_PLAN records are records that are connected with their occurence in current plan, user can see occurence status in current plan and with proper environment settings user can change them in current plan.
IWS ADHOC processes on demand and on time require setting for managing the creation, update and check of JCL scripts.
In data environment of process are located settings used setting for JCL template. For more information see chapter Data environment-> Environment Settings for ADHOC processes.
In process definition are for JCL used settings in interface i_tws_jck to set settings for JCL check. It enables the processing of JCL code by SmartJCL. Results of JCL check are then displayed in operation list. Setting jcl_check=true means that for job is required JCL check result OK or Warning.
In file hos_tws_config.php in etc directory are settings that configure access to z/OS – ip addresses of z/OS machines, workstations, ip addresses of IWS schedulers. The settings for IWS system can be connected also to HOS settings in hos_config2.php. For more information see chapter IWS configuration-> Settings for .
IWS ADHOC ONE TIME process gets JCL from parent JCL process or from JCL archive. JCL scripts are transformed to operations jobs.
The operations are grouped together to one IWS application with automatically generated name.
User cannot set manual hold and priority to the IWS occurrence.
ADHOC ONE TIME process creates record with DB state ONE_TIME, this record is AD record with additional Current plan fields – input arrival, deadline, variable table. ONE_TIME record is after successful update to Z/OS converted to record with DB state HISTORY and the process is finished.