OCL is interpreted within the System/36 environment on the AS/400 – you don’t need to compile procedures to run them. There are several ways to start an OCL procedure :-
Use the STRS36PRC command to start a procedure from a non-S/36 environment job.
Start the S/36 environment using STRS36 (this is only for your job, not the whole system), change to the library where the procedure is (or ensure that the library is in your library list) and type the name of the procedure on the command line and press enter.
Use a menu to start your procedure (basically does the same as starting the procedure from a S/36 environment job).
There is no STRDBG or STRISDB type command for OCL – to debug your procedures you can change the logging level of your job :-
CHGJOB LOG(4 00 *SECLVL) LOGCLPGM(*YES)
You can also specify logging for your OCL procedure :-
CHGS36PRCA MBR(YOURPROC) FILE(YOURLIB/QS36PRC) LOG(*YES)
Bear in mind that your procedure may switch logging off (I think there’s an ATTR LOG-NO command to do this, but it’s been some time since I’ve looked at this).
When debugging, you can also add calls to QCMD to give you a command line at certain points of your procedure – this can be useful to check whether the previous commands have executed correctly or not.
If you have any specific problems with your procedures, just let us know – I’m sure someone here will have a solution for you.
Hope this all helps, regards,