Skip to content
CA Panvalet - 14.6
Documentation powered by DocOps

Configuration Best Practices

Last update December 18, 2017

Library Configuration

CA Panvalet stores individual members in increments of blocks. The recommended block size for a library depends on the size of the library members. In CA Panvalet libraries with relatively large members (such as COBOL), we recommend using a correspondingly large block size. If you are using a library with small members, we recommend using a smaller block size.

Fine-tuning the CA Panvalet library can help improve performance when accessing the library.

The programs PAN#2 with the ++PRINT option and PAN#6 with the ++ANALYSIS option can be run to obtain characteristics of the library and its members.

Date of Last Access

When processing with the CA Panvalet Subsystem interface, we recommend you turn off the Date of Last Access option. This option prevents directory updates for read-only functions. This means that no library enqueueing is performed.

Wait time is reduced when accessing the CA Panvalet library

Eliminating Hardware Reserve

We recommend turning on the CA Panvalet footprint option when working in a multi-CPU environment.

Turning on the CA Panvalet footprint option eliminates the need for long-term hardware reserves and helps protect a CA Panvalet library when it is shared across like or disparate operating systems.

With footprinting, the RESERVE is active only for the time required to read or write the footprint. The footprint, a 2-byte field in the library control record, tells a job from the second CPU that someone else has write-only access to the CA Panvalet library.

Library Upgrades

We recommend using the AFTERDUMP option to upgrade an earlier version of a CA Panvalet library.

The AFTERDUMP option is transparent to the programmer and management. This option also automatically upgrades the CA Panvalet library and creates a backup library of the previous CA Panvalet version.

CA Panvalet Library File Configuration

You should initialize any shared CA Panvalet library files with DSORG=PS. We also recommend using the following block sizes:

  • Device 2311: 3624; 1740; 828
  • Device 2314: 7292; 3520; 1692; 1092; 792
  • Device 3330: 13028; 6444; 3156; 2056; 1508; 1180
  • Device 3340: 8368; 4100; 1966; 1254; 898; 680
  • Device 3350: 9440; 4628; 3024; 2220; 1740; 1416; 1188; 1016
  • Device 3375: 17600; 11616; 8608; 5600; 3200; 2176; 1504; 1056
  • Device 3380: 23476; 15476; 11476; 7476; 4276; 2932; 2044;1044
  • Device 3390: 27998; 18452; 13682; 7548; 4136; 2942; 2082; 1086
  • Device 9345: 22928; 15072; 11156; 8808; 4100; 3008; 2144; 1180

Correctly configuring your CA Panvalet library files helps improve performance and reduce the risk of unpredictable results.

Batch Processing

We recommend using batch processing instead of online processing when performing a high volume of copy-and-move transactions.

CA Panvalet performs batch processing in the background, which helps improve performance for users initiating mass copy-and-move transactions.

Enqueue and Dequeue Processing

We recommend using CA MIM or Global Resource Serialization (GRS) for enqueue and dequeue processing in shared z/OS environments. If you are using CA MIM, define the following QNAMEs:









If you are using GRS, adding to the conversion RNL converts hardware reserves to system enqueues. You should define the following conversion RNL for the queue:





Correctly configuring your enqueue and dequeue processing helps prevent data corruption or loss of data.

Periodic Backups

We recommend you perform periodic backups of your CA Panvalet libraries.

Scheduling periodic backups of your CA Panvalet libraries can help protect against data loss or corruption.

Was this helpful?

Please log in to post comments.