List Subsystem Entries (QWDLSBSE) API


  Required Parameter Group:


  Default Public Authority: *USE

  Threadsafe: No

The List Subsystem Entries (QWDLSBSE) API lists some of the different entries in a subsystem description. See the format information for the types of entries available. QWDLSBSE replaces any data that already exists in the user space.

Other subsystem information is available through the following APIs:


Authorities and Locks

User Space Authority
*CHANGE
User Space Library Authority
*EXECUTE
User Space Lock
*EXCLRD
Subsystem Description Authority
*USE
Subsystem Description Library Authority
*EXECUTE

Required Parameter Group

Qualified user space name
INPUT; CHAR(20)

The user space that receives the list, and the library in which it is located. The first 10 characters contain the user space name, and the second 10 characters contain the library name. You can use these special values for the library name:


List format
INPUT; CHAR(8)

The format of subsystem entries to list. You can use one of the following format names:


Qualified subsystem name
INPUT; CHAR(20)

The subsystem description about which to retrieve information, and the library in which the subsystem description is located. The first 10 characters contain the subsystem description name, and the second 10 characters contain the library name. You can use these special values for the library name:


Error code
I/O; CHAR(*)

The structure in which to return error information. For the format of the structure, see Error code parameter.


Format of the Generated List

The list of entries that the QWDLSBSE API returns into the user space consists of:

The user area and generic header are described in User spaces. The remaining items are described in the following sections. For detailed descriptions of the fields in the tables, see Field Descriptions.

When you retrieve list entry information from a user space, you must use the entry size returned in the generic header. The size of each entry may be padded at the end. If you do not use the entry size, the result may not be valid. For examples of how to process lists, see Examples: APIs and exit programs.


Input Parameter Section



Header Section



SBSE0100 Format



SBSE0200 Format



SBSE0300 Format



SBSE0400 Format



SBSE0500 Format



SBSE0600 Format



SBSE0700 Format



Field Descriptions

Additional number of jobs. The additional number of prestart jobs that are started when the number of prestart jobs drops below the value specified for the threshold parameter.

Autostart job description library name. The name of the library in which the job description for the autostart job entry resides.

Autostart job description name. The name of the job description for the autostart job entry about which information is being returned.

Autostart job name. The simple name of the job that is automatically started when the associated subsystem is started.

Communication entry job description library name. The name of the library in which the communications entry job description resides.

Communication entry job description name. The name of the job description used when a job is started as a result of receiving a program start request and processed through this communications entry. Possible special values follow:

Compare start position. The starting position for the routing data comparison. The comparison between the compare value and the routing data begins with this position in the routing data character string, and the last character position compared must be less than or equal to the length of the routing data used in the comparison.

Compare value. A value that is compared with the routing data to determine whether this is the routing entry that is used for starting a routing step. The special value *ANY means that any routing data is considered a match.

Control job (allocation). How the workstations that are associated with this job entry are allocated. Possible special values follow:

Default user. The name of the default user profile used for evoke requests that enter the subsystem through this entry and contain no security information. Possible special values follow:

Device. The name of the device description or the type of the device being used with this communications entry. Possible special values follow:

First class library name. The name of the library in which the first class resides.

First class name. The name of one of the two classes that the prestart jobs run under. Jobs start by using the first class that is specified until the number of jobs specified for the first class is reached. After the number of jobs that are specified for the first class is reached, then jobs are started by using the second class.

Format name specified. The format name as specified in the call to the API.

Initial number of jobs. The initial number of prestart jobs that are started when the subsystem is started.

Job description library name for type. The name of the library in which the job description for this workstation type resides.

Job description library name for workstation. The name of the library in which the job description for this workstation name resides.

Job description name for type. The name of the job description that is used for jobs started through this type of workstation entry. The possible special value follows:

Job description name for workstation. The name of the job description that is used for jobs started through this workstation name entry. The possible special value follows:

Maximum active jobs. The maximum number of jobs that can be active at the same time through this entry. If the entry specifies *NOMAX, indicating that there is no maximum, this number is -1.

Maximum active routing steps. The maximum number of routing steps (jobs) that can be active at the same time through this routing entry. If the routing entry specifies *NOMAX, indicating that there is no maximum, this number is -1.

Maximum number of jobs. The maximum number of prestart jobs that can be active at the same time for this prestart job entry. If the entry specifies *NOMAX, which indicates that there is no maximum, this number is -1.

