Chris,
I already define all of this ,
my problem is in the initailization of the resolver procedure :
11.06.36 STC01108 TUESDAY, 16 FEB 2010
11.06.36 STC01108 IEF695I START RESOLVER WITH JOBNAME RESOLVER IS ASSI
11.06.36 STC01108 $HASP373 RESOLVER STARTED
11.06.36 STC01108 IEF403I
the strangest thing of all .
after deleting all the marks in the procedure the resolver initialization
was successfully.
thanks .
2010/2/16 מתן כהן matancohen...@gmail.com
Chris,
I already define all of this ,
my problem is in the initailization of the resolver procedure :
11.06.36 STC01108
Matan
I don't understand what you mean by marks. It could be you mean the
comment records in the procedure.[1]
I already define all of this ...
I'm not sure you have. You have *not* shown what you have specified for
the RESOLVER_PROC statement in the BPXPRMxx member used in the
On Tue, 16 Feb 2010 08:50:33 -0600, Chris Mason wrote:
For confirmation of what we said, you should find the log of the address space
with the name RESOLVER which was the one which initiated as part of the IPL
process. That should show the procedure name IEESYSAS - I think since I
can't recall
Chris, Brian,
matan did IPL his system with Resolver_Proc(Resolver) specified in BPXPRMxx
and this started the resolver procedure under IEESYSAS and MSTR. As you
know, RESOLVER can be stoped and strated by regular MVS commands. Afaik,
Matan has stoped the RESOLVER (P RESOLVER) and started it
Hi Chris,
1.i do mean comments.
2. as i already said before . i did all the customization as written in the
books (just as you wrote me) . but my resolver just didn't want to read my
setupres member as i wrote.
after i delete all the comments from the resolver procedure the resolver did
read the
Your original PROC had two EXEC statements and the SETUP DD was after the
second, which didn't run. Could it be that you deleted one of those EXEC
statements along with the comments?
Bob
מתן כהן wrote:
Hi Chris,
1.i do mean comments.
2. as i already said before . i did all the
Bob
Thanks for confirming what I was beginning to suspect - but couldn't really
believe since it was so illogical!
This is yet another reason for getting rid of all those idiotic comment records
so that the dog can see the rabbit!
I took Matan's log and removed all the lines beginning with
you're right , there was 2 EXEC statement as i can see now .
2010/2/17 Chris Mason chrisma...@belgacom.net
Bob
Thanks for confirming what I was beginning to suspect - but couldn't really
believe since it was so illogical!
This is yet another reason for getting rid of all those idiotic
hi,
i have a strange problem .
while customize my tcpip so it will work correctly.
i'm running the resolver procedure with the :
//SETUP DD DSN=PANDAG.USER.TCPPARMS(SETUPRES),DISP=SHR,FREE=CLOSE
when the resolver is initiliaze i can see the following messages in the
procedure log:
EZZ9298I
Did you notice the requirement that the JCL for the RESOLVER proc must be
fetched from MSTJCLxx's PROCLIB concatentation (probably SYS1.PROCLIB)?
Did you code RESOLVER_PROC(name) in BPXPRMxx? When this statement is not
coded, then RESOLVER is started using certain default values you cannot
Matan
You should show the whole procedure and the log of the procedure starting
and you should provide the name that you use to name the procedure in the
procedure library - which I hope is an appropriate library.
You should also show the RESOLVER_PROC statement in the relevant
BPXPRMxx
Matan
When this statement is not coded, then RESOLVER is started using certain
default values you cannot override.
What Brian Peterson is sort-of saving is that, when the system starts
the resolver function address space with the command
START
13 matches
Mail list logo
