There is the KISS system. When you check out a member, replace it with
a template that says something like in block letters checked out
by Then the member is checked out and they should not change. I
know it requires agreement among the people but it is simple and free.
Brad Taylor
-
From: "Martin, Mike" <[EMAIL PROTECTED]>
We have
several folks who will be updating parmib and proclib. There is a
possibility that we might step on each other's changes.
Is there a way to lock member so that only one person
can be working on a member (or members) while they have the lock
As yo
At 18:12 + on 08/25/2006, Dave Salt wrote about Re: Serializing
changes to parmlib/proclib:
If a proc exists in Lib 2, simply selecting it for edit will 'lock
it' for the length of the edit session
While there is a lock, it is on the wrong RNAME. ISPF uses a QNAME of
SYSEDI
> We are beginning to customize our z./OS 1.7 (to
> replace 1.4). We have several folks who will be
> updating parmib and proclib. There is a possibility
> that we might step on each other's changes. Say,
> for instance, two people are making changes to COMMNDxx.
At my last job, I was the
Mike,
In the days when I managed a number of systems for education purposes, in
fact requiring a set of "PARMLIBs" and "PROCLIBs" for each of the courses,
I had to come up with a system that reminded me what each of my members was
and why it was there.
My solution was to create a member named $$
In a recent note, Chris Mason said:
> Date: Sun, 27 Aug 2006 19:06:36 +0200
>
> I dare say there are some products out there which address this sort of
> problem. I just hope whatever technique they employ isn't too
> overcomplicated ...
>
ISPF/LMF. Keep a "source" copy of each library
From: Paul Gilmartin <[EMAIL PROTECTED]>
Does ISPF LM have a filter that will select all members modified
since a given point in time, for generation of IEBCOPY SELECT
statements?
Copying all members that were modified since a given point in time is
extremely easy to accomplish if SimpList is i
On Aug 27, 2006, at 10:48 AM, David Alcock wrote:
---SNIP-
At my last job, I was the "parmlib nazi". All changes to
parmlib went to me (except off hours to fix a problem). IMHO,
there should only be one person updating the parmlib. You
always w
On Sun, 27 Aug 2006 19:00:26 +, Dave Salt <[EMAIL PROTECTED]> wrote:
>
> Copying all members that were modified since a given point in time is
> extremely easy to accomplish if SimpList is installed. First, SEE would be
>
Promo noted. Likely valuable to those who have the product or are cons
>That tipping point happened about TSO/E Rel 2, when Rexx came to MVS.
ESA/3.1.3oE.
On, or about, 1990.
I was told by my manager to stick with CLIST because REXX was 'too' expensive.
But, as I still believe, productivity is more important.
Also, the only LRECL allowed was 80, under EXECIO, back
- Original Message -
From: "Chris Mason" <[EMAIL PROTECTED]>
Newsgroups: bit.listserv.ibm-main
To:
Sent: Sunday, August 27, 2006 1:06 PM
Subject: Re: Serializing changes to parmlib/proclib
Incidentally, with my large number of course-related libraries - and
non-
In a recent note, Ted MacNEIL said:
> Date: Sun, 27 Aug 2006 22:23:47 +
>
> >That tipping point happened about TSO/E Rel 2, when Rexx came to MVS.
>
> ESA/3.1.3oE.
> On, or about, 1990.
>
Feels about right. I stayed with CMS from inertia for many years
after that. I seldom look ba
>recommended coding Rexx using mixed case for legibility (sorry, Ted and Shane)
I don't know why you are appologising to me.
I always use mixed case in REXX.
But, I don't code:
If Then Do
End
When in doubt.
PANIC!!
In <[EMAIL PROTECTED]>, on
08/25/2006
at 01:31 PM, "Martin, Mike" <[EMAIL PROTECTED]> said:
>I know communicating is key, but we are looking for extra controls so
>we don't step on each other. Any good ideas for serializing access
>to libraries we will be customizing?
LMF or SCLM?
--
In <[EMAIL PROTECTED]>, on 08/27/2006
at 11:28 AM, Paul Gilmartin <[EMAIL PROTECTED]> said:
>ISPF/LMF. Keep a "source" copy of each library and a production
>copy. Make all changes to the source copy with ISPF Edit, which
>serializes updates to members. Periodically (e.g. daily plus on
>spec
In <[EMAIL PROTECTED]>, on 08/27/2006
at 05:17 PM, Paul Gilmartin <[EMAIL PROTECTED]> said:
>Likewise, if an edit session is interrupted with RECOVERY ON, does
>ISPF lock out other editing of the same member until the original
>user recovers?
No.
>As others have noted here, CMS UPDATE provide
In a recent note, "Shmuel Metz (Seymour J.)" said:
> Date: Mon, 28 Aug 2006 08:48:46 -0300
>
> In <[EMAIL PROTECTED]>, on 08/27/2006
>at 05:17 PM, Paul Gilmartin <[EMAIL PROTECTED]> said:
>
> >Likewise, if an edit session is interrupted with RECOVERY ON, does
> >ISPF lock out other e
From: Paul Gilmartin <[EMAIL PROTECTED]>
How does WSA deal with the need to update statistics?
Could you run THE on a workstation with TSO?
WSA has an option that allows member statistics to be generated (or not)
when files are transferred to a mainframe.
I don't know if THE works with TSO, b
In <[EMAIL PROTECTED]>, on 08/28/2006
at 08:52 AM, Paul Gilmartin <[EMAIL PROTECTED]> said:
>CMS ISPF supports using either PDF or XEDIT. (This violates the
>"nice numbers" rule: There are just three nice numbers -- zero, one,
>and "as many as you want".)
It would be no big deal to plug addit
If you don't have time to do it right, when will you have time to do it
over?
I like the 'parmlib nazi' approach. Simple, effective, approved by
auditors.
Make all changes via request rather than direct update. A skilled human
makes a better change control system anyway.
My $0.02
-Orig
20 matches
Mail list logo
