Checking
the Results of Actions
All actions except “Updating the table and index monitor” scheduled in the DBA Planning Calendar generate logs, and also give the user details of the results of an action. Background jobs are used to schedule actions and these background jobs generate job logs. You can view all the information using the DBA Planning Calendar. In addition, all previous update statistics actions can be displayed.
Unsuccessful actions are highlighted in red in the DBA Planning Calendar.
If the submission of an z/OS job fails, you can find the error information in the job log. In this case, the SAP job is shown as not run in the DBA Planning Calendar. Refer to the SAP system log (transaction SM21), the SAP Job Overview (transaction SM37) and z/OS system log for further error analysis. Also refer to the troubleshooting tips in this section.
If the submission of the z/OS job is successful, you can choose Action Details to get all information about the job. By choosing Action log, a list will be shown where you find the submitted JCL job on z/OS, the z/OS JES job ID and the SAP name of the job.
To display the utility output, double-click the action and choose DSNUTILS result or DSNACCMO result, depending on the job. The utility output is displayed immediately if the result is available in the SAP system. For tips concerning the handling of the output list, see the section Backup.
Troubleshooting Tips
For all of the stored procedures, SAP produces small trace files in SAP directory DIR_HOME (see transaction AL11) that can come in very handy in the case of an error. They are reset at each invocation of a stored procedure, so they show only the last execution of the stored procedure.
If you encountered an error that you want to analyze at a later time, you must save this file in a different place to prevent it from being overwritten.
In transaction DB13, the bigger jobs like RUNSTATS on all objects produce huge amounts of output that cannot be analyzed easily. If such a job returned with highest condition code 8, you can search in the output for the string CODE=8. If such a job returned with highest condition code Hex0004E000, you best search for the string ABEND. In the latter case, there can additionally be some utilities with condition code 8, so you should search for both strings.
Uploading data sets with stored procedure DSNACCDS can fail with return code 9990 Dataset in use. Then, someone has the partitioned data set allocated, that is the target of the upload. Either organize the release of the data set in question or change the profile parameter Partitioned dataset for JCL jobs in transaction DB2J (button Profiles, tab strip Upload) and restart transaction DB13 subsequently to reload the profile parameters.
Uploading data sets with stored procedure DSNACCDS fails and you find the following message in SAP system log (transaction SM21):
"Error executing stored procedure DSNACCDS - MES_TXT: CC390 Error using STOW service."
This happened because the stored procedure DSNACCDE just failed and wrote an error message in SAP system log (transaction SM21). If DSNACCDE fails, SAP assumes that the data set member already exists, so DSNACCDS tried to replace a non-existent data set member. If you handled the source of the error DSNACCDE reports, the STOW service error will be gone also.
In transaction DB2, you can configure and install stored procedure SAPCL on the tab strip Checks/Settings, button SAP collector settings. There, a synchronous submission of JCL is done. When using stored procedures, this is done by a sequence of SP calls:
1. DSNACCJS to submit the JCL job.
2. DSNACCJQ to query the status of the JCL job, until it is in OUTPUT. If DSNACCJQ fails due to any reason, SAP waits for a minute in the hope that the job will be finished until then and then continues with step 3.
3. DSNACCJF to fetch the output of the JCL job.
4. DSNACCJP to purge the output of the JCL job. Each of the stored procedures directly writes to the log file DSNACCJS.txt in SAP directory DIR_HOME (see transaction AL11), so you can track the progress of the JCL by monitoring the progress in the file. On AIX and Linux, you could use tail -f DSNACCJS.txt.
If you get the following RACF messages in z/OS system log:
ICH420I PROGRAM ... FROM LIBRARY ... CAUSED THE ENVIRONMENT TO BECOME UNCONTROLLED.
BPXP014I ENVIRONMENT MUST BE CONTROLLED FOR DAEMON (BPX.DAEMON) PROCESSING.
then you either:
· Did not define a separate WLM environment for the stored procedures DSNACCJS, JQ, JF, JP, and DSNACCUC
· You missed one of the members of SDSNLOAD, that need to be program controlled.
To solve the first problem, define a separate WLM environment as described in the SAP Planning Guide for z/OS, and redefine the stored procedures with the correct specification of the new WLM environment as WLM_ENVIRONMENT.
If you missed one of the members of SDSNLOAD, let your system programmer execute the following RACF commands:
RDEFINE PROGRAM member ADDMEM('library'//NOPADCHK) UACC(READ) SETROPTS WHEN(PROGRAM) REFRESH
"member" and "library" can be taken directly out of the RACF message.
You find the following message in SAP system log (transaction SM21):
"Error executing stored procedure DSNACCJ? - MES_TXT: EMCS activation failed. Macro MCSOPER: RC=04,RSN=00"
where ? can be Q or P. As already detailed above, DSNACCJQ and JP use EMCS console. SDSF uses the same console, and if the user submitting JCL job is at the same time in SDSF, DSNACCJQ and JP cannot execute. Leave SDSF while submitting JCL jobs from SAP.
Another possible source for this error could be that your system programmer did not execute the following RACF command for the user ID submitting JCL jobs from SAP:
ALTUSER userID OPERPARM(ROUTCODE(ALL) AUTH(INFO))
You find the following message in SAP system log (Tx SM21) or installation log (file upd_stat.log):
"Error executing stored procedure DSNACCMO - Received an invalid NULL value for TIMEOUT...".
The definition of stored procedure DSNACCMO has been changed with APAR PQ75973 (V8: UQ87438, V7: UQ87436). Please apply the corresponding PTF and afterwards adapt and run again member DSNTIJCC in SDSNSAMP data set.This installs stored procedure DSNACCMO again with the correct definition.