ATB60001I

ATB60021I

ATBTRACE REQUEST UNSUCCESSFUL: INTERNAL SYSTEM ERROR IN ATBTRACE PROCESSING, RETURN CODE return_code

Explanation

The system encountered an internal error while processing an ATBTRACE request. Depending on the ATBTRACE processing that was in progress when the error occurred, the trace data set might contain trace data; if so, that data might be unusable.

In the message text:

return code: The return code for the internal error

System action

The system terminates ATBTRACE processing.

System programmer response

Search problem reporting databases for a fix for the problem. If no fix exists, contact the IBM Support Center, and provide the return code and the SVC dump, if one is available.

Detecting Module:

ATBTRACE exec

Programmer response

Contact your system programmer to diagnose the problem.

ATB60022I

ATBTRACE REQUEST UNSUCCESSFUL: APPC/MVS TRACE ROUTINE IS NOT AVAILABLE BECAUSE OF PREVIOUS INTERNAL ERROR

Explanation

An ATBTRACE request was invoked on a system on which the APPC/MVS trace routine is no longer active, because it previously encountered a non-retryable internal error.

System action

The system rejects the request.

Operator response

At the request of the system programmer, bring down and restart the APPC address space.

System programmer response

If you absolutely must have application program interface (API) tracing capability on this system, ask the operator to bring down and restart the APPC address space.

Detecting Module:

ATBVSTS

Programmer response

Contact your system programmer to determine whether to start tracing activity on another system, or restart tracing activity on this system.

ATB60023I

ATBTRACE START UNSUCCESSFUL: DYNAMIC ALLOCATION OF DATA SET dsname FAILED

Explanation

The system could not dynamically allocate the trace data set. A message with prefix IEC, IGD, or IKJ further explains the dynamic allocation error.

In the message text:

dsname: The data set name specified on the ATBTRACE request

System action

The system rejects the request.

Programmer response

To correct the problem, follow the instructions for the accompanying IEC, IGD, or IKJ message.

Detecting Module:

ATBVSTW

ATB60024I

ATBTRACE STOP REQUEST IS QUEUED FOR COMPLETION

Explanation

The system could not complete the stop request because of large number of API trace record yet to be written or because of I/O contention. You will not be able to view the trace data set until the trace stop request is completed by the system.

System action

The system partially completes the request.

Programmer response

Issue an ATBTRACE LIST request specifying the data set name you specified on the STOP request. If the STOP request is completed by the system, ATB60034I message will be returned. You can view the trace data set now. If the STOP request is not complete, system will return ATB60047I message.

Detecting Module:

ATBVSTE

ATB60026I

ATBTRACE NOT AVAILABLE: THE APPC ADDRESS SPACE IS NOT ACTIVE

Explanation

An ATBTRACE request was invoked on a system on which the APPC address space is not active.

System action

The system rejects the request.

Operator response

At the request of the system programmer, restart APPC on this system.

System programmer response

Determine whether the APPC address space should be active on this system. If so, ask the operator to restart APPC.

Detecting Module:

ATBVSTS, ATBVSTT

Programmer response

Contact your system programmer to determine whether the APPC address space should be active on this system.

ATB60027I

ATBTRACE START UNSUCCESSFUL: YOU ARE NOT AUTHORIZED TO START THE TRACE ASSOCIATED WITH LU lu_name AND TP tp_name

Explanation

The issuer of the ATBTRACE START request does not have authorization to start a trace for this LU and TP combination.

In the message text:

lu_name: The LU name specified on the ATBTRACE request
tp_name: The TP name specified on the ATBTRACE request

System action

The system rejects the request.

System programmer response

Issue the appropriate security product command to authorize the user to trace this LU and TP. See z/OS MVS Planning: APPC/MVS Management for more information on security requirements.

Detecting Module:

ATBVSTM

Programmer response

If you should have authority to trace this LU and TP, check with your security administrator. Once you have the proper authorization, re-issue the request.

ATB60028I

ATBTRACE START UNSUCCESSFUL: THE ACTIVE SIDE INFORMATION DATA SET DOES NOT CONTAIN AN ENTRY FOR sym_dest_name

Explanation

The SYMDEST keyword value on an ATBTRACE request does not correspond to an entry in the active side information data set.

In the message text:

sym_dest_name: The symbolic destination name specified on the ATBTRACE request

System action

The system rejects the request.

System programmer response

Determine whether this symbolic destination name should be defined in the active side information data set.

Detecting Module:

ATBSD1G

Programmer response

If you specified a valid symbolic destination name as the SYMDEST keyword value, ask the system programmer to add the name to the active side information data set. Otherwise, correct the symbolic destination name, and re-issue the request.

ATB60029I

ATBTRACE START UNSUCCESSFUL: DYNAMIC ALLOCATION OF DATA SET dsname FAILED – RETURN CODE retcode ERROR REASON CODE rsncode

Explanation

The system could not dynamically allocate the trace data set, and could not issue a message that further explains the error.

