gtpm4m1iMessages (System Error and Offline)

FCTB

FCTB0001Tfilename(function) MEMORY ALLOCATION FAILURE

Where:

filename
The file name that contains the function.

function
The function that issued the error.

Explanation: An attempt was made to allocate memory dynamically and it failed.

System Action: Processing is ended immediately.

User Response: Increase the REGION size in which the job is being run.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0002Tfilen(function) CANNOT OPEN DD:name

Where:

filename
The file name that contains the function.

function
The function that issued the error.

name
Data definition name of the data set and member that cannot be opened.

Explanation: An attempt was made to open the data set and member referenced in the message in the JCL. The open failed.

System Action: Processing is ended immediately.

User Response: Check that the data definition name exists in the JCL.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0003Efilename(function) UNEXPECTED EOF.

Where:

filename
The file name that contains the function.

function
The function that issued the error.

Explanation: The end of the input file (Stage I deck) was reached while parsing a statement.

System Action: Validation of the input is continued but no output is produced.

User Response: Do the following:

  1. Verify that the input file (Stage I deck) is complete.
  2. Verify that the input file can be assembled.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0004Efilename(function) UNEXPECTED END OF LINE.

Where:

filename
The file name that contains the function.

function
The function that issued the error.

Explanation: The end of an input line was encountered yet the statement being read from the input file (Stage I deck) did not have any parameters or the line being read began with a label in column 1 but did not contain any other text on that line.

System Action: Validation of the input is continued but no output is produced.

User Response: Do the following:

  1. Verify that the input file (Stage I deck) is complete.
  2. Verify that the input file can be assembled.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0005Wfilename(function). DUPLICATE statement STATEMENT CODED, IGNORED.

Where:

filename
The file name that contains the function.

function
The function that issued the error.

statement
The name of the duplicate statement.

Explanation: The statement being parsed was already encountered in the input file (Stage I deck). It should only be coded once.

System Action: Validation is continued and output is produced, unless the STOPWARNING parameter is passed to the file address compute program (FACE) table generator.

User Response: A macro or statement was coded twice. Only the first one is processed and the remaining ones are ignored. Ensure that the first macro or statement is the one desired. Duplicates should be removed to avoid confusion.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0006Tfilename(function) READ ERROR.

Where:

filename
The file name that contains the function.

function
The function that issued the error.

Explanation: There was an error reading the input file (Stage I deck). Additional TPF system information is provided.

System Action: Processing is ended immediately.

User Response: Do the following:

  1. Correct the condition preventing the file from being read.
  2. Run the job again.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0007Tfilename(function) WRITE ERROR.

Where:

filename
The file name that contains the function.

function
The function that issued the error.

Explanation: There was an error writing a file out. Additional TPF system information is provided.

System Action: Processing is ended immediately.

User Response: Do the following:

  1. Correct the condition preventing the file from being written.
  2. Run the job again.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0008Efilename(function) UNEXPECTED END OF FILE.

Where:

filename
The file name that contains the function.

function
The function that issued the error.

Explanation: The report generator unexpectedly encountered the end of the input file (Stage I deck).

System Action: Validation of the input is continued but no output is produced.

User Response: See your IBM service representative for more information because an internal software error occurred.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0009Wfilename(function) DUPLICATE name value, IGNORED.

Where:

filename
The file name that contains the function.

function
The function that issued the error.

name
The parameter name.

value
The duplicate value.

Explanation: A duplicate value b was coded on the aaaa parameter.

System Action: Validation is continued and output is produced, unless the STOPWARNING parameter is passed to the file address compute program (FACE) table generator.

User Response: If the value was mistyped, then specify the value correctly.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0010Efilename(function) UNBALANCED PARENTHESIS.

Where:

filename
The file name that contains the function.

function
The function that issued error.

Explanation: An equal number of open and close parentheses were not found.

System Action: Validation of the input is continued but no output is produced.

User Response: Code the correct number of open and close parentheses.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0011Efilename(function) THE error PARAMETER IS INVALID.

Where:

filename
The file name that contains the function.

function
The function that issued the error.

error
The parameter name in error.

Explanation: The parameter referenced in the message was coded with data that is not valid.

System Action: Validation of the input is continued but no output is produced.

User Response: Code the parameter correctly.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0012Wfilename(function) DUPLICATE parameter value, IGNORED.

Where:

filename
The file name that contains the function.

function
The function that issued the error.

parameter
The duplicate parameter.

value
The value on the duplicate parameter.

Explanation: The parameter specified in the message was already coded with the value specified. Duplicate values are not allowed.

System Action: Validation is continued and output is produced, unless the STOPWARNING parameter is passed to the file address compute program (FACE) table generator.

User Response: Change the value coded for the parameter.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0013Efilename(function) INVALID PARAMETER FOUND ON STATEMENT.

Where:

filename
The file name that contains the function.

function
The function that issued the error.

Explanation: The parser did not expect a parameter on the statement.

System Action: Validation of the input is continued but no output is produced.

User Response: Correct the syntax of the statement.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0014Efilename(function) THE FTI SIZE FOR UFT uftnumber IS TOO LARGE TO BE USED ON THE UFTI4 PARAMETER

Where:

filename
The file name that contains the function.

function
The function that issued the error.

uftnumber
The universal format type (UFT) number.

Explanation: The number of bits coded for the format type indicator (FTI) size for the UFT indicated create an FTI size which is too large for a file address reference format 4 (FARF4) address.

System Action: Validation of the input is continued but no output is produced.

User Response: A different UFT should be used on the UFTI4 parameter.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0015Efilename(function) A RIGHT PARENTHESIS MUST BE FOLLOWED BY A COMMA, A SPACE, A RIGHT PARENTHESIS OR AN END-OF-STATEMENT.

Where:

filename
The file name that contains the function.

function
The function that issued the error.

Explanation: The parser detected an error in the syntax of the statement.

System Action: Validation of the input is continued but no output is produced.

User Response: Correct the syntax of the statement.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0016Wfilename(function) parameter PARAMETER HAS BEEN TRUNCATED TO value

Where:

filename
The file name that contains the function.

function
The function that issued the error.

parameter
The parameter that has a value that will be truncated.

value
The truncated value.

Explanation: The value coded on the parameter referenced in the message is too long and was truncated.

System Action: Validation continues and output is produced, unless the STOPWARNING parameter is passed to the FACE table generator.

User Response: Do one of the following:

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0017Efilename(function) MODEvalue1 IS INVALID IN A STAGE value2 SYSTEM

Where:

filename
The file name that contains the function.

function
The function that issued the error.

value1
The dispense mode value coded on the MODE parameter.

value2
The migration stage value coded on the STAGE parameter.

Explanation: The value coded on the parameter referenced in the message parameter does not make sense for the migration stage referenced in the message.

System Action: Validation of the input is continued but no output is produced.

User Response: Update the STAGE or MODE parameter, as necessary, on the UFTIFT statement.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0018Wfilename(function) INVALID parameter PARAMETER, value ASSUMED.

Where:

filename
The file name containing function.

function
The function issuing the error.

parameter
The parameter that has information coded that is not valid.

value
The value assumed for this parameter.

Explanation: The value coded for the parameter referenced in the message is not valid. The default value referenced in the message was used.

System Action: Validation is continues and output is produced, unless the STOPWARNING parameter is passed to the file address compute program (FACE) table generator.

User Response: Do one of the following:

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0019Wfilename(function) INVALID parameter PARAMETER, value ASSUMED.

