Format 5: Starting a Device Controlled by a Device Driving System
Use this format to cause a subsystem, for example PSF,
or program in another partition to start a device under its control
for processing spooled output.
- DEV
- Code this operand as shown.
- devname
- For devname, specify the name of the
device to be used. This name must be the one by which the device-owning
subsystem or application program knows the device. The specified name must be unique in the system. It can consist of up to eight alphameric characters. Do not use R000 through R250 as devname, since these are the reserved RJE user IDs, which are rejected by message 1R52I.Note: If the device name is LOCAL, VSE/POWER returns queue entries destined for local processing or for user ID LOCAL.
- subsystem
- For subsystem, specify the name which the subsystem used to establish a communication path to VSE/POWER.
- A|class
- For class, specify the class or classes as you would for any other VSE/POWER writer task.
- SKIP=YES
- Code this operand if you want VSE/POWER to insert
a skip-to-channel 1 preceding printed output. Insertion takes place:
- If the output entry has either Machine format op-codes or ASA format op-codes converted to machine format during retrieval
- If a write command occurs but no skip-to-channel 1 was found before, while control commands preceding the first write command are all ignored, or
- If only control commands were found in the output entry.
Note: The SKIP option is also passed to a Device Driving System in the PORDSFLG of the PSTART Device Order. For details, refer to VSE/POWER Application Programming. - PARM=‘string’
- For 'string', supply a device and subsystem specific parameter string, if this is required.
VSE/POWER's requirements regarding the parameter string are:
- It may not be longer than 60 characters. This includes blanks and commas that the program may need as delimiters.
- An apostrophe (') within the string must be entered as two successive apostrophes ('').
Note: When PARM is used to pass logical destinations (in addition to the devname) to the Device Driving System, then one should not use R000 through R250 as the destination, since these are reserved RJE user IDs..