IBM Mainframe Forum

where a macro would still have to step through each system and each command.

why ?

Push it out to any system and edit any dataset you want (that you have access to). It doesn't need to open it at all!

does'n' t the command You are using follow the same road ???

it will not open the dataset in an interactive session, but it will anyway open it to process it

To put things in a very simple way

You are in a room and the only door is closed.
Your task is to go through to the next room but you can not open that door.

Presumably PDSE (dumb name if locally written, by the way) is a program/macro. It seems to benefit from being given a datasetname, which it will open (with all the good stuff that that entails), search each line, and make replacements if necessary, and then close (again with all the good stuff). I am at a loss as to understand how that would be different, other than having to write it, than a macro done from scatch.

Glad it works for you, anyway.

PDSE = PDS Edit maybe?

You give it the dataset name and the from/to values and let'er rip. . .

d

dick scherrer wrote:PDSE = PDS Edit maybe?

You give it the dataset name and the from/to values and let'er rip. . .

d

PDSE is just a different way to organize a PDS. You use the same tools to update a PDSE as you use with a PDS.

Hi Steve,

Suggest the PDSE in the "command" is a bit of some kind of code - probably using an edit macro. It would probably work for both a PDS and a PDSE. . .

Maybe the TS will clarify after learning just what is being executed.

d

Most of this thread is based on an unfortunate choice of wording by the OP. He clearly meant 'without editing it interactively'.