Thanks for the responses to far. We definitely use MSG.
I need to elaborate.
I have an EXEC that runs on my userid, lets call that user STEVE
The PropOp userid is HAL <g>
The EXEC I run on STEVE basically edits what is typed in and if the data
typed in meets the req'd criteria, it repackages the input, adds a few pieces (key words)
and then does a CP MSG HAL <repackaged input>.
HAL is sitting there waiting for something to come his way. The specific
char string will kick off an EXEC based on definitions in the RTABLE.
The first thing that EXEC (on HAL) does is to display a message that it is starting (time stamp, etc.)
I never see this message.
. . . even more detail . . .
The command I issue from STEVE to HAL is
MSG HAL PUT <file name> <file type> <and then some more key words for the EXEC on HAL>
This entire string is never longer than 95 characters. The length can from vary from 80 chars to 95 chars.
PUT is the keyword in the RTABLE. When the file name is 7 chars or less it works fine, when file name is 8, it
appears to never get to HAL. The problem is I don't know if it's getting to HAL and the RTABLE is ignoring it
or if it plain doesn't get to HAL.
As mentioned earlier, this all worked in VM 4.3 but has appeared to quite working in VM 5.2
Thanks,
Steve G.
| Kris Buelens <[EMAIL PROTECTED]>
Sent by: The IBM z/VM Operating System <[email protected]> 08/03/2006 06:32 AM
|
To: [email protected] cc: Subject: Re: Programmable Operator |
But, even with DIAG 8, the limit is 240 chars for the command.
'CP MSG ....' silently truncates the message
call diag 8,'MSG ...' gives a REXX syntax error if the command is too
long.
Kris,
IBM Belgium, VM customer support
> On Wednesday, 08/02/2006 at 01:10 MST, Don Russell
> <[EMAIL PROTECTED]> wrote:
> > Steve Gentry wrote:
> > >
> > > Hello.
> > > We use a Programmable Operator to run certain functions. We send a
> > > "command" to the PropOp using
> > > the MSG command. Is there a maximum length the sent MSG can be? If
> > > so, can it be changed somewhere?
> > > We're having a problem getting some things to work that used to work
> > > on VM 4.3 (and I thought was working
> > > on 5.2). We're running VM 5.2 on a z9 box.
> > > Thanks,
> > > Steve G.
> > From help cp msg...
> >
> > 1. If a message is issued from a CMS environment, the command and
the
> > message text cannot be longer than 240 characters.
> But if it used to work on 4.3, then it should continue to work in 5.2.
And
> to answer Steve's question, no, you can't change the 240-character limit
> on CMS commands. Better is to use e.g. diag(8,'MSG ....') to bypass CMS
> command processing if possible.
> Alan Altmark
> z/VM Development
> IBM Endicott
