IBM Mainframe Forum

Posted: **Tue Nov 27, 2012 12:51 am**

without any useful information the only thing that looks suspicious is

SET &DETTBLDS = &STR(XP.xRCOMMON.TABLOUT)
SET &SECTBLDS = &STR(xP.xRCOMMON.TABLOUT)

note the lower case in the dataset name

and if later the DSNAMEs are used, that could be the origin of the message

Posted: **Tue Nov 27, 2012 11:12 am**

enrico-sorichetti wrote:without any useful information the only thing that looks suspicious is
Select all
SET &DETTBLDS = &STR(XP.xRCOMMON.TABLOUT)
SET &SECTBLDS = &STR(xP.xRCOMMON.TABLOUT)

note the lower case in the dataset name

and if later the DSNAMEs are used, that could be the origin of the message

Its a typo mistake, which occurred while pasting the code from notepad to the fora.

Below given is the output which i got after executing the clist program in option 6 of ISPF facility. Some display its sowing which I put in the program.

Select all

ISPF Command Shell
Enter TSO or Workstation commands below:

===> tso exec 'XT.MNP121.PNL(XSTN009)'

XT.XRTS.TABLOUT1
FSTEST
SYS4.XEVL.TABLOUT
FSTEST
FSTEST
FSTEST
(0) ERROR CODE1!
FSTEST
***

After getting the above display, i press enter and got the below output. I am new to Clist, thats why facing difficulty in showing the exact information. Anyway let me know if further information needed in this context.

Select all

ISPF Dialog Error
Command ===>

******************************************************************************
* ISPN104 *
* *
* Invalid dsname list *
* Data set name(s) incorrectly specified. *
* *
* *
* *
* *
* *
* *
* *
* *
* *
* Enter HELP command for further information regarding this error. *
* Press ENTER key to terminate the dialog. *
* *
* *
* *
* *
******************************************************************************

After the above display I entered Help to get any information.
then i got the screen mentioned below.

Select all

Command ===>

A severe error occurred under dialog:

Application : ISP

Function . : Module XRTS2600

Service . . : LIBDEF

Error message ID: ISPN104

Posted: **Tue Nov 27, 2012 12:11 pm**

use the ISPF option 7 ( DIALOG TEST )
put a break before LIBDEF
and look at the variables

Posted: **Tue Nov 27, 2012 9:42 pm**

I don't see any debuging happening,the DIALOG TEST will trace the CLIST and ISPF dialogs and variables if you know how to set it up correctly, and know where to look and when to look before / after the breakpoint
before you venture off and use the DIALOG TEST, please execute your CLIST with the DEBUG ON
tso exec 'XT.MNP121.PNL(XSTN009)' DEBUG

Posted: **Tue Nov 27, 2012 10:27 pm**

if your calling the clist like exec 'XT.MNP121.PNL(XSTN009)'
you'll need to put the debug option in quotes
TSO exec 'XT.MNP121.PNL(XSTN009)' 'DEBUG'

Posted: **Tue Nov 27, 2012 10:34 pm**

There is no LIBDEF in the source that was provided. Based on your output, the LIBDEF must be in XRTS2600.

Without knowing the source, my wild guess is that this:

Select all

ISPEXEC SELECT PGM(XRTSI010) PARM(XRTSI010&ACFID&SYSPROC)

should have some kind of delimiters between the variables... it seems to pass an userid plus a dataset name, with nowaytodeterminewhereoneendsandtheotherbegins.

Posted: **Tue Nov 27, 2012 11:51 pm**

Peter i tried the command tso exec 'XT.MNP121.PNL(XSTN009)' 'DEBUG', i got the output given below. Out put has shown all the Clist program and then shown the same error ISPN104 at the end.

Select all

tso exec 'XT.MNP121.PNL(XSTN009)' 'DEBUG'
IKJ56700A ENTER VALUE FOR KEYWORD DEBUG -
debug on
IKJ56716I EXTRANEOUS INFORMATION WAS IGNORED: on
ISPEXEC CONTROL ERRORS RETURN
ISPEXEC CONTROL ERRORS RETURN
IF &DEBUG = &STR(DEBUG) THEN
IF DEBUG = DEBUG THEN
CONTROL NOFLUSH LIST SYMLIST CONLIST
CONTROL NOFLUSH LIST SYMLIST CONLIST
ERROR

