RC=08 when running the DBFIND (SARSAM9) utility.
search cancel

RC=08 when running the DBFIND (SARSAM9) utility.

book

Article ID: 15141

calendar_today

Updated On:

Products

Deliver View

Issue/Introduction

You're trying to execute the DBFIND program (SARSAM9) to search the database for a string of specific data but the job fails with RC=08 and does not produce the desired results. 

 

You've reviewed the JESMSGLG, JESJCL and JESYSMSG portions of the job output but do not see any error messages or any apparent reason for receiving the RC=08.



What caused the RC=08 and how can it be prevented?

Environment

Release: OUTDTI00200-12.1-Deliver-Output Management-Interface for Native TSO
Component:

Resolution

When the DBLIST (SARSAM9) program returns a return code of 08, it indicates that the utility was unable to allocate or "open" the CA View database that you are trying to run the utility against.

 

The inability for the utility to open or access the CA View database can be caused by specifying an invalid database high level qualifier in the job JCL's PARM='your.dbase.name' field.

 

To determine if the utility was able to successfully allocate the database, review the JESYSMSG portion of the failed jobs output. When the database is allocated/opened successfully, you should see messages similar to the following:

IGD103I SMS ALLOCATED TO DDNAME SYS00001 

IGD103I SMS ALLOCATED TO DDNAME SYS00002 

IGD104I DBHLQ...SARDBASE.I0000001 RETAINED, DDNAME=SYS00001 

IGD104I DBHLQ...SARDBASE.D0000001 RETAINED, DDNAME=SYS00002 

 

If you don't see the above allocation messages, then the utility would be unable to open the database.

 

You should be able to confirm that the RC=08 occurred because of a database allocate/open problem by reviewing the SYSPRINT portion of you job output where you will likely find that you received the following error:

** Error - Database 'your.dbase.name' Open failed ** 

 

To resolve the problem, you would want to investigate the PARM='dbase.name' specification in your job's JCL and make any necessary corrections so that it points to a valid CA VIEW database. Also, make sure that the SYSTEM and INITIATOR that you are running your DBLIST (SARSAM9) job on or in has ACCESS to this same database.