SMARTS API Messages

#### Search Results

Search

# SMARTS API Messages

### Overview of Messages

`PSX0000 | PSX0001 | PSX0002 | PSX0003 | PSX0004 | PSX0005 | PSX0006 | PSX0007 | PSX0008 | PSX0009 | PSX0010 | PSX0012 | PSX0013 | PSX0014 | PSX0015 | PSX0016 | PSX0019 | PSX0020 | PSX0022 | PSX0023 | PSX0024 | PSX0025 | PSX0026 | PSX0029 | PSX0030 | PSX0031 | PSX0033 | PSX0034 | PSX0035 | PSX0036 | PSX0037 | PSX0038 | PSX0040 | PSX0041 | PSX0042 | PSX0043 | PSX0044 | PSX0045 | PSX0046 | PSX0047 | PSX0048 | PSX0049 | PSX0050 | PSX0051 | PSX0052 | PSX0053 | PSX0054 | PSX0055 | PSX0056 | PSX0057 | PSX0058 | PSX0059 | PSX0060 | PSX0062 | PSX0063 | PSX0064 | PSX0065 | PSX0066 | PSX0067 | PSX0068 | PSX0069 | PSX0070 | PSX0071 | PSX0072 | PSX0073 | PSX0074 | PSX0075 | PSX0076 | PSX0077 | PSX0078 | PSX0079 | PSX0080 | PSX0081 | PSX0082 | PSX0083 | PSX0084 | PSX0085 | PSX0086 | PSX0087 | PSX0088 | PSX0089 | PSX0090 | PSX0091 | PSX0092 | PSX0094 | PSX0095 | PSX0096 | PSX0099`

PSX0000 | Insufficient storage ($1 bytes) for $2
Description | An attempt by the SMARTS nucleus to acquire storage failed due to insufficient space either in a user program thread or in the SMARTS address space itself. #### Placeholders
$1 | The number of bytes the system tried to acquire. The number may be suffixed with `K' to denote kilobytes or `M' to denote megabytes. If this value is `0', SMARTS was not able to determine how much storage could not be acquired. This could occur when a request to an underlying system fails due to a storage shortage but does not indicate how much is required.
$2 | A character string indicating what the storage was for and, if applicable, a four digit code in braces indicating which control block this storage was for.
Action |
• | If the storage is thread-related, use the ULIB utility to increase the catalog size of the root application that suffered the error. The root application is the first program to receive control when a program is started under SMARTS and is the basis upon which the storage is allocated. Note that the thread sizes in general may need to be increased in the SMARTS region depending on how much thread space the application requires.
• | If the storage is outside of the thread, there is a shortage of storage in the SMARTS region itself. Where possible, SMARTS will expand its storage areas so it is likely that such an expansion request failed thus resulting in this message. Check for other errors related to any attempted expansion for more details.
#### References
• | The SMARTS Installation and Operations Manual discusses storage allocations and how they relate to the SMARTS components.
• | The following table identifies the storage areas by name, where it may be located and what it is used for:
Storage Name | Location | Description
--- | --- | ---
atexit() registration table | Above | Allocated per process to hold any exit routines registered using the atexit() function.
File subsystem I/O buffer | Below or Above | One of these control blocks is acquired from the SMARTS buffer pool per open file, socket, or pipe. It is required as an input/output buffer to access the underlying subsystem entity. If required for a file, it is allocated below the line. For any other use, it is allocated above the line.
File table storage | Above | This storage is allocated per SMARTS process to hold the file descriptors for each open file in the system.
Kernal storage stack | Above | Allocated by the environment-dependent kernel interface module to drive the SMARTS independent kernel interface.
Working storage | Above | A generic term for required temporary storage.
SMARTS server environment ABEND data area (ABDA) | Above | Allocated per SMARTS pthread in the SMARTS server environment to handle recovery processing for pthread termination (normal or abnormal) in the server environment.
SMARTS server application storage (APPS) | Above | Allocated per SMARTS-based server started within the SMARTS server environment.
Argument buffer (ARGB) | Above | One allocated per invoked process to hold arguments passed to main(), environment variables passed to invoked process (addressable through environ), and pointers.
CDI parameter block (CDIB) | Above | One allocated per open file descriptor in a process to maintain state of the file descriptor and pass information to/from CDI protocol drivers.
CDI PH main anchor block (CDIM) | Above | One allocated per defined CDI protocol handler (driver). Used to hold CDI protocol-related information.
CDI PH process anchor block (CDIP) | Above | One allocated per defined CDI protocol handler per process to hold process-related protocol information.
CDI PH thread anchor block (CDIT) | Above | One allocated per defined CDI protocol handler per thread to hold thread-related protocol information.
Console interface block (CNIB) | Above | Allocated when an fopen() is issued to the console CDI driver.
Console interface command block (CNIC) | Above | Allocated in order to deliver a command to the console CDI driver interface.
Console interface main block (CNIM) | Above | Allocated to centrally control the console interface CDI driver processing.
Environment variable storage (ENVV) | Above | One of these areas is allocated per environment variable. If the environment variable is a global environment variable, it is allocated from the SMARTS buffer pool. If the environment variable is being locally defined using the `putenv' function, it is allocated from the application program thread.
File subsystem control block (FSCB) | Below or Above | One of these control blocks is acquired from the SMARTS buffer pool per open file, socket, or pipe. If required for a file, it is allocated below the line. For any other use, it is allocated above the line.
Internal security control block (ISCB) | Above | Allocated per SMARTS process to hold user-related information.
Language interface process table (LIPT) | Above | Allocated per process to handle languages calling other languages.
Language interface thread table (LITT) | Above | Allocated per pthread to enable language cleanup for each language used within the process.
Master control block (PMCB) | Below | The main control block allocated by SMARTS. Acquired from the underlying SMARTS server environment work storage buffer pool.
Mutex control block (PMXB) | Above | Allocated internally to control access to internal resources using the standard pthread mutex processing logic.
Process control block (PPCB) | Above | The SMARTS process control block, which is allocated once in the program thread the first time a SMARTS function request is issued.
Signal raise control block (PSGR) | Above | Allocated when a signal has to be raised either from the system internally or as a result of a user program request.
Thread control block (PTHB) | Above | Allocated per SMARTS pthread to represent the pthread.
Thread-specific data area (PTSD) | Above | Allocated by the user program per SMARTS pthread to hold any thread-specific dataset.
Thread cancel clean-up table (PTTH) | Above | Allocated per SMARTS pthread in all environments to hold each entry pushed on to the stack using the pthread_cleanup_push() function.
Sockets main control block (SOCB) | Above | Allocated from the SMARTS buffer pool by the subsystem specific sockets initialization module.
System-resident control block (SRCB) | Above | One of these control blocks is allocated from the SMARTS buffer pool per active SMARTS process. It is associated with the PPCB and is used to hold per process storage areas, which must reside outside the application program thread area.
Sockets task API storage (TAIS) | Above | One of these control blocks is allocated for each SMARTS process that uses the sockets interface. It is only allocated if the IBM TCP/IP stack is in use.

PSX0001 | Logic error in program $1 at offset $2
Description | During execution, the SMARTS nucleus encountered an unexpected situation that is likely to lead to other errors or unexpected behavior. #### Placeholders
$1 | Name of the program where the logic error was encountered.
$2 | Offset within the program named in $1 where the logic error was encountered.
Action | Report this message to your technical support representative. #### References Not applicable.

PSX0002 | Function code `$1' not supported
Description | The SMARTS nucleus API was entered with a code for which it had no entry in its internal tables. This is indicative of a mismatch between the SMARTS stubs being used and the nucleus. #### Placeholders
$1 | Code (in decimal) with which the nucleus was entered.
Action | Report this message to your technical support representative. #### References Not applicable.

