Previous Topic: Imbedded Multi-User Facility (IMUF) Option

Next Topic: Other Considerations

IMUF Implementation and Startup

An IMUF is configured and customized exactly as it would have been configured and customized for standard (external) MUF operation as described in the CA Datacom/AD Installation and Maintenance Guide.

IMUF is not "MUFLite". The same rules and regulations that apply to external MUF operation, apply to IMUF operation as well.

IMUF can be MUF-plexed or shared with other CA solution address spaces without any impact on CAIENF operation, though there is likely to be little, if any, benefit on behalf of CAIENF by doing so.

In a mutli-MUF environment, IMUF must be uniquely identified through the CA-Datacom/AD DBSIDPR element like any other MUF.

All of the job steps and DD statements that normally would have been included in the JCL for the external MUF started task procedure, must be included in the CAIENF started task procedure for IMUF operation.

A small amount of "handshaking" logic has been added to both CAIENF and CA-Datacom/AD to support IMUF operation, but essentially, the IMUF is unaware that it is running as an CAIENF subtask.

There are only two discernable differences between standard MUF operation and IMUF operation:

To activate the IMUF feature, place a single "IMUF" statement anywhere in the ENFPARMS PDS member or data set of the CAIENF started task procedure. This directs CAIENF to load the appropriate support routines and initialize the IMUF environment. Datacom/MUF startup/status messages will be posted to the CAIENF job log along with CAIENF startup/status messages.

Partial example illustrating placement of the IMUF statement:

//ENFPARMS   DD  *
……
DCM(CAS9DCM0)
DCM(CAS9DCM2)
……
IMUF
RECORD(YES)
……
/*