On 5 November 2010 21:58, John McKown wrote:
> I really wonder how hard this would be. But I don't know everywhere the
> TSO id is stored. In the few places that I have found, it seems that the
> ID field is defined as CL7, but there always seems to be a FL1 field
> next to it to store the length
I have forgotten the answer to this question long ago and I am not coming up
with any answer to my question to myself.I will pose it to the group and see if
anyone on here knows the answer.I am trying to remember how IBM handles it if
there is an error (or poorly written or whatever error) happe
I am coming late into this thread and did not see the original post.So I will
pipe up and then let others comment. Back in MVT days UADS (technically it
still is) UADS was a PDS and the member name in UADS was limited to 8
characters. In UADS there was a variable length section(s) in each sectio
Scott Barry pisze:
If a tape dataset name is 17 characters or longer (and the last 17
characters do not change), I believe that it can be renamed, using a DEFINE
NVSAM command (with DEVTYPE, VOLUMES and optionally FSEQN), along with the
requisite DELETE '' NOSCRATCH command. At least with CA-1,
On Sat, 2010-11-06 at 18:26 -0500, Paul Gilmartin wrote:
> On Sat, 6 Nov 2010 16:58:47 -0500, John McKown wrote:
> >
> >I think of a REXX stem variable the same way that I do an Perl hash. Or
> >more like a value associated with a "key" where the key is an arbitrary
> >value. And a stem.var1.var2 i
At 09:53 -0500 on 11/06/2010, Scott Barry wrote about Re: IDCAMS
ALTER and GDGs - From A(0) to B(+1) - Relative G:
If a tape dataset name is 17 characters or longer (and the last 17
characters do not change), I believe that it can be renamed, using a DEFINE
NVSAM command (with DEVTYPE, VOLUMES
On 11/6/2010 12:17 PM, Paul Gilmartin wrote:
On Sat, 6 Nov 2010 14:27:26 -0400, J R wrote:
Good point. However, update-in-place really only *need* be done during the
user's session to record profile changes, etc.
Extending the member should only be necessary when the ACCOUNT command is
addi
On Sat, 6 Nov 2010 16:58:47 -0500, John McKown wrote:
>
>I think of a REXX stem variable the same way that I do an Perl hash. Or
>more like a value associated with a "key" where the key is an arbitrary
>value. And a stem.var1.var2 is like a hash of a hash in Perl.
>
If I understand what you mean by
On Sat, 2010-11-06 at 16:04 -0500, Joel C. Ewing wrote:
> I believe that REXX only directly supports one of those two mechanisms,
> namely the symbol table lookup and not true indexed arrays. Although
> one may use in a REXX program "symbol.ix", where ix in that particular
> program is always a
I believe that REXX only directly supports one of those two mechanisms,
namely the symbol table lookup and not true indexed arrays. Although
one may use in a REXX program "symbol.ix", where ix in that particular
program is always a positive numeric integer, I would think this only
gives the il
Elaborating on Sam's response below, users of TSM for z/OS users may well be
lamenting IBM's decision and continue to maintain a strong belief in the
strengths of the mainframe as a backup server by being able to exploit
z/OS's strengths of job scheduling, tape management and system security for
t
I can't believe only 4 licenses for TSM. I'll check to see of there is
something new coming out.
New guy on Tivoli team
--Original Message--
From: Edward Jaffe
Sender: IBM Mainframe Discussion List
To: IBM-MAIN@bama.ua.edu
ReplyTo: IBM Mainframe Discussion List
Subject: Re: Tivoli Storag
In my previous post
. . . have names like counter
should have been
. . . have names like &counter
John Gilmore Ashland, MA 01721-1817 USA
--
For IBM-MAIN subscribe / signoff / arch
On Sat, 6 Nov 2010 14:27:26 -0400, J R wrote:
>Good point. However, update-in-place really only *need* be done during the
>user's session to record profile changes, etc.
>
>Extending the member should only be necessary when the ACCOUNT command is
>adding segments, in which case it shoul be op
Joel Ewing wrote:
| This technique in effect maps any number of dimensions to a single dimension.
and there is an important functional sense in which his statement is correct;
but 1) it confounds two very different mechanisms, 2) it is not a scheme
specific to REXX, and 3) these two mechanism
No. I have no problem with TSO EDIT.
> Date: Sat, 6 Nov 2010 14:23:01 -0400
> From: ibm...@woodsway.com
> Subject: Re: Why are TSO IDs limited to 7 characters
> To: IBM-MAIN@bama.ua.edu
>
> On Friday 05 November 2010 16:46, Shmuel Metz (Seymour J.) wrote:
> > In ,
> > on 11/05/2010
> >
> > a
Good point. However, update-in-place really only *need* be done during the
user's session to record profile changes, etc.
Extending the member should only be necessary when the ACCOUNT command is
adding segments, in which case it shoul be opened for output and recreate the
entire member.
On Friday 05 November 2010 16:46, Shmuel Metz (Seymour J.) wrote:
> In ,
> on 11/05/2010
>
>at 09:46 AM, "Roach, Dennis (N-GHG)" said:
>
> >Try the TSO EDIT command from ready some time.
>
> I have.
>
> >Make you like vi.
>
> No.
Yes.
-
Note: This ISN'T tape we're talking about. (I'm sorry I mentioned it in
passing.)
Thanks for all the replies!
Martin Packer,
Mainframe Performance Consultant, zChampion
Worldwide Banking Center of Excellence, IBM
+44-7802-245-584
email: martin_pac...@uk.ibm.com
Twitter / Facebook IDs: MartinP
I changed the subject from the How Log For SMF to Switch
to answer the question posed in that thread
with regard to MXG and it's handling of compressed SMF
records from CICS and (new in V10) DB2:
For sites executing on z/OS, MXG 28.07 provides
the ASM code in member EXITCICS to create a SAS
"Infi
I've just uploaded a new version of PDOS/390 here:
http://sourceforge.net/projects/pdos/files/pdos/pdos-stage67.zip/download
This beta is far better than previous betas, and is
actually good enough to allow GCC to self-compile
under it.
Obviously there's still a lot lacking, but that is
at least
On Sat, 6 Nov 2010 11:06:09 -0400, J R wrote:
>I'm not sure I buy this highly speculative explanation.
>
>There's a big difference between not allowing multiple blocks per member and
>not considering second blocks to be necessary. Furthermore, to "solve" the
>problem by introducing multiple m
On Sat, 6 Nov 2010 08:33:02 -0500, Joel C. Ewing wrote:
>
>Since the stem index is an arbitrary variable value, whenever I have
>needed a table lookup dependent on multiple variable values I have
>usually been able to use a construct like
>
>table. = 'some default value'
>...
>index = dsname "#" vo
With the nature of the last eight characters of a GDS name, the likelihood of
it not changing between FILE1 and FILE2 is very low. If the GDS is on tape,
renaming is not an option.
> Date: Sat, 6 Nov 2010 09:53:53 -0500
> From: sba...@sbbworks.com
> Subject: Re: IDCAMS ALTER and GDGs - From
I'm not sure I buy this highly speculative explanation.
There's a big difference between not allowing multiple blocks per member and
not considering second blocks to be necessary. Furthermore, to "solve" the
problem by introducing multiple members per userid, rather than multiple blocks
per
If a tape dataset name is 17 characters or longer (and the last 17
characters do not change), I believe that it can be renamed, using a DEFINE
NVSAM command (with DEVTYPE, VOLUMES and optionally FSEQN), along with the
requisite DELETE '' NOSCRATCH command. At least with CA-1, there are
TMC update
If IBM cannot or will not support z/OS in this roll there are good third
party software vendors who do like Innovation.
This will preserve your investment in z/OS and maintain the z/OS
qualities of service and economies of scale you have today.
http://www.fdr.com/products/upstream/index.cfm
http
edja...@phoenixsoftware.com (Edward Jaffe) writes:
> I guess we're one of the other four. TSM for z/OS works great for
> us. It's hooked into our mainframe-based "cron" facilities, uses large
> DASD EAVs, uses the same tapes and drives that HSM uses--which get
> moved by RMM to the same off-site lo
---
I used 2741 with TSO on SVS.
Line mode only.
ISPF did not exist. Its predecessor (SPF/PDF) required 3270.
All working from TSO READY.
Try the TSO EDIT command from ready some time. Make you like vi.
I am quite convinced TSO was from a later period, after MVT and with
3270 screens.
In the distant past, I used TSO on 2741 terminals, as well as 2260 "tubes"
Ric
--
This is a curiosity question sparked by another thread.
The limitation of 7 characters for TSO IDs has caused us extra work in the
past (we use IDs of 3-8 characters across the institution, but the mainframe
can't use the institu
On 11/05/2010 07:24 PM, Gibney, Dave wrote:
-Original Message-
From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On
Behalf Of Phil Smith
Sent: Friday, November 05, 2010 5:09 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: Rexx question - Dynamic generation of variables?
"Ste
On 11/5/2010 5:38 AM, Jim Marshall wrote:
Question - 1:
"SO" I would like to know who are the other four people who had a similar idea
about using TSM for z/OS, to be the data backup place in order to leverage all
the good things z/OS has to offer.
I guess we're one of the other four. TSM for
And then there were those of us "fortunate" enough to have also
experienced the Fujitsu/FACOM equivalents.
One significant contributor to this list has even admitted appreciating
the opportunity.
No accounting for taste ...
Shane ...
On Sat, 6 Nov 2010 02:13:23 -0400
"Robert A. Rosenberg" wrote
34 matches
Mail list logo
