Display only. This field displays the action that you entered on the Control File Maintenance Entry panel.
Optional. Length: 8. Type: alphanumeric.
Enter a valid unit name to use when allocating temporary data sets, for retrieve using the TSO submit method, or for Online Reports.
The value in this field must not be blank, but CA‑PanAPT does not verify if this is a valid value.
These values allow you to specify characteristics of the temporary file created to hold online reports.
Required. Length: 5. Type: numeric.
The Blocksize field is used in two ways. First, it determines the size of the blocks when you are allocating space for report files. Second, it is the size of a physical block in these files that determines the blocking factor number in writing output to the file. This number must be a multiple of 81.
Required. Length: 4. Type: numeric.
Contains the number of blocks allocated for primary extents. The value in this field must be at least one.
Required. Length: 4. Type: numeric.
Shows the amount of space to be allocated for secondary extents. The value of this field can equal 0, but you should give it some positive value.
Required. Length: 1. Type: alphabetic. Valid values: T (TSO Submit) or I (Internal Reader) to modify the checkout job submission method:
TSO SUBMIT JOB submission service. This is the default value. The SUBMIT service has the advantage of giving the site an IBM‑defined exit point to inspect/modify incoming job streams. However, this facility has the disadvantage of requiring the job stream to reside on a sequential file.
CA‑PanAPT modeling output must be directed to a sequential file that must be dynamically allocated and de‑allocated on disk. The combination of the extra allocation and SUBMIT exit processing time can result in longer ONLINE wait time for Retrieve processing.
System Internal Reader. JCL and data records are sent directly to the System Internal Reader as they are formatted rather than sent to a file first. This facility avoids the overhead of allocating disk space or writing and reading a file. However, it provides no system exit point to inspect/modify incoming job streams.
These values allow you to specify characteristics of the temporary file created to hold a Retrieve job stream for TSO Submit. The file is not allocated if you select submission through the internal reader.
A typical CA‑Panvalet Retrieve model can produce 40 records (80 bytes each) for each member to be Checked-out. To illustrate, assume that you are using the CA‑Panvalet Retrieve model to Retrieve 100 members. If an inefficient blocksize of 80 is chosen, 4,000 blocks are required between the primary and secondary allocation. As an alternative, if a more efficient blocksize of 8000 is chosen, only 40 blocks are required between the primary and secondary allocations.
Choose an efficient blocksize for your storage device. Set primary and secondary allocations large enough to handle your largest possible Retrieve or Verification request.
Required. Length: 5. Type: numeric.
The Blocksize field is used in two ways. First, it determines the size of the blocks when you are allocating space for report files. Second, it is the size of a physical block in these files that determines the blocking factor number in writing output to the file. This number must be a multiple of 80.
Required. Length: 4. Type: numeric.
The number of blocks allocated for primary extents. The value in this field must be at least 1.
Required. Length: 4. Type: numeric.
Shows the amount of space to be allocated for secondary extents. The value of this field can equal 0, but you should give it some positive value.
Required. Length: 1-44. Type: alphanumeric.
Specifies the name of an OS/390 data set that to use to save the listings that are generated by various Utility functions. The data set name must be valid OS/390 data set name syntax, and the data set is tested for existence.
Required. Valid values: PO, PV, or L. Specifies the Access Method used for the Utility Listing Dsname:
PO Partitioned Access Method
PV CA‑Panvalet Library Format
L CA‑Librarian Library Format
Required. Valid values: 1 or 2 .
Specifies whether a member is transferred to another user when the member undergoes Reassign/Release processing.
For more information, see the Reassign/Release Processing section in the "Move Requests" chapter.
Required. Valid values: 1, 2, or 3.
This controls whether assignment of Inventory to a Move Request is required. If the value is 1, then assignment of Inventory to a Move Request is not required.
If the value is 2 or 3, then when Inventory is assigned, it is not only assigned to a user, but also to a Move Request. Inventory assignment of members that do not reside on Move Requests is prohibited. A Move Request cannot be closed if Inventory for any of its members is assigned to a different Move Request. Movement of a closed Move Request is halted if any of its Inventory was transferred to another Move Request.
In addition, if the value is 3, Concurrent Development assistance is enabled. This prohibits movement of Move Requests that might require changes due to concurrent development of any of its members on another Move Request. Once someone acknowledges that the members in question are ready, the Move Request can proceed again.
|
Copyright © 2004 CA.
All rights reserved.
|
|