Re: Basic question, sorry in advance

[Bradley Stone <bvstone@xxxxxxxxx>]

I guess I assumed wrong from the lack of information as well and thought
this was an entry plist.

Either way, the plist (entry) will or should look the same on the other
end.  Making it a subprocedure would clean things up and remove any chance
of garbage in the parameters (in most cases).



On Tue, Mar 8, 2016 at 2:12 PM, Michael Schutte <mschutte369@xxxxxxxxx>
wrote:

> You got me confused.  He's trying to call this program from the command
> line from what I can tell?  If parms were greater than 32 bytes, how would
> sub-procedure help? Do you a temporary program so that he can call it?  Yes
> I agree.    Once again, little information is provided. Snippets of code
> that really don't make sense.  But in order to be able to call this
> particular program.
> <snip>
> housek        begsr
> parms         plist
> c                   parm                    ponum            1200
> c                   parm                    whs               3
> </snip>
>
> I can only assume that the name of this parameter list is parms.  Missing
> the beginning of the line for both the begsr and plist.  I can also only
> assume that this is the calling program and not the called program.
>
> -----
> Now that I've re-read it.  I'm not even sure what's not working.
>
> So the question to the OP is, is this working or not?
>
> CALL PGM(MYLIB/WHSCHG) PARM(70118136 '100')
Wouldn't this make it an Entry PLIST?  Maybe it should be, and it's not.

Who knows... too much missing info and misunderstandings.

Brad
www.bvstools.com