PSX0003 | Function `$1' code `$2' not implemented
Description | The function named by placeholder $1 has been requested by the application but is not currently implemented within the SMARTS nucleus. #### Placeholders
$1 | Name of the function which the application requested.
$2 | Internal SMARTS code associated with the function.
Action | Not applicable. #### References Refer to the SMARTS SDK Programmer's Reference Manual to determine which function calls are supported by the level of SMARTS you are running.

PSX0004 | Module `$1' Loaded
Description | The module identified by the $1 placeholder was loaded by the nucleus. This message is issued in the following cases:
• | When more than one version of a module exists, it indicates which version of the module was loaded.
• | For exits that may not normally be part of the nucleus, it indicates when an exit has been loaded and is active in the system.
#### Placeholders
$1 | Name of the module which has been loaded.
Action | This is an informational message, no action is necessary. #### References Not applicable.

PSX0005 | Module `$1' not found
Description | The module identified by the $1 placeholder cannot be found. A request to the operating system to load a module fails. Modules to be loaded by SMARTS must be available either in the COMPLIB DD concatenation or system LNKLST for OS/390 and MSP systems, while it must be in a library identified in the search path for VSE. If this message is issued during the initialization process, initialization fails if the module is required for the correct operation of SMARTS. Otherwise, initialization continues. If this message is issued during termination processing, termination continues; however, depending on the function of the module, the termination process may not complete successfully. #### Placeholders
$1 | Name of the module that could not be found.
Action | If the module should be available during initialization and/or termination processing, determine why it cannot be found. #### References Not applicable.

