Subject: RE: IPL error
dabbate@courts.state.va.us
Date: Wed Aug 20 2008 - 11:26:18 EDT
We rename our production IPL and JCL procs to a backup name and then
catalog new procs using the production names so we always IPL off the same
name procs, easier to keep track of which one is correct. However, we use
an ASIPROC which will always contain the same production names. If we need
to fallback, we just do a LOADPARM ..P and key in the backup names. When
we rename the procs, we do the same thing with the source so we are always
in sync.
Don Abbate
Supreme Court of Virginia
(804) 786-4540
"Mohammed Imam"
<mimam@co.cumberl
and.nc.us> To
Sent by: "VSE Discussion List"
owner-vse-l@Lehig <vse-l@Lehigh.EDU>
h.EDU cc
Subject
08/20/08 11:04 AM RE: IPL error
Please respond to
vse-l@Lehigh.EDU
Ron,
I simply rename $IPLxxx and $0JCL to a new name and modify as per
requirement. Then IPL using the new name. If there is a problem, which
sometime happens, I do IPL again using the running set.
-----Original Message-----
From: owner-vse-l@Lehigh.EDU [mailto:owner-vse-l@Lehigh.EDU] On Behalf
Of Ron Ashley
Sent: Wednesday, August 20, 2008 10:56 AM
To: VSE Discussion List
Subject: RE: IPL error
Mohammed,
I do not know exactly what you mean. We have the actual proc's in
bim-edit.
But we submit these procs to system library:
// EXEC LIBR
ACCESS SUBLIB=IJSYSRS.SYSLIB
CATALOG $IPL100.PROC DATA=YES REPLACE=YES
863,$$A$SUPX,VPOOL=128K,VIO=512K,VSIZE=300M
ADD 380:38F,3480
ADD 860:87F,3277
ADD 920:93F,ECKD
We then IPL using JCL=$JCL100
If we want to make a change to JCL100, we copy the member JCL100 that is
in
Bim-edit and make it member IPL200. We then compile it as IPL200. We
then
ipl using IPL=$IPL200. If this does not work IPL100 in system library is
the
same and hasn't changed. We the IPL using IPL100 and go into bim-edit
and
change IPL200 and resubmit it. We then ipl using IPL200. Once this works
we
use IPL200 from now on. At present we are at IPL800. The other IPL's
(100
through 700) are still there and can be used to IPL. One time we had a
optical character reader that had a pin bent in it and we could not IPL.
We
didn't know what the problem was at that time. It would ipl to a certain
point and stop (the point at which ipl senses all hardware). Well IBM
didn't
know what it was. So we went back a couple IPL's and it would finally
IPL
all right. We then looked at the difference between the two IPL's and
came
up with this piece of hardware was not in the ipl procedure and we could
IPL
quick enough and able to get most of the system up to progress instead
of
being down a long time.
-----Original Message-----
From: owner-vse-l@Lehigh.EDU [mailto:owner-vse-l@Lehigh.EDU] On Behalf
Of
Mohammed Imam
Sent: Wednesday, August 20, 2008 9:06 AM
To: VSE Discussion List
Subject: RE: IPL error
I almost do the same, except that I keep the pair (IPL/JCL) in system
library itself and not Bim Edit. If there is a problem with the
new/changed
pair, I fall, back to the backed up one.
-----Original Message-----
From: owner-vse-l@Lehigh.EDU [mailto:owner-vse-l@Lehigh.EDU] On Behalf
Of
Ron Ashley
Sent: Wednesday, August 20, 2008 9:21 AM
To: VSE Discussion List
Subject: RE: IPL error
I thought I would show VSE/listers what we do with IPL and JCL procs.
1. We punch the IPLEA and JCLEA procs.
2. We pull them into Bim edit. We make procs IPL100 and JCL100.
3. We delete procs IPLEA and JCLEA.
4. We have flex box so we key in I 900 hit enter and then EXT and hit
enter.
5. On VSE screen we hit enter key and it comes up with statement to key
in
IPL and JCL parameters.
6. We key in IPL=$IPL100,JCL=$$JCL100 and hit enter and it starts
ipling.
7. So if there is ANY change to IPL or JCL procs we set up a whole new
JCL
proc and call it IPL200, etc. We then IPL with IPL=$IPL200.
8. THIS WOULD THEREFORE NOT HAVE THE PROBLEM BELOW. IF IPL200 DID NOT
WORK
THEN WE USE IPL100 AGAIN AND CORRECT PROC IPL200.
Ronald Ashley
-----Original Message-----
From: owner-vse-l@Lehigh.EDU [mailto:owner-vse-l@Lehigh.EDU] On Behalf
Of
Dan Gofton
Sent: Wednesday, August 20, 2008 8:03 AM
To: VSE Discussion List
Subject: RE: IPL error
Thank you Mohammed.
Dan Gofton
Technical Services Administrator/Manager County of Saginaw, MI
989 790 5525
> -----Original Message-----
> From: owner-vse-l@Lehigh.EDU [mailto:owner-vse-l@Lehigh.EDU] On Behalf
> Of Mohammed Imam
> Sent: Wednesday, August 20, 2008 8:45 AM
> To: VSE Discussion List
> Subject: RE: IPL error
>
> You may STOP at DLF and reenter the DLF and go.
>
> -----Original Message-----
> From: owner-vse-l@Lehigh.EDU [mailto:owner-vse-l@Lehigh.EDU] On Behalf
> Of Dan Gofton
> Sent: Wednesday, August 20, 2008 8:39 AM
> To: VSE Discussion List
> Subject: IPL error
>
> Good morning.
>
> I screwed up my IPLPROC on my systems LPAR. I added a DLF statement
> for the lock file but failed to add the ADD for the drive it is on.
> Obviously, the IPL then throws up.
>
> Is there an easy way to get around this. I'm hoping either by setting
> a loadparm and executing the IPL one statement at a time and being
> able to add the ADD statement, or by not executing the DLF statement.
>
> Or, am I going to have to restore from my FCOPY backup?
>
> Thanks.
>
> Dan Gofton
> Technical Services Administrator/Manager County of Saginaw, MI
> 989 790 5525
>
>
>
>
This archive was generated by hypermail 2b25 : Fri Aug 29 2008 - 15:50:13 EDT