Re: RPG/400 pgm strange behaviour

[Scott Klement <klemscot@xxxxxxxxxxxx>]

On Tue, 18 Jul 2000, Mark Holliday wrote:

> Actually, Marcin, I had this problem calling from a CL pgm into a CL
> pgm.  I think you might even have this problem calling from an RPG pgm
> into a CL pgm.  Someone down this thread stated that you could create
> a command, which would then allocate memory for the size of a given
> field.  That sounds like a good solution, as well.
> 
> Mark

You shouldn't have this problem calling from a CL program to another CL
program.   However, if you do a SBMJOB from a CL program to call another
CL program, you'll run into this error again.  Maybe thats what you're
thinking of?

The reason for this is simple... When you create a new job, it can no
longer access the memory from the original job.  So it creates a new 
"command-line" to start up the program in the new job.   The proper
fix, as you already pointed out, is to create a command.



+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---