The AR370 Archive Utility

Using the AR370 Archive Utility in TSO

This section describes the LC370 and AR370 CLISTs, which allow you to use the AR370 Archive Utility in TSO. It also describes the OS/390 file attributes and DCB characteristics of AR370 archives.

The AR370 CLIST

The AR370 CLIST invokes the AR370 archive utility in TSO. The syntax is as follows:

AR370 archive action
target [optional-parms]

The archive argument specifies the name of the AR370 archive. The action and optional-parms arguments are listed in the following sections.

action arguments

The action argument can be any of the following:

DELETE

deletes the AR370 archive member specified by the target argument.

DISPLAY

displays information about the AR370 archive member specified by the target argument.

EXTRACT

extracts the AR370 archive member specified by the target argument into the data set specified with the parameter INTO . For example, the following command extracts member GREEN from userid.SPECTRUM.A into the OS/390 file userid.COLOR.OBJ(GREEN).

AR370 SPECTRUM EXTRACT GREEN INTO(COLOR.OBJ(GREEN))

INCLUDE

uses the file specified by the target argument as a list of INCLUDE statements.

MOVE

moves the AR370 archive member specified by the target argument.

QUICK

processes members of existing archives more quickly. This option keeps AR370 from reprocessing every member in the archive. It greatly reduces the amount of I/O needed to add, replace, delete, and move members in an archive, since no work file is used. You should use this option with care, however, because an existing library containing data could be destroyed if space in the data set runs out. Prior to using AR370 with the QUICK option, it is recommended that you back up the archive so that you will not lose your data in the event that the original data set is destroyed.

REPLACE

adds or replaces the file specified by the target argument in the AR370 archive.

The target argument specifies the AR370 archive member or OS/390 data set to perform the action on. If the action is REPLACE or INCLUDE , the target argument is the name of a data set containing the replacement member or INCLUDE statements. When the AR370 utility adds or replaces a member on OS/390, the archive member name is determined by the input filename. If the input file is a PDS member, the archive member name is the same as the PDS member name. If the input file is a sequential data set, the member name is formed from the final two qualifiers of the input data set name. If the action is MOVE , EXTRACT , DELETE , or DISPLAY , the target name is an AR370 archive member name. For the DISPLAY action, you can use an asterisk (*) to specify all AR370 archive members.

optional-parms arguments

The optional-parms argument can be any of the following:

AFTER(member-name )

specifies the AR370 archive member after which the moved or replaced member is to be stored.

BEFORE(member-name)

specifies the AR370 archive member before which the moved or replaced member is to be stored.

DBCLIST

allows debugging of the AR370 CLIST.

INTO(dataset-name )

specifies the name of a TSO data set in which to store the extracted member. If the data set belongs to another user, the fully qualified name of the data set must be specified, and the name must be preceded and followed by three single quotes as follows:

INTO('''FRED.EXTRACT.OBJ''')

OTHER(parameters)

allows miscellaneous parameters to be passed to the AR370 archive utility.

PRINT(dataset-name)

specifies the name of a TSO data set in which to store the printed output from the AR370 archive utility. If the data set belongs to another user, the fully qualified name of the data set must be specified, and the name must be preceded and followed by three single quotes, for example, PRINT('''PROJECT.AR.LIST''').

SYMBOLS

requests display of the symbols that are defined in the members listed by the DISPLAY action. When used with the VERBOSE parameter, a listing of all symbols (both defined and referenced) is produced.

UPPER

specifies that the output from the AR370 archive utility is to be uppercase.

VERBOSE

specifies verbose information. Refer to the verbose ( v ) command modifier under Optional Modifier Characters for more details.

WORKSPC('primary secondary' )

specifies the workfile space allocation. The primary argument specifies the primary allocation, and the secondary argument specifies the secondary allocation.

WORKUNIT(storage-unit)

specifies the workfile allocation unit: track , cylinder , or block .

The LC370 CLIST

The LC370 CLIST has been enhanced to allow the compiler's object code output to be stored in an AR370 archive. The name of the archive in which the object code is to be stored is specified using the arlib compiler option. If the archive belongs to another user, its name must be given in full, and the name must be preceded and followed with three single quotes. For example:

'''userid.archive-name.AR'''

If the archive name is not quoted and does not have a final qualifier of AR, a final qualifier of AR is appended.

The member compiler option is used with the LC370 CLIST to specify the output archive member name, which must also be a valid OS/390 partitioned data set member name. If member is omitted and the input file is a partitioned data set member, the same member name will be used in the AR370 archive. If member is omitted and the input file is not a partitioned data set member, you will be required to enter a member name. Note that you may specify only one of the OBJECT and ARLIB keywords.

Here is an example of the use of the arlib and member compiler options:

LC370 RECIPE(BROIL) ARLIB(KITCHEN) MEMBER(BROILING)

In this example, the object code resulting from the compilation of userid.RECIPE.C(BROIL) is stored as member BROILING of userid.KITCHEN.AR .

OS/390 File Attributes

AR370 creates archives with RECFM FBS file attributes. In earlier releases, AR370 created archives with RECFM U file attributes. If you process an archive with RECFM U file attributes, it obtains an F record format. This record format allows a single, nonconcatenated archive to be processed by COOL without creating virtual copies of the archive members, thus improving prelinker performance.

To concatenate old archives with RECFM U with new archives having an F or FBS record format, specify the DCB characteristics of the concatenation to be RECFM=U.

If the concatenation is not RECFM U and it contains files with RECFM U and RECFM F and/or RECFM FBS, the following error message may be issued:

IEC024I INCONSISTENT RECORD FORMATS F AND U, ddn-n,dsname

You can also convert old style archives to new style archives by performing an add, move, or delete operation on the old archive with AR370.

DCB Characteristics

AR370 archives on OS/390 have the following DCB characteristics:

"RECFM=FBS,RECLEN=4080,BLOCKSIZE=4080"

Chapter Contents
Previous
Next
Top of Page