IBM Mainframe Forum

Thank you so much for all the inputs you gave. I could get the source PDS name using "PARSE SOURCE" and assign it as the DSN in ISPPLIB.

Thank you so much for all the inputs you gave. I could get the source PDS name using "PARSE SOURCE" and assign it as the DSN in ISPPLIB.

pretty flaky design, to mix in the same PDS execs, panels, ...
but if You are happy

flaky design, to mix in the same PDS execs, panels,

I respectfully disagree, it depends on the application and personal preferences. But that is matter for another topic.

remember, this is a beginner' s forum

but as usual it depends on the complexity of the application and the setup standards

that I can aggree with

enrico-sorichetti wrote:

Thank you so much for all the inputs you gave. I could get the source PDS name using "PARSE SOURCE" and assign it as the DSN in ISPPLIB.

pretty flaky design, to mix in the same PDS execs, panels, ...
but if You are happy

Not flakey, plain shyte. What happens if the end user already has a member with the name of the panel in his or her exec library? What does PARSE SOURCE return for a concatenation?

What does PARSE SOURCE return for a concatenation?

IIRC it returns the ddname
and after having issued a libdef by DDNAME
all the dataset in the SYSPROC/SYSEXEC concatenation
will be searched for a panel to display

I believe that PARSE SOURCE returns (among other things) both the DDNAME and the DSNAME.

IIRC**2
for an implicit call (*) the ddname will be returned
(*) entering the command from a bare tso session or from ispf option 6

for an explicit call (*) the dsname should be returned
(*) exec some.data.set(somethng)

sorry but I do not have the system up to check