On Thu, 19 Jun 2008 20:34:08 -0500, Paul Gilmartin [EMAIL PROTECTED] wrote:
How was the temp panel data set allocated? Perhaps by a profile
or by JCL, or by a DYNALLOC in a Rexx exec? If the last, the
RTDDN operand of BPXWDYN returns the DDNAME to you.
Finding the DDNAME wasn't the problem.
On Fri, 20 Jun 2008 08:20:07 -0500, Mark Zelden wrote:
I use TSO ALLOCATE. The problem was I needed to know the exact data
set name allocated so I could do a 2nd ALLOCATE of the temp PDS with
member name included to write the panel PDS member with EXECIO.
When the data set was allocated to VIO
On Fri, 20 Jun 2008 09:52:09 -0500, Paul Gilmartin [EMAIL PROTECTED] wrote:
Circumventions:
o I don't use VIO.
Can't control what other shops use or do in SMS code.
o I pass the returned ddname to the utility in an alternate ddname parameter.
o I allocate to the DDNAME I intend to use later.
Not sure how I would use ISRDDN in a clist? I've considered parsing LISTALC
output, but was just wondering if there was an easier way.
Thanks,
Cathy
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email
On Thu, 19 Jun 2008 15:01:01 -0500, Cathy Taddei
[EMAIL PROTECTED] wrote:
I've got a clist performing LISTDSI on a dd name to see if it is allocated.
Unfortunately, this doesn't work if the file is allocated to VIO. Is there an
alternative to LISTDSI that will tell whether a ddname is allocated?
Cathy - try this simple exec that you can call from your exec. If you get
a return code of 0 then it is allocated and if you get a 4 then it is not
allocated
/* rexx to test if a dd is allocated */
arg ddname
call outtrap 'isa.'
'listalc sta sys'
call outtrap 'off'
do i = 1 to isa.0
On Thu, 19 Jun 2008 15:01:01 -0500 Cathy Taddei [EMAIL PROTECTED]
wrote:
:I've got a clist performing LISTDSI on a dd name to see if it is allocated.
:Unfortunately, this doesn't work if the file is allocated to VIO. Is there
an
:alternative to LISTDSI that will tell whether a ddname is
Thanks, Mark. The problem is with a vendor-provided clist. They've given me
a workaround that involves locally modifying a bunch of their clists, which
I'll
have to track and refit if they should provide PTF's (it's not SMP-maintained).
I thought I'd make it easier on myself by updating
Thanks, Lionel. Nice and compact!
Cathy
On Thu, 19 Jun 2008 13:30:56 -0700, Lionel B Dyck [EMAIL PROTECTED]
wrote:
Cathy - try this simple exec that you can call from your exec. If you get
a return code of 0 then it is allocated and if you get a 4 then it is not
allocated
/* rexx to test if
Hi Binyamin. LISTDSI only works on DASD -- it gives RC=16 for VIO.
Cathy
On Thu, 19 Jun 2008 23:58:33 +0300, Binyamin Dissen
[EMAIL PROTECTED] wrote:
ALLOC F(ddname) DA(*) will generate RC0 if the DDNAME is already
allocated.
What happens when LISTDSI is issued against VIO? RC=4 would
Although I am starting to question the value of VIO...
As well you should.
As a performance/capacity analyst for over 27 years, I used to recommend VIO
for small datasets (small has increased over that period), but now I don't
think it's worth it, any more.
DASD is so fast, cache and channels
Thanks for your feedback, Ted. I have passed it along to my MVS systems
programmers.
Cathy
On Thu, 19 Jun 2008 22:00:23 +, Ted MacNEIL [EMAIL PROTECTED]
wrote:
Although I am starting to question the value of VIO...
As well you should.
As a performance/capacity analyst for over 27 years,
On Thu, 19 Jun 2008 15:28:09 -0500, Mark Zelden wrote:
What exactly is the problem / issue? I ask, because I ran into a problem with
VIO and IPLINFO using LISTDSI a while back. I changed my ISPF panel data set
to a temp PDS and then used LISTDSI to find the DDNAME so I could write
to it with
13 matches
Mail list logo
