In batch, compilation occurs when a COMPILE command is invoked. In CA Ideal, job streams are stored. You can submit them from a member containing the JCL for batch CA Ideal. Submitting a batch job stream is described in the Working in the Environment Guide. The procedure name IDBATCH can change from site to site. See your CA Ideal administrator for procedure names at your site.
The following are sample job streams for compiling a program in Z/OS and VSE:
z/OS Job Stream
//COMP1 JOB . . .
//BATCH EXEC IDLBATCH,PARM='NOPRINT'
//IDEAL.COMPLIST DD SYSOUT=A
//IDEAL.SYSIN DD *
PERSON userid PASSWORD password
SELECT SYSTEM DOC
{ LIB }
COMPILE COMP1 VERSION 1 DESTINATION { SYS name }
{ }
OFF
VSE Job Stream
* $$ JOB JNM=IDBATCH,PRI=n,USER='username',DISP=D
* $$ LST DISP=x,CLASS=x,LST=cuu...
// JOB IDBATCH
// OPTION LOG,NODUMP
// EXEC PROC=IDLPROC,PARM='NOPRINT'
*
// EXEC IDBATCH,SIZE=80K
PERSON userid PASSWORD password
SELECT SYSTEM DOC
{ LIB }
COMPILE COMP1 VERSION 1 DESTINATION { SYS name }
OFF { }
/*
// EXEC LISTLOG
/*
/&
* $$ EOJ
Note: JCL statements for work files and sort work files are necessary for compiles executed with the XREF=FULL or SHORT options.
In the job stream examples above, the DESTINATION clause of the COMPILE command is the output library or a system printer. You can monitor the status of a compilation directed to the output library by displaying the output library. As soon as the compile starts to execute, its status in the library is CRTIN. When the status is READY, the compile has finished executing.
The information in the compilation listing is output in the sequence listed below. For more information and a complete example, see the Sample List appendix.
Displays available compile options for processing and listings. For each option, Yes signifies that the option is on, No signifies that the option is off. For more information, see the description of the SET COMPILE command in the Command Reference Guide.
Displays descriptive information about the program's creation, last edit access, and last compilation. The run status and a short description of the program also display. For more information, see Creating a New Program Definition.
Lists all external components accessed by the procedure, namely dataviews, panels, reports, and other called programs. For more information, see Defining Program Resources.
Displays the components of each dataview accessed by the procedure. For more information, see the Creating Dataviews Guide.
Displays descriptive information about the panel's creation and last edit access. A short description of the panel also displays. For more information, see the Creating Panel Definitions Guide.
Displays a panel representation. For more information, see the Creating Panel Definitions Guide.
Displays a panel as it appears when a program is run. The symbols described in Panel Layout do not appear on this screen. For more information, see the Creating Panel Definitions Guide.
Displays a table that describes each field identified on the panel. For more information, see the Creating Panel Definitions Guide.
Displays input and output fill characters, panels used as help, prefix or suffix panels, and other general options for panel definition. For more information, see the Creating Panel Definitions Guide.
Displays a table that describes the input each field accepts. This information is also found in the Extended Field Definition. For more information, see the Creating Panel Definitions Guide.
Displays a table that describes the output each field displays. This information is also found in the Extended Field Definition. For more information, see the Creating Panel Definitions Guide.
Displays data that is local to the program. For more information, see Defining Working Data.
Displays a listing of names and descriptions of data items that are passed to the program from the calling program. You can also define a parameter in a main (calling) program if it is issued in a RUN command for that program. For more information, see Defining Parameters Used as Input.
Displays descriptive information about the report's creation and last edit access. A short description of the report also displays. For more information, see the Generating Reports Guide.
Displays report layout options such as a report's length and width on a page, the spacing between lines and columns, column headings and how they are highlighted, control breaks, group continuation indication, heading definitions, summary information, and date and page specification. For more information, see the Generating Reports Guide.
Displays the page heading used in the report. The position or location of the page heading is specified. You can use field names, literals, functions, and arithmetic expressions as part of a page heading. For more information, refer the Generating Reports Guide.
Displays the fields to appear in each detail line of the body of the report and specifies sorting, control breaks, summary functions, and so on for these fields. For more information, see the Generating Reports Guide.
Displays a listing of program logic for the application. For complete syntax of all the PDL statements, see the Programming Reference Guide.
Displays SQL generated to support FOR constructs for the current compile. For more information on the SET COMPILE LSQL command, see the Command Reference Guide.
Displays a listing in ascending sequence of the symbols from components the procedure accesses. This listing appears when it is the site default or when the SET COMPILE REF command equals FULL (this is the default). For more information, see the next section.
The compile cross reference listing displays the symbols accessed in the procedure. It is included in batch compilation output when it is the site default or when the command SET COMPILE REF is FULL or SHORT. For an example, see appendix Sample Lists.
The following information displays in the compile cross reference listing:
For DB2 columns, any table or view name that qualifies a column name. For DB2 correlation names, the DB2 qualification (auth-id.table-name).
The entity type PRC is always given to labels.
This column is blank for subprogram names, report names, pseudo functions, and fields in error.
This column contains a value only when type is N, U, or D. For non-numeric data types, this column is blank.
This column is blank for subprogram names, report names, pseudo functions, and fields in error.
200, 300-U
You can reference identifiers, literals, pseudo-functions, and figurative constants in reports and in the procedure. You can reference condition names and labels only in procedures. Symbol names that are referenced in a report have an indicator RPT in front of all references in that entity.
References in the procedure appear first, followed by references in a report. For example:
|
Symbol |
References |
|
FIELDX |
200 300-U 400 RPT RPTX 200 |
The value of FIELDX is referenced at statement numbers 200, 300, and 400 in the procedure. FIELDX is also referenced at sequence number 200 in report RPTX.
The program lists:
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|