PSX0006 | Error loading module `$1' RC=$2 Reason=x$3
Description | The module identified by the $1 placeholder could not be loaded due to an error during LOAD processing. A request to the operating system to load a module fails for some reason other than the fact that module cannot be found. If this message is issued during the initialization process, initialization fails if the module is required for the correct operation of SMARTS. Otherwise, initialization continues. If this message is issued during termination processing, termination continues; however, depending on the function of the module, the termination process may not complete successfully. #### Placeholders
$1 | Name of the module for which the LOAD request failed.
$2 | Return code from the operating system LOAD request.
$3 | Reason code from the operating system LOAD request.
Action | Determine from the return and reason codes why the LOAD request failed and correct the error. #### References
• | MVS/ESA Programming: Assembler Services Reference
• | VSE/ESA Macro Reference

PSX0007 | Module $1 returned return code $2
Description | A number of modules are called internally during the SMARTS initialization/termination process. These modules generally issue a zero (0) return code to indicate that they have completed successfully. A module was called and its return code was not 0. The module responsible has issued a message itself to indicate where the problem lies. When this occurs during the initialization process, if the return code is less than 8, initialization processing continues. If the return code is 8 or greater, initialization processing terminates. When this occurs during the termination process, processing continues; however, if the return code is 8 or greater, there may be additional failures later in the termination process. #### Placeholders
$1 | Name of the module that returned the return code.
$2 | Return code returned by the module identified by $1.
Action | Refer to preceding messages in the log to determine why the return code was returned. Correct the situation to prevent the message. #### References Not applicable.

PSX0008 | POSIX $1 system initialized, nucleus size $2 bytes
Description | The POSIX subsystem has been successfully initialized. #### Placeholders
$1 | Name of the POSIX system as specified on the SMARTS server environment SERVER configuration parameter.
$2 | Size (in bytes) of the SMARTS nucleus. Since most SMARTS modules are loaded above the 16MB line, this storage is allocated above the 16MB line.
Action | No action is necessary as this is an informational message. #### References Not applicable.

PSX0009 | SMARTS $1 initialization failed
Description | The SMARTS initialization failed. A preceding message indicates why it failed. #### Placeholders
$1 | Name of the POSIX system as specified on the SERVER configuration parameter.
Action | Correct the reason for the initialization failure. Restart SMARTS. #### References Not applicable.

PSX0010 | POSIX $1 system already active
Description | An attempt to start the POSIX subsystem failed because it was already active. #### Placeholders
$1 | Name of the POSIX system as specified on the SERVER configuration parameter.
Action | Not applicable. #### References Not applicable.

PSX0012 | POSIX $1 system terminated
Description | The POSIX subsystem has terminated. #### Placeholders
$1 | Name of the POSIX system as specified on the SERVER configuration parameter.
Action | Not applicable. #### References Not applicable.

PSX0013 | Unrecognized command `$1'
Description | An operator command to SMARTS was rejected as it was not a valid SMARTS operator command. #### Placeholders
$1 | Operator command string entered by the operator. SMARTS did not recognize it as a valid SMARTS operator command.
Action | Select a valid SMARTS operator command. #### References The SMARTS Installation and Operations Manual .

PSX0014 | Unrecognized or invalid parameter $1
Description | SMARTS was initialized with $1 as a parameter but SMARTS did not recognize the parameter. Initialization continues, ignoring the invalid parameter. #### Placeholders
$1 | String passed to SMARTS as a parameter. This is specified either as part of the SERVER configuration parameter or as the SERVER operator command used to start SMARTS.
Action | Select a valid SMARTS parameter. #### References The SMARTS Installation and Operations Manual .

PSX0015 | POSIX $1 Build $2 Patch level=$3 Initialization in progress
Description | The POSIX subsystem started its initialization processing. #### Placeholders
$1 | Name of the POSIX system as specified on the SERVER configuration parameter.
Action | Not applicable. #### References Not applicable.

PSX0016 | Function `$1' failed return code $2 (x'$3')
Description | The function $1 was issued by the application; however, an error during the processing of the function in the SMARTS nucleus caused the $2 return code to be generated. A preceding message indicates why the return code was returned. #### Placeholders
$1 | Name of the function issued by the application program.
$2 | Internal return code (decimal) issued by the processing routine.
$3 | Internal return code (hexadecimal) issued by the processing routine.
Action | Determine from the preceding messages what caused the problem and correct these symptoms. #### References Not applicable.

PSX0019 | Error opening `$1' errno=$2
Description | SMARTS attempted to open the file identified by $1, however, the request failed due to the errno $2. The result of this message depends on when the failure occurred and what the file was to be used for. #### Placeholders
$1 | Name of the file that could not be opened in the format used by the `fopen' function as described in the SMARTS SDK Programmer's Reference Manual.
$2 | Error number returned by the open request. These are described in the SMARTS SDK Programmer's Guide.
Action | Determine why the file could not be opened using the errno returned and correct the problem. Generally this should occur when either the file does not exist or there is insufficient storage to open the file. #### References
• | SMARTS SDK Programmer's Reference Manual
• | SMARTS SDK Programmer's Guide

PSX0020 | POSIX process initialization failed
Description | The first time a POSIX function is issued from a program, SMARTS initializes the environment for the process where the application program is running. This message indicates that this processing failed and therefore the function requested by the program could not be completed. #### Placeholders Not applicable
Action | Determine from any preceding messages why the initialization process failed and correct the problem. #### References Not applicable

PSX0022 | Socket $1 request error PID=$2 rc=$3 reason=$4 diag=$5
Description | A sockets subsystem call failed. #### Placeholders
$1 | Name of the TCP/IP request that failed.
$2 | Process ID on which the failure occurred.
$3 | TCP/IP interface return code returned by the request.
$4 | TCP/IP interface reason code returned by the request.
$5 | TCP/IP interface diagnostic code returned by the request.
Action | Determine from the information returned why the error occurred. There are any number of reasons why errors will occur on a sockets call, many due to the peer to an ongoing SOCKETS conversation terminating or dropping the conversation.

PSX0023 | BATCH ENVIRONMENT $1 ERROR, INFO=$2/$3/$4
Description | An error occurred with an operating system macro in the SMARTS batch interface. #### Placeholders
$1 | Name of the operating system macro that failed.
$2 | Return code from the operation (normally register 15).
$3 | Feedback code from the operation (normally register 0).
$4 | Reserved for future use; currently, the same as $2.
Action | Determine the cause of the problem based on the operating system macro return and feedback codes; take action to correct the problem. If the action to take is not obvious, report the error to your Software AG technical support representative. #### References Refer to the manuals specific to your operating system that describe Assembler interface macros and their use.

PSX0024 | ESTAE Processing failed for $1 - RC=$2
Description | An OS/390 ESTAE macro was issued but failed with a $2 return code. Processing may continue; however, if abends occur, no recovery is in place. #### Placeholders
$1 | Function for which the ESTAE was issued.
$2 | Return code from the OS/390 operating system ESTAE macro.
Action | Based on the return codes, determine why the ESTAE failed and correct the error. #### References MVS/ESA Assembler Programmers Macro Reference Manual

PSX0025 | Sockets $1 failed
Description | The subsystem-specific SOCKETS initialization or termination did not complete successfully. If initialization processing fails, SMARTS fails to initialize. If termination processing fails, termination processing continues; however, subsequent errors may occur. In particular, the entire SMARTS address space should be brought down before attempting to restart the SMARTS as there are likely to be sockets problems if the address space is not cycled. #### Placeholders
$1 | Indicates whether `INITIALIZATION' or `TERMINATION' processing failed.
Action | Refer to preceding TCP/IP subsystem-specific error messages to determine why the failure occurred and correct the problem. #### References Not applicable.

