Report generation - Revision history

JAL: /* Directing output to a journal/audit trail */ use syntax template and mixed case

2018-05-18T21:12:14Z

Directing output to a journal/audit trail: use syntax template and mixed case

← Older revision		Revision as of 21:12, 18 May 2018
Line 626:		Line 626:
	If production of a journal and/or an audit trail has been specified for the run, output can be directed to these data sets by using the <var>Audit</var> statement. The <var>Audit</var> statement is the same as the <var>Print</var> statement, substituting the keyword <code>Audit</code> for the <code>Print</code> keyword (see [[#The PRINT statement\|The PRINT statement]] for a description of the <var>Print</var> statement). </p>		If production of a journal and/or an audit trail has been specified for the run, output can be directed to these data sets by using the <var>Audit</var> statement. The <var>Audit</var> statement is the same as the <var>Print</var> statement, substituting the keyword <code>Audit</code> for the <code>Print</code> keyword (see [[#The PRINT statement\|The PRINT statement]] for a description of the <var>Print</var> statement). </p>

	===~~AUDIT ALL INFORMATION~~ statement===		===Audit All Information statement===
	<p>		<p>
	The ~~AUDIT ALL INFORMATION~~ (or AAI) statement writes the output of entire records to the audit trail, CCAAUDIT. </p>		The <var>Audit All Information</var> (or <var>AAI</var>) statement writes the output of entire records to the audit trail, CCAAUDIT. </p>
	<p>		<p>
	The output is identical to the output from the <var>[[Basic SOUL statements and commands#PRINT ALL INFORMATION (or PAI) statement\|Print All Information]]</var> (or <var>PAI</var>) statement but each field=value pair is sent to the audit trail as a series of US lines.</p>		The output is identical to the output from the <var>[[Basic SOUL statements and commands#PRINT ALL INFORMATION (or PAI) statement\|Print All Information]]</var> (or <var>PAI</var>) statement, but each field=value pair is sent to the audit trail as a series of US lines.</p>
	<p>		<p>
	The ~~AUDIT ALL INFORMATION~~ statement occurs in a ~~FOR EACH RECORD~~ or ~~FOR RECORD NUMBER~~ loop.</p>		The <var>Audit All Information</var> statement occurs in a <var>For Each Record</var> or <var>For Record Number</var> loop. </p>

	====Syntax====		====Syntax====
	~~<p class="code">AUDIT ALL INFORMATION [CTOFIELDS]~~		{{Template:Audit All Information statement syntax}}
	~~</p>~~		Where:
	<p>		<p>
	or</p>		<var>CtoFields</var> specifies to print the counter (CTO) field(s). By default CTO fields are not printed.</p>
	~~<p class="code">AAI [CTOFIELDS]~~
	</p>
	~~Where:~~
	<p>~~CTOFIELDS~~ specifies to print the counter (CTO) field(s). By default CTO fields are not printed.</p>

	===~~AUDIT~~ output===		===Audit output===
	<p>		<p>
	~~AUDIT~~ statement output is directed to the journal, the audit trail, or both, depending upon which is included in the run. The ~~AUDIT~~ statement directs the information to the journal or audit trail where it is printed with the prefix US. </p>		<var>Audit</var> statement output is directed to the journal, the audit trail, or both, depending upon which is included in the run. The <var>Audit</var> statement directs the information to the journal or audit trail where it is printed with the prefix <code>US</code>. </p>
	<p>		<p>
	If an ~~AUDIT~~ message is too long to fit on one line, it is continued on a second line with the prefix XX rather than US.</p>		If an <var>Audit</var> message is too long to fit on one line, it is continued on a second line with the prefix <code>XX</code> rather than <code>US</code>. </p>
	<p>		<p>

	[[Tracking system activity (CCAJRNL, CCAAUDIT, CCAJLOG)\|Tracking system activity]] contains a complete description of the journal and audit trail.</p>		[[Tracking system activity (CCAJRNL, CCAAUDIT, CCAJLOG)\|Tracking system activity]] contains a complete description of the journal and audit trail. </p>

	====Example====		====Example====
Line 666:		Line 662:
	</p>		</p>
	<p>		<p>
	In the previous statement, the $~~USERID~~ function is used to obtain the ID of the user making the change. The statement produces the following audit trail record when it is executed:</p>		In the previous statement, the <var>$Userid</var> function is used to obtain the ID of the user making the change. The statement produces the following audit trail record when it is executed: </p>
	<p class="~~code~~">86123110011 1 1 135 US SMITH HAS CHANGED SALARY FROM 20344 TO 45888		<p class="output">86123110011 1 1 135 US SMITH HAS CHANGED SALARY FROM 20344 TO 45888
	</p>		</p>

	===Using the ~~AUDIT~~ and ~~PRINT~~ statements together===		===Using the Audit and Print statements together===
	<p>		<p>
	If the ~~AUDIT~~ statement ends in an ellipsis (...), it can be added to with ~~PRINT~~ or ~~SET~~ statements. For example: </p>		If the <var>Audit</var> statement ends in an ellipsis (<tt>...</tt>), it can be added to with <var>Print</var> or <var>Set</var> statements. For example, the following statements produce <code>US BEGIN123END</code> in the audit trail: </p>
	<p class="code">AUDIT 'BEGIN' ...		<p class="code">AUDIT 'BEGIN' ...
	PRINT '123' ...		PRINT '123' ...
	PRINT 'END'		PRINT 'END' </p>
	~~</p>~~
	~~<p>~~
	~~produces US BEGIN123END in the audit trail.~~</p>
	<p>		<p>
	If the ~~AUDIT~~ statement follows a normal ~~PRINT~~ statement that ends in an ellipsis, the ~~PRINT~~ line is ended by the ~~AUDIT~~ statement. The ~~PRINT~~ line ends when the ~~AUDIT~~ line begins.</p>		If the <var>Audit</var> statement follows a normal <var>Print</var> statement that ends in an ellipsis, the <var>Print</var> line is ended by the <var>Audit</var> statement. The <var>Print</var> line ends when the <var>Audit</var> line begins.</p>

	===Printing records using ~~AUDIT~~===		===Printing records using Audit===
	<p>		<p>
	If a record is printed by means of an ~~AUDIT~~ statement, the lines printed by the user can be broken, and the partial lines intermixed with lines printed by another user in an online system. </p>		If a record is printed by means of an <var>Audit</var> statement, the lines printed by the user can be broken, and the partial lines intermixed with lines printed by another user in an online system. </p>
	<p>		<p>
	This problem can be alleviated by assigning the field value to a variable (see [[Using variables and values in computation#Field name variables\|Field name variables]]) and then referring to the variable in the ~~AUDIT~~ statement, or by using a ~~NOTE~~ statement and referring to it with a ~~VALUE IN~~ phrase in the ~~AUDIT~~ statement. </p>		This problem can be alleviated by assigning the field value to a variable (see [[Using variables and values in computation#Field name variables\|Field name variables]]) and then referring to the variable in the <var>Audit</var> statement, or by using a <var>Note</var> statement and referring to it with a <code>Value In</code> phrase in the <var>Audit</var> statement. </p>
	<p>		<p>
	See [[Record loops#Noting character strings\|Noting character strings]] for more information about the ~~NOTE~~ statement and the ~~VALUE IN~~ phrase. </p>		See [[Record loops#Noting character strings\|Noting character strings]] for more information about the <var>Note</var> statement and the <var>Value In</var> phrase. </p>

	==Directing output to other devices==		==Directing output to other devices==

JAL: /* AUDIT statement */ mixed case for stmts

2018-05-18T20:37:48Z

AUDIT statement: mixed case for stmts

← Older revision		Revision as of 20:37, 18 May 2018
Line 622:		Line 622:
	==Directing output to a journal/audit trail==		==Directing output to a journal/audit trail==

	===~~AUDIT~~ statement===		===Audit statement===
	<p>		<p>
	If production of a journal and/or an audit trail has been specified for the run, output can be directed to these data sets by using the ~~AUDIT~~ statement. The ~~AUDIT~~ statement is the same as the ~~PRINT~~ statement, substituting the keyword ~~AUDIT~~ for the ~~PRINT~~ keyword (see [[#The PRINT statement\|The PRINT statement]] for a description of the ~~PRINT~~ statement). </p>		If production of a journal and/or an audit trail has been specified for the run, output can be directed to these data sets by using the <var>Audit</var> statement. The <var>Audit</var> statement is the same as the <var>Print</var> statement, substituting the keyword <code>Audit</code> for the <code>Print</code> keyword (see [[#The PRINT statement\|The PRINT statement]] for a description of the <var>Print</var> statement). </p>

	===AUDIT ALL INFORMATION statement===		===AUDIT ALL INFORMATION statement===
	<p>		<p>

ELowell: /* Version 7.4 limitation */

2016-09-19T16:32:45Z

Version 7.4 limitation

← Older revision		Revision as of 16:32, 19 September 2016
Line 176:		Line 176:
	<p>In Model 204 version 7.4, there is a limit of 127 on the number of fields that can be added in a PRINT statement using a subscripted variable. If you are currently adding more than this number, the following message will be issued:</p>		<p>In Model 204 version 7.4, there is a limit of 127 on the number of fields that can be added in a PRINT statement using a subscripted variable. If you are currently adding more than this number, the following message will be issued:</p>
	<p class="code">M204.2840: STATEMENT HAS TOO MANY INTERMEDIATE RESULTS</p>		<p class="code">M204.2840: STATEMENT HAS TOO MANY INTERMEDIATE RESULTS</p>
	<p>The issue has been resolved in SirMods 8.1. Therefore, the best solution for 7.4 is to rerun the job with a load module that includes SirMods 8.1 linked in~~; for example, FRELOAD instead of BATCH204~~. As of version 7.5, SirMods is totally integrated into the Model 204 nucleus, so no special linking is required.</p>		<p>The issue has been resolved in SirMods 8.1. Therefore, the best solution for Model 204 version 7.4 is to rerun the job with a load module that includes SirMods 8.1 linked in. As of Model 204 version 7.5, SirMods is totally integrated into the Model 204 nucleus, so no special linking is required.</p>

	==Formatting/printing headers or comments==		==Formatting/printing headers or comments==

ELowell: /* PRINT statement */

2016-09-16T21:25:25Z

PRINT statement

← Older revision		Revision as of 21:25, 16 September 2016
Line 173:		Line 173:
	<p class="code">FOR2100547 FOR2101155		<p class="code">FOR2100547 FOR2101155
	</p>		</p>
			===Version 7.4 limitation===
			<p>In Model 204 version 7.4, there is a limit of 127 on the number of fields that can be added in a PRINT statement using a subscripted variable. If you are currently adding more than this number, the following message will be issued:</p>
			<p class="code">M204.2840: STATEMENT HAS TOO MANY INTERMEDIATE RESULTS</p>
			<p>The issue has been resolved in SirMods 8.1. Therefore, the best solution for 7.4 is to rerun the job with a load module that includes SirMods 8.1 linked in; for example, FRELOAD instead of BATCH204. As of version 7.5, SirMods is totally integrated into the Model 204 nucleus, so no special linking is required.</p>

	==Formatting/printing headers or comments==		==Formatting/printing headers or comments==

ELowell: /* AUDIT output */

2015-08-06T20:18:25Z

AUDIT output

← Older revision		Revision as of 20:18, 6 August 2015
Line 646:		Line 646:
	If an AUDIT message is too long to fit on one line, it is continued on a second line with the prefix XX rather than US.</p>		If an AUDIT message is too long to fit on one line, it is continued on a second line with the prefix XX rather than US.</p>
	<p>		<p>
	~~The~~
	~~<var class="book">~~[~~http://www.rocketsoftware.com/m204/products/model204/documentation/v7r4/M204-System-Mgr/view Rocket Model 204 System Manager's Guide~~]~~</var>~~ contains a complete description of the journal and audit trail. </p>		[[Tracking system activity (CCAJRNL, CCAAUDIT, CCAJLOG)\|Tracking system activity]] contains a complete description of the journal and audit trail.</p>

	====Example====		====Example====
Line 665:		Line 665:
	<p class="code">86123110011 1 1 135 US SMITH HAS CHANGED SALARY FROM 20344 TO 45888		<p class="code">86123110011 1 1 135 US SMITH HAS CHANGED SALARY FROM 20344 TO 45888
	</p>		</p>

	===Using the AUDIT and PRINT statements together===		===Using the AUDIT and PRINT statements together===
	<p>		<p>

ELowell: /* Syntax */

2015-08-06T20:01:46Z

Syntax

← Older revision		Revision as of 20:01, 6 August 2015
Line 638:		Line 638:
	</p>		</p>
	Where:		Where:
	CTOFIELDS specifies to print the counter (CTO) field(s). By default CTO fields are not printed.		<p>CTOFIELDS specifies to print the counter (CTO) field(s). By default CTO fields are not printed.</p>

	===AUDIT output===		===AUDIT output===

ELowell: /* Syntax */

2015-08-06T20:00:34Z

Syntax

← Older revision		Revision as of 20:00, 6 August 2015
Line 631:		Line 631:

	====Syntax====		====Syntax====
	<p class="code">AUDIT ALL INFORMATION		<p class="code">AUDIT ALL INFORMATION [CTOFIELDS]
	</p>		</p>
	<p>		<p>
	or</p>		or</p>
	<p class="code">AAI		<p class="code">AAI [CTOFIELDS]
	</p>		</p>
			Where:
			CTOFIELDS specifies to print the counter (CTO) field(s). By default CTO fields are not printed.

	===AUDIT output===		===AUDIT output===
	<p>		<p>

ELowell: /* Use of quotation marks */

2014-11-11T20:12:09Z

Use of quotation marks

← Older revision		Revision as of 20:12, 11 November 2014
Line 190:		Line 190:
	===Use of quotation marks===		===Use of quotation marks===
	<p>		<p>
	The pair of single quotation marks delineates the quoted string. Any character that appears within the quotation marks (including space) is considered part of the text to be printed. A pair of consecutive single quotation marks (<tt>''</tt>) embedded in quoted text reproduces a single quotation mark in the output. Thus: </p>		The pair of single quotation marks delineates the quoted string. Any character that appears within the quotation marks (including space) is considered part of the text to be printed. A pair of consecutive single quotation marks (<tt>''</tt>) embedded in quoted text reproduces a single quotation mark in the output. Thus: </p>
	<p class="code">PRINT 'WHY JOHNNY CAN''T READ'		<p class="code">PRINT 'WHY JOHNNY CAN''T READ'
	</p>		</p>

ELowell: /* Use of quotation marks */

2014-11-11T19:52:04Z

Use of quotation marks

← Older revision		Revision as of 19:52, 11 November 2014
Line 191:		Line 191:
	<p>		<p>
	The pair of single quotation marks delineates the quoted string. Any character that appears within the quotation marks (including space) is considered part of the text to be printed. A pair of consecutive single quotation marks (<tt>''</tt>) embedded in quoted text reproduces a single quotation mark in the output. Thus: </p>		The pair of single quotation marks delineates the quoted string. Any character that appears within the quotation marks (including space) is considered part of the text to be printed. A pair of consecutive single quotation marks (<tt>''</tt>) embedded in quoted text reproduces a single quotation mark in the output. Thus: </p>
	<p class="code">PRINT 'WHY JOHNNY CAN&~~#39~~;'T READ'		<p class="code">PRINT 'WHY JOHNNY CAN''T READ'
	</p>		</p>
	<p>		<p>

ELowell: /* Example of formatting output */

2014-11-11T19:51:21Z

Example of formatting output

← Older revision		Revision as of 19:51, 11 November 2014
Line 64:		Line 64:
	STATE = MASSACHUSETTS		STATE = MASSACHUSETTS
	END FIND		END FIND
	PRINT &~~#39~~;'MASSACHUSETTS DRIVERS' AT COLUMN 12		PRINT ''MASSACHUSETTS DRIVERS' AT COLUMN 12
	SKIP 1 LINE		SKIP 1 LINE
	PRINT 'POLICY NO' WITH 'NAME' AT COLUMN 15 -		PRINT 'POLICY NO' WITH 'NAME' AT COLUMN 15 -