I see you have your SMPTABL on both
//SMPTABL DD DISP=SHR,DSN=SAURABH.SMPTABL *SAURABH TBLS
//CIDTABL DD DISP=SHR,DSN=SAURABH.SMPTABL *SAURABH TBLS
What is the purpose of CIDTABL? I am not sure your SMP Table dataset
should be on the CIDTABL DD. What is its purpose?
In some shops they have the user PROFILE dataset on other table library DDs.
Next a LIBDEF can have MUTLIPLE datasets allocated at one time.
So the following excerpt you provided:
ALLOC F(CIDTABL) DA('SAURABH.CIDTABL') SHR REUSE why is this
different from your logon proc?
ISPEXEC LIBDEF ISPMLIB DATASET ID('SYS1.SGIMMENU')
ISPEXEC LIBDEF ISPPLIB DATASET ID('SYS1.SGIMPENU')
ISPEXEC LIBDEF ISPTLIB DATASET ID('SYS1.SGIMTENU')
ISPEXEC SELECT PGM(GIMSTART) PARM(&UOPT) NEWAPPL(GIM) PASSLIB
ISPEXEC LIBDEF ISPMLIB
ISPEXEC LIBDEF ISPPLIB
ISPEXEC LIBDEF ISPTLIB
FREE F(SMPTABL CIDTABL) END
If you are using a REXX to allocate files, then you should probably not have
them physically allocated in your logon proc.
So the question becomes, where do you want to do your allocations? In the
logon proc or a REXX?
I prefer creating rexx allocation routines rather than putting them in the
logon proc.
Lizette
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On
Behalf Of saurabh khandelwal
Sent: Saturday, October 05, 2013 8:08 AM
To: [email protected]
Subject: Re: SMPTABL data set severe error
Hello Lizette,
Thanks for response .Below is my logon proc containing
SMPTABL dataset.
//$SYSMJM EXEC PGM=IKJEFT01,
// DYNAMNBR=99,PARM='%PROFILE'
//STEPLIB DD DISP=SHR,DSN=SAURABH.LOADLIB *SAURABH LOADLIB
// DD DISP=SHR,DSN=SYS1.DGTLLIB *ISMF LOADLIB
// DD DISP=SHR,DSN=SYS1.SCBDHENU *HCD LOADLIB
// DD DISP=SHR,DSN=SYS1.SIOALMOD *OSA/SF LOADLIB
// DD DISP=SHR,DSN=SYS1.MIGLIB *MVS MIGLIB
//SYSHELP DD DISP=SHR,DSN=SYS1.HELP *SYS HELP
// DD DISP=SHR,DSN=SYS1.SISPHELP *ISPF HELP
// DD DISP=SHR,DSN=SYS2.HELP *USER HELP
//SYSPROC DD DISP=SHR,DSN=SAURABH.SYSEXEC *SAURABH EXECS
// DD DISP=SHR,DSN=SKHAND9.CNTL.REXX *USER EXECS
// DD DISP=SHR,DSN=SYS3.ISPF.CLIB *USER EXECS
// DD DISP=SHR,DSN=SYS1.SEZAINST *TCPIP EXECS
// DD DISP=SHR,DSN=$SYS.ISPFCLIB *SYSPROG EXECS
// DD DISP=SHR,DSN=SYS1.DGTCLIB *SMS EXECS
// DD DISP=SHR,DSN=SYS1.SEDGEXE1 *DFSMS/RMM EXECS
// DD DISP=SHR,DSN=SYS1.SCSFCLI0 ICSF EXECS
// DD DISP=SHR,DSN=SYS1.SERBCLS *RMF EXECS
// DD DISP=SHR,DSN=SYS1.SBPXEXEC *OE EXECS
// DD DISP=SHR,DSN=SYS1.SGIMCLS0 *SMP/E EXECS
// DD DISP=SHR,DSN=SYS1.HRFCLST *RACF EXECS
// DD DISP=SHR,DSN=SYS1.SCBDCLST *HCD EXECS
// DD DISP=SHR,DSN=SYS1.SISPCLIB *ISPF EXECS
// DD DISP=SHR,DSN=SYS1.SISPEXEC *ISPF EXECS
// DD DISP=SHR,DSN=SYS1.SBLSCLI0 *IPCS EXECS
//ISPPLIB DD DISP=SHR,DSN=$SYS.ISPFPLIB *SYSPROG PANELS
// DD DISP=SHR,DSN=SYS3.ISPF.PLIB *USER PANELS
// DD DISP=SHR,DSN=SYS1.DGTPLIB *SMS PANELS
// DD DISP=SHR,DSN=SYS1.SEDGPENU *DFSMS/RMM PANELS
// DD DISP=SHR,DSN=SYS1.SGIMPENU *SMP/E PANELS
// DD DISP=SHR,DSN=SYS1.SCSFPNL0 ICSF PANELS
// DD DISP=SHR,DSN=SYS1.SEZAPENU *TCPIP PANELS
// DD DISP=SHR,DSN=SYS1.SERBPENU *RMF PANELS
// DD DISP=SHR,DSN=SYS1.SISPPENU *ISPF PANELS
// DD DISP=SHR,DSN=SYS1.SCBDPENU *HCD PANELS
// DD DISP=SHR,DSN=SYS1.SBPXPENU *OE PANELS
// DD DISP=SHR,DSN=SYS1.SBLSPNL0 *IPCS PANELS
//ISPSLIB DD DISP=SHR,DSN=$SYS.ISPFSLIB *SYSPROG SKELS
// DD DISP=SHR,DSN=SYS3.ISPF.SLIB *USER SKELS
// DD DISP=SHR,DSN=SYS1.DGTSLIB *SMS SKELS
// DD DISP=SHR,DSN=SYS1.SGIMSENU *SMP/E SKELS
// DD DISP=SHR,DSN=SYS1.SCSFSKL0 ICSF SKELS
// DD DISP=SHR,DSN=SYS1.SISPSENU *ISPF SKELS
// DD DISP=SHR,DSN=SYS1.SISPSLIB *ISPF SKELS
// DD DISP=SHR,DSN=SYS1.SBLSKEL0 *IPCS SKELS
//ISPMLIB DD DISP=SHR,DSN=SYS3.ISPF.MLIB *USER MSGS
// DD DISP=SHR,DSN=SYS1.DGTMLIB *SMS MSGS
// DD DISP=SHR,DSN=SYS1.SEDGMENU *DFSMS/RMM MSGS
// DD DISP=SHR,DSN=SYS1.SEZAMENU *TCPIP MSGS
// DD DISP=SHR,DSN=SYS1.SERBMENU *RMF MSGS
// DD DISP=SHR,DSN=SYS1.SGIMMENU *SMP/E MSGS
// DD DISP=SHR,DSN=SYS1.SCSFMSG0 ICSF MSGS
// DD DISP=SHR,DSN=SYS1.SBPXMENU *OE MSGS
// DD DISP=SHR,DSN=SYS1.SISPMENU *ISPF MSGS
// DD DISP=SHR,DSN=SYS1.SCBDMENU *HCD MSGS
// DD DISP=SHR,DSN=SYS1.SBLSMSG0 *IPCS SKELS
//ISPTLIB DD DISP=SHR,DSN=SAURABH.SMPTABL *SAURABH TBLS
// DD DISP=SHR,DSN=DCTR.SGIMTENU *DCTR TBLS
// DD DISP=SHR,DSN=SYS3.ISPF.TLIB *USER TBLS
// DD DISP=SHR,DSN=SYS1.DGTTLIB *SMS TBLS
// DD DISP=SHR,DSN=SYS1.SGIMTENU *SMP/E TBLS
// DD DISP=SHR,DSN=SYS1.SCSFTLIB ICSF TBLS
// DD DISP=SHR,DSN=SYS1.SERBTENU *RMF TBLS
// DD DISP=SHR,DSN=SYS1.SCBDTENU *HCD TBLS
// DD DISP=SHR,DSN=SYS1.SBPXTENU *OE TBLS
// DD DISP=SHR,DSN=SYS1.SISPTENU *ISPF TBLS
// DD DISP=SHR,DSN=SYS1.SBLSTBL0 *IPCS TBLS
//SMPTABL DD DISP=SHR,DSN=SAURABH.SMPTABL *SAURABH TBLS
//CIDTABL DD DISP=SHR,DSN=SAURABH.SMPTABL *SAURABH TBLS
//SYSLBC DD DISP=SHR,DSN=SYS1.BRODCAST *BRODCAST
//SYSUADS DD DISP=SHR,DSN=SYS1.UADS *UADS
//SYSPRINT DD TERM=TS,SYSOUT=Z
//SYSTERM DD TERM=TS,SYSOUT=Z
//SYSOUT DD TERM=TS,SYSOUT=Z
//SYSERR DD TERM=TS,SYSOUT=Z
I dont see any other error in using ISPF panel. Yesterday I just received
HOLDDATA in morning and after couple of hours I was trying to invoke SMPE
panel and was unable to do.
SMPE panel is invoked using below code
&ZSEL = TRANS( TRUNC (&ZCMD,'.')
1,'PANEL(TSOID)'
2,'CMD(%SMPEINIT)'
And code of SMPEINIT command is
BROWSE SYS3.ISPF.CLIB(SMPEINIT) - 01.08 Line 000
Command ===>
********************************* Top of Data **************** PROC 0 UOPT()
CONTROL NOMSG FLUSH END(ENDO) FREE F(SMPTABL CIDTABL) ALLOC F(SMPTABL)
DA('DCTR.SGIMTENU') SHR REUSE
ALLOC F(CIDTABL) DA('SAURABH.CIDTABL') SHR REUSE
ISPEXEC LIBDEF ISPMLIB DATASET ID('SYS1.SGIMMENU') ISPEXEC LIBDEF ISPPLIB
DATASET ID('SYS1.SGIMPENU') ISPEXEC LIBDEF ISPTLIB DATASET
ID('SYS1.SGIMTENU') ISPEXEC SELECT PGM(GIMSTART) PARM(&UOPT) NEWAPPL(GIM)
PASSLIB ISPEXEC LIBDEF ISPMLIB ISPEXEC LIBDEF ISPPLIB ISPEXEC LIBDEF ISPTLIB
FREE F(SMPTABL CIDTABL) END
Please suggest ,if you looking for any more data from my side.
Regards
Saurabh
On Sat, Oct 5, 2013 at 6:29 PM, Lizette Koehler
<[email protected]>wrote:
> Please post your JCL statements where your SMPTABL is coded.
>
> Next, check that ALL of the libraries on the DD statement where your
> SMPTABL is coded are ALL PDS or PDSE datasets.
>
> In ISPF, if there is an error, ISPF will flag the first library in the
> list and not necessarily the library in Error.
>
> Without more detail this is a guess.
>
> For SMP/E usage, I believe that the SMPTABL is in both the ISPTLIB and
> SMPTABL DD statements. If this is correct, please post both DD entries.
>
> So you should show us a listing like the following
>
> //ISPTLIB DD DISP=SHR,DSN=SYS2.ISPTLIB
> // DD DISP=SHR,DSN=ISP.SISPTENU
> // DD DISP=SHR,DSN=GIM.SGIMTENU
> // DD DISP=SHR,DSN=SYS1.SMP.SMPTABL
> // DD DISP=SHR,DSN=SYS1.SEDGTBL1
> // DD DISP=SHR,DSN=SYS1.DGTTLIB
> // DD DISP=SHR,DSN=SYS1.SCBDTENU
> // DD DISP=SHR,DSN=SYS1.SBLSTBL0
> //*
> //SMPTABL DD DISP=SHR,DSN=SYS1.SMP.SMPTABL
>
>
>
> Lizette
>
>
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[email protected]]
> On Behalf Of saurabh khandelwal
> Sent: Friday, October 04, 2013 9:28 PM
> To: [email protected]
> Subject: Fwd: SMPTABL data set severe error
>
> Hello,
> I am getting below error, while invoking SMPE panel.
>
> SMP/E INITIALIZATION ERROR ===>
>
>
>
> **********************************************************************
> ******
> ***
> *
> *
> * The following error was detected while attempting to
> *
> * initialize the SMP/E dialogs. The initialization of
> *
> * these dialogs has not completed.
> *
> *
> *
> *
> *
> *
> *
> *
> *
> * The message has been logged in your ISPF log. You may
> *
> * wish to print your log and give it to the system
> *
> * programmer responsible for maintaining this system.
> *
> *
> *
> * To return to ISPF, enter END .
> *
> *
> *
>
>
> **********************************************************************
> ******
> ***
>
> ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
> *³ SMPTABL data set severe error. Check the space allocations.
> ³*
>
>
> I tried checking my logon proc for SMPTABL user dataset. But I dont
> see any issue with this dataset and its has enough free space .
>
> Data Set Information Command ===>
>
> Data Set Name . . . : SAURABH.SMPTABL
>
> General Data Current Allocation
> Volume serial . . . : STOR50 Allocated tracks . : 20
> Device type . . . . : 3390 Allocated extents . : 1
> Organization . . . : PO Maximum dir. blocks : 20
> Record format . . . : FB
> Record length . . . : 80
> Block size . . . . : 27920 Current Utilization
> 1st extent tracks . : 20 Used tracks . . . . : 1
> Secondary tracks . : 2 Used extents . . . : 1
> Used dir. blocks . : 1
> Number of members . : 7
>
> Dates
> Creation date . . . : 2009/11/14
> Referenced date . . : 2013/10/04
> Expiration date . . :
> ***None***
>
>
> I also tried creating new SMPTABL dataset and replaced LOGONPROC
> entry with new dataset name, still same issue.
>
> I am running z/OS 1.13 system. Please help me to isolate this issue.
>
>
> Thanks & Regards
> Saurabh
>
>
>
> --
> Thanks & Regards
> Saurabh Khandelwal
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions, send
> email to [email protected] with the message: INFO IBM-MAIN
>
--
Thanks & Regards
Saurabh Khandelwal
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email
to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
