volume.
-Original Message-
From: Harris, Randy
Sent: Friday, February 22, 2008 7:03 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: ZOS Upgrade Issue
I added the "unit(3390)" parm to my allocate and it ran ok.
I still haven't discovered why I'm getting INELIGIBLE DEVICE w
Unfortunately, you won't see me there. Jim will be though.
Bob
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Steven Conway
Sent: Friday, February 22, 2008 1:01 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: ZOS Upgrade Issue
:-)
See y
ainframe Discussion List
02/22/2008 12:43 PM
Please respond to
IBM Mainframe Discussion List
To
IBM-MAIN@BAMA.UA.EDU
cc
Subject
Re: ZOS Upgrade Issue
If you think I am going to cast the first stone this topic
Let's just say &
That's right SYSALLDA is a system defined ESOTERIC my bad.
From:
Mark Zelden <[EMAIL PROTECTED]>
To:
IBM-MAIN@BAMA.UA.EDU
Date:
02/22/2008 11:21 AM
Subject:
Re: ZOS Upgrade Issue
On Fri, 22 Feb 2008 10:39:01 -0600, Michael Saraco
<[EMAIL PROTECTED]> wrote:
>I hav
ven Conway
Sent: Friday, February 22, 2008 12:31 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: ZOS Upgrade Issue
Adding to the list of stuff I should have, but didn't,
think about before opening my mouth. Those who know me can imagine the
l
Phone: (703) 450-3156
Fax:(703) 450-3197
Mark Zelden <[EMAIL PROTECTED]>
Sent by: IBM Mainframe Discussion List
02/22/2008 12:21 PM
Please respond to
IBM Mainframe Discussion List
To
IBM-MAIN@BAMA.UA.EDU
cc
Subject
Re: ZOS Upgrade Issue
On Fri, 22 Feb
On Fri, 22 Feb 2008 10:39:01 -0600, Michael Saraco
<[EMAIL PROTECTED]> wrote:
>I have worked on numerous systems that never had SYSALLDA setup in HCD or
>ALLOCxx and never had a problem running TSO BATCH. The default for generic
>for DASD is 3390 that has no ESOTERIC assigned to it.
>I tired a Ran
o it.
> I tired a Randy's job on Zos14 and a Zos17 and it ran fine without any
> SYSALLDA in esotrics or a ALLOCxx and without adding the unit to the JCL.
>
>
>
>
> From:
> Steven Conway <[EMAIL PROTECTED]>
> To:
> IBM-MAIN@BAMA.UA.EDU
> Date:
>
In a message dated 2/22/2008 9:04:07 A.M. Central Standard Time,
[EMAIL PROTECTED] writes:
I still haven't discovered why I'm getting INELIGIBLE DEVICE
without the unit parm.
Thank you for your suggestions,
>>
Maybe the ESOTERICs don't match the configuration? D IOS,CONFIG then doodle
ar
trics or a ALLOCxx and without adding the unit to the JCL.
From:
Steven Conway <[EMAIL PROTECTED]>
To:
IBM-MAIN@BAMA.UA.EDU
Date:
02/22/2008 10:17 AM
Subject:
Re: ZOS Upgrade Issue
Randy, without ALLOCxx in your PARMLIB concatenation, the default device
will be SYSALLDA. If that'
Randy, without ALLOCxx in your PARMLIB concatenation, the default device
will be SYSALLDA. If that's not defined in your gen, it would explain the
failure. A browse thru HCD would be interesting.
Cheers,,,Steve
Steve Conway
Lead Systems Programmer
Information Systems & Services Division
Comp
Sent: Friday, February 22, 2008 9:25 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: ZOS Upgrade Issue
Randy, what do you have specified as UNIT in ALLOCxx of SYS1.PARMLIB?
Steve Conway
Lead Systems Programmer
Information Systems & Services Division
Computer & Network Operations
Phone: (703)
Sent by: IBM Mainframe Discussion List
02/22/2008 10:03 AM
Please respond to
IBM Mainframe Discussion List
To
IBM-MAIN@BAMA.UA.EDU
cc
Subject
Re: ZOS Upgrade Issue
I added the "unit(3390)" parm to my allocate and it ran ok.
I still haven't discovered why I'm get
662-566-3447
[EMAIL PROTECTED]
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Jack Kelly
Sent: Thursday, February 21, 2008 10:10 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: ZOS Upgrade Issue
As suggested before, I would put in the unit parm
n List
02/21/2008 10:12 AM
Please respond to
IBM Mainframe Discussion List
To
IBM-MAIN@BAMA.UA.EDU
cc
Subject
Re: ZOS Upgrade Issue
It appears to be defined correctly in the dialogs.
Screen Copy shows:
UPPZFS05F3 3390-9
If I strip out one step of the ALLOCDS job and submit outs
Furniture Industries, Inc.
Tupelo, MS 38802
Phone: 662-566-3447
[EMAIL PROTECTED]
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Steven Conway
Sent: Thursday, February 21, 2008 8:33 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: ZOS Upgrade Issue
Rand
respond to
IBM Mainframe Discussion List
To
IBM-MAIN@BAMA.UA.EDU
cc
Subject
ZOS Upgrade Issue
Good Day,
I am attempting to upgrade from Z/OS V1.4 to Z/OS V1.7 and am having a
bit of a problem
getting the ALLOCDS job to run correctly. I am wondering if any of you
have experienced this
My first guess would be the unit name for that TSO userid.
Bob
Harris, Randy wrote:
Good Day,
I am attempting to upgrade from Z/OS V1.4 to Z/OS V1.7 and am having a
bit of a problem
getting the ALLOCDS job to run correctly. I am wondering if any of you
have experienced this?
I tried search
Good Day,
I am attempting to upgrade from Z/OS V1.4 to Z/OS V1.7 and am having a
bit of a problem
getting the ALLOCDS job to run correctly. I am wondering if any of you
have experienced this?
I tried searching the archives but did not find anything helpful.
My error occurrs in the ALCZFS step
19 matches
Mail list logo