Where:

filename
The file name containing function.

function
The function issuing the error.

parameter
The parameter that has information coded that is not valid.

value
Value assumed for this parameter.

Explanation: Data coded on the parameter referenced in the message is not valid. The TPF system continues processing as if the correct data was coded.

System Action: Validation is continued and output is produced, unless the STOPWARNING parameter is passed to the file address compute program (FACE) table generator.

User Response: Do one of the following:

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0020Wfilename(function) INVALID parameter PARAMETER, value ASSUMED.

Where:

filename
The file name that contains the function.

function
The function that issued the error.

parameter
The parameter that has information coded that is not valid.

value
The value assumed for this parameter.

Explanation: Data coded on the parameter referenced in the message is not valid. The TPF system continues processing as if the correct data was coded.

System Action: Validation is continued and output is produced, unless the STOPWARNING parameter is passed to the file address compute program (FACE) table generator.

User Response: Do one of the following:

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0021Wfilename(function) PERMx MUST BE EVEN IN A FULLY DUPLICATED SYSTEM. PERMx=value ASSUMED.

Where:

filename
The file name thta contains the function.

function
The function that issued the error.

value
The value assumed for PERM parameter.

Explanation: In a fully duplicated TPF system, the value coded on the PERM parameter is divided by 2 to calculate the total number of prime modules. If the number is not even, a fractional module is left over so the TPF system makes the assumption.

System Action: Validation is continued and output is produced, unless the STOPWARNING parameter is passed to the file address compute program (FACE) table generator.

User Response: Do one of the following:

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0022Efilename(function) NO PERM MODS CODED FOR DEVICE device

Where:

filename
The file name that contains the function.

function
The function that issued the error.

device
The device that did not have the PERM parameter coded.

Explanation: The DEVICE parameter was coded for the device referenced in the message but the PERM parameter for that device was not coded or its value was 0.

System Action: Validation of the input is continued but no output is produced.

User Response: Do one of the following:

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0023Efilename(function) TOTAL NUMBER OF MODS MUST BE LESS THAN OR EQUAL TO number

Where:

filename
The file name that contains the function.

function
The function that issued the error.

number
The maximum number of modules allowed to be coded.

Explanation: The total number of DASD modules coded must not exceed the TPF-defined limit referenced in the message.

System Action: Validation of the input is continued but no output is produced.

User Response: Reduce the values coded for the PERM or EXTR parameters on the ONLFIL macro.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0024Efilename(function) BAND MUST BE LESS THAN OR EQUAL TO number

Where:

filename
The file name that contains the function.

function
The function that issued the error.

number
The maximum band number allowed.

Explanation: The value coded on the BAND parameter of the RAMFIL statement must not exceed the number referenced in the message.

System Action: Validation of the input is continued but no output is produced.

User Response: Code a BAND number between 0 and the number referenced in the message.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0025Wfilename(function) DUPLICATE parameter value, IGNORED.

Where:

filename
The file name that contains the function.

function
The function that issued the error.

parameter
The duplicate parameter name.

value
The parameter value that is being ignored.

Explanation: The parameter referenced in the message was coded already for this statement. The value referenced in the message was ignored.

System Action: Validation is continued and output is produced, unless the STOPWARNING parameter is passed to the file address compute program (FACE) table generator.

User Response: Do one of the following:

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0026Wfilename(function) parameter IS NOT VALID FOR type

Where:

filename
The file name that contains the function.

function
The function that issued the error.

parameter
The parameter name that is not valid.

type
The type of RAMFIL statement (POOL, FIXED, SPARE).

Explanation: The parameter referenced in the message is not valid for the type of RAMFIL statement coded. The parameter is ignored.

System Action: Validation is continued and output is produced, unless the STOPWARNING parameter is passed to the file address compute program (FACE) table generator.

User Response: You may want to delete the parameter referenced in the message so the warning message is not issued.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0027Wfilename(function) SHORT TERM POOLS CANNOT BE DUPLICATED. DUPE=NO ASSUMED.

Where:

filename
The file name that contains the function.

function
The function that issued the error.

Explanation: Short term pools must be non-duplicated.

System Action: Validation is continued and output is produced, unless the STOPWARNING parameter is passed to the file address compute program (FACE) table generator.

User Response: Do one of the following to remove the warning message:

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0028Wfilename(function) THE parameter PARAMETER IS ONLY VALID FOR PRIOR=1, IGNORED .

Where:

filename
The file name that contains the function.

function
The function that issued the error.

parameter.
The parameter name that is not valid.

Explanation: The parameter referenced in the message may only be coded on RAMFIL statements that also have PRIOR=1 coded.

System Action: Validation is continued and output is produced, unless the STOPWARNING parameter is passed to the file address compute program (FACE) table generator.

User Response: Do one of the following:

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0029Efilename(function) value IS NOT VALID FOR parameter

Where:

filename
The file name that contains the function.

function
The function that issued the error.

value
The value in error.

parameter
The parameter.

Explanation: The value referenced in the message is not valid for the parameter referenced.

System Action: Validation of the input is continued but no output is produced.

User Response: Do the following:

  1. See TPF System Generation for more information about the parameter in the message.
  2. Correct the parameter.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0030Ifilename(function) PSON DEFAULTED TO value

Where:

filename
The file name that contains the function.

function
The function that issued the error.

value
The value the PSON took by default.

Explanation: Since the PSON parameter was not coded for this POOL, the file address compute program (FACE) table generator created one.

System Action: Processing proceeds normally.

User Response: Do one of the following:

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0031Efilename(function) statement STATEMENT WAS NOT CODED.

Where:

filename
The file name that contains the function.

function
The function that issued the error.

statement
The statement name.

Explanation: The statement referenced in the message is required but was not coded.

System Action: Validation of the input is continued but no output is produced.

User Response: Code the missing statement.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0032Efilename(function) PSON OVERLAP DETECTED.

Where:

filename
The file name that contains the function.

function
The function that issued the error.

Explanation: The PSON coded on the RAMFIL statement overlaps the PSON range defined by another RAMFIL statement.

System Action: Validation of the input is continued but no output is produced.

User Response: Code a different PSON on the RAMFIL statement so that it does not overlap the PSON ranges defined by any other RAMFIL statements.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0033Efilename(function) SINCE THIS RECORD TYPE WAS CODED, RECORD TYPE name MUST ALSO BE CODED

Where:

filename
The file name that contains the function.

function
The function that issued the error.

name
The record type name.

Explanation: The record type coded on the RAMFIL statement flagged and the record type in the message must both be coded

System Action: Validation of the input is continued but no output is produced.

User Response: Code the record type referenced in the message.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0034Efilename(function) THIS RECORD TYPE CAN NOT BE SPANNED. ONLY PRIOR=1 PERMITTED

Where:

filename
The file name that contains the function.

function
The function that issued the error.

Explanation: All the ordinals for the record type indicated must occur in one extent.

System Action: Validation of the input is continued but no output is produced.

User Response: Recode the RAMFIL statements for the record type so that all of the ordinals are contained within one extent.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0035Efilename(function) EQU VALUE CODED ON THIS RAMFIL HAS ALREADY BEEN CODED ON ANOTHER RAMFIL

Where:

filename
The file name that contains the function.

function
The function that issued the error.

Explanation: The value coded on the EQU parameter of the RAMFIL statement can only be associated with a single record type.

System Action: Validation of the input is continued but no output is produced.

