[hercules-390]

['INVERNIZZI, ALBERTO' [e-mail] [hercules-390]]

Hello to everybody
I have destroyed accidentally the member of jes2 starting in proclib on Hercules emulator 3.05 because after the application of a patch that requires the enlargement of the region of jes I have put it in the row of the proc instead of the row of the exec (of the jes).
What I have done after the disaster on the hercules was:

With the utility dasdcat of hercules list the sys1.proclib(jes2) to see where was the error in the jcl.
With the utility dasdpdsu of Hercules download all the files of the sys1.proclib in a directory on the Hercules server with a suffix of .mac (as from the manual of hercules about utility dasdpdsu)
Then I have edited with the vi utility of unix/linux the file jes2.mac and I have corrected the error.

Now for me it arrives the most difficult thing because I don’t understand with what utility of hercules i can put on hercules the correct member of pds (Sys1.proclib(jes2)).
Can I do it with some utility of Hercules?
Thank you very much for helping me


Important Note: This e-mail may contain trade secrets or privileged, undisclosed or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation.

[Mike Schwab [e-mail] [hercules-390]]

Since you can't start your normal system, IPL the MVS3.7 starter system. I
think PDS can undelete the member, or restore from installation volume
(SMP?), or type in the needed member.

On Fri, Dec 22, 2017 at 12:37 PM, 'INVERNIZZI, ALBERTO'

Post by 'INVERNIZZI, ALBERTO' ***@atos.net [hercules-390]
Hello to everybody
I have destroyed accidentally the member of jes2 starting in proclib on
Hercules emulator 3.05 because after the application of a patch that
requires the enlargement of the region of jes I have put it in the row of
the proc instead of the row of the exec (of the jes).
With the utility dasdcat of hercules list the sys1.proclib(jes2) to
see where was the error in the jcl.
With the utility dasdpdsu of Hercules download all the files of the
sys1.proclib in a directory on the Hercules server with a suffix of .mac
(as from the manual of hercules about utility dasdpdsu)
Then I have edited with the vi utility of unix/linux the file jes2.mac
and I have corrected the error.
Now for me it arrives the most difficult thing because I don’t understand
with what utility of hercules i can put on hercules the correct member of
pds (Sys1.proclib(jes2)).
Can I do it with some utility of Hercules?
Thank you very much for helping me
Important Note: This e-mail may contain trade secrets or privileged,
undisclosed or otherwise confidential information. If you have received
this e-mail in error, you are hereby notified that any review, copying or
distribution of it is strictly prohibited. Please inform us immediately and
destroy the original transmittal. Thank you for your cooperation.

[Steve Smith [e-mail] [hercules-390]]

Post by 'INVERNIZZI, ALBERTO' ***@atos.net [hercules-390]
Hello to everybody
I have destroyed accidentally the member of jes2 starting in proclib on
Hercules emulator 3.05 because after the application of a patch that
requires the enlargement of the region of jes I have put it in the row of
the proc instead of the row of the exec (of the jes).
��� With the utility dasdcat of hercules list the sys1.proclib(jes2) to see
where was the error in the jcl.
��� With the utility dasdpdsu of Hercules download all the files of the
sys1.proclib in a directory on the Hercules server with a suffix of .mac (as
from the manual of hercules about utility dasdpdsu)
��� Then I have edited with the vi utility of unix/linux the file jes2.mac
and I have corrected the error.
Now for me it arrives the most difficult thing� because I don�t understand
with what utility of hercules i can put on hercules the correct member of
pds (Sys1.proclib(jes2)).
Can I do it with some utility of Hercules?
Thank you very much for helping me

For a small change like this, you could use ZZSA. This is a small utility
that is available with TK4- and TK3. It is a stand-alone baer metal set of
utilities for edit/browse etc of a disk. See zzsa.conf and the docs from TK4-

Steve



------------------------------------

------------------------------------

Community email addresses:
Post message: hercules-***@yahoogroups.com
Subscribe: hercules-390-***@yahoogroups.com
Unsubscribe: hercules-390-***@yahoogroups.com
List owner: hercules-390-***@yahoogroups.com

Files and archives at:
http://groups.yahoo.com/group/hercules-390

Get the latest version of Hercules from:
http://www.hercules-390.org


------------------------------------

Yahoo Groups Links

