BAS20302E DEPENDENCY HAS BEEN DEFINED FOR FIELD
Article ID: 99177
Updated On:
Products
MICS Resource Management
Issue/Introduction
The xxxCGEN job fails with a U0998 and the MICS LOG contains a BAS20302E message as follows:
BAS20302E DEPENDENCY HAS BEEN DEFINED FOR FIELD THAT IS NOT ON THE FILE, ccceee
where ccc is the Component id (CIC for example) and eee is the element name
BAS20302E DEPENDENCY HAS BEEN DEFINED FOR FIELD THAT IS NOT ON THE FILE, ccceee
where ccc is the Component id (CIC for example) and eee is the element name
Environment
Release:
Component: MCIC
Component: MCIC
Resolution
This indicates that there is an element in your cccGENIN member that is dependent on the element listed in the error message; however,
the timespans for both elements are not in-sync for the defined timespans.
For example,
Suppose the following error is displayed in the CICCGEN output
BAS20302E DEPENDENCY HAS BEEN DEFINED FOR FIELD THAT IS NOT ON THE FILE, CSYTOQTM
If you search the MICS LOG for CSYTOQTM it will show how the element is defined in your CICGENIN member
NAME CSYTOQTM 11 0 N N N N Total Time Queued due to MXT
In this case we can see that the element is 'active' only in the detail timespan whereas it is 'off' in all other timespans.
If you continue to search the sysout for CSYTOQTM it will take you to the following element where CSYTOQTM is a DEPEND element.
NAME CSYAVQTM 11 0 0 0 0 0 AVERAGE MAXTASK QUEUING TIME
EXP 01 IF CSYTOTDT > 0 THEN
EXP 02 CSYAVQTM = CSYTOQTM / CSYTOTDT;
EXP 03 ELSE CSYAVQTM = 0;
DEPEND CSYTOTDT CSYTOQTM
This shows us that element CSYAVQTM is an element that depends on two elements CSYTOTDT and CSYTOQTM.
In addition, we can see that CSYAVQTM is active in ALL timespans.
This is why the BAS20302E is occurring because both CSYTOTDT and CSYTOQTM are turned off in the DAYS, WEEKS, MONTHS and YEARS timespans but CSYAVQTM is active for them all.
To correct the issue you can either turn on the CSYTOTDT and CSYTOQTM elements in the DAYS, WEEKS, MONTHS and YEARS timespands or turn off CSYAVQTM in those timespans.
Once changes have been made to your xxxGENIN member, then resubmit the sp.CNTL(xxxCGEN) job
the timespans for both elements are not in-sync for the defined timespans.
For example,
Suppose the following error is displayed in the CICCGEN output
BAS20302E DEPENDENCY HAS BEEN DEFINED FOR FIELD THAT IS NOT ON THE FILE, CSYTOQTM
If you search the MICS LOG for CSYTOQTM it will show how the element is defined in your CICGENIN member
NAME CSYTOQTM 11 0 N N N N Total Time Queued due to MXT
In this case we can see that the element is 'active' only in the detail timespan whereas it is 'off' in all other timespans.
If you continue to search the sysout for CSYTOQTM it will take you to the following element where CSYTOQTM is a DEPEND element.
NAME CSYAVQTM 11 0 0 0 0 0 AVERAGE MAXTASK QUEUING TIME
EXP 01 IF CSYTOTDT > 0 THEN
EXP 02 CSYAVQTM = CSYTOQTM / CSYTOTDT;
EXP 03 ELSE CSYAVQTM = 0;
DEPEND CSYTOTDT CSYTOQTM
This shows us that element CSYAVQTM is an element that depends on two elements CSYTOTDT and CSYTOQTM.
In addition, we can see that CSYAVQTM is active in ALL timespans.
This is why the BAS20302E is occurring because both CSYTOTDT and CSYTOQTM are turned off in the DAYS, WEEKS, MONTHS and YEARS timespans but CSYAVQTM is active for them all.
To correct the issue you can either turn on the CSYTOTDT and CSYTOQTM elements in the DAYS, WEEKS, MONTHS and YEARS timespands or turn off CSYAVQTM in those timespans.
Once changes have been made to your xxxGENIN member, then resubmit the sp.CNTL(xxxCGEN) job
Feedback
Yes
No
Powered by