PSX0026 | Sockets $1 successful
Description | Sockets initialization or termination processing completed successfully. #### Placeholders
$1 | Indicates whether `INITIALIZATION' or `TERMINATION' processing was successful.
Action | Not applicable. #### References Not applicable.

PSX0029 | IBM TCP/IP $1 failure AS=$2 errno=$3
Description | An error occurred for a request made by the IBM TCP/IP subsystem module. #### Placeholders
$1 | Name of the IBM TCP/IP application programming interface (API) request for which the error occurred.
$2 | Name of the IBM TCP/IP address space with which SMARTS is interfacing. This is specified using the SMARTS ADDRSPCE configuration parameter.
$3 | Error number returned by the IBM TCP/IP interface
Action | Determine from the information returned why the error occurred. There are any number of reasons why errors will occur on a sockets call, many due to the peer to an ongoing SOCKETS conversation terminating or dropping the conversation. #### References SMARTS Installation and Operations Manual IBM TCP/IP VvRr for MVS Programmers Reference

PSX0030 | POSIX $1 is quiescing
Description | The POSIX subsystem is quiescing. In this state, application programs already started may continue to completion; however, no new requests to start the SMARTS programs are allowed. #### Placeholders
$1 | Name of the POSIX system as specified on the SERVER configuration parameter.
Action | Not applicable. #### References Not applicable.

PSX0031 | Waiting for $1 user(s) to terminate
Description | The POSIX subsystem cannot terminate correctly until all application programs that have requested SMARTS functions have terminated. This message indicates the number of users of SMARTS functions upon which the server is waiting. #### Placeholders
$1 | The number of users of SMARTS applications still active who are using or have used SMARTS functions.
Action | Wait until all users have terminated and reissue the request to QUIESCE or TERMINATE the POSIX subsystem. The server may be forced; however, this is not recommended due to the subsequent problems it can cause. #### References Not applicable.

PSX0033 | Waiting on $1 dependent service(s)
Description | When subsystems initialize and have a dependency on SMARTS, they register this dependency. For example, the HTTP server may have one or more active servers in a given system. If these dependent services have not been terminated prior to SMARTS termination, SMARTS issues this message and will not terminate. #### Placeholders
$1 | Number of servers in the system that have registered their dependency on SMARTS but have not removed this dependency by terminating.
Action | Terminate any dependent services prior to requesting the termination of SMARTS. SMARTS may be forced; however, this is not recommended due to the subsequent problems it may cause and the immediate problems it will cause for dependent services. #### References Not applicable.

PSX0034 | I/O Error (errno=$1) reading $2
Description | While reading the file identified by $2, an error was returned by the I/O subsystem interface module. Processing of the file will be terminated. #### Placeholders
$1 | Error number returned by the I/O subsystem interface module as documented in the SMARTS SDK Programmer's Guide.
$2 | Name of the file upon which the I/O error occurred. This is in the format used by the `fopen' function as described in the SMARTS SDK Programmer's Reference Manual.
Action | Determine from the returned information what caused the error and correct the problem. #### References SMARTS SDK Programmer's Reference Manual. SMARTS SDK Programmer's Guide.

PSX0035 | Environment variable `$1' invalid data starting `$2'
Description | While processing the file containing the SMARTS global environment variables, a variable containing invalid data was encountered. This generally occurs when a hexadecimal value is specified for a global environment variable. #### Placeholders
$1 | Name of the global environment variable with the invalid data specified.
$2 | The first characters of the value specification as found in the file.
Action | Correct the value specification for the variable. #### References SMARTS Installation and Operations Manual.