In the message text:

dsname: The data set name specified on the ATBTRACE request
retcode: The return code from dynamic allocation.
rsncode: The error reason code from dynamic allocation.

System action

The system rejects the request.

Programmer response

To correct the problem, follow the instructions in z/OS MVS Programming: Authorized Assembler Services Guide for the dynamic allocation return and error reason code combination.

Detecting Module:

ATBVSTW

ATB60030I

ATBTRACE START UNSUCCESSFUL: userid DOES NOT HAVE UPDATE ACCESS TO DATA SET dsname

Explanation

The issuer of the ATBTRACE START request does not have update access to the data set specified on ATBTRACE request.

In the message text:

userid: The user ID under which the ATBTRACE START request was issued.
dsname: The data set name specified on the ATBTRACE START request

System action

The system rejects the request.

Programmer response

On the ATBTRACE request, specify the name of a data set to which you have update access, and re-issue the request.

Detecting Module:

ATBVSTW

ATB60031I

ATBTRACE STOP UNSUCCESSFUL: YOU ARE NOT AUTHORIZED TO STOP THE TRACE ASSOCIATED WITH LU lu_name AND TP tp_name

Explanation

The issuer of the ATBTRACE STOP request does not have authorization to stop a trace for this LU and TP combination.

In the message text:

lu_name: The name of the LU associated with this ATBTRACE request
tp_name: The name of the TP associated with this ATBTRACE request

System action

The system rejects the request.

System programmer response

Issue the appropriate security product command to authorize the user to trace this LU and TP. See z/OS MVS Planning: APPC/MVS Management for more information on security requirements.

Detecting Module:

ATBVSTM

Programmer response

Make sure you specified the correct data set name on the ATBTRACE request. If you should have authority to stop the trace associated with this LU and TP combination, check with your security administrator. (If the data set specified on the STOP request has active traces for additional LU/TP combinations, make sure you have authority to stop those LU/TP combinations as well, or the system might issue this message again after you re-issue the request.) Once you have the proper authorization, re-issue the request.

ATB60032I

ATBTRACE START UNSUCCESSFUL: AN ATBTRACE STOP REQUEST IS PENDING FOR DATA SET dsname

Explanation

ATBTRACE was invoked to start a trace, but the system is still processing an ATBTRACE STOP request that was already issued for the data set specified on the START request.

In the message text:

dsname: The data set specified on the ATBTRACE requests.

System action

The system rejects the request.

Programmer response

Issue an ATBTRACE LIST request, specifying the data set name you specified on the START request. When the system returns message ATB60034I, you can re-issue the START request.

Detecting Module:

ATBVSTT

ATB60033I

ATBTRACE STOP UNSUCCESSFUL: NO API TRACES ARE ACTIVE FOR DATA SET dsname

Explanation

ATBTRACE was invoked to stop an application program interface (API) trace, but no trace is active for the specified data set, or the trace is already being stopped.

In the message text:

dsname: The data set specified on the ATBTRACE STOP request.

System action

The system rejects the request.

Programmer response

Determine whether the trace was already stopped, or was ever started, and take appropriate action.

Detecting Module:

ATBVSTM

ATB60034I

NO API TRACES ARE ACTIVE

Explanation

ATBTRACE was invoked to list any active application program interface (API) traces, but no traces are active on this system, or no traces are active for the data set specified on the ATBTRACE LIST request.

System action

The system processes the ATBTRACE request by returning this message; no list is produced because no traces are active.

Programmer response

Determine whether an ATBTRACE START was ever requested for the specified data set, or for any data set for this system, and take appropriate action.

Detecting Module:

ATBVSTL

ATB60035I

ATBTRACE START WAS SUCCESSFUL

Explanation

The system successfully processed an ATBTRACE START request.

System action

The system will collect trace data as instructed by the keyword values specified on the ATBTRACE request.

Programmer response

None.

Detecting Module:

ATBTRACE exec

ATB60036I

ATBTRACE STOP WAS SUCCESSFUL

Explanation

The system successfully processed an ATBTRACE STOP request.

System action

The system stops collecting any further trace data for the data set specified on the ATBTRACE request.

Programmer response

None.

Detecting Module:

ATBTRACE exec

ATB60037I

ATBTRACE REQUEST UNSUCCESSFUL: APPC/MVS PROCESSING ENCOUNTERED INTERNAL ERROR RETURN CODE retcode REASON CODE rsncode

Explanation

APPC/MVS encountered an internal error while processing an ATBTRACE START, STOP, or LIST request. Depending on the ATBTRACE processing that was in progress when the error occurred, the trace data set might contain trace data; if so, that data might be unusable.

In the message text:

retcode: 4-byte internal error return code.
rsncode: 12-byte internal error reason code.

System action

The system terminates ATBTRACE processing.

System programmer response

Search problem reporting databases for a fix for the problem. If no fix exists, contact the IBM Support Center, and provide the return and reason codes and the SVC dump, if one is available.

