Output specification


The Output Specification screen allows you to specify whether you’re performing an ANALYSIS, COPY, or UPDATE function. And, if you’re performing a COPY, you can specify the appropriate data set information. This screen is displayed when you press <Enter> on the Criteria Menu. The output specification screens are the same for each function.

An example of the Output Specification screen is shown in the following figure.

Output Specification Screen

.  File-AID/Data Solutions ------- Output Specification -------------------------- .
.  COMMAND ===>                                                                    .
.                                                                                  .
.  Input dataset: PFHJAJ0.FASAMP.EMPMAST                                           .
.  Specify Output Processing Option:                                               .
.    Option             ===> A  (A=ANALYZE; C=COPY; U=UPDATE/PREVIEW)              .
.    Create audit trail ===> N  (Y=Chgd record only; N=No; A=All records in Batch) .
.    Audit trail prefix ===>                                                       .
.  Specify Output Dataset Information (COPY ONLY):                                 .
.    Dataset name   ===>                                                           .
.    Disposition    ===> OLD                (OLD or NEW)                           .
.    New VSAM Type  ===>                    (K=KSDS,E=ESDS,R=RRDS,L=LDS,Z=ZFS)     .
.                                           (Blank = Input Dataset Type)           .
.    I/O exit name  ===>                    (Blank=Use "FROM" I/O exit name;       .
.                                            NONE=No exit)                         .
.  Specify PDS(E) COPY options:                                                    .
.    Copy empty members from input ===> NO     (Y = Yes; N = No)                   .
.    Replace like-named members    ===> YES    (Y = Yes; N = No)                   .
.    Rename copied members mask    ===>                                            .
.                                                                                  .
.  Use ENTER to continue or END to return to Criteria Menu                         .
.  Use VIEW command to display criteria summary                                    .
.  Use SAVE command to write criteria request                                      .
.  Use CANCEL command to restart at Input Specification Panel                      .

Field descriptions

Specify Output Processing Option:

Option

Specify the type of output processing option you want to perform:

A

Perform all requested disguise functions without actually saving or applying any of the changes and will provide a summary report of what would have been changed if Copy or Update had been specified.

C

Perform Copy.

U

Perform Update. If you select preview on the subsequent Execution Options screen, Data Solutions Solution provides the preview report.

Important

Option U (Perform Update) is the only available option when using the Data Generator function to generate new records for a new file or empty data set. See Generation-function.

Create audit trail

Specify whether you want an audit trail created. Enter Y (Changed record only) or A (ALL records) to activate the audit trail feature. A is valid only for Batch UPDATE or COPY function. If A is specified, Data Solutions will force Batch job processing (see Process online or batch). The default is N (No).

Audit trail prefix

Specify the prefix to be used for the audit file. When you specify a prefix value, the audit trail dataset name is:

   audittrailprefix.Dyymmdd.Thhmmss.Msss

Your TSO-ID will precede the value you enter in this field. The combined length of the audit prefix, including the TSO-ID, is limited to 23 characters. Precede the prefix value with a single (‘) or double (“) quote to use the value without your TSO-ID.

If you use the symbolic *USERID*, File-AID will use the running job's user ID.

This value will replace the first node of the audit file dataset name.

Valid format is:

   PREFIX(a.b.c)

       or

   PREFIX(*USERID*)
Example

$$DD01 COPY AUDIT=(A,PREFIX(MYAUDIT.GENERAL.EMPDEPT))

Above example allocates an Audit trail dataset with an audit file data set name that starts with the specified prefix: ‘MYAUDIT.GENERAL.EMPDEPT.Dyymmdd.Thhmmss.Msss’.

If you leave this field blank, the standard audit file naming convention will be used (see Audit trail dataset).

Specify Output Dataset Information (COPY ONLY):

Data set name

Specify the name of the destination data set.

You can enter a pattern data set name in this field to display a list of data sets from which you can make a selection. A pattern data set name or mask consists of explicit characters or a combination of explicit and pattern characters. See Pattern data set names in section Specifying-a-dataset-name for a complete description.

