Ray Mullins wrote:
I remember earlier 3090 models did have 3370's for the service processor;
this was 1987-1988 or thereabouts.
Our IBM FE said that the designers used it because someone said to use up
all the 3370s that weren't selling. Not that I believed that 100%...
by 1988, 3370 were com
I agree with Ted, how Damn hard is it? I can't remember when or why
the one time I got bit, but I run a job with copymod for all loadmodule
copys. And I get a record I can refer to later if I need it.
I don't think I'd approve of ISPF copying for load or PDSE even if it
used copymod under the c
The 3370s supported by DOS/VS and VM, were FBA disks with a 512-byte
sector size.
My memory on DOS/VS is vague, but I believe they had VTOCs that were
similar to CKD VTOCs but structured to fit in 512 sectors and to
describe datasets in sectors. To do something similar in z/OS would
require
> -Original Message-
> From: IBM Mainframe Discussion List
> [mailto:[EMAIL PROTECTED] On Behalf Of Ed Finnell
> Sent: Saturday 03 March 2007 09:53
> To: IBM-MAIN@BAMA.UA.EDU
> Subject: Re: FBA rant
>
>
> In a message dated 3/3/2007 10:59:23 A.M. Central Standard Time,
> [EMAIL PROTEC
[EMAIL PROTECTED] wrote:
Guess the next iteration was the 3380 D/E's and 3880-11's and 13's. Think
the 11's made it to production but the 13's never did. Soon after(mid 80's)I
left for greener pastures and walked into Amdahl hell with the 6880 ESP...and
STK SSDs. Whew, I lived to tell about!
In a message dated 3/3/2007 2:31:29 P.M. Central Standard Time,
[EMAIL PROTECTED] writes:
on every byte transferred. "data streaming" relaxed that requirement ...
doubling both the
typical max. data transfer from 1.5mbyte to 3mbyte and also max channel
distance from 200ft to
400ft. "spee
Anne & Lynn Wheeler wrote:
the consolidation of some of the HONE vm370 datacenters provided
opportunity for development of vm370 "single-system-image" support with
front-end load-balancing and availability infrastructure directing
branch office logon to specific processor. The mechanism utilize
[EMAIL PROTECTED] wrote:
Yeah, we had both on a 4361. I don't remember all the details since it was
under the purview of the VM group. Think they went out of their way to avoid
3330's and 3350's. One of the very sharp MVSer's dad worked at Santa Teresa and
we usually got excellent support fo
Anne & Lynn Wheeler wrote:
that should be 3310 & 3370s ... 3330, 3340, 3350 were all ckd. 3340s
were removable packs that were totally enclosed including the arm access
mechanism. There was 3375 which basically was (hardware) emulation of
CKD on 3370 device.
I worked at a service bureau in th
I'm assuming the Server Pac install (z/os 1.7) used copymod to populate
the linklib originally. There has been updates and deletes from
maintenance being applied. I did compress the library before my copymod
test. Copymod must be cleaning up some things in the process. As I said
earlier, we
On Mar 3, 2007, at 9:57 AM, Ed Finnell wrote:
In a message dated 3/3/2007 12:04:52 A.M. Central Standard Time,
[EMAIL PROTECTED] writes:
There were FBA Drives under DOS/VS. They were transparent to the
user/programs. If it could be done then, why not now?
Err semi transparent.. the dos jcl
In a message dated 3/3/2007 10:59:23 A.M. Central Standard Time,
[EMAIL PROTECTED] writes:
I don't remember for sure whether FBA (3370) was used by the 3090 service
processor or not.
The 3090 service processor started out being a highly customized version of
vm370 release 6 running on 433
In a message dated 3/3/2007 10:44:04 A.M. Central Standard Time,
[EMAIL PROTECTED] writes:
that should be 3310 & 3370s ... 3330, 3340, 3350 were all ckd. 3340s were
removable packs that were totally enclosed including the arm access mechanism.
There was 3375 which basically was (hardware)
Our SMF offload process uses Batch REXX to examine first record of SMF
dataset for a time stamp and uses that as part of a unique dataset name
for the offload tape, rather than using GDG's. The offload SYSOUT is
analyzed and saved in a DASD dataset with a name containing both the
start and end
>I'm assuming with z/OS 1.7 the serverpac uses COPYMOD to populate the load
>libraries.
I still don't understand the issue.
Nor, what people are expecting to gain by using COPY vs COPYMOD.
I've used COPYMOD since it became available for all load libraries. Even on
like to like.
What's the prob
>It's often worth stopping for a bit of Googling!
Possibly, but when you've been working with the terminology for 26 years, would
you automatically stop and think that it has been appropriated for something
else?
IBM does this all the time.
-
Too busy driving to stop for gas!
--
I know, T1 have to be configured in 3490 mode to work with VSM, I
also know T1 can work with z/OS when configured in 3592 mode
(defined as 3590-1).
Q: T1 in 3490 mode, defined in IODF as 3490. Does it work ?
--
Radoslaw Skorupka
Lodz, Poland
--
BRE Bank SA
ul. Senatorska 18
00-9
I'm assuming with z/OS 1.7 the serverpac uses COPYMOD to populate the load
libraries. Modules may have been added and deleted in the linklib due to
maintenance etc. I did compress the library (it was a non-production
linkib) before the copy. It appears copymod is doing some cleanup
somewhere
[EMAIL PROTECTED] wrote:
Not enough caffeine...should be VM/XA
vm370 (and CMS) shipped with 3310 and 3370 support when the devices first
became available in the 70s.
3310/piccolo was used by the 3081 service process (running custom programming on microprocessor) ...
including "paging device"
Speaking of overloading names, search the Utilities Manual:
Title: z/OS V1R7.0 DFSMSdfp Utilities
Document Number: SC26-7414-03
... for COPYMOD. But I'm interested in IEBCOPY's, not the other.
I understand that COPYMOD invokes Binder to to the processing.
But the RM seems to avoid any m
[EMAIL PROTECTED] wrote:
Likewise for VM/ESA 3340's, 3370's.
that should be 3310 & 3370s ... 3330, 3340, 3350 were all ckd. 3340s were
removable packs that were totally enclosed including the arm access mechanism.
There was 3375 which basically was (hardware) emulation of CKD on 3370 device.
Ted
I hope you saw Sam's post where he went into some detail.
It's often worth stopping for a bit of Googling!
Chris Mason
- Original Message -
From: "Ted MacNEIL" <[EMAIL PROTECTED]>
Newsgroups: bit.listserv.ibm-main
To:
Sent: Saturday, March 03, 2007 2:47 PM
Subject: Re: JES2 MTTR
In a message dated 3/3/2007 9:58:40 A.M. Central Standard Time,
[EMAIL PROTECTED] writes:
Likewise for VM/ESA 3340's, 3370's.
>>
Not enough caffeine...should be VM/XA
** AOL now offers free
email to everyone. Find out more about what's free from AOL at
In a message dated 3/3/2007 12:04:52 A.M. Central Standard Time,
[EMAIL PROTECTED] writes:
There were FBA Drives under DOS/VS. They were transparent to the
user/programs. If it could be done then, why not now?
>>
Likewise for VM/ESA 3340's, 3370's.
**
I believe IBM's use of MTTR for the address of a record on disk goes back to
OS360 and HASP. Not exactly new.
""Ted MacNEIL"" <[EMAIL PROTECTED]> wrote in message
news:<[EMAIL PROTECTED]
0.bisx.prod.on.blackberry>...
> >JES2 SPOOL addressing uses 4 byte MTTR where
> >M is SPOOL extent number
> >T
In a recent note, George Dranes said:
> Date: Sat, 3 Mar 2007 07:39:25 -0600
>
> Thanks for the info. Fortunately, I'm copying between 3390 devices only
> so IEBCOPY without copymod should be fine. I did try some tests, for
> example I used copymod to copy my SYS1.LINKLIB and noticed th
>JES2 SPOOL addressing uses 4 byte MTTR where
>M is SPOOL extent number
>TT is track address (up to 64K)
>R is record number
Why does IBM always do that?
Why do they continue to confuse us by appropriating other anacronyms and
re-using them?
I remember when an electonics engineer was in an IMS
>Unfortunately Ted didn't take sufficient account of the qualification in your
>Subject line.
I know of no other meaning for MTTR.
I have been involved in availability and other service levels for 26 years.
If there is another meaning, please enlighten me.
I did state that my version of MTTR di
JES2 SPOOL addressing uses 4 byte MTTR where
M is SPOOL extent number
TT is track address (up to 64K)
R is record number
This is referenced in a number of JES2 documents but you most recently
see it discussed related to large sequential data set support for JES2
SPOOL.
http://publib.boulder.i
Thanks for the info. Fortunately, I'm copying between 3390 devices only
so IEBCOPY without copymod should be fine. I did try some tests, for
example I used copymod to copy my SYS1.LINKLIB and noticed the space
utilization decreased. The linklib had been installed from a server pac
with a blk
Abdullah
I Googled for "JES2 MTTR" and got 106 "hits". One of them, the 4th, "JES2
z/OS 1.7 Migration Considerations", a PowerPoint presentation with notes,
looked possibly useful for you. See page 6.
I leave you to check through the rest.
Unfortunately Ted didn't take sufficient account of
Seems to me like a simpler bit of magic than that which makes PDSEs seem to
have 256-byte directory blocks.
For all of the LE programs, no problem.
For all of the assembler programs doing vanilla GETs and PUTs, no problem.
If you're manipulating BBCCHHRs, well, you're on your own. Similar to
pro
Are you sure? I don't believe BPS became TOS. I think TOS was DOS stripped
of DASD support and with a tape SYSRES.
BPS was not really an operating system, as I recall. It was a bunch of I/O
routines that could be linked with a user program such that the application
programmer did not have to write
>I need explanation of MTTR or if there is document that explains MTTR.
Mean Time to Recover(y) or Repair.
The average duration of an outage.
Not just applicable to JES2 (or even IT).
-
Too busy driving to stop for gas!
--
F
There was an interesting post from John Eells (March 24, 2006;
item 1614 in March 2006's archive) in reply to a thread with the
subject "3380-3390 Conversion - DISAPPOINTMENT".
(Wanted to post URL and tinyurl here when I realised that my mail
address would be part of the cgi string thereby renderi
Hello every one
I need explanation of MTTR or if there is document that explains MTTR.
Best Regards
_
Express yourself instantly with MSN Messenger! Download today it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/di
36 matches
Mail list logo