User Response: Determine which record type the EQU should be associated with and recode the EQU value on the incorrect RAMFIL statement.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0036Wfilename(function) parameter PARAMETER IS BEING IGNORED. THIS PARAMETER MUST BE CODED ON THE FIRST RAMFIL IN THE INPUT DECK FOR THIS RECORD TYPE RECORD TYPE

Where:

filename
The file name that contains the function.

function
The function that issued the error.

parameter
The name of the parameter being ignored.

Explanation: The parameter on the RAMFIL statement referenced in the message is being ignored since the value the TPF system used for this parameter was coded on the first RAMFIL statement in the input deck or is being defaulted to some value.

System Action: Validation is continued and output is produced, unless the STOPWARNING parameter is passed to the file address compute program (FACE) table generator.

User Response: If the value being ignored was what was intended, then the first RAMFIL statement in the input deck for this record type must have the parameter and its associated value coded.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0037Efilename(function) BEGIN TO CONTINUE COLUMNS ARE NOT BLANK.

Where:

filename
The file name that contains the function.

function
The function that issued the error.

Explanation: The parser detected a nonblank character on a continued line between the first column and column 15 in the input file (Stage I deck).

System Action: Validation of the input is continued but no output is produced.

User Response: Correct the line in error so that it conforms to assembler syntax rules.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0038Efilename(function) THE parameter PARAMETER WAS NOT CODED OR IS INVALID.

Where:

filename
The file name that contains the function.

function
The function that issued the error.

parameter
The name of the missing parameter.

Explanation: The parameter referenced in the message is a required parameter and must be coded.

System Action: Validation of the input is continued but no output is produced.

User Response: Code the missing parameter.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0039Efilename(function) DEVICES ARE NOT SEQUENTIAL.

Where:

filename
The file name that contains the function.

function
The function that issued the error.

Explanation: Device types coded on the ONLFIL macro must be in ascending sequential order without gaps. Valid combinations are:

All other combinations are illegal.

System Action: Validation of the input is continued but no output is produced.

User Response: Code the correct DEVICE parameters.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0040Wfilename(function) EQU PARAMETER CODED ON THIS RAMFIL DOES NOT MATCH THE EQU VALUE OF value CODED ON THE FIRST RAMFILE FOR THIS RECORD TYPE

Where:

filename
The file name that contains the function.

function
The function that issued the error.

value
The value the TPF system is taking for the EQU parameter.

Explanation: The value referenced in the message is being assumed for the EQU parameter for this record type.

System Action: Validation is continued and output is produced, unless the STOPWARNING parameter is passed to the file address compute program (FACE) table generator.

User Response: Do one of the following:

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0041Efilename(function) FACE TABLE EXCEEDS 16MEG OF STORAGE.

Where:

filename
The file name that contains the function.

function
The function that issued the error.

Explanation: The size of the file address compute program (FACE) table exceeds 16 MB. The MVS linkage editor cannot handle an object module larger than this.

System Action: Validation of the input is continued but no output is produced.

User Response: There are several ways to lower the size of the FACE table:

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0042Efilename(function) BASE OVERLAP DETECTED. TO NEXT AVAILABLE BASE DEFAULTED LOCATION

Where:

filename
The file name that contains the function.

function
The function that issued the error.

Explanation: The disk space occupied by the previous RAMFIL statement overlaps the space in which the current RAMFIL statement is defined.

System Action: Validation of the input is continued but no output is produced.

User Response: Adjust the RECNO or BASE on the previous RAMFIL statement or code a new BASE on the current RAMFIL statement such that it does not occupy the space taken by the previous RAMFIL statement.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0043Wfilename(function) INVALID PARAMETER parameter. PARAMETER IGNORED.

Where:

filename
The file name that contains the function.

function
The function that issued the error.

parameter
The name of parameter passed to the file address compute program (FACE) table generator.

Explanation: When invoking the FACE table generator, the parameter aaaa was passed to the program. This parameter is not recognized by the FACE table generator and is ignored.

System Action: Validation is continued and output is produced, unless the STOPWARNING parameter is passed to the FACE table generator.

User Response: Check the spelling of the parameter name.

See TPF System Generation for more information about the file address compute program (FACE) table generation and for a list of valid parameters.

FCTB0044Efilename(function) value IS NOT VALID FOR parameter.

Where:

filename
The file name that contains the function.

function
The function that issued the error.

parameter
The parameter name.

value
The character value.

Explanation: The value c is not valid for aaaa

System Action: Validation of the input is continued and is the only output produced.

User Response: Correct the parameter.

See TPF System Generation for more information about the file address compute program (FACE) table generation and for a list of valid parameters.

FCTB0045Ifilename(function) parameter DEFAULTED TO value

Where:

filename
The file name that contains the function.

function
The function that issued the error.

parameter
The parameter name.

value
The default value.

Explanation: The parameter referenced in the message took the value noted in the message because the value was not originally coded on the parameter.

System Action: Processing proceeds normally.

User Response: No response is necessary if the default is acceptable. If the default is not acceptable, then the parameter must be coded with the correct value.

See TPF System Generation for more information about the file address compute program (FACE) table generation and for a list of valid parameters.

FCTB0046Efilename(function) DUPLICATE parameter,value IS INVALID

Where:

filename
The file name that contains the function.

function
The function that issued the error.

parameter
The parameter type.

value
The duplicate value.

Explanation: A duplicate parameter with a duplicate value was found.

System Action: Validation of the input is continued but no output is produced.

User Response: Remove the duplicate value.

See TPF System Generation for more information about the file address compute program (FACE) table generation and for a list of valid parameters.

FCTB0047Efilename(function) value IS OUT OF RANGE FOR parametertype ON THE parameter PARAMETER.

Where:

filename
The file name that contains the function.

function
The function that issued the error.

value
The out of range value.

parametertype
The parameter type.

parameter
The parameter name.

Explanation: The value specified on the parameter referenced in the message is not valid.

System Action: Validation of the input is continued but no output is produced.

User Response: None.

See TPF System Generation for more information about the file address compute program (FACE) table generation and for a list of valid parameters.

FCTB0048Wfilename(function) parameter1 IS NOT A VALID PARAMETER WITHOUT THE parameter2 PARAMETER CODED, PARAMETER IGNORED.

Where:

filename
The file name that contains the function.

function
The function that issued the error.

parameter1
The parameter that is not valid.

parameter2
The parameter not coded.

Explanation: An error occurred because a parameter was coded without its corresponding parameter.

System Action: Validation is continued and output is produced, unless the STOPWARNING parameter is passed to the file address compute program (FACE) table generator.

User Response: Either both or none of the indicated parameters must be coded.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0049Efilename(function) value IS NOT VALID FOR parameter.

Where:

filename
The file name that contains the function.

function
The function that issued the error.

parameter
The parameter name.

value
The parameter value.

Explanation: An error occurred because the value specified on the parameter is not valid.

System Action: Validation of the input is continued but no output is produced.

User Response: Correct the parameter.

See TPF System Generation for more information about the file address compute program (FACE) table generation and for a list of valid parameters.

FCTB0050Ifilename(function) parameter IS EXTRANEOUS.

Where:

filename
The file name that contains the function.

function
The function that issued the error.

parameter
The extraneous parameter name.

Explanation: An error occurred because the parameter is not a recognized parameter on the RAMFIL statement.

System Action: Processing proceeds normally.

User Response: Do one of the following:

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0051Efilename(function). PSON + RECNO OUT OF RANGE.

