Update and submit the following JCL, but from a different LPAR and on
which you can logon:
/*ROUTE XEQ <LPAR on which you are 'already logged on', e.g. LPAR1>
//*
//*********************************************************************
//* ISSUE MVS COMMANDS IN BATCH *
//* *
//*********************************************************************
//*
//INTRDR EXEC PGM=IEBGENER
//SYSPRINT DD SYSOUT=*
//SYSIN DD DUMMY
//SYSUT2 DD SYSOUT=(*,INTRDR)
//SYSUT1 DD *,DLM=@@
/*$VS,'CANCEL <your
userid>'
@@
//*
//
This should terminate your being logged on the other named LPAR (e.g.
LPAR1 or LPAR2) within the sysplex.
CP (retired sysprog)
Tom Marchant wrote:
On Thu, 14 Jul 2016 17:08:28 +0530, Jake Anderson wrote:
I am trying to access one of an LPAR1 within a sysplex. Where I get a
message as you already logged on to LPAR1. When I have someone to check my
ID from other system its shows that My ID is active in LPAR2.
We cannot help you to understand what is happening when you paraphrase the
messages that you receive. Please give the exact messages. Include the response
from D TS,L on both LPARs.
We have MIM but we have not enabled Parallel Logon facility serialization.
I am curious why z/OS is displaying a wrong System Name instead of the One
my ID is active ?
I am curious why you think that the system is giving you the wrong information,
rather than that you are not connecting to the system that you want.
Its like I am logged into LPAR2, but when I try accessing LPAR1, it shows
that you are already logged on to LPAR1..
Does it really say LPAR1? Or does the it just say that you are already logged
on the the current LPAR?
This gets resolved after My ID is cancelled from LPAR 2.
If your session was really cancelled on LPAR2, you were logged on to LPAR2, not
LPAR1
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
