Traditionally, customers using the Symbolic File (PROTSYM) with one or more of the several CA Testing Tools suite of products that make use of this file were limited to storing a single copy of the source for each application program in an individual file. However, beginning with Release 9.1, one of the major changes with this release is the ability to store multiple copies of the same application program in one file. This change has spawned the introduction of one new Control Card function and several additional parameters to the Symbolic File Maintenance Utility, IN25UTIL. This increased capability allows customers to maintain the file more efficiently and optimize the use of this new functionality. The new function and parameters can only be used with files created with Release 9.1 of the utility.
They are as follows:
Control Card Function - UPDATE
Parameters - MAXPGMVER, USEDSPACEMSG, AFTERDATETIME, ALL, BEFOREDATETIME, DATETIME, NEWEST, OLDEST
UPDATE is used to add or change the value of the USEDSPACEMSG parameter to an existing PROTSYM file. The PASSWORD Control Card Function must be specified before this function.
MAXPGMVER=nn specifies the number of versions of each individual program that can be stored defined to a PROTSYM. The nn value can range from 1 to 255. Specifying a value of 1 allows no multiple versions and is equivalent to leaving the parameter off entirely. MAXPGMVER is only supported by the INITIALIZE Control Card when a new file is defined or when an existing file is reorganized.
USEDSPACEMSG=nn specifies the limit of used space in the PROTSYM file in percentage. When the limit is reached, a SYM070 message indicating the amount of space used is issued. The nn value can range from 0 to 99. If 0 is specified then no SYM070 message will be issued. USEDSPACEMSG is supported by both the INITIALIZE Control Card when a new file is defined or when an existing file is reorganized and the newly introduced UPDATE Control Card which allows customers to set the value to an existing file without reorganizing the file itself.
AFTERDATETIME=yyyy/mm/dd hh:mm:ss specifies the action to be taken on all versions of a named program compiled after the specified date and time stamp. Partial timestamps are allowed by omitting the time stamp starting with the smallest value. This parameter is specified following the NAME parameter on any of the following Control Card functions: DELETE, PRINT, RELOAD, or UNLOAD.
ALL specifies the action to be taken on all versions of a named program listing. This parameter is specified following the NAME parameter on any of the following Control Card functions: DELETE, PRINT, RELOAD, or UNLOAD. This is not to be confused with the ALL parameter specified on a RELOAD=ALL or UNLOAD=ALL which apply to every saved listing stored in the entire file and not just to a named program.
BEFOREDATETIME=yyyy/mm/dd hh:mm:ss specifies the action to be taken on all versions of a named program compiled before the specified date and time stamp. Partial timestamps are allowed by omitting the time stamp starting with the smallest value. This parameter is specified following the NAME parameter on any of the following Control Card functions: DELETE, PRINT, RELOAD, or UNLOAD.
DATETIME=yyyy/mm/dd hh:mm:ss specifies the action to be taken on all versions of a named program compiled on the specified date and time stamp. Partial timestamps are allowed by omitting the time stamp starting with the smallest value. This parameter is specified following the NAME parameter on any of the following Control Card functions: DELETE, PRINT, RELOAD, or UNLOAD.
NEWEST specifies the action to be taken on the newest copy of a named program listing. This parameter is specified following the NAME parameter on any of the following Control Card functions: DELETE, PRINT, RELOAD, or UNLOAD.
OLDEST specifies the action to be taken on the oldest copy of a named program listing. This parameter is specified following the NAME parameter on any of the following Control Card functions: DELETE, PRINT, RELOAD, or UNLOAD.
Detailed information on the Control Card Functions, Parameters, and JCL examples of how they are used can be found in Chapter 4: Maintaining a PROTSYM File of the CA Application Quality and Testing Tools Release 9.1 Symbolic Guide.