CA OPS/MVS OPSLOG archiving procedure, ARCHPROC, initializes as JOB versus a started task.

Products

• OPS/MVS Event Management & Automation

Issue/Introduction

When the OPSARCH 'started task' (FROM CCLXCNTL(ARCHPROC) initiates, it gets these messages:
$HASP373 OPSARCH  STARTED                 
OPS1000J OPSARCH OPSARCH S39580 STC39580 S
IEF403I OPSARCH - STARTED - TIME=23.55.00

Normally we see these messages for a started task:
IEF695I START OPSARCH  WITH JOBNAME OPSARCH  IS ASSIGNED TO USER xxxxxxx , GROUP xxxxxx
$HASP373 OPSARCH  STARTED                                                      
OPS1000J OPSARCH OPSARCH S24601 STC24601 S                                     
IEF403I OPSARCH - STARTED - TIME=15.37.38

Why doesn't the ASCRE macro (create address space), for OPSARCH, use the ATTR=JOBSPACE parameter?

According to IBM, if the task-submit macro ASCRE isn’t coded with ATTR=JOBSPACE, it will get treated as a system address space (and not have the IEF695I message) instead of a normal started task. 

Environment

Release: PVLA2.00200-12.2-OPS/MVS-Event Management & Automation-for JES2
Component:

Resolution

The primary reason for not using the ATTR=Jobspace parameter on the OPS/MVS OPSLOG archive address space create was for consistency for all the address spaces that CA OPS/MVS Event Management and Automation starts with an ASCRE.

We would consider a change to this processing via an enhancement request including business reasons why you feel this is necessary.

Additional Information

Archiving and Merging OPSLOG Data

ASCRE - Create address spaces