This chapter contains these topics:
From ECS Sales Order Management (G4910), enter 27
From ECS Sales Order Advanced and Technical Ops (G491031), choose an option
You can automate some processes, such as printing documents or running required procedures, by setting up a subsystem to run them.
Your system might comprise one or more subsystems. You use subsystems to run specific sets of jobs, such as a group of print jobs. Subsystems create a suitable environment in which those jobs can run. It is easier to control a group of jobs through subsystems because you can individually start and stop subsystems.
To define the subsystem, you specify:
The version of the program you want to run
The environment in which the system should run the program
You use the Start Subsystem program to begin running specified jobs in the subsystem.
You must stop the subsystem before you perform end-of-day processing. You can also stop one or more jobs in the subsystem at any time.
You define the subsystem to run specific sets of jobs, such as printing documents or running required procedures. To define the subsystem, you specify:
The version of the program you want to run
The environment in which the system should run the program
For each program you want to run through the subsystem, complete the following fields:
Version
Environment
Figure 46-2 Define Subsystem (Fold Area) screen
To specify a library, complete the following optional field:
Library
Field | Explanation |
---|---|
Program | The RPG program name defined in the Software Versions Repository Master table. See Work with the Software Versions Repository in the JD Edwards World Technical Foundation Guide.
T SS XXX T – Specific member ID number SS – System number (for example, 01 for Address Book) XXX – Member type (for example, P for Program, R for Report, and so on) Form-specific information This code identifies the print program that you want to define within the subsystem. |
Version | Identifies a group of items that the system can process together, such as reports, business units, or subledgers.
Form-specific information The DREAM Writer version of the print control or gantry program identified in the program field. |
Environment | The name associated with a specific list of libraries. The J98INITA initial program uses these library list names to control environments that a user can sign on to. These configurations of library lists are maintained in the Library List Master table (F0094). |
Parameter 1 | A generalized 10 character parameter value passed to a called program.
Form-specific information For Gantry Subsystem: You must enter the name of the library where the Download Data Queue (DTAQGD) exists. For example, *LIBL. |
Length 1 | The length of the parameter which the called program is expecting.
Form-specific information For Gantry Subsystem: You must enter a value of 10. |
You use the Start Subsystem program to begin running specified jobs.
You can start the subsystem for:
A specific program
All programs
To start jobs in the subsystem
On Define Subsystem
For each job you want to start, complete the following field:
Option
The status field displays *ACTIVE for each program you started.
You must stop the subsystem before you perform end-of-day processing. You can also stop one or more jobs in the subsystem at any time.
You can stop jobs in the subsystem for:
A specific program
All programs
On Define Subsystem
For each job you want to stop, complete the following field:
Option
This stops the job in the subsystem, but the subsystem is still active.
You can set up the jobs to start and stop subsystems in Sleeper. First, identify the DREAM Writer versions of Start/Stop Subsystem (P40420) that you are going to use. Second, navigate to Unattended Operations Setup via menu G9643.
On Unattended Operations Setup.
Figure 46-3 Unattended Operations Setup screen
For each version of the Start/Stop Subsystem program you want to run complete the following fields:
Program
Library (the object library in your environment)
Run Date & Time
Days of the week if daily
Frequency
System
User (the ID of the user who normally runs the Start/Stop Subsystem job
Libl (the environment name)
Vers (the DREAM Writer version that is used for starting or stopping the subsystem)