New Encore EXHFILE without Stopping ESP Workload Automation Systems
search cancel

New Encore EXHFILE without Stopping ESP Workload Automation Systems

book

Article ID: 260670

calendar_today

Updated On:

Products

ESP Workload Automation

Issue/Introduction

ESP Audit Log showing errors:

ES5P633E Invalid record header encountered, slot xx data set xxxx

Environment

Component: ESP WORKLOAD AUTOMATION 
Release:   12.0

Cause

After running the encore sanity report utility (CYBRMSAN).  The report showed error messages of bad data in EXH file 

Resolution

Step by step to recreate the Encore EXHFILE.

1. On ESP Master go to pagemode and issue
      oper status
      oper quiesce
      oper encparm quiesce <- To stop ESP from sending requests to Encore and release EXHFILE
      oper encparm status    <-- Check to make sure its QUIESCED  
      

2. On ESP Proxies go to pagemode and issue
     oper status
     oper encparm quiesce <- To stop ESP from sending requests to Encore and release EXHFILE  run master/Proxies
     oper encparm status    <-- Check to make sure its QUIESCED  

3.  If your proxy routing is set to master go to pagemode and issue the following to quiesce
    routing   <--  check to see if its shows master if it does continue below
    routing local 
    oper encparm quiesce  <- To stop ESP from sending requests to Encore and release EXHFILE
    oper encparm status     <-- Check to make sure its QUIESCED 

4. Run CYBRMALC and CYBRMCPY to allocate a new bigger EXHFILE and copy from the old EXHFILE

5. Rename the old EXHFILE, and new EXHFILE to the name of what's in ESP init parm

6. Logon into Master and issue in pagemode
      routing local
      oper restart               <-- run this on Master only
      oper encparm restart <-- Run on Master and Proxies
      oper encparm status
      oper status

7. check your jobs make sure all is now running and restart job or if there were issues with errors in EXHFILE then rerun the jobs.

Additional Information

N/A