Where:

filename
The file name that contains the function.

function
The function that issued the error.

Explanation: The sum of PSON and RECNO cannot exceed 4294967294.

System Action: Validation of the input is continued but no output is produced.

User Response: Do the following:

  1. Reduce the value coded for the PSON parameter.
  2. Define pools in the PSON gaps, if there are any.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0052Efilename(function) THE VALUE CODED FOR PSEUDO, value1, EXCEEDS THE VALUE CODED FOR EXTR ON ONLFIL FOR THIS DEVICE TYPE, value2.

Where:

filename
The file name that contains the function.

function
The function that issued the error.

value1
The value coded for PSEUDO.

value2
The value coded for the EXTR parameter on the ONLFIL macro.

Explanation: The value coded for PSEUDO cannot exceed the value coded for the EXTR parameter on the ONLFIL macro for this device type.

System Action: Validation of the input is continued but no output is produced.

User Response: Do one of the following:

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0053Efilename(function) THERE IS NO PRIOR=1 CODED FOR THIS RECORD TYPE.

Where:

filename
The file name that contains the function.

function
The function that issued the error.

Explanation: Every record type, for which a RAMFIL statement was coded, must have a RAMFIL with PRIOR=1 coded or implied (if the PRIOR= parameter is not coded, it defaults to 1).

System Action: Validation of the input is continued but no output is produced.

User Response: Add a RAMFIL statement that contains PRIOR=1 (explicitly or implicitly).

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0054Efilename(function) DUPLICATE PRIORS.

Where:

filename
The file name that contains the function.

function
The function that issued the error.

Explanation: There is another RAMFIL statement coded for this record type with the same value coded for the PRIOR= parameter.

System Action: Validation of the input is continued but no output is produced.

User Response: Change one of the RAMFIL statements so that there are no duplicate PRIORs.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0055Wfile(func) PRIORS MUST BE CONTIGUOUS; PREVIOUS PRIOR was value.

Where:

filename
The file name that contains the function.

function
The function that issued the error.

value
The value coded for the PRIOR parameter on the previous statement for this record type.

Explanation: The values coded for the PRIOR parameter must be sequential. If there is a PRIOR=1, a PRIOR=2, and a PRIOR=4, then there must be a PRIOR=3. These RAMFIL statements do not have to be coded in this order but they must exist.

System Action: Validation is continued and output is produced, unless the STOPWARNING parameter is passed to the file address compute program (FACE) table generator.

User Response: Code the PRIOR parameters again for the record type in error.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0056Efilename (function) EXPLICIT USER COLLISION WITH RAMFIL number.

Where:

filename
The file name that contains the function.

function
The function that issued the error.

number
The sequence number that this RAMFIL statement collides with.

Explanation: This RAMFIL statement and the one referenced both explicitly code the same user-triplet. This is not allowed.

System Action: Validation of the input is continued but no output is produced.

User Response: Correct the USER parameters on these RAMFIL statements.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0057Efilename(function) UFT value NOT DEFINED ON UFTFTIMACRO; IT WILL BE IGNORED.

Where:

filename
The file name that contains the function.

function
The function that issued the error.

value
The value coded for the UFT parameter.

Explanation: Only the universal format types (UFTs) coded on the UFTFTI macro can be used for the UFT parameter.

System Action: Validation of the input is continued but no output is produced.

User Response: Do one of the following:

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0058Wfilename(function) THE parameter PARAMETER IS ONLY VALID ON THE LOW PSON RAMFILE, PARAMETER IGNORED.

Where:

filename
The file name that contains the function.

function
The function that issued the error.

parameter
The parameter that is not valid.

Explanation: The parameters that follow are only valid on the RAMFIL statement with the lowest PSON for this type.

System Action: The parameter is ignored. Validation is continued and output is produced, STOPWARNING parameter is passed to the file address compute program (FACE) table generator.

User Response: Do one of the following:

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0059Ifilename(function) RAMFIL WAS CODED AS type ON A type DEVICE TYPE

Where:

filename
The file name that contains the function.

function
The function that issued the error.

type
The type of duplication.

Explanation: There is a mismatch between the type of duplication specified for this RAMFIL statement and the duplication of the device. This is allowed but is highlighted for the user's information.

System Action: None.

User Response: Verify that this is what was intended.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0060Efilename(function) THE VALUE CODED FOR OWNER MUST BE CODED FOR USER

Where:

filename
The file name that contains the function.

function
The function that issued the error.

Explanation: The value coded on the OWNER parameter must be one of the members of the set of values coded on the USER parameter

System Action: Validation of the input is continued but no output is produced.

User Response: Do one of the following:

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0061Efilename(function) MUST HAVE AT LEAST records RECORDS DEFINED.

Where:

filename
The file name that contains the function.

function
The function that issued the error.

records
The minimum number of records that must be coded for this record type

Explanation: Too few records were coded for this record type.

System Action: Validation of the input is continued but no output is produced.

User Response: Do one of the following:

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0062Wfilename(function) INCONSISTENT UCOMDATA; FIRST RAMFIL'S UCOMDATA = value.

Where:

filename
The file name that contains the function.

function
The function that issued the error.

value
The value coded for the UCOMDATA parameter.

Explanation: The value coded for the UCOMDATA parameter for a record type, if coded, must be the same.

System Action: Validation is continued and output is produced, unless the STOPWARNING parameter is passed to the file address compute program (FACE) table generator.

User Response: Change the UCOMDATA values to be the same.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0063Efilename(function) INCONSISTENT RECORD SIZE; FIRST RAMFILE'S RECORD SIZE = size.

Where:

filename
The file name that contains the function.

function
The function that issued the error.

size
Size defined on the first RAMFIL statement for this record type.

Explanation: The size must be the same on each RAMFIL statement for this record type.

System Action: Validation of the input is continued but no output is produced.

User Response: Correct either RAMFIL statement.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0064Wfilename(function) BASE MUST BE SPECIFIED GREATER THAN 00001 BASE PARAMETER WAS CHANGED TO 00002.

Where:

filename
The file name that contains the function.

function
The function that issued the error.

Explanation: The BASE parameter cannot be less than 00002.

System Action: Validation is continued and output is produced, unless the STOPWARNING parameter is passed to the file address compute program (FACE) table generator.

User Response: Determine what the BASE parameter should be and recode it.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0065Efilename(function) FTI VALUE IN (type indicator) EXCEEDS DEFINITION FROM UFTFTI STATEMENT.

Where:

filename
The file name that contains the function.

function
The function that issued the error.

type
The universal format type (UFT).

indicator
The format type indicator (FTI).

Explanation: The values coded on the UFTFTI macro determine the number of FTIs for the defined UFTs. The FTI specified in the error message is out of the range defined.

System Action: Validation of the input is continued but no output is produced.

User Response: Determine what the correct value should be and change it or increase the size defined on the UFTFTI macro.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0066Efilename(function) UFT/FTI COMBINATION (type,indicator) ALREADY IN USE

Where:

filename
The file name that contains the function.

function
The function that issued the error.

type
The universal format type (UFT).

indicator
The format type indicator (FTI).

Explanation: UFT/FTI combinations cannot be shared.

System Action: Validation of the input is continued but no output is produced.

User Response: Change this combination to a used one or change the RAMFIL statement that is currently using it.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0067Efilename(function) RAMFILS ARE NOT GROUPED BY DEVICE TYPE.

Where:

filename
The file name that contains the function.

function
The function that issued the error.

Explanation: The RAMFIL statements for each device type must be all together.

System Action: Validation of the input is continued but no output is produced.

User Response: Reorder the RAMFIL statements.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0068Efilename(function) BASE PARAMETER IS REQUIRED IN THIS CASE.

Where:

filename
The file name that contains the function.

function
The function that issued the error.

Explanation: See the reference for reasons why the BASE parameter is required.

System Action: Validation of the input is continued but no output is produced.

User Response: Determine why the BASE parameter is required and correct.

See TPF System Generation for more information about the RAMFIL statement.

FCTB0069Efilename(function) NUMBER OF RECIDS CODED, recordid1, EXCEEDS THE MAXIMUM ALLOWED, recordid2.

Where:

filename
The file name that contains the function.

function
The function that issued the error.

recordid1
The number of record IDs coded.

recordid2
The maximum number of record IDs allowed.

Explanation: Too many record types were coded.

System Action: Validation of the input is continued but no output is produced.

User Response: Delete enough record types to bring the count under the allowed maximum.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0070Efilename(function) RAMFIL NOT CODED FOR DEVICE device.

Where:

filename
The file name that contains the function.

function
The function that issued the error.

device
The device for which this RAMFIL statement was not coded.

Explanation: The RAMFIL statements must only be coded for devices that are defined by the ONLFIL macro.

System Action: Validation of the input is continued but no output is produced.

User Response: Do one of the following:

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0071Wfilename(function) ROLLING MIGRATION IS POSSIBLE

Where:

filename
The file name that contains the function.

function
The function that issued the error.

Explanation: There is not enough RECNO left in the TPF system to migrate all the used RECNO in one shot but migration is possible by moving one record ID at a time.

System Action: Validation is continued and output is produced, unless the STOPWARNING parameter is passed to the file address compute program (FACE) table generator.

User Response: None.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0072Wfilename(function) MIGRATION MAY BE POSSIBLE: CAN COVER THE SHORTEST RECNO BUT NOT THE LONGEST.

Where:

filename
The file name that contains the function.

function
The function that issued the error.

Explanation: Under the right circumstances migration is possible but not for certain.

System Action: Validation is continued and output is produced, unless the STOPWARNING parameter is passed to the file address compute program (FACE) table generator.

User Response: Determine what the best migration strategy would be.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0073Efilename(function) MIGRATION NOT POSSIBLE: CANNOT COVER THE SHORTEST RECNO CODED.

Where:

filename
The file name that contains the function.

function
The function that issued the error.

Explanation: There is no possible way to migrate with the current layout.

System Action: Validation of the input is continued but no output is produced.

User Response: Determine whether there is a better way to lay out the database. Some universal format type/format type indicator (UFT/FTI) combinations might be used inefficiently.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0074Efilename(function) MUST CODE AT LEAST BAND OR UFT14.

Where:

filename
The file name that contains the function.

function
The function that issued the error.

Explanation: In stage 3 to stage 4 migration, one of these parameters must be coded.

System Action: Validation of the input is continued but no output is produced.

User Response: Add one or both of these parameters to this RAMFIL statement.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0075Efilename(function) MUST CODE AT LEAST UFTI4 OR UFTI5.

Where:

filename
The file name that contains the function.

function
The function issuing the error.

Explanation: In stage 4 to stage 5 migration, one of these parameters must be coded.

System Action: Validation of the input is continued but no output is produced.

User Response: Add one or both of these parameters to this RAMFIL statement.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0076Wfilename(function) ALL RECNO FOR THIS RECORD TYPE CAN NOT BE ACCESSED USING format ADDRESSING

Where:

filename
The file name that contains the function.

function
The function that issued the error.

format
The FARF addressing format (FARF3 or FARF4).

Explanation: The record type coded does not have enough FARF3 or FARF4 addressing descriptors defined to cover all the ordinal numbers for the record type.

System Action: Validation is continued and output is produced, unless the STOPWARNING parameter is passed to the file address compute program (FACE) table generator.

User Response: The user should define enough FARF3 or FARF4 addressing descriptors to cover all the ordinals for the record type and regenerate the FACE table. If nothing is done, then some ordinals will not be accessible using the FARF (as referenced in the message) addressing.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0077Efilename(function) RAMFIL DEFINITION EXCEEDS DEVICE END.

Where:

filename
The file name that contains the function.

function
The function that issued the error.

Explanation: The records defined by the RAMFIL statement coded do not fit on the device

System Action: Validation of the input is continued but no output is produced.

User Response: Check the DEVICEx parameter on the ONLFIL macro to make sure the device size value is correct. If it is, then the RAMFIL statement flagged needs to be corrected so that all of its records fit on the device.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0078Efilename(function) SIZE FOR THIS RECORD MUST BE AT LEAST description

Where:

filename
The file name that contains the function.

function
The function that issued the error.

description
The size description.

Explanation: The size coded on this RAMFIL statement does not match the size required for this record type.

System Action: Validation of the input is continued, but no output is produced.

User Response: If the required size for this record type is incorrect, then update its entry in the FTVA04 segment. Otherwise, change the size on this RAMFIL statement to this size.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0079Efilename(function) THIS RECORD MUST BE SSU SHARED. USER=*IS REQUIRED.

Where:

filename
The file name that contains the function.

function
The function that issued the error.

Explanation: The USER parameter is not coded as *, which is required for an SSU shared record.

System Action: Validation of the input is continued but no output is produced.

User Response: If this record is not to be SSU shared, then update its entry in the FTVA04 segment. Otherwise, change the USER parameter on this RAMFIL statement.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0080Wfilename(function) REQUIRED RECORD TYPE recordid NOT FOUND.

Where:

filename
The file name that contains the function.

function
The function that issued the error.

recordid
The record ID.

Explanation: This record type is required but there are no RAMFIL statements coded for it.

System Action: Validation is continued and output is produced, unless the STOPWARNING parameter is passed to the file address compute program (FACE) table generator.

User Response: Code a RAMFIL statement for the record type. If a RAMFIL statement is not coded for this record type, facilities that use this record type will not work

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0081Efilename(function) RAMFILS MUST BE CODED FOR RECORD ID recordid ON DEVICE type

Where:

filename
The file name that contains the function.

function
The function that issued the error.

recordid
The record ID.

type
The device type.

Explanation: This record ID is required on this device type.

System Action: Validation of the input is continued but no output is produced.

User Response: Code a RAMFIL statement for this record type on this device type.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0082Efilename(function) OVERFLOW DETECTED FOR TOTAL RECNO.

Where:

filename
The file name that contains the function.

function
The function that issued the error.

Explanation: Too many RECNOs (total of all RECNO) were coded.

System Action: Validation of the input is continued but no output is produced.

User Response: Determine whether there was a mistake in coding any RECNO parameter. If not, then determine how to reduce the number of RECNO coded.

See TPF System Generation for more information about the RAMFIL statement.

FCTB0083Efilename(function) AT LEAST parameter1 RECORDS MUST BE CODED FOR THIS RECORD TYPE ONLY parameter2 RECORDS WERE CODED

Where:

filename
The file name that contains the function.

function
The function that issued the error.

parameter1
The minimum RECNO parameter that must be coded.

parameter2
The RECNO parameter that was coded.

Explanation: An error occurred because too few records were coded for this record type.

System Action: Validation of the input is continued but no output is produced.