Disposition

Specify OLD or NEW. A disposition of SHR is not allowed because of potentially disastrous results to data integrity.

New VSAM Type

Specify an option to create an output VSAM type different from the input. The disposition must be NEW and the input must a VSAM file.

IOEXIT name

Specify the name of the I/O exit data set.

Specify PDS(E) COPY options:

Copy empty members from input

Specify Y (Yes) or N (No -- default). This parameters specifies whether File-AID/Data Solutions copies FROM members that contain no records to the TO dataset. Specify Y (Yes) and Data Solutions copies empty members from the input PDS to the output PDS. Use the N (No) value and Data Solutions does not copy empty members.

Replace like-named members

Specify Y (Yes -- default) or N (No). Specify Y (Yes) to have Data Solutions copy members to the output PDS, even if the member name already exists. Use the N (No) value to prevent copying the member to the output PDS if the name already exists.

Important

When using a rename copied members mask, the member name that is replaced is the newly-constructed member name.

Rename copied members mask

Specify a mask to apply to each “To” member name and construct a new member name when copying members from one partitioned dataset (PDS) to another.

When constructing the new member name, Data Solutions interprets each ? (question mark) or & (ampersand) in the mask as a null character which preserves the original character at that location. An * (asterisk) or blank at the end of the mask means retain the balance of the original member name. All other characters are treated as constants and are placed in the new member name.

For example, applying the mask A??P to a copied member name of TEST01 results a new member name of AESP01.

If the old member name is smaller than the mask, unused null characters are ignored. The mask A??P applied to a copied member name of XY would result in a new member name of AYP. The last 2 bytes of 10-byte CA Panvalet names are dropped.

New member names are checked against the target PDS and are replaced based on the setting of the Replace like-named members parameter.

Primary commands

The following primary commands are valid on the Output Specification screen:

Command

Description

CANCEL

Returns to Input Specification panel without saving criteria information.

END

Saves the current change criteria and returns to the Criteria Menu.

ENTER

Selects the output specification.

SAVE

Saves the current change criteria in the change criteria data set. If a change criteria data set is not specified, you are prompted for a data set and member name in which to save the criteria.

VIEW

Displays the View Criteria screen, which summarizes the options and change criteria sets into a scrollable display. For more information, see View Criteria.

Audit trail feature

File-AID/Data Solutions allows you to create an audit trail of your Update processing in Online and Copy/Update processing in Batch. To activate the audit trail feature, enter a Y or A in the Create audit trail field on the Output Specification screen. A is valid only for Batch.

When Y is entered, before and after images of changed records are written to the audit trail whenever you change the contents of existing records.

When A is entered, before and after images of all records are written to the audit trail regardless whether or not they are selected, updated or copied.

Disposition of Audit Trail

The following figure is displayed when you perform an Update and set the Create audit trail field to Y (Yes) on the Output Specification screen. This screen enables you to decide what to do with the audit trail dataset just created. You can also use File-AID/Data Solutions option U.2, Print Audit Trail, to print the audit trail dataset.