Detecting Module:

ATBVSTB, ATBVSTE, ATBVSTL,
ATBVSTM, ATBVSTT, ATBVSTW

Programmer response

Contact your system programmer to diagnose the problem.

ATB60038I

ATBTRACE START UNSUCCESSFUL: THE MAXIMUM NUMBER OF API TRACE DATA SETS IS ALREADY IN USE

Explanation

When processing an ATBTRACE START request, the system determined that it was already collecting trace data in the maximum number of application program interface (API) trace data sets. The maximum is 50.

System action

The system rejects the request.

Programmer response

Issue ATBTRACE LIST without specifying any data set name, and examine the resulting list of active traces. If a STOP request is pending for a data set, you can issue the LIST request again, specifying the data set for which the STOP is in progress. When the system returns message ATB60034I, you can re-issue the START request.

If no STOP requests are in progress, examine the list for any active traces that aren't required any more. You can issue an ATBTRACE STOP for the data set associated with those traces, and re-issue the ATBTRACE START request. Keep in mind that issuing an ATBTRACE STOP stops all active traces to the data set specified on the STOP request.

Detecting Module:

ATBVSTT

ATB60039I

ATBTRACE REQUEST UNSUCCESSFUL: THE REQUEST WAS ISSUED WHILE IN SRB MODE

Explanation

An ATBTRACE START, STOP, or LIST request was invoked from a program that is running in service request block (SRB) mode. An ATBTRACE request cannot be issued from an SRB.

System action

The system rejects the request.

Programmer response

Make sure any ATBTRACE request is issued from a program that is running in task mode. For example, if you want to leave the ATBTRACE request in the same program, you'll have to use a method other than the SCHEDULE or IEAMSCHD macro to run that program.

Detecting Module:

ATBVSTM

ATB60040I

ATBTRACE REQUEST UNSUCCESSFUL: THE REQUEST WAS ISSUED WHILE HOLDING LOCKS

Explanation

An ATBTRACE START, STOP, or LIST request was invoked from a program that was holding one or more locks. An ATBTRACE request cannot be issued from a program while it is holding any lock.

System action

The system rejects the request.

Programmer response

Make sure your program is not holding any locks when it issues an ATBTRACE request; then re-run the program.

Detecting Module:

ATBVSTM

ATB60041I

ATBTRACE REQUEST UNSUCCESSFUL: THE REQUEST WAS ISSUED WHILE IN CROSS MEMORY MODE

Explanation

An ATBTRACE START, STOP, or LIST request was invoked from a program that was in cross memory mode. An ATBTRACE request cannot be issued from a program while its home and primary address spaces are not the same.

System action

The system rejects the request.

Programmer response

Make sure your program's home and primary address spaces are the same when it issues an ATBTRACE request. (The secondary address space does not have to be the same as the home and primary address spaces.) Then re-run the program.

Detecting Module:

ATBVSTM

ATB60042I

ATBTRACE LIST IS COMPLETE

Explanation

All the information about active traces has been listed for a specific ATBTRACE LIST request. This message appears at the end of the trace information.

System action

The system continues processing.

Programmer response

None.

Detecting Module:

ATBTRACE exec

ATB60043I

ATBTRACE START UNSUCCESSFUL: TRACE DATA SET dsname ALREADY IN USE BY user FOR API TRACES

Explanation

The issuer of an ATBTRACE START request specified the name of a data set that is already in use for application program interface (API) tracing by a different user. Only one user at a time can use the trace data set for an API trace.

In the message text:

dsname: The data set specified on the ATBTRACE START request.
user: The user ID under which the first ATBTRACE START request was issued for this data set. Additional ATBTRACE START requests for this data set can be issued only under this user ID.

System action

The system rejects the request.

Programmer response

Re-issue the ATBTRACE START with a different data set name or, if you have authority to do so, re-issue the ATBTRACE START from the user ID indicated by this message.

Detecting Module:

ATBVSTT

ATB60044I

ATBTRACE START UNSUCCESSFUL: TRACE DATA SET dsname IS NOT USABLE

Explanation

On an ATBTRACE START request, the user specified a data set that the system cannot use.

In the message text:

dsname: The data set specified on the ATBTRACE START request.

System action

The system rejects the request, and issues a message with prefix AHL to further explain the error.

Programmer response

Follow the instructions for the AHL message to correct the error, and re-issue the ATBTRACE START request.

Detecting Module:

ATBVSTW

ATB60045I

ATBTRACE REQUEST UNSUCCESSFUL: TRACE DATA SET dsname IS NOT SEQUENTIAL

Explanation

The issuer of an ATBTRACE START request specified the name of a partitioned data set (PDS or PDSE). The data set for application program interface (API) trace data must be sequential.

In the message text:

dsname: The data set specified on the ATBTRACE START request.

System action

The system rejects the request.

Programmer response

Re-issue the ATBTRACE START with a different data set name.

Detecting Module:

