Hi,

EA does not consider COMPAREX as a system program/utility by default (Workspace options --> System programs). You will find the program COMPAREX reported as Unresolved, as EA would look for the source code of COMPAREX in the default case, thinking it is an application program.

You can go and add/register COMPAREX as a system program (right click --> add). When you do this, you will remove the program from being reported as missing/unresolved.

Coming to the data cards, are you getting an error, saying "missing control card". One option is to load the control card with its complete name. For example, if CNT11 is coded as //DD02  DD DSN=ABC.DEF.LIB(CNT11), then you can load the control card with its name as ABC.DEF.LIB(CNT11) which will form a relationship between the JCL TEST and control card CNT11.

Hope this helps.

Thanks

PriyaRC

Hi,

Of course COMPAREX was not consider as system program/utility initially so I had it already added to SYSTEM PROGRAMS in WORKSPACE OPTIONS. Thus avoiding the Missing/Unresolved for COMPAREX.

Regarding Contol cards, there is NO error while verification as u expect "Missing control card".

Both the control card that i have said in my example CNT11 and CNT22 are referred in the same manner.

//DD02  DD DSN=ABC.DEF.LIB(CNT11) ==> Used in COMPAREX

//DD02  DD DSN=ABC.DEF.LIB(CNT22) ==> Used in SORT

Thus CNT11 is not being identified, wheras CNT22 is identified in my case.

Hope i made the issue clearer.

Regards,

Ek..

Hi,

Of course COMPAREX was not consider as system program/utility initially so I had it already added to SYSTEM PROGRAMS in WORKSPACE OPTIONS. Thus avoiding the Missing/Unresolved for COMPAREX.

Regarding Contol cards, there is NO error while verification as u expect "Missing control card".

Both the control card that i have said in my example CNT11 and CNT22 are referred in the same manner.

//DD02  DD DSN=ABC.DEF.LIB(CNT11) ==> Used in COMPAREX

//DD02  DD DSN=ABC.DEF.LIB(CNT22) ==> Used in SORT

Thus CNT11 is not being identified, wheras CNT22 is identified in my case.

Hope i made the issue clearer.

Regards,

Ek..

Hi,

Of course COMPAREX was not consider as system program/utility initially so I had it already added to SYSTEM PROGRAMS in WORKSPACE OPTIONS. Thus avoiding the Missing/Unresolved for COMPAREX.

Regarding Contol cards, there is NO error while verification as u expect "Missing control card".

Both the control card that i have said in my example CNT11 and CNT22 are referred in the same manner.

//DD02  DD DSN=ABC.DEF.LIB(CNT11) ==> Used in COMPAREX

//DD02  DD DSN=ABC.DEF.LIB(CNT22) ==> Used in SORT

Thus CNT11 is not being identified, wheras CNT22 is identified in my case.

Hope i made the issue clearer.

Regards,

Ek..

Ok. You can try adding the below entry in legacy.xml file. The recommendation is not to change the legacy.xml file available in the data folder, rather copy and have one inside your workspace folder. Just search for ProgUsesCard and you can add the below either before or after that entry.

<ProgUsesCard>

     <item> COMPAREX,SYSIN,.* </item>

</ProgUsesCard>

But my guess is, the above wold work only when the control card is present against a SYSIN DD statement.  

Thanks.

Ok. You can try adding the below entry in legacy.xml file. The recommendation is not to change the legacy.xml file available in the data folder, rather copy and have one inside your workspace folder. Just search for ProgUsesCard and you can add the below either before or after that entry.

<ProgUsesCard>

     <item> COMPAREX,SYSIN,.* </item>

</ProgUsesCard>

But my guess is, the above wold work only when the control card is present against a SYSIN DD statement.  

Thanks.

Great it worked out.. but still the complexity metrics did not include the Souce line count for which changes were made in WORKSPACE OPTIONS under VERIFICATION => SETTINGS for JCL file the system program using control card were added.

Regards,

Ek..

Not sure if i understand the question correctly.

There will be no changes to the "source line count" as we are not modifying the JCL. The complexity report for JCL file should have an entry for "control card usages" metric and this should capture the control card count.

If you are referring to the complexity report for "control cards file", then it should capture the source line count. You can right click on the "control card file" in browser, choose properties and check the statistics tab to see if the source line, blank line info is collected.

I do not know if this is the intended design. You can check with Micro Focus support on this.

Thanks

PriyaRC

Not sure if i understand the question correctly.

There will be no changes to the "source line count" as we are not modifying the JCL. The complexity report for JCL file should have an entry for "control card usages" metric and this should capture the control card count.

If you are referring to the complexity report for "control cards file", then it should capture the source line count. You can right click on the "control card file" in browser, choose properties and check the statistics tab to see if the source line, blank line info is collected.

I do not know if this is the intended design. You can check with Micro Focus support on this.

Thanks

PriyaRC

Not sure if i understand the question correctly.

There will be no changes to the "source line count" as we are not modifying the JCL. The complexity report for JCL file should have an entry for "control card usages" metric and this should capture the control card count.

If you are referring to the complexity report for "control cards file", then it should capture the source line count. You can right click on the "control card file" in browser, choose properties and check the statistics tab to see if the source line, blank line info is collected.

I do not know if this is the intended design. You can check with Micro Focus support on this.

Thanks

PriyaRC