Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

logon procedure error

1,324 views
Skip to first unread message

G Manohar Rao, Noida

unread,
Feb 7, 2002, 7:44:03 AM2/7/02
to
hi all ,
my tso logon procedure is SYS1.TSOPROC(ISPFPROC).
i have added a SYSPROC statement as
// DD DSN=VTI0HC1.IPERV311.CLIST,DISP=SHR.

after that when i tried to logon i am getting the following error.

ICH70001I VTI0HC1 LAST ACCESS AT 08:37:09 ON THURSDAY, FEBRUARY 7, 2002
IKJ56455I VTI0HC1 LOGON IN PROGRESS AT 08:39:07 ON FEBRUARY 7, 2002
IKJ56457I LOGON FAILED JCL ERROR IN LOGON PROCEDURE
IKJ56470I VTI0HC1 LOGGED OFF TSO AT 08:39:09 ON FEBRUARY 7, 2002

Can anyone tell me how to remove that entry

thanks
manohar

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to list...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Volker Bandke

unread,
Feb 7, 2002, 7:58:31 AM2/7/02
to
Try one of the following

- logon with a different logon procedure
- logon at a different system that has access to the broken logon proc
- restore the procedure library from a backup (possibly stand-alone)
- use a standalone editor (like ZZSA, real great tool, and it is free)

