BMC Software, Inc., Confidential and Proprietary Information
BMC48000–BMC48099 127
1 The execution control record indicates that a BATCH CONTROL
FACILITY (BCF) process had started (status flag of
ACTIVE=ON) but did
not complete (status flag of
ENDED=OFF).
System Action: The job step terminates abnormally with user abend U1550.
User Response: Modify the status of the execution control record by using the BCF
Active Job utility (in batch mode) or by completing the following steps using the
BCF ISPF interface:
1. Make sure that the job is not executing.
2. On the Active Jobstep Display panel, type M beside the job step.
3. On the Active Job Status Modification panel, type Y in the Set Job Abend field
and press Enter.
BMC48062I BCF FAST OSAM PURGE INITIALIZED
Explanation: BATCH CONTROL FACILITY (BCF) is ready to automatically
purge the OSAM database buffer when the buffer pool becomes full of altered
buffers.
System Action: Processing continues.
User Response: This message is for your information only. No action is necessary.
BMC48063I BCF FAST OSAM PURGE NOT INITIALIZED; REASON = rc
Explanation: During initialization, BATCH CONTROL FACILITY (BCF) was
unable to activate the Fast OSAM Buffer Purge function for the reason (rc) provided
in the message. BCF can report the following reason codes:
1 The release of IMS that is executing does not support Fast OSAM Buffer
Purge. The IMS release must be IMS/VS Version 2.2 or any release of
IMS/ESA.
2 The IMS module DFSDBH00 could not be located within the job step’s job
pack area.
3 The IMS module DFSDBH00 is loaded in a protected MVS subpool, and
authorization was not available from the subsystem on the system where
this job is executing.
4 The IMS module DFSDBH00 is not loaded into the private storage of the
job step.
5 The DFSDBH00 found in the job pack area was an alias and not a major
name.
6 It was not possible for BCF to establish a necessary intercept point for Fast
OSAM Buffer Purge initialization.