<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/hercules-390/

<*> Your email settings:
Individual Email | Traditional

<*> To change settings online go to:
http://groups.yahoo.com/group/hercules-390/join
(Yahoo! ID required)

<*> To change settings via email:
hercules-390-***@yahoogroups.com
hercules-390-***@yahoogroups.com

<*> To unsubscribe from this group, send an email to:
hercules-390-***@yahoogroups.com

<*> Your use of Yahoo Groups is subject to:
https://info.yahoo.com/legal/us/yahoo/utos/terms/

[[e-mail] [hercules-390]]

Hi Alberto,

if you use a ADCD set, you should also have a standalone disk. You can ipl also if you destroyed your regular zos. If you ipl from this disk, you could repair your member with regular ISPF and reipl your regular system.


Erwin

['\'Fish\' (David B. Trout)' [e-mail] [hercules-390]]

Post by 'INVERNIZZI, ALBERTO' ***@atos.net [hercules-390]
Hello to everybody
I have destroyed accidentally the member of jes2
starting in proclib on Hercules emulator 3.05 ...

<snip>

For a small change like this, you could use ZZSA. This
is a small utility that is available with TK4- and TK3.
It is a stand-alone bare metal set of utilities for
edit/browse etc of a disk. See zzsa.conf and the docs
from TK4-

This.

This is the correct answer.

Use ZZSA. It is quick and easy and was designed *specifically* for this type of situation.

You can find ZZSA here:


http://www.cbttape.org/~jjaeger/zzsa.html


PROCEDURE:

1. Download the zip file containing the 3 binary images (http://www.cbttape..org/~jjaeger/zzsa.zip). Unzip to a directory of your choosing.

2. Create a temporary Hercules configuration file:

# zzsa.conf

CPUMODEL 3090
CPUSERIAL 000001
MAINSIZE 1024
ARCHMODE z/Arch
CNSLPORT 3270

000C 3505 zzsadir/zzsacard.bin autopad eof
001F 3270 *
0999 3390 hercdir/my_damaged_dasd.999

3. Start hercules using that configuration file:

hercules -f zzsa.conf > zzsa.log

4. IPL from the card reader:

ipl 00c

5. Enter the password: "zzsecret"

6. Use option 2 ("Edit dataset or member") to fix your problem(s).

7. Use option X to exit when you are done.


Hope that helps!

['\'Fish\' (David B. Trout)' [e-mail] [hercules-390]]

Fish wrote:

[...]

Post by '\'Fish\' (David B. Trout)' ***@gmail.com [hercules-390]
hercules -f zzsa.conf > zzsa.log
ipl 00c

(oops!) I forgot a step between 3 and 4:

After starting Hercules (step 3) you of course need to attach a 3270 terminal!

THEN you can IPL (step 4) and proceed as described.

['\'Fish\' (David B. Trout)' [e-mail] [hercules-390]]

Fish wrote:

[...]

Post by '\'Fish\' (David B. Trout)' ***@gmail.com [hercules-390]
5. Enter the password: "zzsecret"
6. Use option 2 ("Edit dataset or member") to fix your problem(s).

(Ack!) I forget yet ANOTHER step between steps 5 and 6! (sigh!)

You must FIRST use option 0 ("List all devices") before you can use any of the other options (except 'X' of course).

[Robert Prins [e-mail] [hercules-390]]

That's why anyone with any sense makes backups:

My backup bat file, I (obviously) run with shadow disks:

ren shadow(-4) shadow-tmp
ren shadow(-3) shadow(-4)
ren shadow(-2) shadow(-3)
ren shadow(-1) shadow(-2)
ren shadow-tmp shadow(-1)
copy shadow\*.* shadow(-1)

Faithfully run after every shut-down of Hercules.

Robert

On 22 December 2017 at 18:37, 'INVERNIZZI, ALBERTO'

Post by 'INVERNIZZI, ALBERTO' ***@atos.net [hercules-390]
Hello to everybody
I have destroyed accidentally the member of jes2 starting in proclib on

Hercules emulator 3.05 because after the application of a patch that
requires the enlargement of the region of jes I have put it in the row of
the proc instead of the row of the exec (of the jes).

Post by 'INVERNIZZI, ALBERTO' ***@atos.net [hercules-390]
With the utility dasdcat of hercules list the sys1.proclib(jes2) to

see where was the error in the jcl.

Post by 'INVERNIZZI, ALBERTO' ***@atos.net [hercules-390]
With the utility dasdpdsu of Hercules download all the files of the

sys1.proclib in a directory on the Hercules server with a suffix of .mac
(as from the manual of hercules about utility dasdpdsu)

Post by 'INVERNIZZI, ALBERTO' ***@atos.net [hercules-390]
Then I have edited with the vi utility of unix/linux the file

jes2.mac and I have corrected the error.

Post by 'INVERNIZZI, ALBERTO' ***@atos.net [hercules-390]
Now for me it arrives the most difficult thing because I don’t

understand with what utility of hercules i can put on hercules the correct
member of pds (Sys1.proclib(jes2)).

Post by 'INVERNIZZI, ALBERTO' ***@atos.net [hercules-390]
Can I do it with some utility of Hercules?
Thank you very much for helping me
Important Note: This e-mail may contain trade secrets or privileged,

undisclosed or otherwise confidential information. If you have received
this e-mail in error, you are hereby notified that any review, copying or
distribution of it is strictly prohibited. Please inform us immediately and
destroy the original transmittal. Thank you for your cooperation.
--
Robert AH Prins
***@gmail.com
Some programming @ <https://prino.neocities.org/zOS/zOS%20Tools.html>

[mario [e-mail] [hercules-390]]

Robert,

Not only does it make sense to do backups, but .....................

1) One should backup to more than one type of media, i.e. removal HD,
CD, DVD, flash drive, etc.., etc. on a periodic basis

