LOGON allocations

This forum provides the support of Dezhi Mainframe systems. Please post your questions about logon, usage of our mainframe environment.

Moderators: sysprog, prino, sfan, steve-myers, Tim001

LOGON allocations

Postby RSI01DD » Sat 29 Dec 2012, 21:42

I see in the FAQs that users can create their own ISPF libraries to be allocated during LOGON. I have done so but for some reason my ISPMLIB is not being allocated. My ISPPLIB, ISPLLIB and ISPTLIB (ISPTABL) are being successfully allocated.

Is this a known problem?
Is there a logon CLIST/REXX that can be called during logon so users can perform their own allocation at this time?

Thanks,
Dan

Part of what's allocated at logon:
ISPMLIB SHR ISP.SISPMENU
SHR ISF.SISFMLIB
ISPSLIB SHR ISP.SISPSLIB
SHR ISP.SISPSENU
SHR ISF.SISFSLIB
ISPPLIB SHR RSI01DD.ISPPLIB
SHR SYSFAN.ISPPLIB
SHR ISP.SISPPENU
SHR ISF.SISFPLIB
ISPTABL SHR RSI01DD.ISPTLIB
ISPTLIB SHR RSI01DD.ISPTLIB
SHR SYSFAN.ISPTLIB
SHR ISP.SISPTENU
SHR ISF.SISFTLIB
ISPLLIB SHR RSI01DD.ISPLLIB
SHR SYSFAN.ISPLLIB
SHR ISP.SISPLOAD
Dan D
RSI01DD
 
Posts: 4
Joined: Thu 13 Dec 2012, 01:39

Re: LOGON allocations

Postby prino » Sat 29 Dec 2012, 22:08

Replied to this post via PM.
Robert AH Prins
robert.ah.prins @ the.17+Gb.Google thingy
Some programming here :mrgreen:
prino
 
Posts: 479
Joined: Sat 06 Jun 2009, 21:41
Location: Vilnius, Lithuania

Re: LOGON allocations

Postby RSI01DD » Sat 29 Dec 2012, 22:15

Robert showed me the REXX that gets executed at logon. It's not that user friendly but at least the allocations are performed for TSO.

The problem with ISPMLIB was that the file name must be userid.SISPMENU not userid.ISPMLIB.

Dan
Dan D
RSI01DD
 
Posts: 4
Joined: Thu 13 Dec 2012, 01:39

Re: LOGON allocations

Postby steve-myers » Sun 30 Dec 2012, 01:44

You can always run something as specified in the LOGON panel --

Command ===> %start

I use that. My member does a TSOLIB to my personal library and a couple of other things. My personal library has a number of personal commands

The problem is it is not run until after you exit the ISPF session started by the LOGON proc.

My last job had a useful feature: if it found a userid.CLIST(#userid) member it would run it before the initial ISPF start. I still miss that feature.
steve-myers
 
Posts: 452
Joined: Tue 04 May 2010, 15:43


Return to Dezhi systems: Mainframe

Who is online

Users browsing this forum: No registered users and 0 guests

cron