This forum provides the support of Dezhi Mainframe systems. Please post your questions about logon, usage of our mainframe environment.
Moderators: sysprog, prino, sfan, steve-myers, Tim001
by nclouston » Fri 22 Oct 2010, 16:31
I have gone bananas!
I submit a job with TYPRUN=SCAN and it picks up the modified procedure from my proclib.
When I dummy out the TYPRUN=SCAN and leave everything else as-is, the procedure is picked up from SYSFAN.ADCD.PROCLIB.
Why?
The job is in N13964.SOURCE.CICS(COMPCOB) if you want to peek.
-
nclouston
-
- Posts: 67
- Joined: Fri 09 Apr 2010, 17:55
by prino » Fri 22 Oct 2010, 20:24
nclouston wrote:I have gone bananas!
I submit a job with TYPRUN=SCAN and it picks up the modified procedure from my proclib.
When I dummy out the TYPRUN=SCAN and leave everything else as-is, the procedure is picked up from SYSFAN.ADCD.PROCLIB.
Why?
The job is in N13964.SOURCE.CICS(COMPCOB) if you want to peek.
Just submitted it (JESNO 40912) and other than the fact that is ended with an RC=12, it did pick up your proclib...
-
prino
-
- Posts: 479
- Joined: Sat 06 Jun 2009, 21:41
- Location: Vilnius, Lithuania
-
by nclouston » Sat 23 Oct 2010, 10:14
Thanks Robert, I really must have gone bananas because I tried it a couple of times. I will look later.
-
nclouston
-
- Posts: 67
- Joined: Fri 09 Apr 2010, 17:55
by nclouston » Sat 23 Oct 2010, 12:20
Well, blow me down with a feather! It is behaving now - I know it was not before because the scan would report no errors but try and execute it and the new symbolic, which is new in my version of the procedure, was 'not used'.
Now to get the thing to compile!
-
nclouston
-
- Posts: 67
- Joined: Fri 09 Apr 2010, 17:55
Return to Dezhi systems: Mainframe
Who is online
Users browsing this forum: No registered users and 0 guests