I am testing CA File Save RCS Automated Recovery. After capturing some changes (I added a couple of records to a VSAM dataset), I ran the CA File Save job to recreate the changed VSAM dataset. I received a FILE-ERRR03 message. Why?

Document ID:  TEC567985
Last Modified Date:  07/13/2017
{{active ? 'Hide' : 'Show'}} Technical Document Details

Products

  • CA Filesave RCS Automated Recovery

Releases

  • CA Filesave RCS Automated Recovery:Release:4.0

Components

  • CA Filesave RCS Automated Recovery:FILESA
Introduction:

The CA File Save recovery job is what restores a dataset from a previous version, to a more current version using transactions stored in the DFHLGLOG. This knowledge document will discuss the FILE-ERRR03 message and what can be done to resolve this error.

Question:

I am testing CA File Save RCS Automated Recovery. After capturing some changes (I added a couple of records to a VSAM dataset), I ran the CA File Save job to recreate the changed VSAM dataset. I received a FILE-ERRR03 message. Why?

Answer:

Let us say for example you are using CA File Save RCS Automated Recovery with the follow steps:

  1. Deallocate the file in CICS 

  2. Backup of the file 

  3. Allocate the file in CICS

  4. Run a transaction to add a couple of records to the file

  5. Deallocate the file in CICS

  6. Delete the file

  7. Run a job to create the JCL to recreate the file & get newest records back 

  8. Execute the JCL that's created in step 7 to recreate the file and get back the records created in step 4

    The step 8 JCL has a RECOVERY jobstep that executes CA FILE SAVE and looks something similar to this:
       //****************************************************************   
       //****************************************************************   
       //*** RECOVERY SKELETON JCL TO RECOVER RECS ON SYS #2 DFHLGLOG ***   
       //****************************************************************   
       //RECOVERY EXEC PGM=FILESAVE   
       //STEPLIB DD DSN=P.CICS.FILSAVE.LOADTS,DISP=SHR   
       //*TEPLIB DD DSN=XY.CICS.FSVE.R400.LOADLIB,DISP=SHR   
       //SYSPRINT DD SYSOUT=*   
       //*   
       //*   
       //************************************   
       //***** START OF FILE DSNAMES *****   
       //************************************   
       //************************************   
       //***** END OF FILE DSNAMES ********   
       //************************************   
       //*   
       //****************************************   
       //*** REQUIRED SORT FILES ***   
       //****************************************   
       //*   
       //SYSOUT DD SYSOUT=*   
       //SORTWK01 DD UNIT=SYSDA,SPACE=(CYL,(10,10)),DISP=(NEW,DELETE)   
       //SORTWK02 DD UNIT=SYSDA,SPACE=(CYL,(10,10)),DISP=(NEW,DELETE)   
       //SORTWK03 DD UNIT=SYSDA,SPACE=(CYL,(10,10)),DISP=(NEW,DELETE)   
       //*   
       //****************************************   
       //*** CA-FILESAVE/RCS WORK FILES ***   
       //****************************************   
       //*   
       //FSWORK01 DD UNIT=SYSDA,SPACE=(CYL,(10,10)),DISP=(NEW,DELETE),   
       // DCB=(LRECL=32756,BLKSIZE=32760,RECFM=VB)   
       //FSWORK02 DD UNIT=SYSDA,SPACE=(CYL,(5,5)),DISP=(NEW,DELETE),   
       // DCB=(LRECL=0,BLKSIZE=23400,RECFM=U)   
       //*   
       //SYSIN DD *

After executing the CA File Save recovery job, you are seeing the following errors at the end of the job:

   FILE-ERRR03 NO VSAM FILE(S) SPECIFIED FOR RECOVERY FUNCTION, FILE RECOVERY IMPOSSIBLE.   
   FILE-MSG001 RECOVER PROCESSING COMPLETED. CONDITION CODE=00012   
   FILE-MSG001 PROGRAM PROCESSING COMPLETED. HIGHEST CONDITION CODE=00012  

What can be done to resolve the FILE-ERRR03 error?

One possibility is that there are no records on the DFHLGLOG dataset. If the DFHLGLOG is empty, one will get the FILE-ERRR03 error when it is processed by the FILESAVE recovery job. To verify this do the following:

  1. Rerun your transactions. 

  2. Flush the logstreams. 

  3. Run a PRINT on them using the following JCL as an example:
       //****************************************************   
       //PRINT EXEC PGM=FILESAVE,REGION=7M   
       //STEPLIB DD DSNAME=hlq.LOADLIB,DISP=SHR   
       //SYSPRINT DD SYSOUT=*   
       //SYSOUT DD SYSOUT=*   
       //LOGSTRM1 DD DSN=log.stream.name,   
       // SUBSYS=(LOGR,,   
       // 'FROM=(2010/154,11:25),TO=(2010/154,11:30),LOCAL')   
       //SYSIN DD *   
       PRINT JOURNAL(LOGSTRM1)   
       //* 

If you see that there are none to PRINT, then the FILE-ERRR03 is coming out because the DFHLGLOG is empty.

If you are seeing records, then the solution is to make sure one flushes the DFHLGLOG and all Journal datasets. Then, revisit the entire CA File Save recovery process, and the FILE-ERRR03 should be resolved.

If you still are receiving the error, please open an issue with CA Support, and a CA Support Technician will assist you.

Be prepared to send in all the output listings up to and including the recovery job that is failing with the FILE-ERRR03 message. Also, you will be sending in the PRINT output of your DFHLGLOG using the PRINT process that is outlined above.

Please help us improve!

Will this information enable you to resolve your issue?

Please tell us what we can do better.

{{feedbackText.length ? feedbackText.length : '0'}}/255

{{status}}

Not what you were looking for?

Search Again >

Product Information

Support by Product >

Communities

Join a Community >

Chat with CA

Just give us some brief information and we'll connect you to the right CA ExpertCA sales representative.

Our hours of availability are 8AM - 5PM CST.

All Fields Required

connecting

We're matching your request.

Unfortunately, we can't connect you to an agent. If you are not automatically redirected please click here.

  • {{message.agentProfile.name}} will be helping you today.

    View Profile


  • Transfered to {{message.agentProfile.name}}

    {{message.agentProfile.name}} joined the conversation

    {{message.agentProfile.name}} left the conversation

  • Your chat with {{$storage.chatSession.messages[$index - 1].agentProfile.name}} has ended.
    Thank you for your interest in CA.


    Rate Your Chat Experience.

    {{chat.statusMsg}}

agent is typing