2) Even MORE important: Make sure that you can restore from backup files BEFORE
a disaster strikes!

3) Most important: Don't forget rules 1 & 2!


I know because I've seen countless people get bit on pc's mid-range boxes, and even on "big iron" ..........


My two cents!

['\'Fish\' (David B. Trout)' [e-mail] [hercules-390]]

(SUBJECT CHANGE)

Post by mario ***@yahoo.com [hercules-390]

Post by Robert Prins ***@gmail.com [hercules-390]
ren shadow(-4) shadow-tmp
ren shadow(-3) shadow(-4)
ren shadow(-2) shadow(-3)
ren shadow(-1) shadow(-2)
ren shadow-tmp shadow(-1)
copy shadow\*.* shadow(-1)
Faithfully run after every shut-down of Hercules.

Good advice.

I too strongly recommend using shadow files.

You keep your base dasd set to read-only(*) and let all writes/updates go to your shadow file. Then to "backup" your Hercules dasd all you need to copy are the shadow files (once the base dasd images are saved at least once to somewhere safe of course). Since shadow files as typically quite small, backing up your Hercules dasd usually only takes a few SECONDS and only consumes, at most, a few megabytes of disk space.

I've been using them for YEARS and YEARS.

------
(*) So Hercules never writes to it so there's less chance of it becoming corrupted, allowing them to be your fail-safe emergency starting point if any of your shadow files somehow become corrupted.

Post by mario ***@yahoo.com [hercules-390]
Robert,
Not only does it make sense to do backups, but .....................
1) One should backup to more than one type of media, i.e. removal HD,
CD, DVD, flash drive, etc.., etc. on a periodic basis
2) Even MORE important: Make sure that you can restore from backup
files BEFORE
a disaster strikes!
3) Most important: Don't forget rules 1 & 2!
I know because I've seen countless people get bit on pc's mid-range
boxes, and even on "big iron" ..........
My two cents!

ALSO very good advice.

I would personally add however, one more bit of advice: periodically recycle copies of your current backup drives to SOMEWHERE ELSE FAR AWAY ("off site") in case of fire or flood or explosion or earthquake, or some other type of unexpected disaster.

Either make a clone/copy of your drive and keep it in your desk at work, or copy it to the cloud, etc.

If using the cloud I would also strongly recommend encrypting everything before uploading it, and then making DAMN sure you have MULTIPLE backups of your Password Safe where you keep all of your passwords! (so you can DECRYPT your cloud data should you ever be unfortunate enough to suffer a disaster).

Being slightly paranoid regarding losing data is usually a good thing. You can never be too careful. Remember: it's not a matter of IF a hard drive will fail. It's only a matter of WHEN.