***

Other command which i tried is TSO EXEC 'XT.MNP121.PNL(XSTN009)''DEBUG'
OUTPUT

Select all

TSO EXEC 'XT.MNP121.PNL(XSTN009)''DEBUG'

IKJ56709I INVALID DATA SET NAME, 'XT.MNP121.PNL(XSTN009)''DEBUG'
IKJ56718A REENTER THIS OPERAND+ -
DEBUG
IKJ56228I DATA SET DTP0107.DEBUG.CLIST NOT IN CATALOG OR CATALOG CAN NOT BE ACC
ESSED
***

@Pedro

Select all

ISPEXEC SELECT PGM(XRTSI010) PARM(XRTSI010&ACFID&SYSPROC)

the libdef is defined in a copybook present in program XRST2600.

Copybook

Select all

05 WS-ISPTLIB PIC X(8) VALUE 'ISPTLIB '.
05 WS-ISPTABL PIC X(8) VALUE 'ISPTABL '.
05 WS-DATASET PIC X(8) VALUE 'DATASET '.
05 WS-DSN-LIST PIC X(200) VALUE SPACES.
05 LIBDEF-DATASET-VAR-NAMES.
10 FILLER PIC X(1) VALUE '('.
10 FILLER PIC X(9) VALUE 'DETTBLDS '.
10 FILLER PIC X(9) VALUE 'SECTBLDS '.
10 FILLER PIC X(1) VALUE ')'.

05 LIBDEF-DATASET-VAR-FIELDS.
10 DETTBLDS PIC X(44) VALUE SPACES.
10 SECTBLDS PIC X(44) VALUE SPACES.

05 LIBDEF-DATASET-VAR-FORMATS.
10 FILLER PIC X(8) VALUE 'CHAR '.
10 FILLER PIC X(8) VALUE 'CHAR '.

05 LIBDEF-DATASET-VAR-LENGTHS COMP.
10 FILLER PIC S9(8) VALUE +44.
10 FILLER PIC S9(8) VALUE +44.

Can anyone tell how to use 7.8 option, so i would be able to put breakpoints.

Posted: **Tue Nov 27, 2012 11:59 pm**

Select all

TSO EXEC 'XT.MNP121.PNL(XSTN009)''DEBUG'

another example of needing a delimiter between objects. You need a blank before 'DEBUG'

Posted: **Wed Nov 28, 2012 12:07 am**

The copybook shows the declares for your cobol program, but we also need to see the call to ISPLINK that performs the LIBDEF.

Can anyone tell how to use 7.8 option, so i would be able to put breakpoints.

1. go to option 7.
2. select option 8 (breakpoints)
3. type LIBDEF in the service column. press Enter. Press F3
4. select option 1 (functions)
6. In the CMD field, type the same thing you did in ISPF option 6 in your previous tests. Press Enter

It will run and show you the LIBDEF statement that it is about to preform. the dataset parameter is malformed.

From the ISPF Services Guide:

If a list of data set names is used, a maximum of 15 data set names
can be specified. Data set names must conform to TSO data set naming
conventions. When several data set names are included in the list,
they must be separated by commas or blanks. For example:

'('USERID1.PANELS1',PANELS2,PANELS3,'PROJECT1.PANELS')'

Posted: **Wed Nov 28, 2012 12:32 am**

Well since the LIBDEFs are in your program I don't think DEBUG or tracing the CLIST will help, DIALOG TEST is the best option.

IBM Mainframe Forum

How to resolve ISPN104 error in ISPF?

Re: How to resolve ISPN104 error in ISPF?

Re: How to resolve ISPN104 error in ISPF?

Re: How to resolve ISPN104 error in ISPF?

Re: How to resolve ISPN104 error in ISPF?

Re: How to resolve ISPN104 error in ISPF?

Re: How to resolve ISPN104 error in ISPF?

Re: How to resolve ISPN104 error in ISPF?

Re: How to resolve ISPN104 error in ISPF?

Re: How to resolve ISPN104 error in ISPF?

Re: How to resolve ISPN104 error in ISPF?