Maximum number of uses. The maximum number of requests that can be handled by each prestart job in the pool before the job is ended. If the entry specifies *NOMAX, which indicates that there is no maximum, this number is -1.

Mode. The mode name of the communications device. The possible special value follows:

Number of jobs to use first class. The maximum number of jobs to run by using the first class. Possible special values follow:

Number of jobs to use second class. The maximum number of jobs to run by using the second class. Possible special values follow:

Pool identifier. The name of the subsystem pool identifier in which the prestart jobs will run.

Prestart job resources affinity group. Specifies whether or not the prestart jobs started by this entry are grouped together having affinity to the same set of processors and memory. The possible values are:

Prestart job thread resources affinity group. Specifies whether or not secondary threads running in the prestart jobs are grouped together with the initial thread, or spread across the system resources. The possible values are:

Prestart job thread resources affinity level. The degree to which the system tries to maintain the affinity between threads and system resources. When the prestart jobs thread resources affinity group is *SYSVAL, this field will contain blanks. The possible special values are:

Prestart job description library name. The name of the library in which the job description for the prestart job entry resides.

Prestart job description name. The name of the job description that is used for the prestart job entry. The possible special value follows:

Prestart job name. The name of the prestart job.

Prestart job program library name. The name of the library in which the prestart job program resides.

Prestart job program name. The program name that is used to match an incoming request with an available prestart job.

Remote location. The name of the remote location for this entry.

Remote location entry job description library name. The name of the library in which the job description resides.

Remote location entry job description name. The name of the job description used when a job is started as a result of receiving a program start request and processed through this remote location entry. Possible special values follow:

Reserved. An ignored field.

Routing entry class library name. The name of the library in which the routing entry class resides.

Routing entry class name. The name of the class that is used when a routing step is started through this routing entry.

Routing entry pool identifier. The pool identifier of the storage pool in which the routing entry program is run.

Routing entry program library name. The name of the library in which the routing entry program resides.

Routing entry program name. The name of the program that is started when a routing step is started through this routing entry in the subsystem description. If *RTGDTA is returned, the program name is taken from the routing data that was supplied and matched against this entry. The qualified program name will be taken from the routing data in this case, where the program name is specified in positions 37 through 46 and the library name is taken from positions 47 through 56.

Routing entry resources affinity group. Specifies whether or not the jobs using this routing entry are grouped together having affinity to the same set of processors and memory. The possible values are:

Routing entry sequence number. The sequence number of the routing entry.

Routing entry thread resources affinity group. Specifies whether or not secondary threads running in jobs that started through this routing entry are grouped together with the initial thread, or spread across the system resources. The possible values are:

Routing entry thread resources affinity level. The degree to which the system tries to maintain the affinity between threads and system resources. When the routing entry thread resources affinity group is *SYSVAL, this field will contain blanks. The possible special values are:

Second class library name. The name of the library in which the second class resides.

Second class name. One of the two classes that the prestart jobs run under. Jobs start by using the first class that is specified until the number of jobs specified for the first class is reached. After the number of jobs that are specified for the first class is reached, then jobs are started using the second class. The possible special value follows:

Start jobs. Whether the prestart jobs are started at the time the subsystem is started. Possible special values follow:

Subsystem library name specified. The name or special value specified in the call to this API for the library in which the subsystem description resides.

Subsystem library name used. The name of the library in which the subsystem description resides.

Subsystem name specified. The name of the subsystem specified in the call to this API.

Subsystem name used. The name of the subsystem about which information is being returned.

Threshold. The number at which additional prestart jobs are started. When the pool of available jobs (jobs available to service a program start request) is reduced below this number, more jobs (specified on the additional number of jobs field) are started and added to the available pool. This number is checked after a prestart job is attached to a procedure start request.

User profile name. The name of the user profile under which the prestart job runs.

User space library name specified. The name specified for the library that contains the user space to receive the generated list.

User space name specified. The name specified for the user space that is to receive the generated list.

Wait for job. Whether requests wait for a prestart job to become available or are rejected if a prestart job is not immediately available when the request is received. Possible special values follow:

Workstation name. The name of the workstation that is used by the subsystem. A generic workstation entry like DSP* is allowed.

Workstation type. The display device type. (See the TYPE keyword in the Communications Configuration manual, SC41-5401. This manual is not included in this release of the IBM® i Information Center; however, it is available from the IBM Publications CenterLink outside information center as a printed hardcopy that you can order or in an online format that you can download at no charge.)

Possible special values follow:


Error Messages



API introduced: V3R7

[ Back to top | Work Management APIs | APIs by category ]