ATBVSTW, ATBTRACE exec

ATB60046I

LIST OF ACTIVE API TRACES FOR DATA SET dsname IN USE BY user API TRACE WAS STARTED AT mm/dd/yyyy hh:mm:ss.nnnnnn FOR:
LU: lu_name
TP: tp_name
SYMDEST: {sym_dest_name|N/A}
{USERID: {userid|*} | SECNONE}

Explanation

For an ATBTRACE LIST request, the system displays active application program interface (API) traces. If a data set name was specified on the request, the system displays only those active traces associated with the data set. The text beginning with "API TRACE WAS STARTED..." and the subsequent information is repeated for each trace (that is, repeated as many times as the system wrote message ATB60051I to the data set for an ATBTRACE START request).

If a data set name was not specified, the system displays the entire message for each active API trace data set on the system, repeating the text beginning with "API TRACE WAS STARTED..." for each trace associated with each data set.

In the message text:

dsname: The name of a data set containing trace data.
user: The user ID under which the ATBTRACE START request was issued for this data set.
mm/dd/yyyy hh:mm:ss.nnnnnn: The month, date, year, hour, minute, second, and microsecond at which APPC/MVS processed the ATBTRACE START request for the API trace. The time is local time.
lu_name: The name of the logical unit (LU) associated with a currently active trace.
tp_name: The name of the transaction program (TP) associated with a currently active trace.
sym_dest_name: The symbolic destination name associated with a currently active trace. If the ATBTRACE START request specified a value for the SYMDEST keyword, that value is displayed for sym_dest_name, and the LU and TP values represented by sym_dest_name also appear for lu_name and tp_name, respectively. If the START request did not specify the SYMDEST keyword and value (that is, the LU and TP keywords and values were specified), "N/A" appears to indicate that sym_dest_name does not apply.
userid: The user ID associated with a currently active trace. If the ATBTRACE START request did not specify a USERID keyword and value, an asterisk (*) appears for userid; if the START request specified the SECNONE keyword instead of the USERID keyword and value, SECNONE appears instead of USERID.

System action

The system continues processing.

Programmer response

None.

Detecting Module:

ATBVSTM

ATB60047I

ATBTRACE STOP IS IN PROGRESS FOR DATA SET dsname

Explanation

An ATBTRACE LIST request was issued when APPC/MVS is still processing an ATBTRACE STOP request. In this case, the system does not include any application program interface (API) trace information for this data set in the output resulting from the ATBTRACE LIST request. If the ATBTRACE LIST request did not specify a data set name, this message is repeated for each data set for which an ATBTRACE STOP request is still in progress.

In the message text:

dsname: The name of a data set containing trace data.

System action

The system continues processing.

Programmer response

None.

Detecting Module:

ATBVSTM

ATB60048I

ATBTRACE STOP WAS SUCCESSFUL, BUT AN ERROR ENCOUNTERED WHILE CLOSING THE DATA SET MIGHT HAVE CAUSED TRACE DATA TO BE LOST

Explanation

The system successfully processed an ATBTRACE STOP request; however, the system encountered an error while closing the data set. Because of the error, trace data might have been lost.

System action

The system stops collecting any further trace data for the data set specified on the ATBTRACE request.

Programmer response

None.

Detecting Module:

ATBVSTW

ATB60049I

API TRACE WAS STARTED AT mm/dd/yyyy hh:mm:ss.nnnnnn FOR:
LU: lu_name
  TP: tp_name
  SYMDEST: {sym_dest_name|N/A}
  SECNONE

Explanation

For ATBTRACE START requests for a particular data set, the system writes this message to the data set for each unique combination of LU and TP keyword values, with the SECNONE keyword. (If you specify the SYMDEST keyword instead of LU and TP, the system resolves the SYMDEST keyword value to actual LU and TP values before determining whether the START request specifies a unique LU/TP combination.)

If you issue a START request that is identical to a previous START request, without an intervening STOP request for this data set, the system returns message ATB60035I to indicate that the request was successful— tracing has already begun for that LU/TP combination.

In the message text:

mm/dd/yyyy hh:mm:ss.nnnnnn: The month, date, year, hour, minute, second, and microsecond at which APPC/MVS processed the START request for the API trace. The time is local time.
lu_name: The name of the logical unit (LU) associated with a currently active trace.
tp_name: The name of the transaction program (TP) associated with a currently active trace.
sym_dest_name: The symbolic destination name associated with a currently active trace. If the ATBTRACE START request specified a value for the SYMDEST keyword, that value is displayed for sym_dest_name, and the LU and TP values represented by sym_dest_name also appear for lu_name and tp_name, respectively. If the START request did not specify the SYMDEST keyword and value (that is, the LU and TP keywords and values were specified), "N/A" appears to indicate that sym_dest_name does not apply.

System action

The system continues processing.

Programmer response

None.

Detecting Module:

ATBVSTT

ATB60050I

