Hi David, Frank Kyne, in one of his monthly newsletters, was noticing the same thing: it is hard to have a full "view" of where all the WF service definition files are "sourced", for both ones you've used and ones you are looking for. Happily, though, WF does remember individually where the source of *that* WF instance was created from (under the Workflow Details twisty).
However - I think this might make a nice customer requirement, so an enterprise can "bookmark" their favorite location where the WF service definition came from, and make it available for all to see. Might not help with those you've not used, but at least we'd have something to perhaps work with should it get implemented.... I do like Kurt's suggestion of using zMSC! It was precisely created for common (even complicated) WFs that you want to run again and again, with perhaps only slightly changed inputs. AND, if I could even take it a step further (although I haven't personally tried it), the zMSC team tells me you can invoke a zMSC service with a supported REST API, making it even nicely leveraged by any program/automation you might want to use, if you didn't want to use the GUI. Meaning, you'd then have both GUI for interactive, and REST API for automation support. Something for everyone. -Marna WALLE z/OS System Install and Upgrade IBM Poughkeepsie ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
