I'm pretty sure SMP/E ISPF dialogs reads tables from the ISPTLIB DD
concatenation and stores updated tables using the SMPTABL DD, so your
SMP/E table library must be in both places, should be the only PDS/PDSE
library allocated under SMPTABL, and there shouldn't be any other
library preceding it in the ISPTLIB concatenation that contains members
that conflict with the table naming conventions of the SMP/E dialog.
If you are trying to use a unique SMP/E table library for each user of
SMP/E (which is totally unnecessary) or for distinct groups of SMP/E
users, you must insure that their ISPF environment includes only their
SMPTABL dataset in SMPTABL and ISPTLIB allocations and no references to
SMPTABL libraries associated with other users or groups.
Also, it used to be the case that only one instance of the SMP/E dialog
was allowed within a single TSO/ISPF session - a 2nd concurrent
invocation in split screen was not allowed and would produce a failure
message..
Joel C. Ewing
On 10/05/2013 07:59 AM, Lizette Koehler 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
