Messages FLW0 through FLW0xx

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

FLW001S OPEN OF DDNAME "DAFLOW" FAILED

Explanation: Open of jobs flow printout file failed in the DAFLOW DD statement of the CTMRFLW or CTMRAFL utility.

Possible causes are:

• The DAFLOW DD statement missing.
• The data set described by the DAFLOW DD statement cannot be accessed for sequential write.

The program stops executing with a condition code of 08.

Corrective Action: Correct the JCL for the job.

FLW002S OPEN OF DDNAME "DAJOB" FAILED

Explanation: Open of the scheduling tables file failed in the DAJOB DD statement of the CTMRFLW utility, or open of the Control-M Active Jobs file failed in the DACKPTIN DD statement of the CTMRAFL utility.

The DAJOB DD statement describes the production parameters tables on which a job flow report is requested. Many data sets or members can be concatenated to this DD statement. The DACKPTIN DD statement describes the Control-M Active Jobs file.

Possible causes are:

• The DAJOB (DACKPTIN) DD statement missing.
• The data set described by the DAJOB (DACKPTIN) DD statement cannot be opened for sequential read or record length is not 80 (600).

The program stops executing with a condition code of 08.

Corrective Action: Correct the JCL for the job.

FLW003E SCHEDULING TABLE(S) CONTAINS TOO MANY CARDS

Explanation: There are too many statements in the scheduling table or tables of the CTMRFLW utility. There are too many jobs to be analyzed in one run of the utility.

The program stops executing with a condition code of 08.

Corrective Action: Divide the scheduling tables list into two runs of the utility.

FLW004E SCHEDULING TABLE IS EMPTY

Explanation: The scheduling table does not contain any scheduling parameters for the CTMRFLW utility, or the Active Jobs file does not contain any job for the CTMRAFL utility. Scheduling tables described by the DAJOB DD statement do not contain any scheduling data for CTMRFLW.

The program stops executing with a condition code of 08.

Corrective Action: Correct the JCL for the job.

FLW005W A CYCLIC FLOW DETECTED IN GROUP grp, JOB FLOW MAY CONTAIN ERRORS

Explanation: A cyclic job flow detected in a group processed by the CTMRFLW or CTMRAFL utility. A cyclic flow detected inside a specific group may contain errors because there is no recognized parent to start a chain. The job flow of the specific group is terminated where the cyclic job flow is detected.

Corrective Action: Check the specified group using the Online Scheduling Definition Facility.

FLW006S OPEN OF DDNAME "SORTIN" FAILED

Explanation: Open of work file failed in the SORTIN DD statement of the CTMRFLW or CTMRAFL utility.

Possible causes are:

• The SORTIN DD statement missing.
• The data set described by the SORTIN DD statement cannot be opened for sequential write.

The program stops executing with a condition code of 08.

Corrective Action: Correct the JCL for the job.

FLW007S OPEN OF DDNAME "SORTOUT" FAILED

Explanation: Open of work file failed in DD statement SORTOUT of the CTMRFLW or CTMRAFL utility.

Possible causes are:

• The DD statement SORTOUT is missing.
• The data set described by the DD statement SORTOUT cannot be opened for sequential read.

The program stops executing with a condition code of 08.

Corrective Action: Correct the JCL for the job.

FLW008S SORT FAILED RC = code

Explanation: Internal sort failed in the CTMRFLW or CTMRAFL utility. The CTMRFLW or CTMRAFL utility activates the regular sort program of the installation. The return code is specific to the sort program.

The program stops executing with a condition code of 08.

Corrective Action: Check the sort program literature for the meaning of the sort return code, and correct the JCL for the job accordingly.

FLW009E A JOB FLOW LOOP DETECTED. CHART CANNOT BE COMPLETED FOR GROUP grp

Explanation: Although the input is valid for the Job Flow Report, a cyclic job flow, or loop, was detected in the specified group. As a result, a Job Flow Chart cannot be generated. In a job flow loop, it is impossible to determine which job is first. Therefore, the Job Flow Report program breaks the loop at a job it selects arbitrarily, places an asterisk (*) to the left of the job selected, and issues this message.

Report generation continues, but the Job Flow Chart is not produced.

Corrective Action: No action is required.

FLW010E MAXIMUM NUMBER OF DEPENDENCIES FOR JOB jobName EXCEEDED. ONLY FIRST 50 ARE TAKEN

Explanation: At least one job in the input tables depends on more than 50 other jobs. The Job Flow Chart can analyze up to 50 dependencies per job.

The chart is produced, but only the 50 first dependencies of that job are included.

Corrective Action: No action is required.

FLW011I CHART CONSISTS OF pg_count VERTICAL PAGES AND pg_count HORIZONTAL PAGES

Explanation: This information message indicates the number of logical pages produced.

Corrective Action: No action is required.

FLW012W INTERNAL ERROR DETECTED. CHART MAY CONTAIN ERRORS, CODE=errCode

Explanation: An internal error occurred.

The program proceeds, but it may contain a logical error.

Corrective Action: Provide the INCONTROL administrator with the message code and the error code specified in the error message.

FLW013I **** MESSAGES OF JOB FLOW REPORT ****

Explanation: This information message is the title of the Messages List and indicates the beginning of the list.

Corrective Action: No action is required.

FLW014E INTERNAL ERROR (CODE=err_cod), PROCESSING STOPPED

Explanation: An internal error occurred.

Processing stops.