API TRACES STOPPED BY APPC/MVS AT mm/dd/yyyy hh:mm:ss.nnnnnn BECAUSE OF AN APPC/MVS INTERNAL ERROR. THE DATA SET CONTAINS TRACE DATA FOR: API TRACE WAS STARTED AT mm/dd/yyyy hh:mm:ss.nnnnnn FOR:
LU: lu_name
TP: tp_name
SYMDEST: {sym_dest_name|N/A}
{USERID: {userid|*} | SECNONE }

Explanation

If APPC/MVS encounters an internal error and stops the APPC/MVS trace routine, the system writes this message to any data set with active application program interface (API) traces. Any API trace entries that were collected but not written to a data set are lost.

In each data set, this message appears at the end of the most current trace data entries. (If the system had to wrap the trace entries, this message might not be the last message in the data set; a fragment of or entire trace entries for previous trace data might follow this message.

In each data set, the text beginning with "API TRACE STARTED..." and the subsequent information is repeated for each trace (that is, repeated as many times as the system wrote message ATB60051I to the data set for an ATBTRACE START request).

In the message text:

mm/dd/yyyy hh:mm:ss.nnnnnn: The month, date, year, hour, minute, second, and microsecond at which APPC/MVS processed the ATBTRACE START request for the API trace. The time is local time.
lu_name: The name of the logical unit (LU) associated with a currently active trace.
tp_name: The name of the transaction program (TP) associated with a currently active trace.
sym_dest_name: The symbolic destination name associated with a currently active trace. If the ATBTRACE START request specified a value for the SYMDEST keyword, that value is displayed for sym_dest_name, and the LU and TP values represented by sym_dest_name also appear for lu_name and tp_name, respectively. If the START request did not specify the SYMDEST keyword and value (that is, the LU and TP keywords and values were specified), "N/A" appears to indicate that sym_dest_name does not apply.
userid: The user ID associated with a currently active trace. If the ATBTRACE START request did not specify a USERID keyword and value, an asterisk (*) appears for userid; if the START request specified the SECNONE keyword instead of the USERID keyword and value, SECNONE appears instead of USERID.

System action

The system stops all active API traces because of APPC/MVS trace routine termination, and issues message ATB499I to the console.

Programmer response

None.

Detecting Module:

ATBVSTW

ATB60051I

API TRACE WAS STARTED AT mm/dd/yyyy hh:mm:ss.nnnnnn FOR:
  LU: lu_name
  TP: tp_name
  SYMDEST: {sym_dest_name|N/A}
  USERID: {userid|*}

Explanation

For ATBTRACE START requests for a particular data set, the system writes this message to the data set for each unique combination of LU, TP, and USERID keyword values. (If you specify the SYMDEST keyword instead of LU and TP, the system resolves the SYMDEST keyword value to actual LU and TP values before determining whether the START request specifies a unique LU/TP/USERID combination.)

In the message text:

mm/dd/yyyy hh:mm:ss.nnnnnn: The month, date, year, hour, minute, second, and microsecond at which APPC/MVS processed the START request for the API trace. The time is local time.
lu_name: The name of the logical unit (LU) associated with a currently active trace.
tp_name: The name of the transaction program (TP) associated with a currently active trace.
sym_dest_name: The symbolic destination name associated with a currently active trace. If the ATBTRACE START request specified a value for the SYMDEST keyword, that value is displayed for sym_dest_name, and the LU and TP values represented by sym_dest_name also appear for lu_name and tp_name, respectively. If the START request did not specify the SYMDEST keyword and value (that is, the LU and TP keywords and values were specified), "N/A" appears to indicate that sym_dest_name does not apply.
userid: The user ID associated with a currently active trace. If the ATBTRACE START request did not specify a USERID keyword and value, an asterisk (*) appears for userid.

System action

The system continues processing.

Programmer response

None.

Detecting Module:

ATBVSTT

ATB60052I

ATBTRACE STOP REQUEST ISSUED BY user AT mm/dd/yyyy hh:mm:ss.nnnnnn. THE DATA SET CONTAINS TRACE DATA FOR: API TRACE WAS STARTED AT mm/dd/yyyy hh:mm:ss.nnnnnn FOR:
  LU: lu_name
  TP: tp_name
  SYMDEST: {sym_dest_name|N/A}
{USERID: {userid|*} | SECNONE }

Explanation

For an ATBTRACE STOP request, the system writes this message to the data set specified on the STOP request. This message appears at the end of the most current application program interface (API) trace data entries. (If the system had to wrap the trace entries, this message might not be the last message in the data set; a fragment of or entire trace entries for previous trace data might follow this message.

The text beginning with "API TRACE STARTED..." and the subsequent information is repeated for each trace (that is, repeated as many times as the system wrote message ATB60051I to the data set for an ATBTRACE START request).

In the message text:

user: The user ID of the issuer of the ATBTRACE STOP request for this data set.
mm/dd/yyyy hh:mm:ss.nnnnnn: The month, date, year, hour, minute, second, and microsecond at which APPC/MVS processed the ATBTRACE START request for the API trace. The time is local time.
lu_name: The name of the logical unit (LU) associated with a currently active trace.
tp_name: The name of the transaction program (TP) associated with a currently active trace.
sym_dest_name: The symbolic destination name associated with a currently active trace. If the ATBTRACE START request specified a value for the SYMDEST keyword, that value is displayed for sym_dest_name, and the LU and TP values represented by sym_dest_name also appear for lu_name and tp_name, respectively. If the START request did not specify the SYMDEST keyword and value (that is, the LU and TP keywords and values were specified), "N/A" appears to indicate that sym_dest_name does not apply.
userid: The user ID associated with a currently active trace. If the ATBTRACE START request did not specify a USERID keyword and value, an asterisk (*) appears for userid; if the START request specified the SECNONE keyword instead of the USERID keyword and value, SECNONE appears instead of USERID.

System action

The system stops all active API traces associated with this data set.

Programmer response

None.

Detecting Module:

ATBVSTW

ATB60054I

API TRACE WAS SUSPENDED AT mm/dd/yyyy hh:mm:ss.nnnnnn, number ENTRIES WERE LOST

Explanation

When the system becomes overloaded with entries for a particular application program interface (API) trace, it suspends the trace until it can write the entries it has already collected to the data set. The system issues this message only if trace entries were lost while the trace was suspended.

The system might suspend an API trace because conversation activity for the TPs being traced is very high, because the data set block size is not optimal for the volume of entries, or because of environmental constraints. For example, if conversation activity is high and many trace entries are generated, but I/O to the data set has stopped because another system issued a RESERVE for the volume on which that data set resides, the system might temporarily suspend the trace. Similarly, system tuning problems might also cause the system to suspend tracing activity.

In the message text:

mm/dd/yyyy hh:mm:ss.nnnnnn: Is the month, date, year, hour, minute, second, and microsecond at which APPC/MVS suspended the API traces. The time is local time.
number: The number of trace entries that were lost. The maximum value for this number is 2147483648; once the system reaches the maximum value, it resets the counter to zero and continues to count lost entries.

System action

When it issues this message, the system has been able to resume the trace already. It continues collecting and writing current trace data to the data set.

Programmer response

If you determine that you have lost important trace entries, you can stop the trace and restart it after making some adjustments to avoid losing entries. For example, you might issue an ATBTRACE LIST request and examine the resulting information, only to find you are tracing more conversations than you need. In that case, you might reduce tracing activity by specifying a different value for the USERID keyword on the START request.

Alternatively, you could allocate another data set without specifying the block size, and issue a START request with the name of that data set. Then the system will select a block size that is optimal for the tracing activity.

Detecting Module:

ATBVSTW

ATB60055I

ENTRY TO THE service_name SERVICE:

Explanation

TIMESTAMP: mm/dd/yyyy hh:mm:ss.nnnnnn

ASID: asid

TCB ADDR: tcb_address

JOB NAME: jobname

LU: lu_name

TP: tp_name

USERID: userid

CONVID: conversation_id

PARAMETERS: list_of_parameters

In a conversation being traced, a transaction program (TP) issued a call to an APPC/MVS or CPI-C service identified by service_name. (Refer to Table 1 for list of supported services.) This message contains the following details about the call on entry to that service:

service_name: The call name of the APPC/MVS callable service or CPI-C verb that was issued.
mm/dd/yyyy hh:mm:ss.nnnnnn: Is the month, date, year, hour, minute, second, and microsecond at which APPC/MVS received the service call. The time is local time.
asid: The address space identifier (ASID) associated with the TP that issued the call.
tcb_address: The address of the task that called the service. This value is zero if a service request block (SRB) routine called the service.
jobname: The job name associated with the TP that issued the call.
lu_name: The name of the logical unit (LU) associated with the currently active trace.
tp_name: The name of the TP associated with the currently active trace.
userid: The user ID associated with the address space where the TP is running.
conversation_id: The hexadecimal value that the system uses to identify a particular conversation. If zero appears in this field, either service call does not contain a parameter for the conversation ID, or the caller specified zero as the conversation ID.
list_of_parameters: The supplied parameters that were specified on the service call. Refer to individual service descriptions in the appropriate APPC/MVS or CPI-C reference document for descriptions of the parameters for which the caller must supply a value on the service call.

System action

The system continues processing.

Programmer response

None.

Detecting Module:

ATBVSTW

ATB60056I

THE service_name SERVICE COMPLETED.

Explanation

TIMESTAMP: mm/dd/yyyy hh:mm:ss.nnnnnn

ASID: asid

TCB ADDR: tcb_address

JOB NAME: jobname

LU: lu_name

TP: tp_name

USERID: userid

CONVID: conversation_id

PARAMETERS: list_of_parameters

[ERROR_INFO:

MESSAGE_TEXT_LENGTH: msg_text_length

MESSAGE_TEXT: msg_text

[ERROR_LOG_PRODUCT_SET_ID_LENGTH: id_length

ERROR_LOG_PRODUCT_SET_ID: product_id

ERROR_LOG_INFORMATION_LENGTH: info_length

ERROR_LOG_INFORMATION: log_info] ]

service_name

The call name of the APPC/MVS callable service or CPI-C verb that was issued.

mm/dd/yyyy hh:mm:ss.nnnnnn

Is the month, date, year, hour, minute, second, and microsecond at which APPC/MVS completed the service call. The time is local time.

asid

The address space identifier (ASID) associated with the TP that issued the call.

tcb_address

The address of the task that called the service. This value is zero if a service request block (SRB) routine called the service.

jobname

The job name associated with the TP that issued the call.

lu_name

The name of the logical unit (LU) associated with the currently active trace.

tp_name

The name of the TP associated with the currently active trace.

userid

The user ID associated with the address space where the TP is running.

conversation_id

The hexadecimal value that the system uses to identify a particular conversation. If zero appears in this field, either service call does not contain a parameter for the conversation ID, or the caller specified zero as the conversation ID.

list_of_parameters

The parameters for which the system returns specific values after processing the service call. If an error is encountered for the service call, the only parameters included in the list are the return code and reason code, if a reason code applies. Refer to individual service descriptions in the appropriate APPC/MVS or CPI-C reference document for descriptions of the parameters for which the system returns specific values.

msg_text_length

The total number of characters that appear in msg_text.

msg_text

A message that describes an error on the call to the service identified by service_name. The data returned for this parameter will appear as a message in the format ATB8xxxxI. See Error_Extract (ATB8) Messages for explanations of messages returned by APPC/MVS.

id_length

The length of the value product_id.

If no product set ID information is available from the partner system, APPC/MVS sets the value on this parameter to zero.
If product set ID information is available from the partner system, APPC/MVS sets the value on this parameter to a number from 1 through 256.
If more than 256 bytes of product set ID information is available, APPC/MVS returns only the first 256 bytes of that information.

product_id

The identifier of the partner system that supplies the error log information. If the product set ID is more than 256 bytes long, APPC/MVS returns only the first 256 bytes of the product set ID.

For information about the format of a product set ID, see the descriptions of the Product Set ID (X'10') and the Product Identifier (X'11') MS Common Subvectors in SNA Formats

info_length

The length of the log information received from a partner TP or system. If no error log information is available from the partner TP or system, APPC/MVS sets the value on this parameter to zero.

log_info

A message that describes an error found by a partner system or TP. If APPC/MVS is the partner system that supplies this error log information, the data returned for this parameter will appear as a message in the format ASB7xxxxI or ATB7xxxxI. See Error_Extract Error Log Information (ASB, ATB7) Messages for explanations of messages returned by APPC/MVS.

System action

The system continues processing.

Programmer response

None.

Detecting Module:

ATBVSTW

ATB60057I

SYNCHRONOUS RETURN FROM THE service_name SERVICE.

Explanation

TIMESTAMP: mm/dd/yyyy hh:mm:ss.nnnnnn

ASID: asid

TCB ADDR: tcb_address

JOB NAME: jobname

LU: lu_name

TP: tp_name

USERID: userid

CONVID: conversation_id

In a conversation being traced, a transaction program (TP) issued a call to an APPC/MVS service identified by service_name, specifying a Notify_type of Notify_ECB. (Refer to Table 1 for list of supported services.) In this case, the system returns control to the TP before processing the call. This message indicates that the system has accepted the call for asynchronous processing, and includes the following details about the call on initial return from the system:

service_name: The call name of the APPC/MVS callable service or CPI-C verb that was issued.
mm/dd/yyyy hh:mm:ss.nnnnnn: Is the month, date, year, hour, minute, second, and microsecond at which APPC/MVS first returns control to the program that issued the service call. The time is local time.
asid: The address space identifier (ASID) associated with the TP that issued the call.
tcb_address: This value is zero.
jobname: The job name associated with the TP that issued the call.
lu_name: The name of the logical unit (LU) associated with the currently active trace.
tp_name: The name of the TP associated with the currently active trace.
userid: The user ID associated with the address space where the TP is running.
conversation_id: The hexadecimal value that the system uses to identify a particular conversation. If zero appears in this field, either service call does not contain a parameter for the conversation ID, or the caller specified zero as the conversation ID.

System action

The system continues processing. When the system finishes processing the call, it writes message ATB60056I to the data set.

Programmer response

None.

Detecting Module:

ATBVSTW

ATB60058I

ATBTRACE STOP WAS SUCCESSFUL, BUT number ENTRIES WERE LOST AT mm/dd/yyyy hh:mm:ss.nnnnnn BECAUSE OF BUFFER SHORTAGE

Explanation

The system successfully processed an ATBTRACE STOP request; however, the system was unable to write all trace entries to the data set because of a buffer shortage.

In the message text:

number: The number of trace entries that were lost. The maximum value for this number is 2147483648 entries.
mm/dd/yyyy hh:mm:ss.nnnnnn: Is the month, date, year, hour, minute, second, and microsecond at which APPC/MVS lost the API trace data entries. The time is local time.

System action

The system stops collecting any further trace data for the data set specified on the ATBTRACE request.

Programmer response

None.

Detecting Module:

ATBVSTW

ATB60061I

AN FMH-5 WAS SENT TO PARTNER LU partner_lu.

Explanation

TIMESTAMP: mm/dd/yyyy hh:mm:ss.nnnnnn

ASID: asid

TCB ADDR: tcb_address

JOB NAME: jobname

LU: lu_name

TP: tp_name

USERID: userid

CONVID: conversation_id

FMH-5: fmh-5

For a conversation being traced, APPC/MVS sent an FMH-5 to the partner LU.

In the message text:

partner_lu: The 17-character name of the partner LU to which the FMH-5 was sent.
mm/dd/yyyy hh:mm:ss.nnnnnn: Is the month, date, year, hour, minute, second, and microsecond at which APPC/MVS sent the FMH-5. The time is local time.
asid: The address space identifier (ASID) of the APPC address space.
tcb_address: The address of the task that sent the FMH-5.
jobname: The job name associated with the task that sent the FMH-5.
lu_name: The name of the logical unit (LU) associated with the currently active trace.
tp_name: The name of the TP associated with the currently active trace.
userid: The user ID associated with the address space where the TP is running.
conversation_id: The hexadecimal value that the system uses to identify a particular conversation.
fmh-5: 256 bytes of hexadecimal FMH-5 data. Refer to SNA Formats for more information on FMH-5 format and contents.

System action

The system continues processing.

Programmer response

None.

Detecting Module:

ATBVSTW

ATB60062I

AN FMH-5 WAS RECEIVED ON LOCAL LU local_lu FROM PARTNER LU partner_lu.

Explanation

TIMESTAMP: mm/dd/yyyy hh:mm:ss.nnnnnn

ASID: asid

TCB ADDR: tcb_address

JOB NAME: jobname

LU: lu_name

TP: tp_name

USERID: userid

CONVID: conversation_id

FMH-5: fmh-5

For a conversation being traced, APPC/MVS received an FMH-5 from the partner LU.

In the message text:

partner_lu: The 17-character name of the partner LU that sent the FMH-5.
mm/dd/yyyy hh:mm:ss.nnnnnn: Is the month, date, year, hour, minute, second, and microsecond at which APPC/MVS received the FMH-5. The time is local time.
asid: The address space identifier (ASID) of the APPC address space.
tcb_address: The address of the task that received the FMH-5.
jobname: The job name associated with the task that received the FMH-5.
lu_name: The name of the logical unit (LU) associated with the currently active trace.
tp_name: The name of the TP associated with the currently active trace.
userid: Userid associated with the APPC/MVS address space.
conversation_id: This value is zero.
fmh-5: 256 bytes of hexadecimal FMH-5 data. Refer to SNA Formats for more information on FMH-5 format and contents.

System action

The system continues processing.

Programmer response

None.

Detecting Module:

ATBVSTW

ATB60063I

AN FMH-7 WAS SENT TO PARTNER LU partner_lu.

Explanation

TIMESTAMP: mm/dd/yyyy hh:mm:ss.nnnnnn

ASID: asid

TCB ADDR: tcb_address

JOB NAME: jobname

LU: lu_name

TP: tp_name

USERID: userid

CONVID: conversation_id

FMH-7: fmh-7

ERROR_INFO:

MESSAGE_TEXT_LENGTH: msg_text_length

MESSAGE_TEXT: msg_text

For a conversation being traced, APPC/MVS sent an FMH-7 to the partner LU.

In the message text:

partner_lu: The 17-character name of the partner LU to which the FMH-7 was sent.
mm/dd/yyyy hh:mm:ss.nnnnnn: Is the month, date, year, hour, minute, second, and microsecond at which APPC/MVS sent the FMH-7. The time is local time.
asid: The address space identifier (ASID) of the APPC address space.
tcb_address: The address of the task that sent the FMH-7.
jobname: The job name associated with the task that sent the FMH-7.
lu_name: The name of the logical unit (LU) associated with the currently active trace.
tp_name: The name of the TP associated with the currently active trace.
userid: Userid associated with the APPC/MVS address space.
conversation_id: This value is zero.
fmh-7: The 7-character FMH-7 data, which includes the sense code back to VTAM. Refer to SNA Formats for more information on FMH-7 format and contents.
msg_text_length: The total number of characters that appear in msg_text.
msg_text: The explanation of an error that occurred during the processing of the service call, in the form of an ATB7xxxxI message. For detailed information about ATB messages, refer to Diagnosing Problems with APPC/MVS TPs.

System action

The system continues processing.

Programmer response

None.

Detecting Module:

ATBVSTW