Re: Service entry point not working for User ID *ALL

On 22-Jan-2015 01:35 -0600, Thomas Raddatz wrote:

<<SNIP>> I like the idea of submitting a comment regarding to the
documentation of SBREAK. I am going to set a mark for me to do that
once we updated our boxes to v7. <<SNIP>>

FWiW, this serves as a reminder, a followup, for the [original, quoted-above] discussion thread [that was apparently broken into the following two distinct threads in the archive]:
[http://archive.midrange.com/wdsci-l/201501/threads.html#00094]
[http://archive.midrange.com/wdsci-l/201501/threads.html#00096]

IIRC, one of your posts this year\summer had since implied that the transition to v7 had transpired. But AFaIK the IBM KC has also dropped /comment/ support :-( Perhaps instead, and IMO more appropriately, pursue a defect call [i.e. a PMR raised], to discuss the failure of a specification of * or *ALL for the USER on SBREAK, either to diagnose that specification as an error or to effect making "all non-debug jobs to stop at" the requested statement per that specification.

If the specification should be an error, then likely just correcting the QSYRUSRA API to diagnose the '*' or '*ALL' as unsupported [which seems the only logical effect] would suffice; the error would be percolated to the invoker -- though what is the effect would best be verified for usability, from the SEP debugger(s).

If the specification should not be an error, then the QSYRUSRA API I infer would still require the same correction [noted above], but also the invokers would have to stop passing the illegal values on to that API, and thus they would have to determine in an alternate manner whatever that API intended to provide, and make whatever happen that should [according to the updated documentation].