Also, check to see if you have anything in your ISPF Allocation that might
be pre-empting your vendor functions.

Use TSO ISRDDN to review your current session allocations.  Also see if you
can identify the REXX/CLIST/Command that is being used.  Then use M
name-of-rexx/clist/command in the COMMAND Line.

There might be a same named member that is getting into the way.

Lizette


> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[email protected]] On
> Behalf Of Lizette Koehler
> Sent: Friday, January 03, 2014 5:50 PM
> To: [email protected]
> Subject: Re: Vendor task failing to populate ISPF.SPFTEMP0.CNTL
> 
> Also,  Does this member have details in it?
> 
> 
> Source Dsname,===>,'SYSP.CW.MLXT930.SLXTSAMP(TRIMAIN)'
> 
> Lizette
> 
> 
> > -----Original Message-----
> > From: IBM Mainframe Discussion List [mailto:[email protected]]
> > On Behalf Of Lizette Koehler
> > Sent: Friday, January 03, 2014 5:47 PM
> > To: [email protected]
> > Subject: Re: Vendor task failing to populate ISPF.SPFTEMP0.CNTL
> >
> > A couple of questions.
> >
> > 1) Any maintenance applied to the vendor product?
> > 2) Any changes to the ISPF environment?
> > 3) When was the last time it was successfully used? Is it the same
> > LPAR
> where you
> > are working from now?
> >
> > I like ISPVCALL for diagnosing the ISPF environment.
> >
> > Type in TSO ISPVCALL, run the application, then TSO ISPVCALL after it
> > completes.
> >
> > You will have a very large file to browse, but should have sufficient
> details for the
> > VENDOR.
> >
> > Lizette
> >
> >
> > > -----Original Message-----
> > > From: IBM Mainframe Discussion List
> > > [mailto:[email protected]] On Behalf Of John Norgauer
> > > Sent: Friday, January 03, 2014 3:46 PM
> > > To: [email protected]
> > > Subject: Vendor task failing to populate ISPF.SPFTEMP0.CNTL
> > >
> > > A vendor software task fails to insert JCL's into my SPFTEMP0.CNTL
> > dataset. I get
> > > the message:
> > >
> > > IKJ56265I THE DATA SET IS EMPTY.
> > >
> > > The vendor says that there is an ISPF problem but I am not sure
> > > about
> > this.
> > >
> > > Anyone have an idea on why this message is occuring?
> > >
> > > Thanks.
> > >
> > >
> > >
> > > John Norgauer
> > > Senior Systems Programmer
> > > Mainframe Technical Support Services University of California Davis
> > > Medical Center
> > > 1651 Alhambra Blvd
> > > Suite 200
> > > Sacramento, Ca 95816
> > > 916-734-0536
> > >
> > >  SYSTEMS PROGRAMMING......  Guilty, until proven innocent !! "    JN
> 2004
> > > ........
> > > "Hardware eventually breaks - Software eventually works"      anon
> > > ........
> > >
> >

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to