Why did RECEIVE job receive more FMIDs than selected?
search cancel

Why did RECEIVE job receive more FMIDs than selected?

book

Article ID: 33691

calendar_today

Updated On:

Products

COMMON SERVICES FOR Z/OS 90S SERVICES Common Services

Issue/Introduction

I am in the process of installing CCS r14.1 S1401. I ran the AW03RECD job to receive 11 FMIDs. When I checked the output, I discovered that there were 12 FMIDs received. I did not select CAW3E11 (CAIENF/CICS SPAWN) but this was received anyway.

Why was CAW3E11 received?
Is it a mandatory component/FMID?

Environment

Release: CA90SV00200-14.1-Common Services-for z/OS
Component:

Resolution

The reason CAW3E11 was received is a direct result of how SMP/E is designed and how the SMPMCS provided by CA Common Services (CCS) was delivered. Take a look at the following excerpts taken from the SMPMCS file delivered with the previous and current releases of CCS.

 

At CCS v14.0, the ++FUNCTION statement for CAIENF/CICS SPAWN looked like this:

++FUNCTION(CAW3E01) REWORK(2011152)
++VER     (Z038)

Beginning with CCS r14.1, the ++FUNCTION statement for CAIENF/CICS SPAWN looks like this:

++FUNCTION(CAW3E11) REWORK(2014042)
++VER(Z038) FMID(CAW3E10)

Notice how the ++VER statement changed to include FMID(CAW3E10). This is the FMID for CAIENF/CICS. So based on the SMP/E design, the control card RECEIVE FORFMID (CAW3E10), will cause the the FMID of CAW3E11 to be selected as a result.

 

The CAIENF/CICS SPAWN component is not mandatory. If you do not have a requirement for the CAIENF/CICS SPAWN component as specifically requested by a CA mainframe product, than you have no need to install this component. You may elect to run an SMP/E REJECT of CAW3E11 to remove it from the GLOBAL zone, or simply exclude it from the SELECT list in the subsequent apply job, AW04APP.