With kind Regards |\ _,,,---,,_
ZZZzz /,`.-'`' -. ;-;;,
Volker Bandke |,4- ) )-,_. ,\ ( `'-'
(BSP GmbH) '---''(_/--' `-'\_)

Life is an illusion and reality is a figment of the imagination. --
The Rocky Horror Picture Show

(Another Wisdom from my fortune cookie jar)


-----Ursprüngliche Nachricht-----
Von: IBM Mainframe Discussion List [mailto:IBM-...@BAMA.UA.EDU]Im
Auftrag von G Manohar Rao, Noida
Gesendet: Donnerstag, 7. Februar 2002 13:44
An: IBM-...@BAMA.UA.EDU
Betreff: [IBM-MAIN] logon procedure error

Rick Fochtman

unread,
Feb 7, 2002, 7:59:45 AM2/7/02
to
----------------------<snip>----------------------

my tso logon procedure is SYS1.TSOPROC(ISPFPROC).
i have added a SYSPROC statement as
// DD DSN=VTI0HC1.IPERV311.CLIST,DISP=SHR.

after that when i tried to logon i am getting the following error.

ICH70001I VTI0HC1 LAST ACCESS AT 08:37:09 ON THURSDAY, FEBRUARY 7, 2002
IKJ56455I VTI0HC1 LOGON IN PROGRESS AT 08:39:07 ON FEBRUARY 7, 2002
IKJ56457I LOGON FAILED JCL ERROR IN LOGON PROCEDURE
IKJ56470I VTI0HC1 LOGGED OFF TSO AT 08:39:09 ON FEBRUARY 7, 2002

Can anyone tell me how to remove that entry

---------------------<unsnip>-------------------------
This is an excellent argument for having an alternate LOGON proc.

Try logging on with procedure IKJACCT and using the TSO line editor to
insert a '*' into position 3 of the offending line.

Henry Alirio Rincon Niño

unread,
Feb 7, 2002, 8:01:36 AM2/7/02
to
// DD DSN=VTI0HC1.IPERV311.CLIST,DISP=SHR.

If you line have at doc (.) at the end, It is the trouble.
You have to remove it.

Henry.

-----Mensaje original-----
De: G Manohar Rao, Noida [mailto:gman...@NOIDA.HCLTECH.COM]
Enviado el: Jueves, 07 de Febrero de 2002 07:44 a.m.
Para: IBM-...@BAMA.UA.EDU
Asunto: logon procedure error


hi all ,


my tso logon procedure is SYS1.TSOPROC(ISPFPROC).
i have added a SYSPROC statement as
// DD DSN=VTI0HC1.IPERV311.CLIST,DISP=SHR.

after that when i tried to logon i am getting the following error.

ICH70001I VTI0HC1 LAST ACCESS AT 08:37:09 ON THURSDAY, FEBRUARY 7, 2002
IKJ56455I VTI0HC1 LOGON IN PROGRESS AT 08:39:07 ON FEBRUARY 7, 2002
IKJ56457I LOGON FAILED JCL ERROR IN LOGON PROCEDURE
IKJ56470I VTI0HC1 LOGGED OFF TSO AT 08:39:09 ON FEBRUARY 7, 2002

Can anyone tell me how to remove that entry

thanks
manohar

Henry Alirio Rincon Niño

unread,
Feb 7, 2002, 8:03:21 AM2/7/02
to
You have to do this remove with another tso user or you can use another
tsoproc.

henry.

G Manohar Rao, Noida

unread,
Feb 7, 2002, 8:32:29 AM2/7/02
to
rick,
PROCEDURE NAME IKJACCT NOT AUTHORIZED

-----Original Message-----
From: Rick Fochtman [mailto:Rick.F...@BOTCC.COM]
Sent: Thursday, February 07, 2002 6:29 PM
To: IBM-...@BAMA.UA.EDU
Subject: Re: logon procedure error


----------------------<snip>----------------------


my tso logon procedure is SYS1.TSOPROC(ISPFPROC).
i have added a SYSPROC statement as
// DD DSN=VTI0HC1.IPERV311.CLIST,DISP=SHR.

after that when i tried to logon i am getting the following error.

ICH70001I VTI0HC1 LAST ACCESS AT 08:37:09 ON THURSDAY, FEBRUARY 7, 2002
IKJ56455I VTI0HC1 LOGON IN PROGRESS AT 08:39:07 ON FEBRUARY 7, 2002
IKJ56457I LOGON FAILED JCL ERROR IN LOGON PROCEDURE
IKJ56470I VTI0HC1 LOGGED OFF TSO AT 08:39:09 ON FEBRUARY 7, 2002

Can anyone tell me how to remove that entry

---------------------<unsnip>-------------------------
This is an excellent argument for having an alternate LOGON proc.

Try logging on with procedure IKJACCT and using the TSO line editor to
insert a '*' into position 3 of the offending line.

----------------------------------------------------------------------

Rick Fochtman

unread,
Feb 7, 2002, 8:39:53 AM2/7/02
to
--------------------<snip>---------------------

PROCEDURE NAME IKJACCT NOT AUTHORIZED

-------------------<unsnip>--------------------
Got another LOGON proc you can use?

Or someone else handy who can edit that library?

Francois LE MANER

unread,
Feb 7, 2002, 8:56:37 AM2/7/02
to
restore the backup prior your modification :

F DFHSM,RECOVER you-clist-pds

is an there another TSO user logged on that can edit the proc you
modify ?

For IKJACCNT not authorized , use TSO ACCOUNT command to add this proc
to your user , so next time you can alternativly logon with IKJACCNT

Volker Bandke

unread,
Feb 7, 2002, 9:10:28 AM2/7/02
to
Use IBMUSER to logon


With kind Regards |\ _,,,---,,_
ZZZzz /,`.-'`' -. ;-;;,
Volker Bandke |,4- ) )-,_. ,\ ( `'-'
(BSP GmbH) '---''(_/--' `-'\_)

Life is an illusion and reality is a figment of the imagination. --
The Rocky Horror Picture Show

(Another Wisdom from my fortune cookie jar)


-----Ursprüngliche Nachricht-----
Von: IBM Mainframe Discussion List [mailto:IBM-...@BAMA.UA.EDU]Im
Auftrag von G Manohar Rao, Noida

Gesendet: Donnerstag, 7. Februar 2002 14:32
An: IBM-...@BAMA.UA.EDU
Betreff: Re: [IBM-MAIN] logon procedure error

Matthew Stitt

unread,
Feb 7, 2002, 9:34:50 AM2/7/02
to
You missed one, Volker.

Have someone else edit the logon procedure and fix it.

Volker Bandke

unread,
Feb 7, 2002, 10:09:25 AM2/7/02
to
Could be. I have the strong feeling, though, that he is all alone on that
machine.....


With kind Regards |\ _,,,---,,_
ZZZzz /,`.-'`' -. ;-;;,
Volker Bandke |,4- ) )-,_. ,\ ( `'-'
(BSP GmbH) '---''(_/--' `-'\_)

Life is an illusion and reality is a figment of the imagination. --
The Rocky Horror Picture Show

(Another Wisdom from my fortune cookie jar)


-----Ursprüngliche Nachricht-----
Von: IBM Mainframe Discussion List [mailto:IBM-...@BAMA.UA.EDU]Im

Auftrag von Matthew Stitt
Gesendet: Donnerstag, 7. Februar 2002 15:40
An: IBM-...@BAMA.UA.EDU
Betreff: Re: [IBM-MAIN] AW: [IBM-MAIN] logon procedure error

Fred Hoffman

unread,
Feb 7, 2002, 10:46:23 AM2/7/02
to
I don't have my P390 cookbook with me, but, I believe that it mentions 2 or
3 alternative procedures that could be used for logon procs. If someone has
that book available, maybe they could check to see what they are, or maybe
my memory is failing and I'm just fantasizing. Oh well. Fred

Mark Zelden

unread,
Feb 7, 2002, 11:09:46 AM2/7/02
to
On Thu, 7 Feb 2002 09:56:48 -0600, Fred Hoffman <fhof...@TAD.ORG> wrote:

>I don't have my P390 cookbook with me, but, I believe that it mentions 2 or
>3 alternative procedures that could be used for logon procs. If someone
has
>that book available, maybe they could check to see what they are, or maybe
>my memory is failing and I'm just fantasizing. Oh well. Fred
>

What makes you think this is a P/390 system?

Mark

--
+------------------------------------------------------------------+
| Mark Zelden - OS/390 and z/OS consultant - Chicago |
| mailto:mze...@flash.net |
| Mark's MVS Utilites: http://home.flash.net/~mzelden/mvsutil.html |
+------------------------------------------------------------------+

Greg Dorner

unread,
Feb 7, 2002, 11:21:46 AM2/7/02
to
In a message dated 2/7/02 7:32:35 AM Central Standard Time,
gman...@NOIDA.HCLTECH.COM writes:

> rick,
> PROCEDURE NAME IKJACCT NOT AUTHORIZED

I believe that would be IKJACCNT.

Fred Hoffman

unread,
Feb 7, 2002, 11:23:22 AM2/7/02
to
It probably isn't a p390, but the information that he might be able to use
is in that book. (Like I said, I think it is). It may be on some of the
cd's that contain documentation, but having had a similar problem to the one
he has now, I ran across the additional logon procs in an area of the p390
cookbook that deals with tso logons. The cookbook is sort of a P390 help aid
for dummies. Maybe I should have spelled it all out, but I was just trying
to be helpful without going into too long of an explanation. Fred

-----Original Message-----
From: Mark Zelden [mailto:mze...@FLASH.NET]
Sent: Thursday, February 07, 2002 10:09 AM
To: IBM-...@BAMA.UA.EDU
Subject: Re: logon procedure error

On Thu, 7 Feb 2002 09:56:48 -0600, Fred Hoffman <fhof...@TAD.ORG> wrote:

>I don't have my P390 cookbook with me, but, I believe that it mentions 2 or
>3 alternative procedures that could be used for logon procs. If someone
has
>that book available, maybe they could check to see what they are, or maybe
>my memory is failing and I'm just fantasizing. Oh well. Fred
>

What makes you think this is a P/390 system?

Mark

--
+------------------------------------------------------------------+
| Mark Zelden - OS/390 and z/OS consultant - Chicago |
| mailto:mze...@flash.net |
| Mark's MVS Utilites: http://home.flash.net/~mzelden/mvsutil.html |
+------------------------------------------------------------------+

----------------------------------------------------------------------

Greg Dorner

unread,
Feb 7, 2002, 11:39:31 AM2/7/02
to
Fo future reference, I usually create two additional logon procs which are
'off limits' to modification that I place in SYS1.PROCLIB. One, I call
TSOONLY, which has no data sets referenced, and allows you to at least get
into TSO and use the line editor, or IDCAMS, etc. The other I call TSOISPF,
and it only contains references to IBM ISPF and SDSF libraries. No user
libraries or additional product libraries. Make sure you miminally authorize
your system programmers access to these procs via ACCOUNT or your security
product.

Greg Dorner
Ultraserv Corp
dor...@ultraserv.net

John Eells

unread,
Feb 7, 2002, 11:40:27 AM2/7/02
to
If I remember right, the TSO-only PROC on the AD systems, which was
created just for this eventuality, is named either IKJACCNT (note the
*N*) or TSOPROC.

If he has an AD system, he can log on with that PROC using IBMUSER (if
it's not revoked) and use TSO/E EDIT to remove the line:

EDIT SYS1.TSOPROC(ISPFPROC) CNTL
LIST <=== To get the line number
DELETE nnnnnn <=== To delete the line
SAVE
END

Or he could use any other working logon PROC from any ID authorized to
update the SYS1.TSOPROC data set.

On a P/390, if all else fails, then given enough disk space he could
restore another the SCPxxx volume for his release from the CDs, IPL with
his existing one offline, rename his existing SCPxxx, bring it online,
edit the PROC, rename the volume back, and re-IPL. (This assumes the
system configuration hasn't been changed to break the setup on a virgin
SCPxxx volume. If it has, then at least the z/OS target volumes will
also be needed to IPL.)

John Eells (Original AD system builder)
ServerPac Design
IBM Poughkeepsie

Fred Hoffman wrote:
>
> I don't have my P390 cookbook with me, but, I believe that it mentions 2 or
> 3 alternative procedures that could be used for logon procs. If someone has
> that book available, maybe they could check to see what they are, or maybe
> my memory is failing and I'm just fantasizing. Oh well. Fred
>

----------------------------------------------------------------------

David Alcock

unread,
Feb 8, 2002, 12:07:27 PM2/8/02
to
-snip-

> after that when i tried to logon i am getting the following error.
-snip-

> IKJ56457I LOGON FAILED JCL ERROR IN LOGON PROCEDURE

I see that Greg Dorner already posted my cure for tso proc failures:
have a proc handy that allocates no datasets and another one that only
allocates the standard (bare minimum) IBM ISPF libraries. You should
test using these procs before depending on using them!

Another thing to so is when you make a change, logon with an alternate
userid or have a cow-orker do it while you stay logged on .

Yet another thing you could do if you have TCPIP FTP server running (and
who doesn't anymore): FTP to MVS, download the offending proc, edit it
on the PC and upload the proc back to MVS. Logon FD&H.

Mark Zelden

unread,
Feb 8, 2002, 12:21:22 PM2/8/02
to
On Fri, 8 Feb 2002 12:18:48 EST, Greg Dorner <GregL...@CS.COM> wrote:

>
>A decidedly less proactive approach I used once (a long time ago) is when
you
>realize your mistake, run feverishly from cubicle to cubicle yelling 'DON'T
>LOGOFF'!! Sometimes this works, but it is a bit embarrassing! Also is not
>recommended in a single user environment.
>

That also doesn't work if the person logged on doesn't have the
authority to update the proclib!

Mark

--
+------------------------------------------------------------------+
| Mark Zelden - OS/390 and z/OS consultant - Chicago |
| mailto:mze...@flash.net |
| Mark's MVS Utilites: http://home.flash.net/~mzelden/mvsutil.html |
+------------------------------------------------------------------+

----------------------------------------------------------------------

Greg Dorner

unread,
Feb 8, 2002, 12:19:39 PM2/8/02
to
In a message dated 2/8/02 11:07:23 AM Central Standard Time, dal...@CSW.COM
writes:

> Another thing to so is when you make a change, logon with an alternate
> userid or have a cow-orker do it while you stay logged on .

A decidedly less proactive approach I used once (a long time ago) is when you


realize your mistake, run feverishly from cubicle to cubicle yelling 'DON'T
LOGOFF'!! Sometimes this works, but it is a bit embarrassing! Also is not
recommended in a single user environment.

----------------------------------------------------------------------

Larry Kahm

unread,
Feb 8, 2002, 1:15:07 PM2/8/02
to
And of course, running a JCL check >before< you try to use the proc wouldn't
hurt you any, either...


Deru Sudibyo

unread,
Feb 8, 2002, 10:02:16 PM2/8/02
to
Error on logon proc is really painful. Could be anything, jcl error
(typo), dsn doesn't exist, security aspect, etc. To avoid this, simplify
your logonproc to minimun config, ie; only required DD for TSO. Then,
the rest can be added via logon clist (profile). If necessary, you can
give a chance to each user to have their own profile clist. We can
discuss it later.

If you do not want to bother with ds concatenation in logon proc, use
CCAT command in your clist instead of FREE/ALLOCATE command. CCAT is
non-standard TSO cmd, but you can download file # 535 from
http://www.cbttape.org/cbtdowns.htmCBT. Hope this help.

regards,

--
Deru Sudibyo


posted via MFF : http://www.mainframeforum.com/f1363/s

registration is required to reply to posts

0 new messages