| View previous topic :: View next topic |
| Author |
Message |
ROBOTIS
Beginner
Joined: 08 Jun 2006
Posts: 1
Topics: 1
|
 Posted: Sat Jun 10, 2006 10:38 am Post subject: ISPF File Allocations: Need Help On Production Rollout |
 |
|
Gents:
I'm rolling-out a development ISPF app to a many production TSO users. My method of allocating private development ISPF panel libs etc is too cumbersome for production use.
In Dev - I ran a sysexec (shown below) from ISPF = 6 Command Shell, which has 3 steps, it allocats the libs using Libdef, invokes the app with Ispexec Select, then frees the lib's with null Libdef (occurring each time I PF3 out of the app).
For production I need:
1: A way to allo all libs in the logon Clist, and especially how to free
them EACH TIME we PF3 out of the app. Is a null LIBDEF
appropriate in a logon Clist?
2: A way to use a 'SYSP.' system-level qualifer for each allocated
library - avoiding hundreds of user-id prefixed copies of panel libs etc,
(one for each user).
3: A way to suppress TSO from prefixing the user's id to each library -
without requiring them to key in the TSO 'No Prefix' command each
time they use the app.
Any Ideas ?
Rob
| Code: |
/* MY OLD DEVELOPMENT METHOD */
ISPEXEC 'LIBDEF ISPLLIB DATASET ID('USERID.MYAPP.V201.ISPLLIB')'
ISPEXEC 'LIBDEF ISPMLIB DATASET ID('USERID.MYAPP.V201.ISPMLIB')'
ISPEXEC 'LIBDEF ISPPLIB DATASET ID('USERID.MYAPP.V201.ISPPLIB')'
ISPEXEC 'LIBDEF ISPTLIB DATASET ID('USERID.MYAPP.V201.ISPTLIB')'
/*-----------------------------------------------------------------*/
/* INVOKE DIALOG */
/*-----------------------------------------------------------------*/
/* */
ISPEXEC 'SELECT CMD(%MYAPPL) NEWAPPL(ABC) NEWPOOL' */
/*-----------------------------------------------------------------*/
/* LIBARARY DE-ALLOCATIONS */
/*-----------------------------------------------------------------*/
ISPEXEC 'LIBDEF ISPLLIB'
ISPEXEC 'LIBDEF ISPMLIB'
ISPEXEC 'LIBDEF ISPPLIB'
ISPEXEC 'LIBDEF ISPTLIB' |
|
|
| Back to top |
|
 |
semigeezer
Supermod
Joined: 03 Jan 2003
Posts: 1014
Topics: 13
Location: Atlantis
|
| Posted: Sat Jun 10, 2006 5:32 pm Post subject: |
|
|
You can't use ISPF services like libdef before entering ISPF so they are not appropriate for a logon CLIST. ALTLIB and TSOLIB are OK there.
The naming problems you are having are because you don't understand TSO naming conventions. Place a name in single quotes and and the prefix will not be added:
Finally, use STACK on your LIBDEF calls so that you don't destroy the underlying allocations.
| Code: | /* follow TSO naming conventions and use STACK */
ISPEXEC "LIBDEF ISPLLIB DATASET ID('SYSP.MYAPP.V201.ISPLLIB') STACK"
ISPEXEC "LIBDEF ISPMLIB DATASET ID('SYSP.MYAPP.V201.ISPMLIB') STACK"
ISPEXEC "LIBDEF ISPPLIB DATASET ID('SYSP.MYAPP.V201.ISPPLIB') STACK"
ISPEXEC "LIBDEF ISPTLIB DATASET ID('SYSP.MYAPP.V201.ISPTLIB') STACK"
/*-----------------------------------------------------------------*/
/* INVOKE DIALOG */
/*-----------------------------------------------------------------*/
/* */
ISPEXEC "SELECT CMD(%MYAPPL) NEWAPPL(ABC) NEWPOOL" */
/*-----------------------------------------------------------------*/
/* LIBARARY DE-ALLOCATIONS */
/*-----------------------------------------------------------------*/
ISPEXEC "LIBDEF ISPLLIB"
ISPEXEC "LIBDEF ISPMLIB"
ISPEXEC "LIBDEF ISPPLIB"
ISPEXEC "LIBDEF ISPTLIB" |
Also, I don't think you need newpool since newappl should cover that and you may need you may need PASSLIB. See the ISPF services book to see how those will affect your application. |
|
| Back to top |
|
|
|
|
|
FAQ
Search
Quick Manuals
Register
Profile
Log in to check your private messages
Log in