PSX0036 | Global environment variables processed successfully
Description | The global environment variable file as specified by the GENVNAME SMARTS configuration parameter was processed successfully and the global environment variables specified in the file have been successfully defined. #### Placeholders Not applicable.
Action | Not applicable. #### References SMARTS Installation and Operations Manual.

PSX0037 | DYNALLOC FAILED (CODE=$1), DSN=$2
Description | The SMARTS attempt to allocate dataset ($2) failed. #### Placeholders
$1 | Error and information codes returned from the OS DYNALLOC macro.
$2 | Name of the dataset that SMARTS tried to allocate.
Action | Determine the cause of the problem based on the OS DYNALLOC macro error and information codes; take action to correct the problem. If the action to take is not obvious, report the error to your Software AG technical support representative. #### References Refer to the manuals specific to your operating system that describe Assembler interface macros and their use.

PSX0038 | TISP/ISP $1 failure TID=$2 RC=$3 Reason=$4
Description | TISP/ISP macro call failed. #### Placeholders
$1 | Name of the TISP/ISP request that failed.
$2 | Process ID on which the error occurred.
$3 | TISP/ISP interface return code returned by the request.
$4 | TISP/ISP interface reason code returned by the request.
Action | Use the information returned to determine why the error occurred. Errors on a TISP API call often occur when the peer to an ongoing TISP API conversation terminates or drops the conversation. #### References SMARTS Installation and Operations Manual. The Fujitsu manual TISP Handbook .

PSX0040 | R=$1 T=$2 U=$3 S=$4 RC=$5 errno=$6
Description | This message is used when sockets tracing is active and the IBM TCP/IP subsystem module is in use. #### Placeholders
$1 | Name of the IBM TCP/IP sockets request.
$2 | Address of the TCB on which the request was issued in hexadecimal format.
$3 | Number of sockets open for this process ID.
$4 | Number of the IBM TCP/IP socket for which the request was issued.
$5 | Return code from the IBM TCP/IP sockets request.
$6 | Error number returned from the IBM TCP/IP sockets request.
Action | Not applicable. #### References IBM TCP/IP VvRr for MVS Programmers Reference.

PSX0041 | Context locate/initialization failed rc=$1
Description | An attempt to build a new SMARTS context failed. Each program running under SMARTS, including the SMARTS main task itself, requires a context. When the context build fails, no further processing can occur. #### Placeholders `RC' is the return code:
8 | Error during context initialization.
Action | The reason why the build for the context failed is indicated in a preceding message. Take action to correct the problem based on that information. #### References Not applicable.

PSX0042 | Independent Kernel $1 Request failed rc=$2
Description | An attempt by the environment-specific module to make a request of the independent kernel interface failed. This can happen during SMARTS kernel initialization or termination, or while processing an operator command. If the error occurs during initialization, processing cannot continue. #### Placeholders
$1 | The request that failed:
| initialize | initialization request
| terminate | termination request
| command | command processing
$2 | Return code:
| 8 | general error
| 12 | catastrophic error
| 16 | logic error within SMARTS
Action | Take action based on a previous message that indicates why the request failed. Report return codes 12 and 16 to your Software AG technical support representative. #### References Not applicable.

PSX0043 | Resource $1 not authorized for user $2, reason $3
Description | Access to a resource (for example, a file) has been denied by the active security subsystem. #### Placeholders
$1 | Name of the requested resource.
$2 | Name of user requesting access to resource.
$3 | An implementation-specific reason code.
Action | Use the implementation-specific reason code to determine the cause of the denied access. #### References Not applicable.

