SCOUG-HELP Mailing List Archives

<< Previous Message << >> Next Message >>

Date:	Sun, 4 Aug 2002 23:42:34 PST7
From:	"Info2SYNass.NET" <Info@SYNass.NET >
Reply-To:	scoug-help@scoug.com
To:	scoug-help@scoug.com
Subject:	SCOUG-Help: REXX script ... "PARM" & control file

Content Type: text/plain

=====================================================
If you are responding to someone asking for help who
may not be a member of this list, be sure to use the
REPLY TO ALL feature of your email program.
=====================================================

Hi Harry
please excuse me for the inconvenience I cause with
my "Swiss-German-English" wording ;-(

> OK! Sorry, but I'm a little slow with the wording here, so you
will have
> to explain it a little better. I don't understand the words:
"but use
> PARMS for standard settings i.e. Drive, ..."
>
> What are PARMS?

PARM or PARMS is my substitute of paramaters ;-)

From Steven I got 2 better interpretations:

1) make the script more generic
2) easily editable control file

These 2 aspects are also very important in my thinkings !

Your script is adjusted to a specific system environment (C to G)
and needs multiple adjustments if you add another partition(s) !!

Your present menu, with 9 partitions, exceeds the display ...
... and this brought me to the idea of PARM but Steven used a
better expression: the easily editable control file ;-))

My easily editable control or CFG file may contain these data
as my preset my environment:

%Drive=C
%Drive=D
%Drive=E
%Drive=F
%Drive=G
%Drive=H
(%Drive=J)
%Drive=I
%Drive=K
%Drive=L
%Drive=$

%Source=H:
%Target=J:\OS2\BA2\DATs
%DAT_ID=Drive_H

These parameters describe my environment with drives C: to $
and H: my data partition to be backed up to J:\OS2\BA\DATs
with the preset DAT-ID: Drive_H ...
... and manually I would add one of the following numbers i.e:

Drive_H1, where the number identifies the day:

1=MON
2=TUE
3=WED
4=THU
5=FRI
6=SAT
7=SUN

Once again my reply is a very long to explantation and I
hope you can understand better now ;-)

I can and do not interfear how you write your script ...
... you are the expert ;-))

Once again thanks a lot !

Regards, svobi

PS:
I am already thinking of something more !
How do I build in this backup process into a command
to do it before the final system shutdown in the evening !?

hmotin@attglobal.net on 04.08.2002 23.09.38
Please respond to scoug-help@scoug.com
To: scoug-help@scoug.com
cc:
Subject: SCOUG-Help: Re: Your REXX script ...

OK! Sorry, but I'm a little slow with the wording here, so you
will have
to explain it a little better. I don't understand the words: "but
use
PARMS for standard settings i.e. Drive, ..."

What are PARMS?

My intention in my new version was to use the SYSDRIVEMAP()
function to
automatically get a listing of all the drives, or partitions, on
your
system. Then, using this information, the script would construct a
temporary ASCII file, which is in fact a new REXX procedure. It
would
construct it, using the LINEOUT or STREAM functions. The script
would
call this new REXX procedure and temporarily hand over control to
it.
The
temporary procedure would present you with a listing of your
partitions
and ask you to select one for backing it up, or to type in the
desired
backup path (source). You would select the desired partition, or
type in
a desired backup path. Then the original script would again take
over
and proceed with that information.

By the way, I would weed out from the SYSDRIVEMAP() result any
partition
that is not FAT, HPFS or JSF. This means that CD drives would not
be
included, even if they are CD-R or CD-RW drives. SYSDRIVEMAP()
already
does not include floppy drives. Therefore, the final outcome
would be a
listing of only the local and network hard drive partitions.

In the same fashion, the script would construct another temporary
REXX
file and temporarily turn over control to that REXX procedure.
Here you
would be selecting a partition as the target for receiving your
backup
file, or you would type in a path you desired.

In the end the script would erase both temporary REXX files.

OK!

Steven, I agree that I can automate the size checking logic. But
I think
that will have to wait until round two.

Is the above proposed way of handling the different partitions on
different systems acceptable to all? I need an answer from
everyone.

HCM
__________________________________________________________________
____________

Steven Levine wrote:
>
> =====================================================
> If you are responding to someone asking for help who
> may not be a member of this list, be sure to use the
> REPLY TO ALL feature of your email program.
> =====================================================
>
> In <1028498966-0-Info@SYNass.NET>, on 08/04/02
> at 08:09 AM, "Info2SYNass.NET" said:
>
> >... just do the same as now but use PARMS for standard
settings i.e.
> >Drives, Souces & Target !
>
> That's one option. Some sort of control file would be better.
Your
> environment variable method could work, but is somewhat clumsy.
The
> reason for a control file rather than command line arguments is
that a
> long command lines are hard to read and hard to maintain and
the command
> line is easy to overflow. That said, just defining the
defaults at the
> start of the script along with instructions how to edit the
site specific
> values would work too.
>
> I would expect the backup settings to change slowly over time,
so an
> easily edited control file seems to be a good solution.
>
> >sensitive part of the script but I must adjust environment
> >settings accordingly
> >to my system and my needs once and only if my system
environments changes
> >;-)
>
> Harry could have made the script somewhat more generic by using:
>
> SysDriveMap('C:", 'L')
>
> to locate the drives and by using a stem to store the backup
settings for
> each drive.
>
> >The rest of your script works like now ;-)
>
> Another thing I would attempt to do is automate the avaiable
size logic
> somewhat. This could be done by reading the log for the
previous backup
> and extracting the uncompressed sizes. This can be used to
calculate an
> average compression ratio. This along with the remaining space
in the
> container and the backup size from SysDriveInfo() should be a
pretty good
> estimator.
>
> Steven
>
> --
>
------------------------------------------------------------------
---
> "Steven Levine" MR2/ICE 2.31a #10183
Warp4/FP15/14.085_W4
> www.scoug.com irc.webbnet.org #scoug (Wed 7pm PST)
>
------------------------------------------------------------------
---
>
> =====================================================
>
> To unsubscribe from this list, send an email message
> to "steward@scoug.com". In the body of the message,
> put the command "unsubscribe scoug-help".
>
> For problems, contact the list owner at
> "rollin@scoug.com".
>
> =====================================================

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".

For problems, contact the list owner at
"rollin@scoug.com".

=====================================================

************************************************************
*** >>> Say NO to HTML in Mail and News <<< ***
*** ++++++++++++++++++++++++++++++++++++++++++++++++ ***
*** >>> AGAINST TERROR +++ AGAINST WAR <<< ***
************************************************************

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".

For problems, contact the list owner at
"rollin@scoug.com".

=====================================================

Return to [ 04 | August | 2002 ]

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.