Mainframe, MVS and zOS Discussion

You could try one of the turnkey Hercules offerings - Anuj posted a link the other day. I got it up and running with almost no problems. The problems arise when you get logged on - no ISPF and, so far, I find what documentation there is for the options available is a bit lacking. Example, I created ...

After a few tests...starting with a new GDG base so no generations yet: step 1: create +1 creates G0001V00 step 2: create +2 creates G0002V00 step 3: delete +2 (now left with #1) step 4: create +2 creates G0002V00 DSLIST shows #1 and #2 Second test: step 1: create +1 creates G0003V00 step 2: create ...

I do not understand what the real problem is as it has not been explained as to why 10 more bytes are required. Assuming the requirement is to amend an existing dataset then the simplest way is to change the program that creates the dataset to declare the dataset as being 90 bytes record length, cha...

Looks like my backspace key has migrated (again)!

Oz - Australian English, Austria - IBM so internal language is English, Belgium - Air Traffic - Pan-european so internal language is English, Ireland - Irish English, Enh=gland - Punjabi (joking - English English). I have a smattering of French, German, Greek, Thai...

I live down on the pig farm! Actually I am a Scot, living in England and working wherever which has include England, Australia, Austria, Belgium and currently (for the 3rd time) Ireland.

Google

It means that the data element starts on a double-word boundary which Robert has described above - basically an address that is evenly divisible by 8 or is 0 (hence the 0, 8, 16 etc in robert's post)

If your dataset is empty then simply delete it and redefine it. If it has data in it that needs to be of the new record length then you will have to write something - possibly a sort - to read the old data, reformat it to the new format and write it out to a new dataset with the new dataset attribut...