I am using TXT2PDF to create PDFs from text files on our z/VM system.
TXT2PDF is written in Rexx and is also Pipe aware.
The are some Call statements in this program and they have me confused.
Example:
Call Value zb123, lz99pe
I cannot find a procedure named zb123. If I write the
Also there isn't a procedure named Value either.
Jim Hughes
603-271-5586
It is fun to do the impossible.
From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On
Behalf Of Hughes, Jim
Sent: Monday, May 10, 2010 12:25 PM
Value is a built-in rexx function.
Call Value blah
will call the procedure/routine whose name is in the variable blah.
i.e.
blah = myFunc
call value blah parm1 parm2
exit
myFunc: procedure
parse arg p1 p2
say 'Hello world!'
return
---
Hey! Hey! You! You! Get off of my cloud!
Oops, that assignment statement should be
blah = 'myFunc'
(Note use of quotes around literal values)
---
Hey! Hey! You! You! Get off of my cloud!
http://news.cnet.com/8301-13578_3-20002423-38.html
On Mon, May 10, 2010 at 09:38, Donald Russell d...@drussell.dnsalias.com
wrote:
Value is a
It is a REXX built-in function. Enter HELP REXX VALUE' for doc.
From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf
Of Hughes, Jim
Sent: Monday, May 10, 2010 10:27 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Rexx Question
Also there isn't a procedure named Value
My question is not about using VALUE. I've used it 100's of times.
My question is about this statement:
Call Value abc123, aaabbccc444555666
Value is NOT called here as a function, no parenthensis().
This format of Call is not documented.
There isn't a Value: in the routine as
On Mon, May 10, 2010 at 12:52 PM, Hughes, Jim jim.hug...@doit.nh.gov wrote:
My question is not about using VALUE. I've used it 100's of times.
My question is about this statement:
Call Value abc123, aaabbccc444555666
Value is NOT called here as a function, no parenthensis().
This format of
Phil,
Look at the sample I included. I do not get an error and the procedure
whose value is in $tocall is never called.
Jim Hughes
603-271-5586
It is fun to do the impossible.
-Original Message-
From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On
Set lightbulb on
The call value isn't calling anything except VALUE and the result is
placed into RESULT.
Thanks to all for helping over this stumbling block.
Best regards,
Jim Hughes
603-271-5586
It is fun to do the impossible.
Still not out the woods.
What does this statement hope to achieve?
IF lnqsI lnqsQ THEN DO
CALL Value laqsN || lnqsQ,,
Value( laqsN || lnqsI, Value( laqsN || lnqsQ ) )
END
I am just not seeing the intent of what is written.
Jim
We're running z/VM 5.3. On our system, we use VM1RES, VM1SPL, and VM1PGx
as our volsers.
Now, I know that when migrating to z/VM 5.4, I'll end up with 540RES,
540SPL, etc.
What do other shops do regarding volsers when migrating? We have 2
z/VM systems (all running z/Linux guests).
On Mon, May 10, 2010 at 1:16 PM, Hughes, Jim jim.hug...@doit.nh.gov wrote:
Still not out the woods.
What does this statement hope to achieve?
IF lnqsI lnqsQ THEN DO
CALL Value laqsN || lnqsQ,,
Value( laqsN || lnqsI, Value( laqsN || lnqsQ ) )
END
I am just
Never mind again.
I looked up VALUE and see can use up to three arguments.
Set Bulb Bright
Jim Hughes
603-271-5586
It is fun to do the impossible.
-Original Message-
From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On
Behalf Of Phil Smith III
After installation I rename as follows:
1. The installation of new releases of z/VM will be installed using
IBM defined VOLSERs. The VOLSERs for production z/VM systems will be
renamed as follows, for information on how to change the VOLSERs, please
see Changing VM VOLSERs:
Thank you PS-Cubed.
I finally have it.
Jim Hughes
603-271-5586
It is fun to do the impossible.
-Original Message-
From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On
Behalf Of Phil Smith III
Sent: Monday, May 10, 2010 1:25 PM
To:
That is how I do my maintenance/migrations too. When I need to move from
5.3
to 5.4, I create alternate mdisks in the production systems (VMARES, VMLR
ES)
and copy the stuff from 540RES to the alternate mdisks. Then on cutover,
I
use dirmaint to switch the production and alternate mdisks. If I
Rename them to your 'standard'..Stick with VM1RES, etc. that's my
advice. I don't like tying volume labels to z/VM releases. It seems
especially silly with paging volumes...Q CPLEVEL if you can't remember
the release your'e running :-)
When you migrate -- relabel the 'old'
That's because Value is a Rexx Built-in Function. A Rexx function doesn't
know (or care) if it was invoked as a function or Call'ed as a subroutine, as
long as it Return's a value of some sort. Thus,
Say Left('Rexx Rox',4)
is exactly equivalent to
Call Left 'Rexx Rox',4
Say Result
It has value when you are running many VM systems at different levels.
Thank you,
Scott
From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On
Behalf Of Scott Rohling
Sent: Monday, May 10, 2010 12:35 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Migration questions
Got it.
Thanks Chip.
Jim Hughes
603-271-5586
It is fun to do the impossible.
-Original Message-
From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On
Behalf Of Chip Davis
Sent: Monday, May 10, 2010 1:39 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re:
This assigns the value aaabbbccc444555666 to variable abc123
and also assigns the old value of abc123 to the built-in variable
RESULT, which call sets.
call Value var, value, selector
is very similar to
result = Value(var,value,selector)
---
Hey! Hey! You! You! Get off of my cloud!
I started using VMxRES, VMxW01, VMxPG1,2,3 VMxSP1,2,3.. and VMxTD1,2..
etc. Where x is A and B in my case since I generally only have two version
on the go.
It also helps if you can move key userids used for testing/operations to a
volume such as VMxS01. Key userids may be OPERATOR,
22 matches
Mail list logo
