Format 6: Putting a Static Partition Under VSE/POWER Control

If the partition already is controlled by VSE/POWER, this command works like a VSE START command. You get a message if the partition is still active or not supported, or if its priority is not lower than that of the VSE/POWER partition and NPC is not specified.

Notes:

¹ You may specify up to four classes.
² Each option may be specified only once.

BG|Fn

Specify BG to place the background partition under control of VSE/POWER.

For n in Fn, specify the number of the applicable foreground partition.

partition_related_class|class

For class, specify the class(es) of the jobs that may be processed in the partition. You can specify up to four classes, every one as a letter of the alphabet.

One of the specified classes may be partition related. This is specified as one of the numbers 0 through 9 (where 0 = partition BG, 1 = partition F1, 2 = partition F2, and so on); Only one of the specified classes can be partition related. For details, see VSE/POWER Classes.

The order in which you specify the classes is the order in which VSE/POWER processes jobs in the partition. If you omit the operand, VSE/POWER selects processing classes as follows:

  0 - for BG (partition-related class)
  1 - for F1 (partition-related class)
  . . . .
  9 - for F9 (partition-related class)
  A - for FA (not partition-related class)
  B - for FB (not partition-related class)

A|outclass

For outclass, specify the default class (an alphabetic character or numeral 0 through 9), which VSE/POWER is to use for output spooled from programs executed in the partition. VSE/POWER assigns class A if you omit the operand.

MT

Specify MT if the involved partition is to be used for a long running program that does not return to z/VSE® Job Control at the end of its VSE/POWER reader job, but continues to read and process statements of further VSE/POWER jobs made dispatchable for the execution class of the 'MT' ¹ partition. For this partition, spooled output is not made available at the VSE/POWER job boundaries.

'MT' support causes VSE/POWER to do the following:

If the user program still resides in the partition and there are no more input records for the partition, only the associated execution reader task is placed into the wait state accompanied by message 1Q34A. The writer tasks are not stopped as in normal partitions. Instead, they accept more output from the partition.
Output from the partition is made available as a corresponding queue entry only if:
- An LFCB macro is requested for output to printers with a forms control buffer, or
- An IPWSEGM or SEGMENT macro is requested for other printers or punched output, or
- Further processed jobs contain an * $$ LST or a * $$ PUN JECL statement, or
- The partition is removed from VSE/POWER control by the PSTOP partition-id command.
In order to keep all collected output together as one queue entry, the initial input job for this partition must include an * $$ LST or an * $$ PUN statement for every spool device that may be used later.

If normal programs (returning to z/VSE Job Control at end of the reader queue entry) are processed in the 'MT' partition, the above described handling of output may be beneficial under certain circumstances.

For details on how the 'MT' partition's VSE security authorization may be affected, see Data Security and Multi-Tasking (MT) Partition.

NPC

Bypasses the check that VSE/POWER has the highest dispatching priority.

¹ 'MT' stands for 'multi-tasking'. This is a historical term reminding of a certain long running program coded in multi-tasking technique. Amongst other functions, this program was able to send the statements of further VSE/POWER jobs to other networking applications.