Identifying the LPAR



Support for MQSeries and Websphere Message Oriented Middleware communication systems for z/OS

Identifying the LPAR

Postby Frnd » Tue Apr 06, 2010 1:04 am

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.
Frnd
 
Posts: 3
Joined: Tue Apr 06, 2010 12:55 am
Has thanked: 0 time
Been thanked: 0 time

Re: Identifying the LPAR

Postby dick scherrer » Tue Apr 06, 2010 2:22 am

Hello,

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

Try looking at the $HASP373 message.
Hope this helps,
d.sch.
User avatar
dick scherrer
Global moderator
 
Posts: 6268
Joined: Sat Jun 09, 2007 8:58 am
Has thanked: 3 times
Been thanked: 93 times

Re: Identifying the LPAR

Postby Frnd » Tue Apr 06, 2010 2:28 am

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?
Frnd
 
Posts: 3
Joined: Tue Apr 06, 2010 12:55 am
Has thanked: 0 time
Been thanked: 0 time

Re: Identifying the LPAR

Postby dick scherrer » Tue Apr 06, 2010 2:49 am

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?
Hope this helps,
d.sch.
User avatar
dick scherrer
Global moderator
 
Posts: 6268
Joined: Sat Jun 09, 2007 8:58 am
Has thanked: 3 times
Been thanked: 93 times


Return to WebSphere MQ