Corrective Action: Provide the INCONTROL administrator with the Control-M message code and the error code specified in the error message.

FLW015S NUMBER OF LINES PER PAGE MUST BE A MULTIPLE OF 4

Explanation: The value specified in the PAGESIZE parameter is not a multiple of 4. For additional information regarding the PAGESIZE parameter, see the job flow chart in the chapter that describes KSL and the Reporting facility in the Control-M for z/OS User Guide.

Reports and charts are not produced.

Corrective Action: Correct the PAGESIZE parameter.

FLW016S LINE SIZE MUST BE A MULTIPLE OF 16 CHARACTERS

Explanation: The subparameter specified in the LINESIZE parameter is not a multiple of 16. See the job flow chart in the chapter that describes KSL and the Reporting facility in the KeyStroke Language (KSL) User Guide for additional information regarding the LINESIZE parameter.

Reports and charts are not produced.

Corrective Action: Correct the LINESIZE parameter.

FLW017I PREPARING CHART FOR GROUP grp (job_count JOBS IN GROUP)

Explanation: This information message indicates that CTMRFLW began preparing a chart for the specified group.

Corrective Action: No action is required.

FLW018E MAXIMUM CHART SIZE FOR GROUP grp EXCEEDED

Explanation: There are too many jobs and dependencies in the specified group. Internal capacity exceeded.

Chart cannot be produced for that group.

Corrective Action: If this occurs when the GROUP UNITED parameter is specified in the CTMRFLW batch utility, avoid using the UNITED subparameter for these tables. If the GROUP UNITED parameter was not specified, separate this group into several groups.

If the error occurred while you were trying to see a graphic jobflow in the Graphic Jobflow online screen, the limit of 15 levels of dependencies has probably been exceeded. In such a case, use the CTMRFLW utility to display the graphic jobflow.

FLW019I CHARS=(char_set,char_set) IN DD STATEMENT ddName

Explanation: This informative message indicates the character sets and DD name used for printing the chart.

Corrective Action: No action is required.

FLW01AE PROCESSING OF AJF FILE TERMINATED rsn

Explanation: A problem arose while the Active Jobs file (AJF) was being processed.

In this message, rsn identifies the problem that caused this message to be issued. The explanation, system action, and user response depend on the value of rsn.

If the value of rsn is GETMAIN, there is insufficient storage space and the processing of the AJF stops.

If the value of rsn is nnnnnn/ mmmmm/ jobName, an invalid field format was detected in an entry in the AJF. The variables in this version of the message identify the problematic entry. They are:

• nnnnnn - the Relative Block Address (RBA)
• mmmmm - the order ID
• jobName - the job name

Processing of the AJF stops.

Corrective Action: The user response depends on the value of rsn:

• If the value of rsn is GETMAIN, increase the REGION size.
• If the value of rsn is nnnnnn/ mmmmm/ jobName, do the following:
• Use the Zoom facility (Screen 3.Z) to check the entry, and print the contents of Screen 3.Z.
• Copy the Active Jobs file, for use (if necessary) by BMC Customer Support.
• Run the CTMRFLW utility, and print the output.
• Send the printed contents of Screen 3.Z and the printed output of the CTMRFLW utility to your local BMC representative.

FLW0A1W SPECIFIED LINESIZE TOO LARGE FOR CHARACTER SETS

Explanation: The specified LINESIZE is too large to be printed by the specified character sets. For example, standard English character set GS10 supports up to 132 characters per line while GS12 supports up to 160 characters per line. If GS10 was specified with a LINESIZE of 144, this warning message would be displayed. If GS12 was specified, this warning message would not be displayed.

Corrective Action: Either correct the specified LINESIZE or change the character sets which are specified in the JCL procedure.

FLW0A2E TOO MANY GROUP PARAMETER CARDS ARE SPECIFIED

Explanation: The number of GROUP parameter statements exceeded the maximum allowed. Do not specify more than 10 GROUP statements for CTMRFLW.

The utility terminates without processing.

Corrective Action: Decrease the number of GROUP statements.

FLW0A3E SPECIFIED GROUPS WERE NOT FOUND IN THE TABLE(S)

Explanation: None of the names specified in the GROUP parameter was found in the table or tables. No table contains a job whose group name matches the GROUP name parameters. It is also possible that the table is empty.

The utility terminates without processing.

Corrective Action: Delete or correct the GROUP parameter statements.

FLW0A4W MEMBER memName DEPENDS ON "|" CONDITIONS. THE "|" SIGN WAS IGNORED

Explanation: Normal message issued by the CTMRFLW utility, when the memName member depends on | (OR) conditions.

When processing OR conditions, the utility ignores the | sign. Conditions are displayed without the | sign.

Corrective Action: No action is required.

FLW0A5S OPEN OF DDNAME "DACTO" FAILED

Explanation: Open of the Control-O rule tables specified by the DACTO DD statement failed. Possible causes are:

• The DACTO DD statement is missing.
• The data set described by the DACTO DD statement cannot be opened for sequential processing.

The CTMRFLW utility ends with errors.

Corrective Action: Check the JCL for the job. Correct it, and rerun the utility.

FLW0A6I MANUAL CONDITIONS PRECEDED BY "*" WERE DETECTED AS CONTROL-O "DO COND" CONDITIONS

Explanation: This information message indicates that the CTMRFLW utility detected the addition of manual conditions by Control-O rules using DO COND statements.

Manual conditions added by DO COND statements are marked with an asterisk * by the utility.

Corrective Action: No action is required.