Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

FGG - Edit all files of an FGG

&pagelevel(4)&pagelevel

The FGG statement serves to edit all the files of an FGG jointly in a single output file. The name of the output file is specified with the OUTFILE operand. In command mode, the user is free to issue any number of FGG commands.

FGG

 {fgg-name| *linkprefix }

 [,EDIT = { PRINTER | TERMINAL } ]

 [,INFO = { LONG | DUMP | SHORT } ]

 [,OUTFILE = filename ]

fgg-name

edits all dump files in the directory fgg-name. openUTM creates a separate FGG file for each work process in the application.

EDIT=

This operand controls editing:

With EDIT=PRINTER (default), an output file is created which is intended for printing on the printer. The output contains feed control characters, page headers, with a maximum line length of 132 characters. The table of contents at the end of the output relates to print pages (default). 
With EDIT=TERMINAL, the output file is edited in such a way that it can be evaluated on screen using an editor. The maximum line length is 80 characters. The table of contents at the end of the output relates to line numbers.

INFO=

This operand controls output of the summary information. This is an extract of the complete dump information and contains the data frequently required for diagnosis.

INFO=LONG: editing with summary information (default).

INFO=DUMP: editing without summary information.

INFO=SHORT: KDCDUMP outputs only summary information.

OUTFILE=

This operand allows you to specify that output is to be written to a file with the name filename.If you do not specify OUTFILE, KDCDUMP assigns the default name dmplst/appl-name/reason.pid.no (see "The files of the UTM dump" for a description) and writes the output file to the current directory.

Notes

  • When the FGG control statement is entered, a UTM dump file which was read in by means of the DUMP command is removed in its entirety from memory. Consequently, the UTM dump under examination prior to the FGG command will no longer be available for diagnostic purposes.

  • The individual file generations of the FGG are read consecutively and removed from memory again after processing, so that after execution of this command none of the files remains in memory.