User Response: Code enough record ordinals on the RECNO parameter for this record type to reach the required minimum RECNO parameter.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0084Efilename(function) REQUIRED RECORD TYPE recordid NOT FOUND.

Where:

filename
The file name that contains the function.

function
The function that issued the error.

recordid
The record ID.

Explanation: This record type is required but there are no RAMFIL statements coded for it.

System Action: Validation of the input is continued but no output is produced.

User Response: Code a RAMFIL statement for the required record type.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0085Efilename(function) SSU UNIQUE RECORD NOT CODED FOR SSU: ssu.

Where:

filename
The file name that contains the function.

function
The function that issued the error.

ssu
The SSU on which this record type is not coded.

Explanation: A unique copy of this record is required for all SSUs but it was not coded for SSU referenced in the message.

System Action: Validation of the input is continued but no output is produced.

User Response: Code the appropriate RAMFIL statements for this record type on this SSU.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0086Efilename(function) INVALID USER PARAMETER FOR A UNIQUE RECORD. MUST BE CODED AS (SSUN,*,*) WHERE SSUN IS THE SSU NAME

Where:

filename
The file name that contains the function.

function
The function that issued the error.

Explanation: This record type must be subsystem user (SSU) unique.

System Action: Validation of the input is continued but no output is produced.

User Response: Code the USER parameter for this record type as SSUN,*,* where SSUN is a subsystem user (SSU) name.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0087Wfilename(function) MORE THAN option OPTION CODED. FIRST OPTION CODED FOR THIS TYPE ASSUMED.

Where:

filename
The file name that contains the function.

function
The function that issued the error.

option
The type of option.

Explanation: Certain options passed to the file address compute program (FACE) table generator belong to a class of options in which only one member of that class (type) of option can be coded. More than one member from a class was coded

System Action: Validation is continued and output is produced, unless the STOPWARNING parameter is passed to the FACE table generator.

User Response: If the assumed default is alright, then no user action is necessary. If the assumed default is incorrect, then the options passed to the generator need to be updated so that only one option from a class is passed.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0088Wfilename(function) PSON OVERLAP DETECTED, PSON DEFAULTED TO value.

Where:

filename
The file name that contains the function.

function
The function that issued the error.

value
The value that PSON is changed to.

Explanation: The PSON coded on the RAMFIL statement overlaps the PSON range defined by another RAMFIL statement.

System Action: Validation is continued and output is produced, unless the STOPWARNING parameter is passed to the file address compute program (FACE) table generator.

User Response: If the defaulted value is acceptable then no user response is required. If the default is not acceptable, then PSON needs to be recoded so that it falls outside of the range of already coded psons for this pool type.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0089Efilename(function) MINIMUM OF records RECORDS NEEDED FOR #KEYPT ON DEVICE type.

Where:

filename
The file name that contains the function.

function
The function that issued the error.

records
The minimum number of records needed.

type
The device type.

Explanation: Too few #KEYPT records were coded for this device type.

System Action: Validation of the input is continued but no output is produced.

User Response: Increase the amount to above the minimum.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0090Efilename(function) parameter EXCEEDS THE NUMBER OF MODULES DEFINED IN ONLFIL.

Where:

filename
The file name that contains the function.

function
The function that issued the error.

parameter
The LOMOD or NOMOD parameter.

Explanation: The valid coded for the LOMOD or NOMOD parameter must be less than or equal to the number of prime and pseudo modules coded on the ONLFIL macro.

System Action: Validation of the input is continued but no output is produced.

User Response: Recode the LOMOD or NOMOD parameter so that its value does not exceed the number of prime and pseudo modules combined.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0091Efilename(function) BAND number IN USE BY PROCESSOR OR I-STREAM UNIQUE RECOR D.

Where:

filename
The file name that contained the function.

function
The function that issued the error.

number
The BAND number in conflict.

Explanation: Only subsystem user (SSU) unique records can share BAND numbers.

System Action: Validation of the input is continued but no output is produced.

User Response: Verify that these records are supposed to be processor or I-stream unique. If they are, then they must use a different BAND number. Otherwise, correct the USER parameter.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0092Efilename(function) BAND number IN USE.

Where:

filename
The file name that contained the function.

function
The function that issued the error.

number
The BAND number.

Explanation: This BAND is in use by another record type.

System Action: Validation of the input is continued but no output is produced.

User Response: Use another BAND number

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0093Wfilename(function) THE NUMBER OF DEVICE type1 POOL DIRECTORY RECORDS FOR A type2 POOLTYPE IS type2. IT SHOULD BE type3. THIS WILL RESULT IN AN UNUSABLE DGF

Where:

filename
The file name that contained the function.

function
The function that issued the error.

type1
The device type.

type2
The current pool type.

type3
The pool type as it should be.

Explanation: The number of pool directories generated for each pool type must be greater than or equal to two times the number of processors coded on the SYSID parameter of the CONFIG macro plus 1.

System Action: Validation is continued and output is produced, unless the STOPWARNING parameter is passed to the file address compute program (FACE) table generator. Pools will not be able to be cycled up.

User Response: A pool directory is created each time a RAMFIL statement is coded for pool type. If the RAMFIL statement has more than 8000 records coded then additional pool directories are created for every 8000 records.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0094Efilename(function) NO type POOLS WERE CODED. THEY ARE REQUIRED.

Where:

filename
The file name that contained the function.

function
The function that issued the error.

type
The pool type.

Explanation: Both large and small short-term pools are required.

System Action: Validation of the input is continued but no output is produced.

User Response: Code the RAMFIL statements for this pool type.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0095Efilename(function) RAMFIL CODED FOR A DEVICE NOT DEFINED BY ONLFIL.

Where:

filename
The file name that contained the function.

function
The function that issued the error.

Explanation: The device that this RAMFIL statement is to be on does not exist.

System Action: Validation of the input is continued but no output is produced.

User Response: Do one of the following:

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0096Efilename(function) TOTAL RECNO CODED FOR THIS POOL TYPE (type) EXCEEDS THE FARF3 CAPACITY.

Where:

filename
The file name that contained the function.

function
The function that issued the error.

type
The RECNO coded for this pool type.

Explanation: The maximum RECNO allowable for pools is 226. This pool type exceeds that.

System Action: Validation of the input is continued but no output is produced.

User Response: Correct the RECNO for this pool type so that is under the maximum value.

See TPF System Generation for more information about FACE table generation.

FCTB0097Wfilename(function) TOTAL RECNO CODED FOR THIS POOL TYPE (type) EXCEEDS THE FARF3 CAPACITY. THIS IS IGNORED IN STAGE=FARF45.

Where:

filename
file name containing function

function
function issuing error

type
RECNO coded for this pool type

Explanation: The maximum RECNO allowable for pools is 226. This pool type exceeds that. Since this is a FARF Stage 4 to FARF Stage 5 migration path, it is ignored.

System Action: Validation continues and output is produced, unless the STOPWARNING parameter is passed to the file address compute program (FACE) table generator.

User Response: Determine whether this is permissible and correct it if not.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0098Efilename(function) INSUFFICIENT INSUFFICIENT parameter ALLOCATED TO COVER RECNO. TOTAL RECNO: type parameter CODED: recno

Where:

filename
The file name that contained the function.

function
The function that issued the error.

parameter
The BAND/UFTI4/UFTI5 parameter.

type
The total RECNO coded for this record type.

recno
The RECNO covered by the parameter.