PSX0044 | Invalid length supplied to `$1' function. Program will be aborted
Description | A number of functions are supported using inline coding generated by the C compiler that generated the C code. Normally, any length below 16 megabytes is dealt with inline; however, if a length greater than this is encountered, it is considered an error and this message is issued. #### Placeholders
$1 | The name of the function that received an invalid length.
Action | Trace back to the C code and determine where the length supplied was invalid; determine why the length was invalid. #### References Not applicable.

PSX0045 | pthread $1 $2 failure rc=$3
Description | An error occurred during the initialization or termination of a pthread. #### Placeholders
$1 | Initialization / termination processing
$2 | PAANTINI / PMANENVF end-of-job (EOJ) indicator
$3 | Return code
Action | Normally, a previous error indicates the reason for the error. Take action based on this information. If no reason is provided, report the problem to your Software AG technical support representative. #### References Not applicable.

PSX0046 | Pthread id $1 $2
Description | A pthread ABENDed or was cancelled. #### Placeholders
$1 | The pthread ID.
$2 | Cancelled / ABENDed.
Action | A pthread_cancel() request from the application indicates that the application has taken the decision, or an abend in a pthread indicates an error in the application code running on the pthread. Otherwise, an attempt was made to cancel all outstanding pthreads when a SMARTS instance was terminated. #### References Not applicable.

PSX0047 | DXR Server environment $1 error, info=$2/$3/$4
Description | An error occurred with an operating system macro in the SMARTS server environment. #### Placeholders
$1 | Name of the SMARTS server system macro that failed.
$2 | Return code from the operation (normally register 15).
$3 | Feedback code from the operation (normally register 0).
$4 | Reserved for future use; currently the same as $2.
Action | Based on any preceding messages and the SMARTS server macro return and feedback codes, determine the cause of the problem and take action to correct it. If the action to take is not obvious, report the error to your Software AG technical support representative. #### References Refer to appendix G in this manual.

PSX0048 | Thread id $1 Abended code X$2/$3
Description | A pthread ABENDed in the SMARTS server environment. #### Placeholders
$1 | The pthread ID.
$2 | The ABEND code in hexadecimal.
$3 | The ABEND code in binary.
Action | This message is provided as a diagnostics message: determine why the ABEND is occurring. #### References Not applicable.

PSX0049 | Required configuration parameter $1 missing oR invalid
Description | During initialization of a CDI protocol driver, a required configuration parameter was missing or invalid. As a result, the initialization of the protocol driver cannot proceed. #### Placeholders
$1 | Name of the missing or invalid configuration parameter.
Action | Add or correct the required configuration parameter and restart SMARTS. #### References SMARTS Installation and Operations Manual.

PSX0050 | CDI $1 protocol initialized
Description | A CDI protocol driver implementing the protocol specified in $1 has been successfully initialized. #### Placeholders
$1 | Name of the CDI protocol initialized.
Action | Not applicable. #### References Not applicable.

PSX0051 | Too many arguments to fit in argv list
Description | The nucleus attempted to build an argb buffer based on the input provided by the user for a SMARTS spawn*() or exec*() request; however, there was insufficient room in the ARGB buffer to hold all of the data. The size of the ARGB buffer may be determined from the _POSIX_ARG_MAX macro variable. #### Placeholders None
Action | Reduce the amount of data being passed in the ARGB buffer. #### References SMARTS SDK Programmer's Reference Manual SMARTS SDK Programmer's Guide

PSX0052 | Function $1 `$2' Unsupported
Description | FUNCLIST=YES is specified in the SMARTS configuration. A message is issued for each POSIX function that is registered within SMARTS but for which support has not yet been implemented. Note: The fact that the function has been registered within the SMARTS nucleus does not imply that it will be supported at any time in the future. #### Placeholders
$1 | Name of the POSIX function.
$2 | A short description of what the POSIX function does.
Action | No action required. If the message is no longer required, turn off the FUNCLIST configuration parameter. #### References Not applicable.

PSX0053 | Statistics Collection for: $1
Description | Indicates the functions for which statistics are being collected. #### Placeholders
$1 | List of all functions for which statistics are being collected. “NONE” if no statistics are being collected.
Action | This message is for information only. No action is required. #### References SMARTS Installation and Operations Manual.

PSX0054 | CDI $1 protocol terminated
Description | A CDI protocol handler has been terminated. This normally only happens during termination of the SMARTS environment. #### Placeholders
$1 | Name of the CDI protocol.
Action | No action is required. #### References Not applicable.

PSX0055 | CDI $1 protocol initialization error: $2
Description | An error occurred during CDI protocol handler initialization. #### Placeholders
$1 | Name of the CDI protocol.
$2 | Return code from the CDI protocol handler.
Action | This will normally be a parameter error. Correct and retry. #### References SMARTS Installation and Operations Manual.

PSX0056 | Failure to delete file `$1'
Description | An error occurred in the processing of a file delete. The file delete is attempted subsequently to a return value indicating success. This may occur if a file is open at the time of the delete command and the file is marked to be deleted at a later stage. #### Placeholders
$1 | Name of the file that was not deleted.
Action | Check for messages in the log that may indicate the reason for failure, such as a security violation. The file should be deleted if required. #### References Not applicable.

PSX0057 | Pipe $1 request error PID=$2 RC=$3 REASON=$4
Description | An error has occurred while reading form or writing to a pipe. The placeholders indicate the action that encountered the error. #### Placeholders
$1 | The file descriptor number of the pipe.
$2 | The ID of the process that encountered the error.
$3 | The return code from the pipe CDI protocol handler.
$4 | An internal reason code.
Action | This error may be caused by other error situations in the environment, such as lack of memory. Look for other symptoms, correct and retry. If the problem persists, contact your Software AG technical support representative. #### References Not applicable.

PSX0058 | DXR Server $1 $2 $3
Description | An error has occurred while dealing with a SMARTS-based server running in the SMARTS server environment. The placeholders indicate the action that encountered the error. #### Placeholders
$1 | The name of the server.
$2 | an indication as to what the issue was: Initialization — Problems with initialization. Termination — Problems with termination. Command processing — Problems processing a command for this server. Not Active — The server is not active. No longer active — The server has terminated since the last activity.
$3 | `FAILED' or blanks, depending on the context of the message.
Action | Clear up the problem leading to the message and retry the operation. #### References Not applicable.

PSX0059 | DXR server $1 $2 $3 PID=$4
Description | An operation on a SMARTS-based server running in the SMARTS server environment was completed successfully. #### Placeholders
$1 | The name of the server.
$2 | An indication of what was successful: initialization, termination, or command processing.
$4 | The process ID for the named server.
Action | No action required. #### References Not applicable.