ALL hard drives eventually fail, so be prepared.

You can go to the store and buy a new hard drive or a new computer but you can't go to the store and buy all of your personal data that you lost (family pictures, legal documents, etc).

Be wise: make a backup of your system EVERY SINGLE DAY.

To not do so is foolish and you WILL eventually regret it someday.

Here endeth the lesson.

[Joe Monk [e-mail] [hercules-390]]

Why would you need a backup.bat file?

The Hercules console command SF+ creates a new set of shadow files... Just
do it before you IPL and you're golden.

Joe

On Fri, Dec 22, 2017 at 7:14 PM, ''Fish' (David B. Trout)'

Post by '\'Fish\' (David B. Trout)' ***@gmail.com [hercules-390]
(SUBJECT CHANGE)

Post by mario ***@yahoo.com [hercules-390]

ren shadow(-4) shadow-tmp
ren shadow(-3) shadow(-4)
ren shadow(-2) shadow(-3)
ren shadow(-1) shadow(-2)
ren shadow-tmp shadow(-1)
copy shadow\*.* shadow(-1)
Faithfully run after every shut-down of Hercules.

Good advice.
I too strongly recommend using shadow files.
You keep your base dasd set to read-only(*) and let all writes/updates go
to your shadow file. Then to "backup" your Hercules dasd all you need to
copy are the shadow files (once the base dasd images are saved at least
once to somewhere safe of course). Since shadow files as typically quite
small, backing up your Hercules dasd usually only takes a few SECONDS and
only consumes, at most, a few megabytes of disk space.
I've been using them for YEARS and YEARS.
------
(*) So Hercules never writes to it so there's less chance of it becoming
corrupted, allowing them to be your fail-safe emergency starting point if
any of your shadow files somehow become corrupted.

Post by mario ***@yahoo.com [hercules-390]
Robert,
Not only does it make sense to do backups, but .....................
1) One should backup to more than one type of media, i.e. removal HD,
CD, DVD, flash drive, etc.., etc. on a periodic basis
2) Even MORE important: Make sure that you can restore from backup
files BEFORE
a disaster strikes!
3) Most important: Don't forget rules 1 & 2!
I know because I've seen countless people get bit on pc's mid-range
boxes, and even on "big iron" ..........
My two cents!

ALSO very good advice.
I would personally add however, one more bit of advice: periodically
recycle copies of your current backup drives to SOMEWHERE ELSE FAR AWAY
("off site") in case of fire or flood or explosion or earthquake, or some
other type of unexpected disaster.
Either make a clone/copy of your drive and keep it in your desk at work,
or copy it to the cloud, etc.
If using the cloud I would also strongly recommend encrypting everything
before uploading it, and then making DAMN sure you have MULTIPLE backups of
your Password Safe where you keep all of your passwords! (so you can
DECRYPT your cloud data should you ever be unfortunate enough to suffer a
disaster).
Being slightly paranoid regarding losing data is usually a good thing. You
can never be too careful. Remember: it's not a matter of IF a hard drive
will fail. It's only a matter of WHEN.
ALL hard drives eventually fail, so be prepared.
You can go to the store and buy a new hard drive or a new computer but you
can't go to the store and buy all of your personal data that you lost
(family pictures, legal documents, etc).
Be wise: make a backup of your system EVERY SINGLE DAY.
To not do so is foolish and you WILL eventually regret it someday.
Here endeth the lesson.
--
"Fish" (David B. Trout)
Software Development Laboratories
http://www.softdevlabs.com

['\'Fish\' (David B. Trout)' [e-mail] [hercules-390]]

Fish wrote:

[...]

Post by '\'Fish\' (David B. Trout)' ***@gmail.com [hercules-390]
Be wise: make a backup of your system EVERY SINGLE DAY.

Another quick addendum:

Maintain a HISTORY of backups too so you can retrieve valuable data that isn't *currently* on your system but WAS on your system several weeks or months ago. That is to say, don't simply backup your current system over top of your current backup, etc.

Keep making NEW system backups *without* deleting any of your *previous* system backups in case you some day discover you're missing an important file or folder that you accidentally deleted days or weeks or months ago. If you keep a HISTORY of backups you can always go back to one of your old backups and retrieve the lost file or folder.

Using RAID is *not* a replacement for doing full system backups every day!