Explanation: The amount of RECNO covered by the BAND/UFTI4/UFTI5 parameter is not sufficient to cover the amount of RECNO specified for this record type.

System Action: Validation of the input is continued but no output is produced.

User Response: Do one of the following:

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0099Wfilename(function) INSUFFICIENT parameter ALLOCATED TO COVER RECNO. TOTAL RECNO: type parameter CODED: recno THIS IS IGNORED IN STAGE=stage

Where:

filename
The file name that contained the function.

function
The function that issued the error.

parameter
The BAND/UFTI4/UFTI5 parameter.

type
The total RECNO coded for this record type.

recno
The RECNO covered by the parameter.

stage
The current TPF system stage.

Explanation: The amount of RECNO covered by the BAND/UFTI5 parameter is not sufficient to cover the amount of RECNO specified for this record type. However, the BAND parameter is ignored in a FARF Stage 4 to FARF Stage 5 migration path and the UFTI5 parameter is ignored in the FARF Stage 3 to FARF Stage 4 migration path.

System Action: Validation is continued and output is produced, unless the STOPWARNING parameter is passed to the file address compute program (FACE) table generator.

User Response: Do one of the following:

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0100Wfilename(function) THE THE parameter PARAMETER MUST BE CODED THE SAME ON ALL PRIOR=1 RAMFILS FOR THIS RECORD TYPE. VALUE HAS BEEN DEFAULTED TO value

Where:

filename
The file name that contained the function.

function
The function that issued the error.

parameter
The RAMFIL parameter which is in error

value
The value that the RAMFIL parameter was defaulted to.

Explanation: The parameter referenced in the message must be coded with the same value on all PRIOR=1 RAMFILs for the same RECID.

System Action: Validation is continued and output is produced, unless the STOPWARNING parameter is passed to the file address compute program (FACE) table generator.

User Response: If the default is acceptable, then no action is needed. If the default is unacceptable then the parameter must be coded the same on all PRIOR=1 RAMFILs for this RECID.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0101Efilename(function) EITHER ALL OR NONE OF THE FOLLOWING RECORDS MUST BE CODED: #NCBRI, #RRTRI, #RV1RU, #RV2RU

Where:

filename
The file name that contained the function.

function
The function that issued the error.

Explanation: These Systems Network Architecture (SNA) records must all exist or all not exist.

System Action: Validation of the input is continued but no output is produced.

User Response: Determine whether the SNA records should be coded and make the appropriate corrections.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0102Efilename(function) TOO MANY SSU NAMES CODED

Where:

filename
The file name that contained the function.

function
The function that issued the error.

Explanation: More than 64 subsystem user (SSU) names were coded on the SSUIDx parameter of the SSDEF macro.

System Action: Validation of the input is continued but no output is produced.

User Response: Code less than 65 SSU names.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0103Wfilename(function) DUPLICATE parameter PARAMETER. DUPLICATE IGNORED

Where:

filename
The file name that contained the function.

function
The function that issued the error.

parameter
The parameter name.

Explanation: The parameter referenced in the message was coded more than once for a statement.

System Action: Validation is continued and output is produced, unless the STOPWARNING parameter is passed to the file address compute program (FACE) table generator.

User Response: Correct the statement so that the parameter is only coded once.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0104Efilename(function) PARAMETER IS REQUIRED WHEN STAGE=stage

Where:

filename
The file name that contained the function.

function
The function that issued the error.

stage
The migration stage.

Explanation: The parameter must be coded when the migration stage is the one referenced in the message.

System Action: Validation of the input is continued but no output is produced.

User Response: Code the required parameter.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0105Efilename(function) THE name STATEMENT HAS NO PARAMETERS CODED

Where:

filename
The file name that contained the function.

function
The function that issued the error.

name
The statement name.

Explanation: The statement referenced in the message has no parameters coded. Certain parameters on this statement must be coded.

System Action: Validation of the input is continued but no output is produced.

User Response: Code the required parameters.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0106Ifilename(function) RESTORE=YES CODED FOR A RECORD TYPE WHICH SHOULD NOT BE RESTORED

Where:

filename
The file name that contained the function.

function
The function that issued the error.

Explanation: RESTORE=YES was coded on one of the following record types:

These record types have information in them that should not be changed when a restore is done.

System Action: None.

User Response: Do not code RESTORE or code RESTORE=NO for this record type.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0107Efilename(function) EITHER ALL OR NONE OF THE FOLLOWING RECORDS MUST BE CODED FOR A PROGRAM BASE (WHERE n = PROGRAM BASE NUMBER): #PROGn, #XPRGn, #PVRn

Where:

filename
The file name that contained the function.

function
The function that issued the error.

Explanation: These program base records must all exist or all not exist. For example, if you want to define program base number 4, you need to define records #PROG4, #XPRG4, and #PVR4. This error is generated if you define only #PROG4 records.

System Action: Validation of the input continues but no output is produced.

User Response: Do the following:

  1. Determine which program base numbers have only been partially defined.
  2. Correct the partially defined program base numbers.

See TPF System Generation for more information about the file address compute program (FACE) table generation.

FCTB0108Efilename(function) INODE AND FLOCK RECORDS NEED TO HAVE THE SAME NUMBER ALLOCATED. INODE HAS number1 FLOCK HAS number2

Where:

filename
The file name that contained the function.

function
The function that issued the error.

number1
The number of records allocated for the #INODE fixed file record.

number2
The number of records allocated for the #FLOCK fixed file record.

Explanation: The #INODE and #FLOCK fixed file records must have the same number allocated in the file address compute program (FACE) table. For example, if you want to have 100 #FLOCK fixed file records allocated, you must allocate 100 #INODE fixed file records.

System Action: Verifying the input continues but no output is produced.

User Response: Do the following:

  1. Determine which record must be increased or decreased.
  2. Correct the #INODE or #FLOCK fixed file record.

See TPF System Generation for more information about the FACE table generation.

FCTB0109Efilename(function) #RLOG RECNO MUST FILL A WHOLE TRACK

Where:

filename
The file name that contains the function.

function
The function that issued the error.

Explanation: The number of ordinals coded for the RECNO parameter of the RAMFIL statement must be a multiple of the number of records for each track of a 4-K record for the device type being used.

System Action: Verification of the input continues, but no output is produced.

User Response: Code the RAMFIL statement, specifying enough records for the RECNO parameter so the value is an even multiple of the number of records for each track for a 4-K record for the device type being used.

FCTB0110Efilename(function) #RLOG MUST FILL AT LEAST TWO TRACKS

Where:

filename
The file name that contains the function.

function
The function that issued the error.

Explanation: The number of ordinals coded for the RECNO parameter of the RAMFIL statement must fill at least two tracks.

System Action: Verification of the input continues, but no output is produced.

User Response: Code the RAMFIL statement, specifying enough records for the RECNO parameter so that two full tracks are defined.

FCTB0111Efilename(function) ALL #RLOG RECORDS MUST BE DEFINED ON THE SAME LOGICAL DEVICE

Where:

filename
The file name that contains the function.

function
The function that issued the error.

Explanation: An #RLOG record type was found on more than one device type.

System Action: Verification of the input continues, but no output is produced.

User Response: Code all ordinals for a particular #RLOG record type for the same device type.

FCTB0112Efilename(function) AT LEAST ONE #RLOG RECORD TYPE NEEDS TO BE CODED

Where:

filename
The file name that contains the function.

function
The function that issued the error.

Explanation: #RLOG is a required record type and at least one of the eight valid #RLOG record types must be coded.

