Installation Verification for Natural Advanced Facilities under CICS on z/OS

#### Search Results

Search

# Installation Verification for Natural Advanced Facilities under CICS on z/OS

You can verify the successful installation of Natural Advanced Facilities by following the instructions provided in this section.

- System Testing

- NATSPOOL Reason Codes

- NATSPOOL Initialization Console Messages

- NATSPOOL Print Server Messages

- NATSPOOL Abend Codes

## System Testing

You can perform the following steps to determine whether Natural Advanced Facilities functions correctly.

To print a test report

- In the appropriate logical printer, set the `Disposition` to `K` for testing.

  Log on to the Natural system library `SYSPOOL` and execute the programs `NTEST` and `SPPTEST`. These programs contain `WRITE (1)` statements.

  Oder:
  Create test reports with Function 42 described in the Natural Advanced Facilities documentation.

To proceed if a test report cannot be printed

1. Check that the CICS printer status is `IN SERVICE`.

2. Use the CICS message switching transaction `CMSG` to route a message to the specified printer:

       CMSG 'message',ROUTE=term-id,SEND

   where `term-id` is the terminal identification of the CICS printer as specified in the TCT.

3. If Natural Security is installed, check whether logon error records (of the `NATSPOOL` spool server `NATP`) have been written to the Natural Security system file. The maintenance system for these error records can be invoked by entering `ERROR` in the command line of Natural Security.

4. Check that the standard Natural `LOGON` object has not been replaced. The `NATSPOOL` spool server `NATP` must be able to execute the `SVPCIC01` module in the `SYSPRINT` library.

   Also check whether the `LOGON` user exit causes the `LOGON` of the spool server to `SYSPRINT` to terminate.

5. Check that the catalog dates of the objects in `SYSPRINT` and `SYSPOOL` are identical to one another.

6. Check that the parameters for the spool server match the Natural Advanced Facilities environment. To do so, invoke `MENU` in the `SYSPOOL` library and check the CICS Options defined with Function 30.5 (see the Natural Advanced Facilities documentation).

7. Check that neither the external security (`EXTSEC` operand of CICS PCT) nor the security levels (`TRANSEC` operand of CICS PCT) are defined for the spool server `NATP`. This ensures that `NATP` can be initiated without security violations.

8. Check the TCT and VTAM definitions (see Step 10: Define Natural Advanced Facilities for Natural Security, Step 13: Define Natural Advanced Facilities for VTAM/SNA and Step 14: Define Natural Advanced Facilities for VTAM/non-SNA in the section Installing Natural Advanced Facilities under CICS).

9. Allocate a screen device instead of a printer device to the `Destination/Form` pairing of the first logical printer, execute `NTEST` in the `SYSPOOL` library, and check for error messages on the screen.

   On certain devices, the CICS abend ATNI may occur.

   Since the Natural Security logon processing checks whether the device is a printer, this test is only possible if Natural Security is not installed.

10. Start the transaction `CEDF` for your terminal device and check whether the command `EXEC CICS START` (to start the spool server) is executed.

11. Start the transaction `CEDF` for your printer device (`CEDF` terminal ID of printer) and check which commands are executed.

