Text |
Error on NATSPOOL file. |
Explanation |
A response code different from 0 was returned when accessing the NATSPOOL file. |
Action |
Check status of the NATSPOOL file and correct error. |
Text |
NATSPOOL: Record not found for a report being printed. |
Explanation |
To store a report on the NATSPOOL file, NATSPOOL tries to read the current DETAIL record (for update). This request failed because the record could not be found. |
Action |
Re-run the Natural program which generates the report. |
Text |
NATSPOOL: Invalid output length in WRITE (rep) statement. |
Explanation |
The NATSPOOL nucleus receives lines of output from the Natural nucleus. The length of one of these lines is not positive. |
Action |
Contact Software AG support. |
Text |
NATSPOOL: No message group record found for a group. |
Explanation |
To store a queue on the NATSPOOL file, NATSPOOL reads a free group, updates the DETAIL record and then tries to read the previous group record (for update). This request failed because the record could not be found. |
Action |
Re-run the Natural program which generates the queue. |
Text |
DMS error DXXX occurred during work- or print file access. |
Action |
Check file command settings for work- or print file. |
Text |
NATSPOOL file is full. |
Explanation |
The NATSPOOL file, which is used as the physical spool file for all reports produced by Natural programs, is full. The maximum number of reports that may be contained in the NATSPOOL file, is defined via the formatting function of the Spool File Maintenance. |
Action |
(1) Print some reports with disposition D; or (2) Delete some reports; or (3) Increase the spool file (see Spool File Maintenance). |
Text |
NATSPOOL: Job number record not found on checkpoint. |
Explanation |
The NATSPOOL environment (user profiles, logical printer profiles) has been correctly defined, but the part of the file which is to contain the printout queues has not been pre-formatted. |
Action |
Format the NATSPOOL file, using the F-function of the NATSPOOL operator commands. |
Text |
NATSPOOL: Interval control error. |
Explanation |
The NATSPOOL printer task could not be started because an invalid type of request was received for processing by the CICS interval control program. |
Action |
Contact your system programmer. |
Text |
NATSPOOL: GETMAIN for work area failed. |
Explanation |
This error may be caused by one of the following: 1) During initialisation, the Natural Advanced Facilities work area (2 KB) could not be allocated. 2) During execution, the size of this work area was not sufficient. |
Action |
1) Increase the thread size. 2) Contact Software AG support. |
Text |
NATSPOOL: Index record not found for a queue. |
Explanation |
This error is caused by an internal error within the NATSPOOL nucleus. |
Action |
Contact your Natural adminstrator; if necessary, contact Software AG support. |
Text |
NATSPOOL: Invalid form or destination. |
Explanation |
An internal error has occurred in the NATSPOOL nucleus. |
Action |
Contact your Natural administrator; if necessary, contact Software AG support. |
Text |
NATSPOOL: Index record not found during close processing. |
Explanation |
To close a report on the NATSPOOL file, the index record is updated with 'number of pages' and status 'to be printed'. This request failed because the index record could not be found. |
Action |
Re-run the Natural program which creates the report. |
Text |
NATSPOOL: EXEC CICS START, invalid SYSID. |
Explanation |
The SYSID of the printer associated with the NATSPOOL printer task could not be found. |
Action |
Contact your Natural administrator. |
Text |
NATSPOOL: EXEC CICS START, invalid transaction ID. |
Explanation |
The transaction ID of the NATSPOOL printer task could not be found in the CICS Program Control Table. |
Action |
Contact your Natural administrator. |
Text |
NATSPOOL: EXEC CICS START, invalid printer ID. |
Explanation |
The terminal ID of the printer associated with the NATSPOOL printer task could not be found in the CICS Terminal Control Table. Possible reasons are: - a misspelt printer name in the NATSPOOL Allocation Table; or - the terminal ID of the printer is not contained in the CICS TCT. |
Action |
Check NATSPOOL Allocation Table or contact your Natural administrator. |
Text |
NATSPOOL: Printer not defined in CICS, or LOCATE failed. |
Explanation |
When scanning the CICS Terminal Control Table (DFHTC CTYPE=LOCATE), the terminal ID specified in TCATPTA could not be located. |
Action |
Contact your Natural administrator. |
Text |
NATSPOOL: CICS locate failed. |
Explanation |
When scanning the CICS Terminal Control Table (DFHTC CTYPE=LOCATE), an error occurred. |
Action |
Contact your Natural administrator. See program NATAF in the Natural ADVANCED FACILITIES source library. |
Text |
NATSPOOL: Open printer for hardcopy output failed. |
Explanation |
The hardcopy system was invoked with the request 'OPEN PRINTER FOR OUTPUT', but the OPEN failed. |
Action |
Contact your Natural administrator. |
Text |
Duplicate index record on NATSPOOL file. |
Explanation |
To close a queue on the NATSPOOL file, NATSPOOL updates the index record with 'number of pages' and status 'to be printed'. This request failed because more than one index record with the same key was found. |
Action |
Re-run the Natural program which generates the print queue. |
Text |
NATSPOOL: CSECT 'NOMPUT' is missing. |
Explanation |
The CSECT 'NOMPUT', which is used when routing reports from NAF to NOM is either missing in the link-edit stream or the name of the CSECT 'NOMPUT' has been changed. |
Action |
Check for the presence of NOMPUT in the link-edit stream. |
Text |
NATSPOOL: NOM has not been installed. |
Explanation |
A NAF report has been created for NOM (Entire Output Management), but NOM has not been installed. |
Action |
Install NOM. |
Text |
Logical printer profile ... not found on spool file. |
Explanation |
When using RSO direct support for printing, NAF reads the corresponding LPF from the spool file. During CLOSE processing, this LPF could not be read, either because it did not exist or because an Adabas error occurred. |
Action |
Check why the LPF could not be read. |
Text |
Logical printer profile ... not found on spool file. |
Explanation |
(1) The logical printer referred to in the user's Natural program,
has not been associated with the user profile.
(2) The Natural session was not started with a correct PRINTER
parameter for NATSPOOL, i.e. PRINTER=(NATSPOOL,...).
(3) The OUTPUT operand of a DEFINE PRINTER statement references
a logical printer profile which does not exist on the spool file. |
Action |
(1) Define a logical printer profile for the user,
using the U function of the NATSPOOL operator command.
(2) Define a correct PRINTER parameter for NATSPOOL. |
Text |
NATSPOOL: No physical printer allocated to hardcopy. |
Explanation |
A hardcopy was requested (%H), but no physical printer is allocated. When hardcopies are requested, an allocation between the logical printer DESTINATION: TERMID of the user's terminal FORM: A and at least one physical printer must be defined. The allocated printer(s) must be added to the NATSPOOL file. |
Action |
Define an allocation between logical and physical printer, by using the hardcopy allocation function of SYSPOOL. |
Text |
NATSPOOL: Invalid function code in hardcopy write. |
Explanation |
The hardcopy system was invoked with a request different from OPEN, PUT, or CLOSE. |
Action |
Contact your Natural administrator. |
Text |
NATSPOOL: Hardcopy system not available. |
Explanation |
A hardcopy was requested (%H), but NATSPOOL did not provide
support for hardcopy due to one of the following reasons:
(1) The module NATSPOOL is not included in the link-edit of Natural.
(2) During initialization of Natural, the GETMAIN for the
hardcopy system has failed. |
Action |
(1) Include NATSPOOL in the link-edit of Natural. (2) Ensure that sufficient storage is available. |
Text |
NATSPOOL: CSECT 'NAFPARM' is missing. |
Explanation |
This error may be caused by one of the following: - The Natural Advanced Facilities parameter module NAFPARMC/NAFPARMI is missing in the link-edit stream. - The CSECT instruction is missing in the source of the parameter module. - The name in the CSECT instruction has been changed; the name must be 'NAFPARM'. |
Action |
Check for the presence of the parameter module in the link-edit stream; check if the source of the parameter module is correct/complete. |
Text |
No logical printer profile for hardcopy found. |
Explanation |
When the user issues %H, NAF needs a logical printer profile (LPF). The name of this LPF is built from CMTERMID or USRID, depending on NAF customization. This LPF was not found during session initialization - probably it has been deleted from the spool file. |
Action |
Provide such an LPF or issue %Hxyz where xyz is the name of an existing LPF. |
Text |
NATSPOOL: Logical printer :1: not available. |
Explanation |
The logical printer number in the user's Natural program referres to a logical printer profile that does not exist in the currently active user profile. If the session is protected by Natural Security, the usage of this printer might have been restricted by means of the SPOOL profile. |
Action |
Correct the printer number or contact your Natural Security administrator. |
Text |
NATSPOOL: FSPOOL version not compatible (... error ...) |
Explanation |
A database error (Adabas/VSAM) occurred when trying to access FSPOOL. The error number is specified in the error message. Most likely, FSPOOL does not have the layout (FDT) required by the current version of Natural Advanced Facilities. |
Action |
Ensure that FSPOOL has the correct layout (DBID/FNR). |
Text |
NATSPOOL: CSECT :1: is missing. |
Explanation |
The CSECT specified in this error message is missing in the link-edit stream. |
Action |
If NAFIO is missing, check for the presence of module NAFAF. If NAFBS2FC is missing, check for the presence of module NAFSERVR. |
Text |
NATSPOOL: Job number record not found during 'close'. |
Explanation |
When closing a report, NATSPOOL has to update the job number record. However, this record was not found. |
Action |
Contact Software AG support. |
Text |
Unable to close report on spool file. |
Explanation |
When closing a report, NATSPOOL has to update the job number record. If this record is in 'hold' by another user, NATSPOOL retries 10 times. Thereafter, 'close' processing is terminated with this error. This error condition may occur if there are reports on the spool file which are assigned the status NOT CLOSED. This report status indicates that an END OF TRANSACTION statement is missing in the respective application. |
Action |
Check the spool file for reports with status NOT CLOSED; then check why report status NOT CLOSED is assigned. |
Text |
NATSPOOL: Unable to start printer. |
Explanation |
To start a printer, NATSPOOL has to update the printer status. If this record is in 'hold' by another user, NATSPOOL retries 10 times; thereafter, processing is terminated with this error. |
Action |
Try to restart the printer. Increase ADARUN NH parameter to prevent Adabas response code 145. |
Text |
NATSPOOL: Unable to set printer to status HUNG. |
Explanation |
When assigning status HUNG to a printer, NATSPOOL has to update the printer status. When this record is in 'hold' by another user, NATSPOOL retries 10 times; thereafter, processing is terminated with this error. |
Action |
Check why the printer record is in 'hold'. |
Text |
Physical printer ... is not defined on spool file. |
Explanation |
The terminal command '%Hdddddddd' was entered, but the output destination 'dddddddd' has not been defined on the spool file. |
Action |
Define the physical printer 'dddddddd' on the spool file. |
Text |
NATSPOOL: NAFEXIT4 completed with errors. |
Explanation |
The user written exit NAFEXIT4 returns with error(s). |
Action |
Please check program. |
Text |
NATSPOOL: NAFEXIT4 not found. |
Explanation |
The module NAFEXIT4 was not linked to the Natural nucleus. |
Action |
Please check you installation. |
Text |
NATSPOOL: Getmain for RSO buffer failed. |
Explanation |
To support RSO directly, Natural Advanced Facilities needs a buffer with a size of approximately 3700 bytes. This buffer could not be allocated. |
Action |
Please check your installation. |
Text |
NATSPOOL: WRLST macro failed using RSO support. |
Explanation |
Reports to be created using the RSO support of Natural Advanced Facilities are written to a BS2000 *SYSLST dataset. Execution of the WRLST macro failed. |
Action |
Please switch on protocol and check for any errors. |
Text |
NATSPOOL: PRNT macro failed using RSO support. |
Explanation |
Reports closed for printout are spooled to RSO using the PRNT macro. Execution of this macro failed. |
Action |
Please switch on protocol and check for any errors. |
Text |
NATSPOOL: Invalid printer no. for RSO support (internal). |
Explanation |
The internal printer number given to module NAFRSO was invalid. |
Action |
Please check assembly of NAFRSO and take dump. |
Text |
NATSPOOL: Invalid func. code for RSO support (internal). |
Explanation |
The module to handle the RSO direct support was called using an incorrect internal function code. |
Action |
Please check assembly of NAFRSO and take dump. |
Text |
NATSPOOL: No device name found for RSO support (internal) |
Explanation |
The module to handle the RSO direct support was called without setting a device name. |
Action |
Please check assembly of NAFRSO and take dump. |
Text |
NATSPOOL: Allocate SYSLST failed for RSO support. |
Explanation |
The allocation of the *SYSLST dataset failed. |
Action |
Please switch on protocl and check for any errors. |
Text |
NATSPOOL: Line starts with invalid control character. |
Explanation |
One or more lines of the report spooled by RSO direct support do not contain a valid control character (line feed, form feed, etc.) |
Action |
Please check program. |
Text |
NATSPOOL: Release SYSLST failed for RSO support. |
Explanation |
Resetting the *SYSLST allocation to the primary one has failed. |
Action |
Please switch on protocol and check for any errors. |
Text |
Attempt to execute READ/WRITE WORK to non-existent file. |
Explanation |
The work file specified in the job control does not exist. |
Action |
Check allocation of work files. |
Text |
Invalid stack function requested. |
Explanation |
See Natural Programmer's Guide for information on available stack functions. |
Action |
Correct error. |