In
a90e503c23f97441b05ee302853b0e6241dc0ac...@fspas01ev010.fspa.myntet.se,
on 12/09/2011
at 11:54 PM, Thomas Berg thomas.b...@swedbank.se said:
Ok, If I rephrase it like: as seen from the initiator before the
actual execution starts ? :)
That works.
--
Shmuel (Seymour J.) Metz,
In 1323571698.77546.yahoomailmob...@web161406.mail.bf1.yahoo.com, on
12/10/2011
at 06:48 PM, Ed Gould ps2...@yahoo.com said:
Someone (John?) suggested that a language (Pearl?)
Presumably Perl.
could do it
Quoting the context would help. See RFC for the standard format of a
quote in Internet
In
capd5f5qmau-nfsclejlgzrdt+joqrcsdh8sd6zfxu5vtavs...@mail.gmail.com,
on 12/10/2011
at 09:57 PM, John Gilmore johnwgilmore0...@gmail.com said:
Shmuel's egregiously out-of-context comments
FSVO out of context unknown to dictionaries.
--
Shmuel (Seymour J.) Metz, SysProg and JOAT
In 3666973419482586.wa.paulgboulderaim@bama.ua.edu, on
12/10/2011
at 10:04 PM, Paul Gilmartin paulgboul...@aim.com said:
I've seen it done
So have I, but what reader of IBM-MAIN claimed that it was desirable?
C, for example, allows as many or as few (even only one) tokens on
each line.
In 6321277460713310.wa.paulgboulderaim@bama.ua.edu, on
12/10/2011
at 09:56 PM, Paul Gilmartin paulgboul...@aim.com said:
Does it merit an RCF?
Yes.
In fact the behavior of aliased DSNs is perhaps even worse.
Yes, and hard to fix. Every approach that I can think of breaks
something.
--
On Sun, 11 Dec 2011 09:16:25 -0500, Shmuel Metz (Seymour J.) wrote:
In 1323571698.77546.yahoomailmob...@web161406.mail.bf1.yahoo.com, on
12/10/2011 at 06:48 PM, Ed Gould said:
Someone (John?) suggested that a language (Pearl?)
Presumably Perl.
could do it
Quoting the context would help.
I don't think there is a way to do this using normal IBM supplied
facilities. At present, we propagate the SYSIKJUA enqueue across our
entire sysplex via the GRSRNL member. When we convert to z/OS 1.12, I am
going to remove this entry from the RNL. This will allows a single TSO
user to logon to
A DISP=OLD zero track SYSUID dataset in a programmer only logon proc?
On Dec 11, 2011 10:34 AM, John McKown joa...@swbell.net wrote:
I don't think there is a way to do this using normal IBM supplied
facilities. At present, we propagate the SYSIKJUA enqueue across our
entire sysplex via the
Good idea slapping head. I do that sometimes to enforce job single
threading because we've set some job classes to allow duplicate job
names in execution. I don't __think__ that I would ever need to allow
some programmers to do concurrent logons while restricting others.
On Sun, 2011-12-11 at
On Sun, 11 Dec 2011 09:44:37 -0600, John McKown joa...@swbell.net wrote:
But, if it is easy, I would like to restrict
who can logon to multiple systems concurrently. Note, I must allow
everyone to logon to all systems for support purposes. But I only want
__concurrent__ logons for a few support
In 0451543888042535.wa.paulgboulderaim@bama.ua.edu, on
12/11/2011
at 10:14 AM, Paul Gilmartin paulgboul...@aim.com said:
PKB.
ROTF,LMAO! I always quote the context, as well as providing an
attribution line.
--
Shmuel (Seymour J.) Metz, SysProg and JOAT
ISO position; see
On Sun, 11 Dec 2011 12:48:46 -0500, Shmuel Metz (Seymour J.) wrote:
on 12/11/2011 at 10:14 AM, Paul Gilmartin said:
PKB.
ROTF,LMAO! I always quote the context,
At least one word. Sometimes several.
as well as providing an attribution line.
Thanks. Sometimes I rely on the quotation
On Sun, 11 Dec 2011 11:28:53 -0600, Mark Zelden wrote:
As long as you don't enable ISPF profile sharing (which I never did because it
is
a kludge anyway - see past posts on ISPF-L), it is simple. ...
It wasn't that we wanted to protect multiple system logon at my client
when I did it back in
On Sun, 11 Dec 2011 09:20:41 -0500, Shmuel Metz (Seymour J.) wrote:
Yes.
OK. Done. Does this say the right stuff? Is the example suitable?:
Hello, MHVRCFs,
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/iea2b6a0/12.47
Title: z/OS V1R12.0 MVS JCL Reference
Document Number:
I suppose that I could test the SYSUID in our TSO logon REXX program
and have a system-unique ISPF profile for those few who will normally
need multisystem logon. I definitely do __NOT__ want it in general. I'll
have programmers and actuaries crawling over my dead body about ISPF
doesn't always
RACF might enforce certain limits if you're accessing RACF resources via
the z/OS LDAP Server. If you're not doing that -- it's not required to do
that -- then no, I don't think there's any 256 character limit.
In 9480536010373504.wa.paulgboulderaim@bama.ua.edu, on
12/11/2011
at 12:00 PM, Paul Gilmartin paulgboul...@aim.com said:
At least one word. Sometimes several.
Always enough to identify the text that I an responding to. If I'm
responding to an entire paragraph then I quote the entire
Sheesh!!-kabob for today
Chris hoelscher
Database Administrator |Technical Services
Humana
123 East Main Street |Louisville, KY 40202
T 502.476.2538
F
choelsc...@humana.com
Humana.com
Keeping CAS and Metavance safe for all HUMANAty
The information transmitted is intended only for the person
On 12/11/2011 9:28 AM, Mark Zelden wrote:
As long as you don't enable ISPF profile sharing (which I never did because it
is a kludge anyway - see past posts on ISPF-L), it is simple.
IBM says profile sharing is needed to run ISPF as a 'classic' interface under
z/OSMF.
--
Edward E Jaffe
19 matches
Mail list logo
