Common routine among projects
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
You can acually "globally catalog" the routine.
But this involves a number of steps and will not be supported by IBM, so any maintenance issues will be your own.
Essentially the steps are as follows:
But this involves a number of steps and will not be supported by IBM, so any maintenance issues will be your own.
Essentially the steps are as follows:
- copy the source code into a Type 19 file (create one if you don't have one - CREATE.FILE DSU_BP 19 will suffice as a command) including the FUNCTION or SUBROUTINE definition, the RETURN function/statement and a terminating END statement
compile (for example BASIC DSU_BP MyRoutine)
catalog using a name that begins with an asterisk (for example CATALOG DSU_BP *MyRoutine)
call or declare your routine with the asterisk prefix (for example DEFFUN MyRoutine(Arg1, Arg2) CALLING "*MyRoutine")
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
It has since occurred to me that, because it's in IBM's manual, they would have to support it.
And it IS used in the product itself. Any job sequence will have calls to *DSR*Message, for example.
And it IS used in the product itself. Any job sequence will have calls to *DSR*Message, for example.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.