OPERCMD - syncsort_cobol_migration_manager - syncsort_clone_center - syncsort_space_recovery_system - syncsort_scc_monitor - syncsort_simulate_2000 - syncsort_allocation_control_center - Latest

Syncsort™ Storage Management Product Installation Guide And DIF User Guide

Product type
Software
Portfolio
Integrate
Product family
Syncsort™ software
Product
Syncsort™ Storage Management > Syncsort™ Cobol Migration Manager
Syncsort™ Storage Management > Syncsort™ Clone Center
Syncsort™ Storage Management > Syncsort™ Space Recovery System
Syncsort™ Storage Management > Syncsort™ SCC Monitor
Syncsort™ Storage Management > Syncsort™ Simulate 2000
Syncsort™ Storage Management > Syncsort™ Allocation Control Center
Version
Latest
ft:locale
en-US
Product name
Syncsort Storage Management
ft:title
Syncsort™ Storage Management Product Installation Guide And DIF User Guide
Copyright
2023
First publish date
1991
ft:lastEdition
2026-01-22
ft:lastPublication
2026-01-22T05:50:39.722000
L1_Product_Gateway
Integrate
L2_Product_Segment
IBM Infrastructure
L3_Product_Brand
Precisely Syncsort
L4_Investment_Segment
Mainframe
L5_Product_Group
Mainframe Storage Optimization
L6_Product_Name
Syncsort Storage Management

Purpose: The OPERCMD command can be used to invoke an operator console command. OPERCMD is not normally used from the DIF command interface but can be useful when processing parameter members during product initialization and shutdown. OPERCMD can also be used by the command scripts in the MON-Explorer PC Application.

Capturing Command Output: Command output can be captured using two methods:

  • Subsystem Console - If OPERCMD(BUFFER(len)) is specified in the DIF startup parameters, the Extended CSA storage is used to buffer the command output using a subsystem console. The buffer request also causes DIF to obtain a subsystem console from the operating system.

    Subsystem consoles are defined in the CONSOLnn member in the system parameter library - typically SYS1.PARMLIB. A D C,N console command can be used to display your current console configuration. If a D C,N command is performed after DIF allocates to a subsystem console, a DTS-nnnn is displayed next to the console allocated to DIF.

  • Extended MCS (EMCS) Console (Recommended Method for z/OS systems) - If OPERCMD(BUFFER(len)) has NOT been specified in the DIF startup parameters, on a z/OS system the DIF OPERCMD interface uses the EMCS console interface to capture command output.

    The EMCS console interface has several advantages over using subsystem consoles:

    • No setup or console definitions are required on either the Host system or the Explorer.
    • The EMCS console interface is multi-threaded.
    • The console honors the Security environment established for the Explorer user.

If the operating system supports Extended MCS Consoles (EMCS) or the OPERCMD(BUFFER(len)) DIF parameter was used to set up a subsystem console, DIF attempts to capture the output of the command. The output capture process is terminated by either the last WTO being marked as the last of the command, or the wait time is exceeded. The WAIT parameter defaults to 5 seconds.

Tip: If WAIT(0) is specified, DIF will not capture the output of the command, and DIF will not wait for command completion.

The CN parameter can be used if you want to issue the command from a specific console.

Note: If the WAIT and/or CN keyword parameters are specified, they must be positioned before the requested operator command and parameters.

Syntax:

OPERCMD [WAIT(sec)] [CN(id)] {command} {parameters}    

Comments: This command is typically used by SCC Monitor (MON) and Easy-Exit (EXT) product initialization and termination routines: prdINIT and prdTERM. You might also find the command useful in command lists executed by the DIF EXEC command.

Examples: If you want to automatically activate SCC Monitor tasks during DIF START MON processing, you can create two new members in the DIF parameter library: MONINIT and MONTERM. The MONINIT member might contain the following statement to activate a started task called MONSTC. The MONSTC member should be placed in a system procedure library.

OPERCMD START MONSTC    

Multiple monitor tasks can be activated simultaneously to monitor different pools, or at different interval times. For example, another monitor task named MONSTC1 could be started by adding an OPERCMD START MONSTC1 statement in the MONINIT member. The MONTERM member should contain corresponding STOP statements for the tasks that were started in MONINIT, for example:

OPERCMD STOP MONSTC