I didn't say the dataset "DCTR.SGIMTENU' had been destroyed. I said the
SMPEINIT "ALLOC" to SMPTABL with REUSE probably destroyed (lost) the
effect of the allocation (The DD statement) for SMPTABL in your logon
proc, which appears to associate SMPTABL with 'DCTR'SGIMTENU'. If you
were lucky, the SMPE dialog may have seen something amiss before it
actually tried to store anything in SMPTABL while it was allocated to
'DCTR.SGIMTENU".
Since both 'SYS1.SGIMTENU' and 'DCTR.SGIMTENU' are in your ISPTLIB
concatenation, and SMPEINIT is also attempting to allocate the DCTR
version to SMPTABL, I am guessing the DCTR version was a previous group
or installation SMPE table library, even though it lacks the normal
naming conventions for such usage. If you are now for some reason
trying to use a personal SMPE table library in its place, leaving the
DCTR.SGIMTENU in your ISPTLIB concatenation may cause the SMPE dialog
confusion and problems.
If DCTR.SGIMTENU is just intended to have some installation customized
versions of SYS1.SGIMTENU (its name actually suggests that usage), then
it's all right to keep it in ISPTLIB, but in that case it should never
be associated with SMPTABL, and doing so may have introduced some
"garbage" members.
Joel C. Ewing
On 10/05/2013 10:50 AM, saurabh khandelwal wrote:
> Hello Joel,
> Initially I also thought same but not sure how can I confirm
> that this dataset been destroyed.
>
> Data Set Name . . . : DCTR.SGIMTENU
>
> General Data Current Allocation
> Volume serial . . . : SYS051 Allocated cylinders : 14
> Device type . . . . : 3390 Allocated extents . : 1
> Organization . . . : PO Maximum dir. blocks : 2
> Record format . . . : FB
> Record length . . . : 80
> Block size . . . . : 27920 Current Utilization
> 1st extent cylinders: 14 Used cylinders . . : 3
> Secondary cylinders : 1 Used extents . . . : 1
> Used dir. blocks . : 2
> Number of members . : 41
>
> Dates
> Creation date . . . : 1995/10/06
> Referenced date . . : 2013/10/05
> Expiration date . . : ***None***
>
> I am able open this dataset as well. Please suggest.
>
> Regards
> Saurabh
>
>
>
> On Sat, Oct 5, 2013 at 9:14 PM, Joel C. Ewing <[email protected]> wrote:
>
>> "ALLOC F(SMPTABL) DA('DCTR.SGIMTENU') SHR REUSE" ???
>> Sure looks like that may destroy your intended Logon proc SMPTABL
>> allocation.
>> Joel C. Ewing
>>
>> 10/05/2013 10:07 AM, saurabh khandelwal wrote:
>>> 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
>>>>
>>>
>>>
>>>
>>
>>
>> --
>> Joel C. Ewing, Bentonville, AR [email protected]
>>
>> ----------------------------------------------------------------------
>> For IBM-MAIN subscribe / signoff / archive access instructions,
>> send email to [email protected] with the message: INFO IBM-MAIN
>>
>
>
>
--
Joel C. Ewing, Bentonville, AR [email protected]
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
