TPX Batch Report message : IEF861I FOLLOWING RESERVED DATA SET NAMES UNAVAILABLE hilvl.ADMIN2
search cancel

TPX Batch Report message : IEF861I FOLLOWING RESERVED DATA SET NAMES UNAVAILABLE hilvl.ADMIN2

book

Article ID: 206570

calendar_today

Updated On:

Products

TPX - Session Management

Issue/Introduction

When executing the following Batch report, this message is shown:

    IEF861I FOLLOWING RESERVED DATA SET NAMES UNAVAILABLE TO userid

    IEF863I DSN = hilvl.TPX.ADMIN2 userid RC = 04 RSN = 00000000 FROM SERVICE ENQ

The job will not run unless TPX is down, why does this occur?

Batch Report:

//BATCHADM  EXEC TPX,VNODE='*BATCH*'                           
//EXTFILE  DD    UNIT=SYSDA,SPACE=(CYL,(1,1))                       
//RPTFILE  DD    SYSOUT=*                                           
//*  COPYING FROM KD 51575 HOW TO PRINT THE ACT TABLE               
//SYSIN DD *                                                        
C                                                                   
C PRINT ACT TABLE                                                   
C                                                                   
EXTRACT GIVING(EXTFILE) ACT (VACTTBL(ACTDMV))                       
C                                                                   
SET RTITLE1                                                         
' ACTNAME    ACTLABEL           ACTSESS      VACTTBL'               
SET RTITLE2                                                         
' ====================================================='            
REPORT GIVING(RPTFILE) USING(EXTFILE)                               
(( ' &ACTNAME' '  &ACTLABEL        ' ' &ACTSESS'  '      &VACTTBL'))
//                                                                  

 

Environment

Release : 5.4

Component : CA-TPX for OS/390

Resolution

Batch Reporting will execute the TPX proc.

The message occurs because hilvl.ADMIN2 has DISP=OLD in the TPX startup proc. This means the dataset is allocated for exclusive use. TPX is up and running and uses this file therefore no

other process can access the file until TPX is down. 

Changing the DISP on ADMIN2 to DISP=SHR resolves the problem.