MVSFORUMS.com

[misi01]

When debugging an IMS online program, we have the option of specifying a file for Commands data set and Preference data set

My very first question. It seems as if you can't use a PDS/member for each file, you have (?) to use a simple sequential file.

I find this so unusual and unexpected that I'm thinking we're doing something wrong rather than that you can't.

Are there any limitations that aren't obvious. For example, a PDS is okay, but not a PDSE. A PDS(E) is okay, but it has to be defined with specific DCB's.

Like I say, we must (?) be doing something wrong.

Here are the contents of my default debug file

[kolusu]

[misi01]

Okay, here is where I am. Remember, this is IDz, and not "standard" DEBUG tool (though I appreciate that a lot of the latter has probably been hooked into IDz).

Starting question here. How do I embed an img (I thought Id embed images instead of writing everything, but I don't know how to)? I appreciate that I click on the Img tag, but what do I then do to include it in the post?

First of all, my attempts with a PDS was based on DCB's organization PO, RECFM F, LRECL 80, BLOCK 80 and data set name type LIBRARY.

When debuging in IDz, I specified (under debugger options):-

Test level Test, Error level ALL, and Prompt level PROMPT.

Commands data set my.pds.ds(member1)
Preference data set my.pds.ds(member2)

I then ran the debug scenario, but the code was never interrupted in any way.

I then changed the following (where both DS point to a sequential file):

Commands data set my.pds.ds.member1
Preference data set my.pds.ds.member2

This time I see the following in the debug console tab

[kolusu]

[misi01]

Fair comment. I'll try again today, but if it suddenly works, that would mean that a PDSE is not supported.
Okay. Here are the new definitions.
Commands/preference datasets are xxxxxx.IDZ.DEBUG.PARMS.PDS(member1) and member2.
DCB's for that file

[kolusu]

misi01,

Did you try issuing the commands

[misi01]

Are you sure we're not talking at x-purposes?

My take on it is as follows. Irrespective of which columns the commands should be in, the basic starting point is:-

- defining the command files as sequential files results in the commands within the files being run and shown in the debug console tab in IDz
- doing exactly the same using a PDS member results in nothing being run and nothing ending up in the console tab

The contents of the files are the same, the only difference I can see is PDS vs sequential.

I'll repeat my original question. When posting to the forum, one of the tag options is IMG. Are we able to post an image to the forum, or is the option a red herring?
_________________
Michael

[kolusu]

[misi01]

So why do i only see those messages when the debug files are sequential, but when they're a PDS, I see nothing at all?
_________________
Michael

[kolusu]

[misi01]

No, I didn't read the reference in your last reply. I'll try looking into that.

But ..... I still don't get the mismatch in behavior when using one alternative with sequential files (and where IDz at least tries to run the commands contained there) and the other where the SAME commands
are contained in PDS members. (I even went so far so as to check whether the PDS members contained nums on and the sequential files didn't or similar - neither had any numbers in pos 73-80)

Note also that in both scenarios, the initial load module is called TFEDA0, and from what I understood of what you wrote, ONE of the two debug command files should have been named as such.
And yet, the sequential file variation stops in TFEDA0.

Just so we're on the same page ... I've used Dbeug Tool under CICS where I had a typical 3270 screen and I specified the load module and the file containing the debug commands I wanted run at the start of the debug session for that particular program. Here is an example of what that file looked like (and that worked fine). Commands started in position 2 (FWIW)

[kolusu]

[misi01]

Quick question. Have you personally used IDz to debug an IMS online program?
_________________
Michael

[kolusu]