12. Check the Natural Advanced Facilities messages on the system operator console and/or in the log file (the destination of messages is defined with Function 30.5 (see the Natural Advanced Facilities documentation).

    Console messages sent by the spool server start with:

        NAF SP-SERV:

    Console messages sent by the terminal task start with:

        NAF-

13. Obtain a `NATSPOOL` trace and check which Natural Advanced Facilities modules are called, which Adabas commands are executed, and which return codes are encountered.

### NATSPOOL Trace using SYSRDC

To obtain an online `NATSPOOL` trace by using the Natural SYSRDC utility

1. Start a Natural session with the following dynamic parameters:

       RDCSIZE=100, TRACE=(NATAM08), ITRACE=ON

2. Log on to the `SYSRDC` library.

3. Execute the following command to select the internal trace type:

       RDCSET N

4. Execute the following command to start the trace:

       RDCSTART

5. Execute a program which creates a report, for example, `NTEST` in the `SYSPOOL` library.

6. Log on to the `SYSRDC` library.

7. Execute the following command to display the trace entries:

       RDCDISP

   You will now see when a `NATSPOOL` module begins (marked as `BEG`) and ends (marked as `END`) as well as its return code in decimal representation.

   After the execution of an Adabas call (marked as `ADA`), you will see the command code, the first byte of the command ID and the return code in decimal representation.

For detailed information on the SYSRDC utility, see the Utilities documentation.

## NATSPOOL Reason Codes

Errors that may occur during the check for printer availability:

Error | Description
--- | ---
`INV REQU` | Invalid request
`INV ID` | Invalid ID
`INV ADDR` | Invalid address
`INV DEVC` | Invalid logical device code for page status
`ATI REQU` | ATI required on NON-ATI terminal
`RESO PRO` | Resource problem for inter-partition session
`INV PROG` | Invalid program name
`UNAB PER` | Unable to perform request
`INV TYPE` | Type is not LUC
`RESO QUI` | Resource quiesced by TMP
`LOCATERR` | Any error different from those listed above

Errors that may occur during the start of the spool server:

Error | Description
--- | ---
`TERMIDER` | Terminal ID error
`TRANIDER` | Transaction ID error
`SYSIDERR` | `SYSID` error
`INVREQ` | Invalid request
`IOERR` | I/O error
`LENGERR` | Length error
`ISCINVRE` | ISC invalid request
`NOTAUTH` | Not authorized
`STARTERR` | Any error different from those listed above

## NATSPOOL Initialization Console Messages

Messages that may occur during the initialization of `NATSPOOL`:

Message | Text
--- | ---
`NAF-01C` | `ADABAS RCxxx, DBIDxxx, FNRxxx, AT OPEN`
`NAF-02C` | Not used
`NAF-03C` | `ADABAS RCxxx, DBIDxxx, FNRxxx, AT READ REPORT`
`NAF-04C` | `ADABAS RCxxx, DBIDxxx, FNRxxx, AT READ PRINTER`
`NAF-05C` | `ADABAS RCxxx, DBIDxxx, FNRxxx, AT CLOSE`
`NAF-06C` | `ADABAS RCxxx, DBIDxxx, FNRxxx, AT UPDATE REPORT`
`NAF-07C` | `ADABAS RCxxx, DBIDxxx, FNRxxx, AT UPDATE PRINTER`
`NAF-08I` | `REPORT xxxxxxxxx`, `JOBxx.xxx`, `SET -TO BE PRINTED-`
`NAF-09I` | `PRINTER xxxx SET -FREE-`
`NAF-10I` | `PRINTER xxxx RESTARTS IN 20 SECONDS, DEST=xxxxxxxx, FORM=x`
`NAF-11C` | `RESTART ERROR NAT xxxx ON PRINTER xxxx`

## NATSPOOL Print Server Messages

See the online help for descriptions of the `NATSPOOL` print server messages.

To invoke online help for print server messages

1. In the Natural Spool Administration Menu, press PF1.

2. Enter function code `99` (miscellaneous information).

3. Enter function code `4` (Natural Advanced Facilities `SP-SERV` messages from spool server).

## NATSPOOL Abend Codes

Abend Code | Reason | Action
--- | --- | ---
`NAF1 - INVALID LENGTH` | The length of the data to be printed is not positive. | Obtain the dump and contact Software AG technical support.
`NAF2 - INVALID LENGTH` | The length of the data to be printed is greater than the maximum length of the terminal I/O buffer (`TIOBM`). | Obtain the dump and contact Software AG technical support.
`NAF3 - INVALID RETURN CODE` | The return code of the task-end routine `CMTSKND` is not zero. | Obtain the dump and contact Software AG technical support.
`NAF4 - INVALID RETURN CODE` | The return code of the print routine `CMWTERM` is not zero. | Obtain the dump and contact Software AG technical support.

### On this page

- System Testing
- NATSPOOL Reason Codes
- NATSPOOL Initialization Console Messages
- NATSPOOL Print Server Messages
- NATSPOOL Abend Codes