ACCT Parameter

Purpose

The ACCT parameter specifies accounting information for a particular job step. While the JOB statement includes accounting information for the entire job, the ACCT parameter on the EXEC statement provides step-specific accounting information. This allows organizations to track resource usage, charge for computer time, and allocate costs at the step level.

Syntax

On the EXEC Statement

jcl
1
2
3
//stepname EXEC PGM=program,ACCT=accounting-information
//stepname EXEC PROC=procedure,ACCT=accounting-information
//stepname EXEC PROC=procedure,ACCT.procstep=accounting-information

Format

The ACCT parameter can be specified in several formats, depending on your installation's accounting requirements:

  • Single value: ACCT=number
  • Multiple subparameters: ACCT=(subparam1,subparam2,...)
  • Procedure step specific: ACCT.procstep=(subparam1,subparam2,...)
  • Omitting the parameter: If omitted, the step uses the accounting information from the JOB statement

Accounting Data Format

The format of accounting information is installation-defined and can vary widely between organizations. Common formats include:

FormatExampleDescription
Single numberACCT=123456Simple account number
Department and projectACCT=(D123,P456)Department D123, Project P456
Complex structureACCT=(1234,SMITH,'PAYROLL',50)Account, user, application, minutes
Specific to procedure stepACCT.STEP1=(1234,SMITH)Account info for STEP1 in a procedure

Examples

Basic Usage

jcl
1
//STEP1 EXEC PGM=PAYROLL,ACCT=45678

Specifies account number 45678 for the STEP1 step.

Multiple Subparameters

jcl
1
//STEP2 EXEC PGM=REPORT,ACCT=(DEPT27,PROJECT3,USER01)

Provides more detailed accounting information with multiple fields.

With a Procedure

jcl
1
//STEP3 EXEC PROC=MONTHLY,ACCT=(A123,50,SMITH)

Specifies accounting information for all steps in the MONTHLY procedure.

For a Specific Procedure Step

jcl
1
//STEP4 EXEC PROC=PAYROLL,ACCT.CALC=(FINANCE,30),ACCT.PRINT=(ADMIN,10)

Provides different accounting information for the CALC and PRINT steps within the PAYROLL procedure.

Combined with Other Parameters

jcl
1
//STEP5 EXEC PGM=SORT,REGION=2M,TIME=5,ACCT=(DEPT01,'SORT UTILITY',15)

Combines ACCT with other EXEC parameters for complete step control.

Processing Details

  • Collection Process: The operating system collects ACCT parameter information during step initialization
  • SMF Records: Accounting information is written to System Management Facilities (SMF) records
  • Accounting Applications: Organizations use SMF record data to perform billing and resource tracking
  • Defaults: If ACCT is omitted, the accounting information from the JOB statement is used
  • Installation-Specific: Many sites use installation-specific SMF exits to enhance accounting data

Use Cases

Cost Allocation

  • Track computing costs by department
  • Bill users or departments for resources used
  • Allocate costs for specific applications or projects

Resource Management

  • Monitor resource usage patterns by application
  • Identify resource-intensive steps
  • Plan capacity based on departmental usage

Auditing and Compliance

  • Track who ran specific job steps
  • Record purpose of processing for audit trails
  • Document resource usage for regulatory compliance

Budgeting

  • Compare actual resource usage against budgeted amounts
  • Forecast future computing needs
  • Justify IT expenses based on departmental usage

Security Considerations

  • Validation: Many installations validate accounting information against authorized values
  • Authorization: Users may be restricted to using only certain account numbers
  • Audit Trails: ACCT information creates an audit trail of resource usage
  • Access Control: Security systems may use accounting data for access decisions

Relationship to JOB Accounting Information

AspectJOB Statement AccountingACCT Parameter
ScopeEntire jobSpecific step
RequiredOften required by installationOptional
Default behaviorN/A (must be specified if required)Uses JOB accounting info if omitted
PositionFirst positional parameterKeyword parameter

Limitations

  • Installation-Dependent: Format and meaning of accounting information varies by installation
  • No Standardization: Unlike many JCL parameters, there's no standard format across z/OS installations
  • Limited Validation: The system doesn't validate accounting data format unless installation exits are added
  • Historical Usage: Many modern environments rely less on ACCT for billing purposes than in the past
  • Storage Limitations: Total length of accounting data is limited

Common Mistakes

  • Using incorrect account numbers: Specifying invalid or unauthorized account numbers
    jcl
    1
    //STEP1 EXEC PGM=REPORT,ACCT=999999  // Error if 999999 is not valid
  • Incorrect subparameter format: Not following installation-specific accounting data format
    jcl
    1
    //STEP2 EXEC PGM=PAYROLL,ACCT=DEPT123  // Error if numeric format expected
  • Missing parentheses: Forgetting to enclose multiple subparameters in parentheses
    jcl
    1
    //STEP3 EXEC PGM=INVENTORY,ACCT=D123,P456  // Should be ACCT=(D123,P456)
  • Incorrect procedure step reference: Specifying a non-existent procedure step name
    jcl
    1
    //STEP4 EXEC PROC=MONTHLY,ACCT.STEP9=12345  // Error if STEP9 doesn't exist
  • Inconsistent accounting info: Using different formats across jobs, making reporting difficult

Best Practices

  • Consistent format: Use consistent accounting information formats across all JCL
  • Documentation: Document the meaning and expected format of accounting fields
  • Validation: Implement validation of account numbers before job submission
  • Automation: Use automation tools to inject correct accounting information
  • Periodic review: Regularly review and update accounting information for accuracy
  • Default when appropriate: Only specify ACCT when different from JOB statement accounting
  • Templates: Provide templates showing correct accounting format for users

Related Concepts

Related Pages