This section describes the messages produced in the plug-in (PIN) modules of the error handling and message buffering facility.
SM-PINTAUTOR1 | SM-PINAUTOR2 | SM-PINAUTOR3 | SM-PINAUTOR4 | SM-PINAUTOR5 | SM-PINAUTOR6| SM-PINTAUTOR1 | File number not found in thread |
| Explanation |
An autorestart error occurred and PINAUTOR attempted to exclude the file from autorestart processing. Because the file number is not contained in the thread, it is not possible to exclude the file and the nucleus terminates. |
| Action |
Follow normal procedures for the parameter error 31 message. |
| SM-PINAUTOR2 | Will exclude file file-number from autorestart |
| Explanation |
The parameter error 31 message is related to the file number indicated in the message. The file has now been excluded from autorestart processing and an attempt will be made to perform autorestart without the file. |
| Action |
An excluded file may become inconsistent and need to be restored from a backup using ADASAV RESTORE. |
| SM-PINAUTOR3 | Maximum number of files excluded from autorestart |
| Explanation |
The maximum number of files allowed to be excluded has been exceeded. |
| Action |
Adjust the number of files allowed for exclusion in ADASMXIT and retry autorestart, or restore and regenerate your database. |
| SM-PINAUTOR4 | File or response code invalid for exclusion |
| Explanation |
The file or response code has been specified as ineligible for exclusion in ADASMXIT. |
| Action |
Modify the ADASMXIT table to allow the response code or file and retry autorestart or follow the same recovery guidelines as for a parameter error 31. |
| SM-PINAUTOR5 | Not possible to exclude RSP response-code |
| Explanation |
The response code encountered may not be excluded |
| Action |
Follow the recovery guidelines as specified for a parameter error 31 |
| SM-PINAUTOR6 | Cannot exclude system file |
| Explanation |
The error relates to the checkpoint or security file. It is not possible to exclude either of these files. |
| Action |
Follow the recovery guidelines as outlined for a parameter error 31. |