PSX0060 | DXR $1 function failed RC=$2 RV=$3 errno=$4
Description | SMARTS itself issued a POSIX interface request that failed. #### Placeholders
$1 | Name of the POSIX function.
$2 | The assembler interface return code received from the function.
$3 | Return value received from the function.
$4 | Errno returned from the function.
Action | Determine the cause of the problem using the return value, errno, and the SMARTS SDK Programmer's Reference Manual . If the error is expected for some reason, ignore the message. If it should not have occurred, correct the problem leading to the error. #### References SMARTS SDK Programmer's Reference Manual SMARTS SDK Programmer's Guide

PSX0062 | Member $1 not stored in $2. No space left in directory
Description | No space remains in the directory: the file could not be added or the file name could not be changed. #### Placeholders
$1 | File name.
$2 | Directory name.
Action | Increase the directory or the directory index space as appropriate for the operating system file system. #### References Refer to the manuals specific to your operating system.

PSX0063 | Invalid keyword value specified for `$1'
Description | An invalid keyword value was passed in by the configuration file. Initialization continues, ignoring the invalid value. #### Placeholders
$1 | Name of the keyword that received an invalid value.
Action | Check the SMARTS Installation and Operations Manual for a valid keyword value. #### References SMARTS Installation and Operations Manual .

PSX0064 | Trace DataSpace InitialiZed, ESIZE=$1:BSIZE=$2:NBLKS=$3
Description | Informational message issued at SMARTS initialization. #### Placeholders
$1 | Trace data space element size.
$2 | Trace data space block size.
$3 | Number of blocks in the trace data space.
Action | If different values are required, set them in the configuration file. #### References SMARTS data collection facilities document.

PSX0065 | Log DataSpace InitialiZed, ESIZE=$1:BSIZE=$2:NBLKS=$3
Description | Informational message issued at SMARTS initialization. #### Placeholders
$1 | Log data space element size.
$2 | Log data space block size.
$3 | Number of blocks in the log data space.
Action | If different values are required, set them in the configuration file. #### References SMARTS data collection facilities document.

PSX0066 | Trace level = `$1'
Description | Indicates the level of tracing in the system. #### Placeholders
$1 | Level of tracing between 1 and 5, `1' being the least amount of trace data and 5 being the greatest.
Action | This message is for information only. No action is required. #### References SMARTS Installation and Operations Manual .

PSX0067 | System tracing enabled = `$1'
Description | Indicates the system tracing that is turned on. #### Placeholders
$1 | List of system tracing that is turned on.
Action | This message is for information only. No action is required. #### References SMARTS Installation and Operations Manual .

PSX0068 | No System Tracing enabled
Description | Indicates that no system tracing is enabled. #### Placeholders Not applicable.
Action | This message is for information only. No action is required. #### References SMARTS Installation and Operations Manual .

PSX0069 | No functions are being traced
Description | Indicates that no system tracing is enabled. #### Placeholders Not applicable.
Action | This message is for information only. No action is required. #### References SMARTS Installation and Operations Manual .

PSX0070 | All functions are being traced
Description | Indicates that all functions are being traced. #### Placeholders Not applicable.
Action | This message is for information only. No action is required. #### References SMARTS Installation and Operations Manual .

PSX0071 | Functions being traced: `$'
Description | Indicates the functions that are being traced. #### Placeholders
$1 | List of all functions that are being traced.
Action | This message is for information only. No action is required. #### References SMARTS Installation and Operations Manual .

PSX0072 | Functions not being traced: `$'
Description | Indicates the functions that are not being traced. #### Placeholders
$1 | List of all functions that are not being traced.
Action | This message is for information only. No action is required. #### References SMARTS Installation and Operations Manual .

PSX0073 | P=$1 T=$2 $3 at $4+X$5
Description | Back trace message. #### Placeholders
$1 | Process ID
$2 | Thread ID
$3 | 'Function call' or 'Abend'
$4 | Function name
$5 | Offset
Action | This message is for information only. No action is required. #### References Not applicable.

PSX0074 | P=$1 T=$2 $3:$4 $5 $6 $7 *$8*
Description | Back trace data. #### Placeholders
$1 | Process ID
$2 | Thread ID
$3 | Storage address
$4 | Storage contents - hex
$5 | Storage contents - hex
$6 | Storage contents - hex
$7 | Storage contents - hex
$8 | Storage contents - character
Action | This message is for information only. No action is required. #### References Not applicable

PSX0075 | P=$1 T=$2 aborted due to $3 signal
Description | Abort due to signal. #### Placeholders
$1 | Process ID
$2 | Thread ID
$3 | Signal number
Action | This message is for information only. No action is required. #### References Not applicable

PSX0076 | Out of storage - increase region size
Description | Error - increase region size. #### Placeholders None
Action | Increase region size, rerun. #### References SMARTS Installation and Operations Manual.

PSX0077 | PFS termination checkpoint failed
Description | PFS checkpoint failure. #### Placeholders None
Action | Report this message to your technical support representative. #### References Not applicable.