System Action: Verification of the input continues, but no output is produced.

User Response: Code a RAMFIL statement for at least one #RLOG record type.

FCTB0113Wfilename(function) record_type WAS NOT CODED

Where:

filename
The file name that contains the function.

function
The function that issued the error.

record_type
An #RLOGx record type, where x is a number from 1 to 8.

Explanation: There are fewer #RLOGx record types coded than processors.

System Action: Verification of the input continues and output is produced unless the STOPWARNING parameter is passed to the FACE table generator (FCTBG).

User Response: Do one of the following:

FCTB0114Ifilename(function) THIS RECORD TYPE WAS SPANNED. THIS WILL AFFECT RECORD ACCESS EFFICIENCY

Where:

filename
The file name that contains the function.

function
The function that issued the error.

Explanation: A PRIOR=2 or higher was coded for an #RLOG record type. This reduces the effectiveness of the record log processing.

System Action: None.

User Response: Code an #RLOG record type with just one RAMFIL statement for each record type to improve the effectiveness.

FCTB0115Efilename(function) INVALID USER PARAMETER FOR A UNIQUE RECORD. MUST BE CODED AS (*,PROC,*) WHERE PROC IS THE PROCESSOR NAME

Explanation: The USER parameter on the RAMFIL statement was not coded correctly. It must be coded as USER=(*,proc,*), where proc is a valid processor identifier (ID).

System Action: Validation of the input is continued, but no output is produced.

User Response: Code the USER parameter on the RAMFIL statement again.

See TPF System Generation for more information about file address compute (FACE) program table generation.

FCTB0116Efilename(function) PROCESSOR UNIQUE RECORD NOT CODED FOR PROC: processor

Where:

processor
The processor identifier (ID).

Explanation: A RAMFIL statement was not coded for the specified record type and processor.

System Action: Validation of the input is continued, but no output is produced.

User Response: Code a RAMFIL statement for the specified record type and processor.

See TPF System Generation for more information about file address compute (FACE) program table generation.

FCTB0117Efilename(function) RAMFIL OVERLAYS DEFAULT VTOC AREA

Where:

filename
The file name that contains the function.

function
The function that issues the error.

Explanation: A RAMFIL statement was coded that overlays the default volume table of contents (VTOC) location. The location for the VTOC placement defaults to the last valid track location for the specified device type.

System Action: Validation of the input continues, but no output is produced.

User Response: Do one of the following:

See TPF System Generation for more information about file address compute (FACE) program table generation.

FCTB0118Efilename(function) VTOC MUST COVER A FULL TRACK

Where:

filename
The file name that contains the function.

function
The function that issues the error.

Explanation: A RAMFIL statement was coded that specified a volume table of contents (VTOC) location, but the number of records that was specified does not fill the entire track.

System Action: Validation of the input continues, but no output is produced.

User Response: Code the RAMFIL statement, specifying enough records to allocate a full track.

See TPF System Generation for more information about file address compute (FACE) program table generation.

FCTB0119Efilename(function) VTOC MUST END BEFORE CYLINDER 4369 TRACK 1

Where:

filename
The file name that contains the function.

function
The function that issues the error.

Explanation: A RAMFIL statement was coded that specified a volume table of contents (VTOC), but the track location is beyond the last valid track address of cylinder 4369, head 0.

System Action: Validation of the input continues, but no output is produced.

User Response: Code the RAMFIL statement, specifying a track location before cylinder 4369, head 1.

See TPF System Generation for more information about file address compute (FACE) program table generation.

FCTB0120Efilename(function) INVALID USER PARAMETER FOR A UNIQUE RECORD. MUST BE CODED AS (SSUN,PROC,*) WHERE SSUN IS THE SUBSYSTEM USER NAME AND PROC IS THE PROCESSOR NAME

Where:

filename
The file name that contains the function.

function
The function that issues the error.

Explanation: The USER parameter for the RAMFIL statement was not coded correctly. The parameter must be coded as USER=(ssun,proc,*), where ssun is a valid subsystem user (SSU) name and proc is a valid processor identifier (ID).

System Action: Validation of the input continues, but no output is produced.

User Response: Correct the USER parameter for the RAMFIL statement.

See TPF System Generation for more information about file address compute (FACE) program table generation.

FCTB0121Efilename(function) SUBSYSTEM USER AND PROCESSOR UNIQUE RECORD NOT CODED FOR SUBSYSTEM USER ssun AND PROCESSOR proc

Where:

filename
The file name that contains the function.

function
The function that issues the error.

ssun
The name of a subsystem user (SSU).

proc
The processor identifier (ID).

Explanation: A RAMFIL statement was not coded for the specified record type with a USER parameter of USER=(ssun,proc,*).

System Action: Validation of the input continues, but no output is produced.

User Response: Code a RAMFIL statement for the specified record type for this subsystem user and processor combination.

See TPF System Generation for more information about file address compute (FACE) program table generation.

FCTB0122Efilename(function) NFBACK=f ON RAM STATEMENT REQUIRES kfbxn range NOT CODED

Where:

filename
The file name that contains the function.

function
The function that issues the error.

f
The value of the NFBACK parameter of the RAM macro statement.

kfbxn
The highest keypoint fallback extent required by the NFBACK parameter.

range
The range of required fallback extents not coded. This can be a single fallback extent such as #KFBX5 or a range of extents as in #KFBX3 - #KFBX5.

Explanation: When the NFBACK parameter of the RAM macro is not zero, the number of #KFBXn definitions must be equal to or greater than the number of fallback extents defined by the NFBACK parameter. The range of required #KFBXn definitions is #KFBX0 - #KFBXn, where n is the value of the NFBACK parameter minus 1 (n = f - 1).

System Action: Validation of the input continues, but no output is produced.

User Response: Do one of the following:

See TPF System Generation for more information about the FACE table (FCTB).

FCTB0123Wfilename(function) NFBACK=f ON RAM STATEMENT REQUIRES kfbxn range WILL NOT BE USED FOR FALLBACK EXTENTS

Where:

filename
The file name that contains the function.

function
The function that issues the error.

f
The value of the NFBACK parameter of the RAM macro statement.

kfbxn
The highest keypoint fallback extent required by the NFBACK parameter.

range
The range of excess fallback extents coded. This can be a single fallback extent such as #KFBX5 or a range of extents as in #KFBX3 - #KFBX5.

Explanation: When the NFBACK parameter of the RAM macro is not zero, the number of #KFBXn definitions must be equal to or greater than the number of fallback extents defined by the NFBACK parameter. The range of required #KFBXn definitions is #KFBX0 - #KFBXn, where n is the value of the NFBACK parameter minus 1 (n = f - 1). Only the number of definitions specified by the NFBACK parameter are used. If the NFBACK parameter is set to zero, all the #KFBXn definitions are used.

System Action: Validation of the input continues. Output is produced unless the STOPWARNING parameter is passed to the FACE table generator (FCTBG).

User Response: To avoid confusion, remove the excess #KFBXn definitions or change the value of the NFBACK parameter to zero.

See TPF System Generation for more information about the FCTBG.

FCTB0999Tfilename(function) UNDEFINED ERROR NUMBER number.

Where:

filename
The file name that contained the function.

function
The function that issued the error.

number
The error number.

Explanation: The error number is not recognized.

System Action: Processing is ended immediately.

User Response: See your IBM service representative.

See TPF System Generation for more information about the file address compute (FACE) program table generation.