├── DEFine PACkage ─ package-id ──────────────────────────────────────────────► ►─┬─ COPy ─┬────────┬ ─ PACkage ─ package-id ────────────────────────────┬───► │ └─ FROm ─┘ │ └─ IMPort SCL FROm ─┬─ DDName ─ ddname ──────────────────────────────┬─┘ └─ DSName ─ 'dsname' ─┬────────────────────────┬─┘ └─ MEMber ─ member-name ─┘ ►─┬───────────────────┬──────────────────────────────────────────────────────► ├─ DO NOT APPEnd ◄ ─┤ └─ APPEnd ──────────┘ ►─ DEScription ─ description-text ─┬───────────────────────┬─ . ──────────────┤ └─ OPTion ─┤ OPTIONS ├ ─┘
Expansion of OPTIONS
├── ¤ ─┬─┬─ STANdard ◄ ─┬─┬───────────┬────────┬─ ¤ ───────────────────────────┤ │ └─ EMErgency ──┘ └─ PACkage ─┘ │ ├─┬─ NONsharable ◄ ─┬─┬───────────┬─────┤ │ └─ SHArable ──────┘ └─ PACkage ─┘ │ ├─┬─ BACKOut ─┬──────┬ ─ ENAbled ◄ ───┬─┤ │ │ └─ IS ─┘ │ │ │ └─ BACKout ─┬──────┬ ─ NOT ENAbled ─┘ │ │ └─ IS ─┘ │ ├─ EXECUTion WINdow ─┤ FROM TO ├ ───────┤ │ ┌─ , ─────────┐ │ ├─ NOTEs ─ = ─ ( ─▼─ note_text ─┴─ ) ───┤ ├─ DO NOT VALIDATE SCL ─────────────────┤ └─┬─ NONPromotion ◄ ─┬─┬───────────┬────┘ └─ PROMotion ──────┘ └─ PACkage ─┘
Expansion of FROM TO
├── FROm ─ from-date ─ from-time ─┬──────────────────────────┬─────────────────┤ └─ TO ─ to-date ─ to-time ─┘
DEFINE PACKAGE package-id
The DEFINE PACKAGE clause identifies the package you are creating or updating. An update occurs if the package ID exists and a create occurs if it does not exist.
You must use a fully specified non-blank package ID. If you specify a blank package ID and have the GENPKGID exit defined, the GENPKGID exit invokes to generate a new package ID. If you do not have the GENPKGID exit installed or if the GENPKGID exit does not supply a package ID, an error message generates and the DEFINE PACKAGE action fails.
To specify a blank package ID place one or more blanks in single or double quotation marks as the DEFINE PACKAGE package-id statement. A blank package ID implies that the package is to be created.
Note: For more information about the GENPKID exit function, see the Exits Guide.
COPY FROM PACKAGE package-id
The COPY FROM PACKAGE clause directs the DEFINE action to copy the SCL from the package you specify into the package you are creating or updating. You must use a fully specified package ID.
If you are creating a new package you must specify either the COPY FROM PACKAGE or the IMPORT SCL FROM clause. If you are updating an existing package, the clauses are optional.
IMPORT SCL FROM
The IMPORT SCL FROM clause directs the DEFINE action to copy the SCL from the DD statement or data set name you specify into the package you are creating or updating.
If you are creating a new package you must specify either the COPY FROM PACKAGE or the IMPORT SCL FROM clause. If you are updating an existing package, the clauses are optional.
APPEND/DO NOT APPEND
The APPEND clause indicates whether to append the SCL you are adding to the existing package SCL or to replace it. You can only use the clause if you specify the COPY PACKAGE or IMPORT SCL FROM clauses. The default is DO NOT APPEND.
DESCRIPTION
The DESCRIPTION clause allows you to associate a 50-character description with the package. You must specify this clause if you are creating a new package. If you are updating an existing package the clause is optional. If the description text contains imbedded spaces enclose it in single quotation marks. The description text you enter is not converted to uppercase. Lowercase characters remain in lowercase.
OPTIONS
OPTION clauses allow you to further specify package actions.
STANDARD/EMERGENCY PACKAGE-This option allows you to specify the package type. If you do not specify the STANDARD/EMERGENCY PACKAGE clause and you are creating a new package, the package defaults to a STANDARD package.
SHARABLE/NONSHARABLE PACKAGE-This option allows you to specify whether this package can be edited by more than one person when in In-edit status. If the package is sharable it can be edited by someone other than the package creator. If the package is non-sharable it can only be edited by its creator. If you do not specify the SHARABLE/NONSHARABLE PACKAGE clause and you are creating a new package, the package defaults to a NONSHARABLE package.
BACKOUT IS ENABLED/NOT ENABLED-The BACKOUT IS ENABLED/NOT ENABLED option indicates whether you wish to have the backout facility available for this package. Use this clause when creating a new package only. The default is BACKOUT IS ENABLED.
PROMotion/NONPromotion PACkage-This option lets you define the package as a promotion package or a nonpromotion package. If you do not specify the PROMOTION/NONPROMOTION PACKAGE clause and you are creating a new package, the package defaults to a NONPROMOTION package.
EXECUTION WINDOW FROM from-date from-time TO to-date to-time-This option allows you to specify the time frame within which to execute the package. Specify date values in DDMMMYY format and the time values in HH:MM format.
If you specify the from-date, you must also specify the from-time. If you specify neither the from-date nor the from-time and you are creating a new package, the from-date and the from-time default to the current date and time, respectively.
If you specify the to-date, you must also specify the to-time. If you specify neither the to-date nor the to-time and you are creating a new package, the to-date and the to-time default to 31DEC79 and 00:00, respectively.
NOTES-Use the NOTES clause to add remarks to the package definition. Enclose the note text in either single or double quotation marks. If you use multiple text lines, enclose all the lines in parentheses () and enclose each text line in single quotation marks, separated with a comma. You can specify up to 8 text lines of up to 60 characters each. A note line cannot be split across syntax lines (that is, the beginning and ending quote must be on the same line). The text including the last quote cannot exceed column 72. The text replaces any text which is already associated with the package.
DO NOT VALIDATE SCL-If you specify the DO NOT VALIDATE SCL option, the package components are not validated while creating or updating a package.
Example: Define Package SCL
The following is an example of DEFINE PACKAGE SCL. The SCL defines a new package called PAYROLLPKG01, to be used to implement a new payroll system. The SCL is copied from the data set specified by the IMPORT SCL FROM DSNAME clause.
DEFINE PACKAGE PAYROLLPKG01
DESCRIPTION 'PACKAGE TO IMPLEMENT THE NEW PAYROLL SYSTEM'
IMPORT SCL FROM DSNAME 'PAY.PACKAGE.SCL' MEMBER 'ADDSCL01'
OPTIONS EXECUTION WINDOW FROM 01JAN93 00:01 TO 31DEC93 23:59
BACKOUT IS ENABLED
SHARABLE PACKAGE
STANDARD PACKAGE
NOTES=('THIS PACKAGE IMPLEMENTS THE NEW PAYROLL SYSTEM.',
'THE SCL FOR THIS PACKAGE WAS IMPORTED','FROM SERVICE PACK SP01.',
'THE PACKAGE MUST BE CAST AND APPROVED BY JUNE 30.').
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|