HLASM Toolkit Feature User's Guide
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Spreadsheet Oriented Report (SOR)

HLASM Toolkit Feature User's Guide
GC26-8710-10

The Spreadsheet Oriented (SOR) report is a comma-delimited file that you can import into a spreadsheet application, such as Lotus 1-2-3, to estimate effort and impact assessment.

On CMS ASMXREF creates the SOR in a file named filename OUTSOR A, where filename is the name of the control file.

on z/OS, the default name for the SOR, defined in the procedure supplied with ASMXREF, is userid.XREFOUT.SOR.

On z/VSE the SOR is printed from SYSPRT.

The Spreadsheet Oriented report shows occurrences of specified tokens in the search library. Default tokens are specified in the XRFLANG file; tokens you have specified are contained in your XRFTOKN token file. For details on the default tokens see ASMXREF XRFLANG Statements. For details of the TOKEN control statements see ASMXREF Token Statement. The first record for each token set in the report is the "heading" record with the following quoted strings:
  • Member Name
  • Lines Of Code
  • Total Matches
  • token_1
  • token_n

The remaining records are detail records containing the module name, the number of lines of code, the total matches for the module, and the number of matches for each token.

The report segments each header and detail record in 80 byte segments, with the last segment having an EBCDIC CR (carriage return) and a LF (line feed) character. The report pads each record with spaces to fill the 80 characters. The report specifies the carriage return and line feed characters with a <.

Set title delimiters and cell separator characters with the report parameters. For details on the report parameters see ASMXREP Options.

When you run the ASMXREF scan phase, for the SOR report, ASMXREF generates the TSP (Tagged Source Program). The ASMXREF report phase uses the Tagged Source Program to create the SOR report.
Figure 1. Sample Spreadsheet Oriented Report for z/OS and CMS
'Module ID','LOC','Total Matches','*DATE','*YR','=C'20','=P'20','CSECT','DAT*',
'DATE','DAY','DD/MM/YY','MM/DD/YY','MM/YY','MONTH','TIME','YEAR','YR','YY/MM/DD'
','YYDDD'

ASMTEST,0069,0007,0002,0000,0000,0000,0001,0004,0000,0000,0000,0000,0000,0000,00
00,0000,0000,0000,0000
Figure 2. Sample Spreadsheet Oriented report for z/VSE
'Module ID','LOC','Total Matches','*DATE','*YR','=C'20','=P'20','CSECT','DAT*','
'DATE','DAY','DD/MM/YY','MM/DD/YY','MM/YY','MONTH','TIME','YEAR','YR','YY/MM/DD
','YYDDD'

ASMTEST,0069,0007,0002,0000,0000,0000,0001,0004,0000,0000,0000,0000,0000,0000,00
00,0000,0000,0000,0000

/+
/*
Note: When you create the Spreadsheet Oriented report on z/VSE, it generates two records at the end of the file:
/+
/*

Before importing the file into a spreadsheet, delete these records.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014