PSX0078 | PFS container capacity at $1%
Description | PFS container is in danger of filling up. #### Placeholders
$1 | Percentage used
Action | Once this message has been received more than once for a particular container it should be resized #### References SMARTS Installation and Operations Manual.

PSX0079 | $2 block $1 corrupted
Description | A block was corrupted. #### Placeholders
Action | Report this message to your technical support representative. #### References Not applicable.

PSX0080 | Error in ''$1'', record number $2
Description | Invalid record in hosts, protocols, services or networks file. #### Placeholders
$1 | Name of file containing invalid record.
$2 | Record number of invalid record in file.
Action | Check relevant record in input file for error. #### References SMARTS Installation and Operations Manual.

PSX0081 | Error on PUT, DDNAME=$1
Description | PUT error, Data collection file. #### Placeholders
$1 | ddname
Action | Report this message to your technical support representative. #### References SMARTS Installation and Operations Manual.

PSX0082 | ENQ/DEQ failure, DDNAME=$1
Description | ENDQ/DEQ Data collection problem. #### Placeholders
$1 | ddname
Action | Report this message to your technical support representative. #### References SMARTS Installation and Operations Manual.

PSX0083 | Dataspace Max Size $1 exceeded
Description | Maximum dataspace size exceeded. #### Placeholders
$1 | Maximum size
Action | Report this message to your technical support representative. #### References SMARTS Installation and Operations Manual.

PSX0084 | PAeNDSM Module not available
Description | DSM module not available. #### Placeholders None
Action | Report this message to your technical support representative. #### References SMARTS Installation and Operations Manual.

PSX0085 | Dataspace $1 not initialised correctly
Description | The Dataspace was not successfully initialised. #### Placeholders
$1 | Dataspace name
Action | Report this message to your technical support representative. #### References SMARTS Installation and Operations Manual.

PSX0086 | Dataspace $1 not terminated correctly
Description | The Dataspace was not successfully terminated. #### Placeholders
$1 | Dataspace name
Action | Report this message to your technical support representative. #### References SMARTS Installation and Operations Manual.

PSX0087 | CEEPIPI Interface module not available
Explanation | Unable to load the LE PIPI interface module, CEEPIPI
Action | Make the module available to the job and rerun. #### References OS/390 LE Manuals.

PSX0088 | LE PIPI $1 Error rf=$2 rc=$3 rsnc=X$4 fbc=X$5
Explanation | An error has occurred while interfacing with the LE subsystem on OS/390. It indicates a possible installation problem for SMARTS. #### Placeholders
$1 | LE Call
$2 | response code
$3 | return code
$4 | reason code
$5 | feedback code
Action | Report this message to your technical support representative. #### References Relevant OS/390 LE Manuals.

PSX0089 | DXR/IMS: $1 of token failed - $2, return code $3
Explanation | An MVS token creation, retrieval or deletion has failed. #### Placeholders
$1 | failing request
$2 | token
$3 | return code
Action | Report this message to your technical support representative. #### References IBM MVS Programming Assembler Services Reference

PSX0090 | Warning: Error in freeing of storage addr $1
Explanation | An Error occurred during the freeing of storage - corruption detected
Action | Contact Tech Support

PSX0091 | TCPIP System Id (SYSPARM) specified='$1'
Explanation | Identifies the TCP/IP for VSE partition that the SMARTS Sockets interface has connected with. #### Placeholders
$1 | This was indicated by the // OPTION SYSPARM='nn' statement in the application startup JCL. The ID assignment is made in the parameter field of the EXEC statement of the TCP/IP for VSE startup JCL.
Action | This message is for information only. #### References VSE/ESA V2R6 System Control Statements

PSX0092 | Error freeing storage for $1 (address $2)
Explanation | An Error occurred during the freeing of a DXR Control Block at Address $2
Action | Contact Tech Support with the text of this message

PSX0094 | Sockets BUFSZ=$1, MINQ=$2, MAXQ=$3
Explanation | Indicates the values used (explicitly or by default) by the Sockets subsystem. #### Placeholders
$1 | The size of the input and output buffers.
$2 | The minimum listen() queue length or backlog that can be specified by an application.
$3 | The maximum listen() queue length or backlog that can be specified by an application.
Action | This message is for information only. #### References Not applicable

PSX0095 | Sockets Port $1 listening. Queue length $2
Explanation | A server has opened a socket and is waiting for work. #### Placeholders
$1 | The port number of the server.
$2 | The listen() queue length or backlog that the Sockets subsystem will use for the socket. This has been specified by the server application or has been forced by default.
Action | This message is for information only. #### References Not applicable

PSX0096 | Sockets Port $1 closed. Connections $2, Concurrent $3
Explanation | Indicates that a previously listening port has been closed. #### Placeholders
$1 | The port number of the server.
$2 | The total number of connections made with the server port.
$3 | The highest number of concurrent connections made.
Action | This message is for information only. #### References Not applicable

PSX0099 | $1 $2 $3 $4 $5 $6 $7 $8
Explanation | Trace data. #### Placeholders
$1-$8 | Variable information.
Action | This message is for information only. Report this message to your technical support representative. #### References Not applicable