I'll shut up now. :)

[Gregg Levine [e-mail] [hercules-390]]

Hello!
While Fish was busily typing via his fins, several ideas came to me.
For example despite the fact that I run the original VM/370rel6 system
here, I've got several different tarballs created, and they differ
only by date. And whatever I manage with that creation, before moving
on, I'll do the same again.

The motto, keep backing things up, seems to run here.
---
The fact still remains, what is that big hairy whatsit in the rain, in
Fish's driveway and leaning against a rusty Chevy Nova?
-----
Gregg C Levine ***@gmail.com
"This signature fought the Time Wars, time and again."


On Fri, Dec 22, 2017 at 8:29 PM, ''Fish' (David B. Trout)'

Post by '\'Fish\' (David B. Trout)' ***@gmail.com [hercules-390]
[...]

Post by '\'Fish\' (David B. Trout)' ***@gmail.com [hercules-390]
Be wise: make a backup of your system EVERY SINGLE DAY.

Maintain a HISTORY of backups too so you can retrieve valuable data that isn't *currently* on your system but WAS on your system several weeks or months ago. That is to say, don't simply backup your current system over top of your current backup, etc.
Keep making NEW system backups *without* deleting any of your *previous* system backups in case you some day discover you're missing an important file or folder that you accidentally deleted days or weeks or months ago. If you keep a HISTORY of backups you can always go back to one of your old backups and retrieve the lost file or folder.
Using RAID is *not* a replacement for doing full system backups every day!
I'll shut up now. :)
--
"Fish" (David B. Trout)
Software Development Laboratories
http://www.softdevlabs.com

[Ivan Warren [e-mail] [hercules-390]]

Le 12/23/2017 à 2:29 AM, ''Fish' (David B. Trout)'

Post by '\'Fish\' (David B. Trout)' ***@gmail.com [hercules-390]
Using RAID is *not* a replacement for doing full system backups every day!
I'll shut up now. :)

I can only fully agree.

I personally find that 'git[1]' can be used as a fully capable
"incremental forever" backup solution !

- It only stores the delta between each backup version
- It only keeps what you want (with a bit of handling)
- Is a powerful disk->disk backup (you still need a way to externalize -
but rsync[2] or a storage cloud solution can do the trick)
- Getting to any time/date can be achieved by a simple 'git checkout' !

--Ivan

[1] My mail servers are backed up this way (PS : Fish, I still backup
some of your old mail archives you have on my server :P )
[2] for a personal computing solution, rsync to USB keys and an external
rotation of USB keys (one out, one with you, one connected in the
computer) - but you need an external location.



[Non-text portions of this message have been removed]

[Ivan Warren [e-mail] [hercules-390]]

Le 12/23/2017 à 1:34 PM, Mark Morgan Lloyd

I don't much care for Git, and I'm afraid that I'm inclined to dig my
heels in whenever somebody come along and claims that it cures all
ailments including laryngitis and piles... I'm sure you recognise the
type :-)

I certainly wouldn't claim that git is a Panacea ! But it can serve
(within certain constraints) more needs than its original intended purpose.

The use of "git" (as an incremental backup solution) here is probably
not the originally intended use (as a source version control mechanism).

However, it does appear to be possible to use it to very good effect as
a community/groupware shared resource, for example KiCad has a facility
(I think via a plugin) to automatically download updated component
footprints from the relevant area of a Git repository.

That's the point - I'm using git for *other* purposes than just that
(because the technology it employs can be easily hijacked !)

For example, I have my mailbox on my server (a dovecot mdbox structure)
which I backup every hour - The current contents is about 2Gig - and I
have hourly history (which I can retrieve for each of those backups) for
every hour for the last 6 month - and it's only 2.8Gig in size. (Meaning
I could retrieve the status of my mailbox as it was on the 8th of
October 2017 at 3am should I wish). Because I use some cloud storage
service - I only backup the differential every hour (but it can be
consolidated to save some space - without losing a single bit).

The same could be done with DASD base files and shadow files (although
it would require some cooperation with hercules to sync/freeze the
shadow at some point - but it's not overly complicated : create a new
shadow file (ie create a snapshot), backup all files except the new one
(which is in flux), consolidate the newly created shadow file and the
previous one once the backup is done).

--Ivan



[Non-text portions of this message have been removed]