Disposition of Audit Trail Screen

 File-AID/Data Solutions --- Disposition of Audit Trail ----------------
 COMMAND ===>  

 Audit trail disposition ===>            (PK = Print dataset and keep
                                         PD = Print dataset and delete
                                         D  = Delete dataset without printing  

 Audit trail dataset     ===>  

 Audit trail description ===>
                         ===>  

 Specify Batch JCL Information:
  Sysout class           ===>  

 Specify JOB Statement Information:
 ===>
 ===>
 ===>
 ===>
 Use JCL command to edit generated JCL
 Use ENTER to submit batch job
 Use END to keep audit trail without printing

Field descriptions

Audit trail disposition

Specify one of the following:

PK

Print and keep the audit trail.

PD

Print and delete the audit trail.

D

Delete the audit trail without printing it.

Audit trail dataset

File-AID/Data Solutions allocates the audit trail dataset during execution of your Data Solutions function. If your tso-prefix matches your tso-id, and no audit trail prefix (Audit trail prefix) is specified, the audit trail dataset name is:

 tso-id.DATASOL.AUDT.Dyymmdd.Thhmmss.Msss

tso-id

Your TSO user ID, up to seven characters, or up to eight characters if eight character user ID has been implemented with z/OS 2.3 or later.

Dyymmdd

Gregorian date when the audit trail is created.

Thhmmss

Hour, minute, and second the audit trail is created.

Msss

Millisecond the audit trail is created.

tso-prefix

Your TSO user prefix, up to seven characters, or up to eight characters if eight character user ID has been implemented with z/OS 2.3 or later.

If your TSO-prefix does not match your user ID and the audit data set name does not exceed 44 characters, the audit trail dataset name is:

    tso-prefix.tso-id.DATASOL.AUDT.Dyymmdd.Thhmmss.Msss

When the tso-prefix is included and the construction of the audit data set name exceeds 44 characters, then millisecond will be omitted. For example, if you had a 4 character tso-prefix and a 5 character tso-id, millisecond would be included. If you had a 4 character tso-prefix and a 7 character tso-id, millisecond would be omitted:

    tso-prefix.tso-id.DATASOL.AUDT.Dyymmdd.Thhmmss

If you specified an audit trail prefix (Audit trail prefix), the audit trail dataset name is:

    audittrailprefix.Dyymmdd.Thhmmss.Msss

Important

When no audit trail prefix is specified for a batch job, the audit trail prefix will default to the batch job name minus the last character.

Audit trail description

Enter an optional 96-position description of the update that just completed. This description is written to the audit trail dataset and prints on the Audit Trail Report.

Specify Batch JCL Information:

Sysout class

Specify the SYSOUT class for the Audit Trail Report.

Specify JOB Statement Information:

Specify the JOB statement JCL for the batch print job submitted when you specify the PK or PD options.

When you complete this screen, press <Enter> to process the option or, if you want to keep the audit trail dataset to print later, use the END command (PF3).

When the END command (PF3) was used on the Disposition of Audit Trail screen, you can use option U.2, Print Audit Trail, to print the audit trail. Print Audit Trail describes the Audit Trail Report and the Audit Trail Print feature.

Guidelines

The audit trail dataset that File-AID/Data Solutions creates is a sequential, variable-blocked spanned file. Because each audit trail record contains a File-AID control area, you cannot create an audit trail for a non-keyed file whose LRECL is greater than 32,724. For keyed files, the sum of the key length and LRECL must not exceed 32,724.

File-AID/Data Solutions writes all audit records after the Update is processed. If the number of updates written to the audit file exceeds the available audit file space, File-AID notifies you and discontinues auditing. The audit records are not written to the audit data set and cannot be recovered. File-AID/Data Solutions still displays the Disposition of Audit Trail screen.

The default amount of space allocated to the audit trail dataset by File-AID/Data Solutions is (1,5) cylinders. If you make massive changes, it is important to increase the size of the audit trail dataset. You can modify it with File-AID/Data Solutions option 0.5.

Output data set allocation

The following figure is displayed when the output data set does not exist. The allocate screen that File-AID/Data Solutions displays is based on the input data set type. The following figure shows the allocation screen for a Sequential dataset, but Data Solutions displays a VSAM or BDAM allocation screen when appropriate. Specify the allocation parameters for the new output data set.

Allocate New Dataset Screen

 File-AID/Data Solutions ----- Allocate New Dataset----------------------------
 COMMAND ===>

  Dataset name: USERID0.DASAMP.NEW  

    Management Class    ===>  SAMPLE@S (Blank for default)
    Storage Class       ===>  STDD0DFW (Blank for default)
    Data Class          ===>           (Blank for default)
                                       Specify one of the following two fields:
     Volume serial      ===>  PRD921    (Blank for authorized default volume)
     Generic unit       ===>            (Generic group name or unit)  

     Space units        ===>  TRKS      (TRKS; CYLS; BLKS)
     Primary quantity   ===>  1         (In above units)
     Secondary quantity ===>  1         (In above units)
     Directory quantity ===>  0         (Partitioned only)
     Record format      ===>  FB
     Record length      ===>  80
     Block size         ===>  3120
     Expiration date    ===>            (YYYY/MM/DD or blank)
     Dataset Name Type  ===>            (Library, PDS, LArge, or blank)

  Number of Volumes  ===>  N            (N = None; Y = Multiple VOLSERs:
                                        or enter generic volume count)

Field descriptions

The displayed values can be accepted or changed by overtyping them.

Dataset name

Name of new data set specified in the Output Dataset name field on the Output Specification screen.

Management Class

Specify the management class to use for the allocation of the data set. The management class describes the migration, backup, and retention for the data set.

Storage Class

Specify the storage class to use for the allocation of the data set. The storage class describes the hardware requirements of the data set.

Data Class

Specify the data class to use for the allocation of the data set. The data class describes the attributes of the data set such as RECFM, DSORG, LRECL, BLKSIZE, etc.

Specify Allocation Parameters:

Volume serial

Specify the volume serial of the direct access device that you want to contain the data set. Specify the location in either the Volume serial or Generic unit field.

Generic unit

Generic unit address for the direct access volume to contain the data set. Specify the location in either the Volume serial or Generic unit field.

Space units

Specify one of the following storage unit types depending on how the data set size is expressed:

TRKS

Tracks

CYLS

Cylinders

BLKS

Number of blocks.

Primary quantity

Specify the primary allocation quantity as specified in the space units field.

Secondary quantity

Specify the secondary allocation quantity as specified in the space units field.

Directory quantity

For a PDS, specify the number of directory blocks.

Record format

Specify a value with a combination of the following codes (F, V, or U is required):

F

Fixed length

V

Variable length

U

Undefined format

B

Blocked

A

ANSI printer control characters

M

Machine code printer control characters

S

For Sequential data sets only: Standard for F or spanned for V.

T

Track-overflow feature.

Record length

Specify a logical record length, in bytes, of the records to be stored in the data set. File-AID/Data Solutions validates this value with the record format and block size.

Block size

Specify the physical record length, in bytes, of the blocks to be stored in the data set. File-AID/Data Solutions validates this value with the record format and record length.

Important

For DFP version 3 and all DFSMS users, if you specify 0 or do not enter a block size, the system determines an optimum block size for the direct access device assigned to the data set.

Expiration date

(Optional) Specify a date value in the format: YYYY/MM/DD. This value specifies the date when the data set may be deleted. If this field is left blank, the data set can be deleted immediately.

Dataset name type

Specify the type of new dataset name. Valid entries are: Library, PDS, LArge, or blank (default).

Important

Entering LArge in this field specifies a LARGE format sequential data set, which is supported in z/OS 1.7 and above. The initial allocation of the data set does not have to exceed 65,535 tracks; the combined space allocated by primary and secondary allocations is allowed to exceed 65,535 tracks when the data set is allocated as LARGE. There is still a limit of 16 extents for data set allocation. Data sets defined with DSNTYPE=LARGE can be either SMS or non-SMS managed.

Number of Volumes

Specify whether you want to allocate the data set on multiple volumes. Valid entries are Y (Yes), N (No), or a number from 2 to 255 for the number of generic volumes to allocate. When you specify Y, File-AID/Data Solutions displays the Specify Volume Serial Numbers pop-up window. You may enter up to 40 specific volume serial numbers.

Press <Enter> to allocate the data set, or use the END command (PF3) to cancel the allocation. When allocation is complete, Data Solutions displays the message: DATASET ALLOCATED in the upper-right corner of the screen. If an error occurs (such as duplicate data set name), Data Solutions displays the appropriate error message. Use the HELP command (PF1) to obtain information on the error.


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*