MVSFORUMS.com

[semigeezer]

I wouldn't defend reflist... I hate it, but you can use it quickly.
Assuming you have a personal data set list called XYZ:
Assign a PF key to REFACTD XYZ
then in option 2 (edit) type the number of the dataset you want on the command line, press the PF key, and press enter. I haven't timed it, but I'd think it is about 2 seconds or less.

Option 11 (workplace) does this too (enter a number next to a reflist), but I never learned workplace because it just isn't intuitive at all, and the usability is pretty bad.

I've never seen the storage problem you are having, so I don't know where it is coming from. I do know that ISPF has some enormous execs (ISPDTLC for example is 25000 lines and uses lots of stem variables which take lots of storage) and they don't fail with this error. Are you stacking ISPF applications? That could cause you to run out of storage after a few invocations if the underlying application is still there.

[Phantom]

Well, I didn't find REFLIST (REFACTD) that easy. My goal is to reduce the number of Key press. We can assign a function key to "TSO %EZ" and just type in "<dataset number> <member name>" (ex: 1 XXXPROC) in the command line to open the member. Anyway, we can probably discuss more on this in another thread.

[quote]
Are you stacking ISPF applications ?
[/code]
I'm not using any STACK in my program and as I mentioned in my last post, I'm facing this problem in a ISREDIT macro on the first invocation itself. The macro has nearly 1500 lines, but even the first line is not being executed (I verified it using a SAY command in the second line - after the "ISREDIT MACRO" statement). But the macro is running fine when I deleted around 500-600 lines.

From this I understand that, ISPF is trying to store my entire rexx in some temporary buffer and execute line-by-line. The buffer at my shop seems to be so small that if the rexx code gets bigger, ISPF ends in an error.

Not sure how to get around this.

Thanks,
Phantom