In external security, the DEFAULT verb is considered as UPDATE, in the same way as DELETE, DEFINE...
We obtained already a PTF, reducing the amount of calls to the DEFAULT for the GLOBAL variables as result of a case.In this case the calls were routed to the own system and had nothing to do with the real usage of MSF.
In the past we also had a discussion about the values of the parameter SEC.AUCTSYNA, used in the security rule, who doesn't returns in some cases the right target.In certain cases, especially when the option SECURE/NOSECURE of the DEFINE is working as designed (we have a case open for this item) and the authority checking is passed from the system of origin to the target system (see idea), we want authorize the use of the verb DEFAULT.The problem is that is really unclear when OPSCTL.MSF with the verb DEFAULT is called in OPS/MVS and what is the routing. Putting a "?"-sign in 2.6 results in a OPSCTL.MSF DEFAULT to all systems, even before a target system is selected. Can somebody provide a clear list of the internal calls to OPSCTL.MSF with the verb DEFAULT?Best Regards,
Please open a Support case to address.
although still believe that the question is not relevant for me only, I opened a case today.Best Regards,
Frank, I think you're right. I too would like to see that behaviour explained. Is it to block unauthorized targets from the list? IE: if the disp=reject, will the target not be shown?
Marcel van Ek
Hi Frank, Marcel, there is currently a case open for this and the outcome will be shared at this space, so that everyone can take notice of it... Thanks for bringing it up...
Frank Ternest - Mainframe System • Engineering Enterprise Technology
Services • Corporate Technology
Euroclear SA/NV, 1 Boulevard du Roi Albert II, 1210 Brussels, Belgium
Please consider the environment and do not print this email unless