Page 1 of 1

Identifying the LPAR

PostPosted: Tue Apr 06, 2010 1:04 am
by Frnd
I am a newbie to mainframes.When we use /*JOBPARM S=ANY , the job could really run on any LPAR in a sysplex.Is there a way to fine where the job actually did start up ? Please help me asap.

Re: Identifying the LPAR

PostPosted: Tue Apr 06, 2010 2:22 am
by dick scherrer
Hello,

Please help me asap.
We don't do asap. . . :(

Try looking at the $HASP373 message.

Re: Identifying the LPAR

PostPosted: Tue Apr 06, 2010 2:28 am
by Frnd
Thanks for the response.Can you please help me with little more detail on how to use this as I am very new to mainframes.Can this be included in a step and this would be returning the LPAR info?

Re: Identifying the LPAR

PostPosted: Tue Apr 06, 2010 2:49 am
by dick scherrer
Hello,

Did you look at the message in your JES output? If not, do so and confirm this is what you are looking for.

Can this be included in a step and this would be returning the LPAR info?
Probably not. . . I'm not sure what you are asking. The lpar will not change from step to step. Once the process is allocated to some lpar, the entire job runs on that lpar.

Why do you believe you want/need this as part of a job's execution?