RE: RUNJOBCMD V5R4 replacement (was QTEMP in LIBL...)

midrange-l-request@xxxxxxxxxxxx wrote:

  5. RUNJOBCMD V5R4 replacement (was QTEMP in LIBL...) (Elvis Budimlic)

Per "useful replacement" comment and as I use RUNJOBCMD occasionally...

In one of the COMMON sessions Bruce Vining mentioned new Job Interrupt API
in V5R4.  It seemed to me that it could be used in lieu of RUNJOBCMD so I
coded to it.  
Works... although I think I've run into a bug where program data buffer
passed to the job interrupt exit point program is corrupted after a certain
point (320 bytes instead of 2000 bytes).  Any PTFs Bruce?

Tom, I can send you 3 required sources if you wish.  You'll either need a C
compiler or rework it in RPG or CL.

Elvis:

I've known about that API for quite a while, but didn't consider it as a 
"useful replacement" due to a particular restriction or two that the API has. 
However, I didn't do any _serious_ testing of it except on a pre-release V5R4 
that was very short on PTFs.

Your comment has me looking at it again and my first run is promising. I'll 
have some more thorough tests in a few days, I hope.

Thanks for the reminder.

Tom Liotta

-----Original Message-----
Subject: RE: QTEMP in LIBL (Was Re: OVRDBF problem or maybe itis
earlyAlzheimer's


Minor note...

The RUNJOBCMD command should not work at V5R4 and above. The TRCJOB
EXITPGM() parameter is no longer used. AFAIK, there is no replacement for
this particular functionality (outside of MI-style programming tricks). If
anybody knows of a useful replacement, many of us would find it handy I'm
sure.