bit.listserv.ibm-main

• Date Index

---

• Defining DASD to OS390 V2R10 System, Robert Pelletier
  • Re: Defining DASD to OS390 V2R10 System, Steve Arnett
  • <Possible follow-ups>
  • Re: Defining DASD to OS390 V2R10 System, Efinnell15
  • RE: Defining DASD to OS390 V2R10 System, Robert Pelletier
  • RE: Defining DASD to OS390 V2R10 System, Robert Pelletier
  • Re: Defining DASD to OS390 V2R10 System, Matthew Stitt
• VTS allocation & performance problems, hanan
• MIGRATION 31 to 64bit IEFUSI and MEMLIMIT, D-Arbigny Pierre-Andre
  • Re: MIGRATION 31 to 64bit IEFUSI and MEMLIMIT, ibm-main
• ISPF REXX : edit or view, François LE MANER
  • Re: ISPF REXX : edit or view, Todd Burch
• ICETOOL & ABEND vs RC, DOMINGUEZ MARTIN, ANGEL LUIS
  • <Possible follow-ups>
  • Re: ICETOOL & ABEND vs RC, Norbert Friemel
  • RE: ICETOOL & ABEND vs RC, DOMINGUEZ MARTIN, ANGEL LUIS
    • Re: ICETOOL & ABEND vs RC, Frank Yaeger
  • Fw: ICETOOL & ABEND vs RC, Frank Yaeger
• AW: DFSORT - "OVERLAY"-Function, Thomas . Ramseier
  • Re: AW: DFSORT - "OVERLAY"-Function, Frank Yaeger
• CA sees $$$$'s on IBM's announcemnts, Ed Gould
• SHARE will be 50, Ed Gould
• Third party Maintenance of z/OS R4 after March 2007, Gee, Norman
  • Re: Third party Maintenance of z/OS R4 after March 2007, R.S.
  • Re: Third party Maintenance of z/OS R4 after March 2007, Bruce Black
  • <Possible follow-ups>
  • Re: Third party Maintenance of z/OS R4 after March 2007, Dave Cartwright
    • Re: Third party Maintenance of z/OS R4 after March 2007, Ed Gould
  • RE: Third party Maintenance of z/OS R4 after March 2007, Gee, Norman
    • Re: Third party Maintenance of z/OS R4 after March 2007, R.S.
  • Re: Third party Maintenance of z/OS R4 after March 2007, Bob Shannon
  • Re: Third party Maintenance of z/OS R4 after March 2007, Ted MacNEIL
• Re: Other DASD Erase programs, David Speake
  • <Possible follow-ups>
  • Re: Other DASD Erase programs, DASDBill2
  • Re: Other DASD Erase programs, David Speake
  • Re: Other DASD Erase programs, DASDBill2
    • Re: Other DASD Erase programs, R.S.
    • Re: Other DASD Erase programs, Walt Farrell
      • Re: Other DASD Erase programs, Bruce Black
  • Re: Other DASD Erase programs, DASDBill2
• EOF at Beginning of PDS, Martin, Mike
  • Re: EOF at Beginning of PDS, Mike Bell
  • RE: EOF at Beginning of PDS, Lizette Koehler
  • Re: EOF at Beginning of PDS, martin_kline
    • Re: EOF at Beginning of PDS, Bernd Oppolzer
• SMPE 3.4, Matthew Stitt
  • Re: SMPE 3.4, David Andrews
  • Re: SMPE 3.4, Edward E. Jaffe
  • <Possible follow-ups>
  • Re: SMPE 3.4, Ted MacNEIL
  • Re: SMPE 3.4, gilmap
  • RE: SMPE 3.4, Pommier, Rex R.
  • Re: SMPE 3.4, Matthew Stitt
    • Server Time Protocol (Was: Re: SMPE 3.4), Edward E. Jaffe
• DFSORT - "OVERLAY"-Function, Thomas . Ramseier
  • Re: DFSORT - "OVERLAY"-Function, Frank Yaeger
• What happened to iSource?, Mark Yuhas
  • RE: What happened to iSource?, Ray Mullins
  • Re: What happened to iSource?, Ed Gould
  • Re: What happened to iSource?, Shmuel Metz , Seymour J.
  • <Possible follow-ups>
  • RE: What happened to iSource?, McKown, John
    • RE: What happened to iSource?, Paul Hanrahan
  • Re: What happened to iSource?, Efinnell15
  • Re: What happened to iSource?, Efinnell15
  • Re: What happened to iSource?, Ted MacNEIL
    • RE: What happened to iSource?, Ray Mullins
  • Re: What happened to iSource?, Ted MacNEIL
    • Re: What happened to iSource?, Shmuel Metz , Seymour J.
  • Re: What happened to iSource?, Efinnell15
  • Re: What happened to iSource?, Mark Yuhas
  • Re: What happened to iSource?, Ted MacNEIL
  • RE: What happened to iSource?, Hylton Tom P
  • Re: What happened to iSource?, Ted MacNEIL
  • RE: What happened to iSource?, Hylton Tom P
• RE: [IBM-MAIN] AW: How to access return codes of previous jobstep s, Beate . Kawelke
• re: 31-bit to 64-bit, john gilmore
  • Re: 31-bit to 64-bit, Jim Mulder
  • <Possible follow-ups>
  • 31-bit to 64-bit, Keith E. Moe
    • Re: 31-bit to 64-bit, Edward E. Jaffe
• New processor., ibm-main
• SMP sloppiness, ibm-main
  • Re: SMP sloppiness, ibm-main
  • Re: SMP sloppiness, Shmuel Metz , Seymour J.
  • Re: SMP sloppiness, Robert Justice
  • <Possible follow-ups>
  • RE: SMP sloppiness, Taddei, Cathy
    • Re: SMP sloppiness, Ed Gould
    • Re: SMP sloppiness, Shmuel Metz , Seymour J.
      • Re: SMP sloppiness, Robert Justice
      • RE: SMP sloppiness, Paul Hanrahan
    • Re: SMP sloppiness, Shmuel Metz , Seymour J.
  • Re: SMP sloppiness, DASDBill2
    • Re: SMP sloppiness, Steve Arnett
      • Re: SMP sloppiness, Shmuel Metz , Seymour J.
      • Re: SMP sloppiness, SArnett
      • Re: SMP sloppiness, Birger Heede
      • Re: SMP sloppiness, SArnett
      • Re: SMP sloppiness, Ed Gould
      • Re: SMP sloppiness, Steve Arnett
    • Re: SMP sloppiness, Shmuel Metz , Seymour J.
      • RE: SMP sloppiness, Paul Hanrahan
  • RE: SMP sloppiness, Hylton Tom P
    • RE: SMP sloppiness, Paul Hanrahan
  • Re: SMP sloppiness, Efinnell15
  • RE: SMP sloppiness, Taddei, Cathy
  • Re: SMP sloppiness, Ted MacNEIL
    • RE: SMP sloppiness, Paul Hanrahan
      • Re: SMP sloppiness, Ed Gould
  • RE: SMP sloppiness, Taddei, Cathy
  • RE: SMP sloppiness, Richards.Bob
  • RE: SMP sloppiness, Taddei, Cathy
    • Re: SMP sloppiness, Robert Justice
      • Re: SMP sloppiness, Shane Ginnane
      • Re: SMP sloppiness, Ed Gould
      • Yet more of the vernacular, Shane Ginnane
    • Re: SMP sloppiness, Ed Gould
  • Re: SMP sloppiness, Paul Gilmartin
    • Re: SMP sloppiness, Robert Justice
  • RE: SMP sloppiness, Chase, John
  • Re: SMP sloppiness, Efinnell15
• How to detect a missing link list library?, Knutson, Sam
  • <Possible follow-ups>
  • RE: How to detect a missing link list library?, Rob Scott
    • Re: How to detect a missing link list library?, ibm-main
    • Re: How to detect a missing link list library?, Shmuel Metz , Seymour J.
  • RE: How to detect a missing link list library?, Rob Scott
  • RE: How to detect a missing link list library?, Gibney, David Allen,Jr
  • Re: How to detect a missing link list library?, Mark Yuhas
  • How to detect a missing link list library?, John_Mattson
  • RE: How to detect a missing link list library?, Knutson, Sam
• Re: NetView message automation, Barbara Nitz
• NetView message automation, Perryman, Brian
  • <Possible follow-ups>
  • RE: NetView message automation, Perryman, Brian
• 54 Processors?, Ed Gould
  • Re: 54 Processors?, Anne & Lynn Wheeler
  • Re: 54 Processors?, Nicolai Tufar
    • Re: 54 Processors?, Cyber
  • Re: 54 Processors?, Martin Packer
  • RE: 54 Processors?, Bruce boda
  • Re: 54 Processors?, SArnett
    • Re: [IBM-MAIN] 54 Processors?, Volker Bandke
  • <Possible follow-ups>
  • Re: 54 Processors?, Ted MacNEIL
    • Re: 54 Processors?, Martin Packer
  • RE: 54 Processors?, Horne, Jim - James S
    • Re: 54 Processors?, ibm-main
      • Re: 54 Processors?, R.S.
      • Re: 54 Processors?, Doug Fuerst
  • Re: 54 Processors?, Ted MacNEIL
  • Re: 54 Processors?, Ted MacNEIL
    • Re: [IBM-MAIN] 54 Processors?, Marian Gasparovic
    • Re: 54 Processors?, Edward E. Jaffe
      • Re: [IBM-MAIN] 54 Processors?, Marian Gasparovic
  • Re: 54 Processors?, Vernooy, C.P. - SPLXM
    • Re: 54 Processors?, Martin Packer
  • Re: 54 Processors?, Ted MacNEIL
    • Re: 54 Processors?, R.S.
  • RE: 54 Processors?, Chase, John
    • Re: 54 Processors?, gerard46
  • Re: 54 Processors?, Doug Fuerst
    • Re: 54 Processors?, Ed Gould
      • Re: 54 Processors?, Doug Fuerst
  • Re: 54 Processors?, Ted MacNEIL
    • Re: 54 Processors?, Martin Packer
    • Re: 54 Processors?, David Andrews
    • Re: 54 Processors?, Jim Mulder
  • Re: 54 Processors?, Efinnell15
  • RE: 54 Processors?, Craddock, Chris
  • RE: 54 Processors?, Craddock, Chris
  • Re: 54 Processors?, rkuebbin
    • Re: 54 Processors?, R.S.
  • Re: 54 Processors?, Ted MacNEIL
  • Re: 54 Processors?, Timothy Sipples
  • Re: 54 Processors?, Ted MacNEIL
  • RE: 54 Processors?, Richards.Bob
  • Re: 54 Processors?, Phil Smith III
  • Re: 54 Processors?, Ted MacNEIL
    • Re: 54 Processors?, Edward E. Jaffe
  • Re: 54 Processors?, Efinnell15
• Macro GTRACE QUERY, Schiradin,Roland HG-Dir itb-db/dc
  • Re: Macro GTRACE QUERY, Edward E. Jaffe
  • <Possible follow-ups>
  • Re: Macro GTRACE QUERY, Peter Relson
    • Re: Macro GTRACE QUERY, Edward E. Jaffe
      • Re: Macro GTRACE QUERY, Edward E. Jaffe
  • RE: Macro GTRACE QUERY, Schiradin,Roland HG-Dir itb-db/dc
• Value of the REXX Compiler/Library on Z/os, Tony
  • Re: Value of the REXX Compiler/Library on Z/os, Tom Longfellow
• RMM Bins, Frank Habura
  • Re: RMM Bins, Thomas Conley
  • <Possible follow-ups>
  • Re: RMM Bins, Mike Wood
• Red Alert is now available, Ken . Porowski
• z9 Announcement, Ted MacNEIL
  • Re: z9 Announcement, Edward E. Jaffe
  • Re: z9 Announcement, Al Sherkow
    • RE: z9 Announcement, Bruce boda
      • Re: z9 Announcement, Edward E. Jaffe
  • <Possible follow-ups>
  • RE: z9 Announcement, Bob Shannon
    • RE: z9 Announcement, Ray Mullins
    • Re: z9 Announcement, Edward E. Jaffe
      • Re: z9 Announcement, mcknight-b-a
      • Re: z9 Announcement, Bill Ogden
  • RE: z9 Announcement, Gibney, David Allen,Jr
  • Re: z9 Announcement, Efinnell15
  • Re: z9 Announcement, Tom Schmidt
  • RE: z9 Announcement, Staller, Allan
    • RE: z9 Announcement, Bruce boda
    • Re: z9 Announcement, Ed Gould
  • Re: z9 Announcement, Timothy Sipples
    • Re: z9 Announcement, R.S.
      • Re: [IBM-MAIN] z9 Announcement, Marian Gasparovic
      • Re: z9 Announcement, ibm-main
      • Re: z9 Announcement, Bruce Black
  • Re: z9 Announcement, Tom Schmidt
  • RE: z9 Announcement, Bob Shannon
• 3390P?, Edward E. Jaffe
  • <Possible follow-ups>
  • RE: 3390P?, Horne, Jim - James S
    • Re: 3390P?, Edward E. Jaffe
  • RE: 3390P?, Horne, Jim - James S
• Good News For a Change, Ed Gould
  • Re: Good News For a Change, Edward E. Jaffe
    • Re: Good News For a Change, Ed Gould
  • <Possible follow-ups>
  • RE: Good News For a Change, Hal Merritt
  • Re: Good News For a Change, Bill Seubert
    • Re: Good News For a Change, Edward E. Jaffe
  • Re: Good News For a Change, Efinnell15
    • Re: Good News For a Change, Eric Chevalier
      • Re: Good News For a Change, Edward E. Jaffe
      • Re: Good News For a Change, Barry Schwarz
      • Re: Good News For a Change, Edward E. Jaffe
      • Re: Good News For a Change, Bruce Black
  • Re: Good News For a Change, Howard Brazee
  • Re: Good News For a Change, Ted MacNEIL
    • Re: Good News For a Change, Robert Justice
  • Re: Good News For a Change, Ted MacNEIL
    • Re: Good News For a Change, Robert Justice
  • RE: Good News For a Change, Richards.Bob
  • RE: Good News For a Change, Richards.Bob
    • Re: Good News For a Change, Robert Justice
  • Re: Good News For a Change, Ted MacNEIL
  • Re: Good News For a Change, Ted MacNEIL
    • Re: Good News For a Change, Shmuel Metz , Seymour J.
  • Re: Good News For a Change, Ted MacNEIL
  • Re: Good News For a Change, Efinnell15
• A newbie question..., mathaias
  • RE: A newbie question..., Wayne Driscoll
  • Re: A newbie question..., R.S.
    • Re: [IBM-MAIN] A newbie question..., Marian Gasparovic
      • Re: A newbie question..., pauls2272
  • Re: A newbie question..., pauls2272
  • <Possible follow-ups>
  • Re: A newbie question..., Efinnell15
    • Re: A newbie question..., mcknight-b-a
    • RE: A newbie question..., Ron and Jenny Hawkins
  • RE: A newbie question..., Hal Merritt
    • Re: A newbie question..., R.S.
  • Re: A newbie question..., mathaias
• JES2 OUTCLASS PROTECTION, Bob H
  • Re: JES2 OUTCLASS PROTECTION, Mark Jacobs
  • Re: JES2 OUTCLASS PROTECTION, R.S.
• Full HFS (cont), mcknight-b-a
• zSeries Red alerts, john . ticic . extern
  • Re: zSeries Red alerts, Mark Jacobs
  • <Possible follow-ups>
  • Re: zSeries Red alerts, Robert Justice
  • RE: zSeries Red alerts, Hal Merritt
• AW: OSA-EXPRESS ICC and IOCDS, Thomas . Ramseier
• OSA-EXPRESS ICC and IOCDS, D-Arbigny Pierre-Andre
• Routine name/srb, mary george
  • Re: Routine name/srb, Todd Burch
    • Re: Routine name/srb, mary george
      • Re: Routine name/srb, Gil Peleg
      • Re: Routine name/srb, mary george
      • Re: Routine name/srb, ibm-main
      • Re: Routine name/srb, Gil Peleg
      • Re: Routine name/srb, mary george
      • Re: Routine name/srb, Edward E. Jaffe
      • Re: Routine name/srb, Steve Comstock
      • Re: Routine name/srb, Todd Burch
      • Re: Routine name/srb, Shmuel Metz , Seymour J.
      • Re: Routine name/srb, Ed Gould
      • Re: 54 Processors, Martin Packer
  • Re: Routine name/srb, Shmuel Metz , Seymour J.
  • <Possible follow-ups>
  • RE: Routine name/srb, McKown, John
  • Re: Routine name/srb, Efinnell15
• Mass PDS member string substitution utility?, Charles Mills
  • RE: Mass PDS member string substitution utility?, Ray Mullins
  • <Possible follow-ups>
  • Re: Mass PDS member string substitution utility?, Efinnell15
    • Re: Mass PDS member string substitution utility?, John P Kalinich
    • Re: Mass PDS member string substitution utility?, David Mierowsky
• Re: CA-1: blocked TMC / Audit?, Barry Schwarz
  • <Possible follow-ups>
  • Re: CA-1: blocked TMC / Audit?, Barry Schwarz
  • RE: CA-1: blocked TMC / Audit?, Bielskie, Stephen
    • Re: CA-1: blocked TMC / Audit?, Barry Schwarz
• 3592 Internal x external label, Carlos Soares da Silva
• SysAdmin Day, kittendorf . craig
• Duplicate sort order, Howard Brazee
  • Re: Duplicate sort order, Frank Yaeger
  • Re: Duplicate sort order, Mike Bell
  • <Possible follow-ups>
  • Re: Duplicate sort order, Howard Brazee
    • Re: Duplicate sort order, Frank Yaeger
      • Re: Duplicate sort order, Howard Brazee
  • Re: Duplicate sort order, Howard Brazee
    • Re: Duplicate sort order, Frank Yaeger
  • RE: Duplicate sort order, Coatney, Bill
  • Re: Duplicate sort order, Howard Brazee
  • Re: Duplicate sort order, Howard Brazee
    • Re: Duplicate sort order, Mike Bell
  • Re: Duplicate sort order, Howard Brazee
  • Re: Duplicate sort order, Howard Brazee
    • Re: Duplicate sort order, Frank Yaeger
      • Re: Duplicate sort order, Howard Brazee
  • Re: Duplicate sort order, Howard Brazee
    • Re: Duplicate sort order, Frank Yaeger
  • Re: Duplicate sort order, Howard Brazee
    • Re: Duplicate sort order, Frank Yaeger
  • Re: Duplicate sort order, Frank Yaeger
  • Fw: Duplicate sort order, Frank Yaeger
• checkpoint cancel and tokens, Paul Schuster
• utility to print PDS list?, Adams, Tracy
  • RE: utility to print PDS list?, Dave Salt
  • RE: utility to print PDS list?, Lizette Koehler
  • Re: utility to print PDS list?, Shmuel Metz , Seymour J.
  • <Possible follow-ups>
  • Re: utility to print PDS list?, Rob Wunderlich
  • utility to print PDS list?, Adams, Tracy
    • RE: utility to print PDS list?, Dave Salt
  • Re: utility to print PDS list?, Rob Wunderlich
• Forcing an ABEND from REXX, dragonmsw
• GDPS CF duplexing, Yi Ming
  • Re: GDPS CF duplexing, john . ticic . extern
  • <Possible follow-ups>
  • Re: GDPS CF duplexing, Ted MacNEIL
    • Re: GDPS CF duplexing, john . ticic . extern
  • Re: GDPS CF duplexing, Ted MacNEIL
  • Re: GDPS CF duplexing, Ron Hawkins
  • Re: GDPS CF duplexing, Ron Hawkins
  • Re: GDPS CF duplexing, Ted MacNEIL
    • Re: GDPS CF duplexing, john . ticic . extern
  • Re: GDPS CF duplexing, Ted MacNEIL
    • RE: GDPS CF duplexing, Ron and Jenny Hawkins
  • Re: GDPS CF duplexing, Yi Ming
    • Re: GDPS CF duplexing, john . ticic . extern
• RE: Align MF & Open backups?, Hal Merritt
• Re: why no PAV? [was: How to free up space from deleted datasets wtihout IXFP], Neil Duffee
• a shared cat question, Tsai Laurence
  • <Possible follow-ups>
  • RE: a shared cat question, McKown, John
  • RE: a shared cat question, Knutson, Sam
    • RE: a shared cat question, Bruce boda
    • Re: a shared cat question, Tsai Laurence
  • Re: a shared cat question, Mark Thomen
• New IBM Mainframes, Eric Bielefeld
• IBMLINK, Alan . C . Field
  • Re: IBMLINK, alan . schwartz
  • Re: IBMLINK, Bruce Black
  • Re: IBMLINK, Edward E. Jaffe
  • <Possible follow-ups>
  • RE: IBMLINK, Finch, Steve
  • RE: IBMLINK, Gibney, David Allen,Jr
  • Re: IBMLINK, Efinnell15
  • Re: IBMLINK, Alan . C . Field
    • Re: IBMLINK, Edward E. Jaffe
  • IBMLINK, Alan . C . Field
    • Re: IBMLINK, Bruce Black
• ILR005E PLPA PAGE DATA SET FULL, kittendorf . craig
  • RE: ILR005E PLPA PAGE DATA SET FULL, Lizette Koehler
  • Re: ILR005E PLPA PAGE DATA SET FULL, Ed Gould
  • Re: ILR005E PLPA PAGE DATA SET FULL, Shmuel Metz , Seymour J.
  • <Possible follow-ups>
  • RE: ILR005E PLPA PAGE DATA SET FULL, Bob Shannon
  • Re: ILR005E PLPA PAGE DATA SET FULL, Vernooy, C.P. - SPLXM
  • RE: ILR005E PLPA PAGE DATA SET FULL, kittendorf . craig
  • Re: ILR005E PLPA PAGE DATA SET FULL, Ted MacNEIL
    • Re: ILR005E PLPA PAGE DATA SET FULL, R.S.
    • Re: ILR005E PLPA PAGE DATA SET FULL, Ed Gould
  • RE: ILR005E PLPA PAGE DATA SET FULL, kittendorf . craig
    • Re: ILR005E PLPA PAGE DATA SET FULL, martin_kline
    • RE: ILR005E PLPA PAGE DATA SET FULL, Wayne Driscoll
  • RE: ILR005E PLPA PAGE DATA SET FULL, Dean Montevago
  • Re: ILR005E PLPA PAGE DATA SET FULL, Rob Wunderlich
  • RE: ILR005E PLPA PAGE DATA SET FULL, kittendorf . craig
    • Re: ILR005E PLPA PAGE DATA SET FULL, martin_kline
  • RE: ILR005E PLPA PAGE DATA SET FULL, kittendorf . craig
  • RE: ILR005E PLPA PAGE DATA SET FULL, kittendorf . craig
  • Re: ILR005E PLPA PAGE DATA SET FULL, Ted MacNEIL
  • Re: ILR005E PLPA PAGE DATA SET FULL, Ted MacNEIL
  • Re: ILR005E PLPA PAGE DATA SET FULL, Ted MacNEIL
  • Re: ILR005E PLPA PAGE DATA SET FULL, Ted MacNEIL
    • RE: ILR005E PLPA PAGE DATA SET FULL, Ron and Jenny Hawkins
      • Re: ILR005E PLPA PAGE DATA SET FULL, Eric Bielefeld
      • RE: ILR005E PLPA PAGE DATA SET FULL, Ron and Jenny Hawkins
      • Re: ILR005E PLPA PAGE DATA SET FULL, Ed Gould
  • Re: ILR005E PLPA PAGE DATA SET FULL, Ted MacNEIL
    • Re: ILR005E PLPA PAGE DATA SET FULL, Steve Samson
      • Re: ILR005E PLPA PAGE DATA SET FULL, Shane Ginnane
      • RE: ILR005E PLPA PAGE DATA SET FULL, Ron and Jenny Hawkins
      • Re: ILR005E PLPA PAGE DATA SET FULL, R.S.
      • Re: ILR005E PLPA PAGE DATA SET FULL, ibm-main
      • Re: ILR005E PLPA PAGE DATA SET FULL, Shmuel Metz , Seymour J.
    • RE: ILR005E PLPA PAGE DATA SET FULL, Ron and Jenny Hawkins
      • Re: ILR005E PLPA PAGE DATA SET FULL, Shmuel Metz , Seymour J.
      • RE: ILR005E PLPA PAGE DATA SET FULL, Ron and Jenny Hawkins
      • Re: ILR005E PLPA PAGE DATA SET FULL, R.S.
      • RE: ILR005E PLPA PAGE DATA SET FULL, Ron and Jenny Hawkins
      • Re: ILR005E PLPA PAGE DATA SET FULL, R.S.
      • Re: ILR005E PLPA PAGE DATA SET FULL, Shmuel Metz , Seymour J.
      • RE: ILR005E PLPA PAGE DATA SET FULL, Ron and Jenny Hawkins
    • Re: ILR005E PLPA PAGE DATA SET FULL, Ed Gould
    • Re: ILR005E PLPA PAGE DATA SET FULL, Ambat Ravi Nair
  • Re: ILR005E PLPA PAGE DATA SET FULL, Ted MacNEIL
  • Re: ILR005E PLPA PAGE DATA SET FULL, Ted MacNEIL
  • Re: ILR005E PLPA PAGE DATA SET FULL, DASDBill2
    • Re: ILR005E PLPA PAGE DATA SET FULL, Greg Dyck
  • Re: ILR005E PLPA PAGE DATA SET FULL, Ron Hawkins
    • Re: ILR005E PLPA PAGE DATA SET FULL, Jim Mulder
  • Re: ILR005E PLPA PAGE DATA SET FULL, DASDBill2
  • Re: ILR005E PLPA PAGE DATA SET FULL, Ted MacNEIL
    • RE: ILR005E PLPA PAGE DATA SET FULL, Ron and Jenny Hawkins
  • Re: ILR005E PLPA PAGE DATA SET FULL, Ted MacNEIL
    • RE: ILR005E PLPA PAGE DATA SET FULL, Ron and Jenny Hawkins
  • Re: ILR005E PLPA PAGE DATA SET FULL, Ted MacNEIL
    • RE: ILR005E PLPA PAGE DATA SET FULL, Ron and Jenny Hawkins
    • RE: ILR005E PLPA PAGE DATA SET FULL, Wayne Driscoll
  • Re: ILR005E PLPA PAGE DATA SET FULL, Vernooy, C.P. - SPLXM
    • RE: ILR005E PLPA PAGE DATA SET FULL, Ron and Jenny Hawkins
  • Re: ILR005E PLPA PAGE DATA SET FULL, Ted MacNEIL
  • RE: ILR005E PLPA PAGE DATA SET FULL, kittendorf . craig
  • RE: ILR005E PLPA PAGE DATA SET FULL, Dean Montevago
    • RE: ILR005E PLPA PAGE DATA SET FULL, Ron and Jenny Hawkins
  • Re: ILR005E PLPA PAGE DATA SET FULL, Ted MacNEIL
  • RE: ILR005E PLPA PAGE DATA SET FULL, Dean Montevago
  • RE: ILR005E PLPA PAGE DATA SET FULL, Dean Montevago
    • RE: ILR005E PLPA PAGE DATA SET FULL, Ron and Jenny Hawkins
  • Re: ILR005E PLPA PAGE DATA SET FULL, DASDBill2
    • RE: ILR005E PLPA PAGE DATA SET FULL, Ron and Jenny Hawkins
      • Re: ILR005E PLPA PAGE DATA SET FULL, Jim Mulder
      • RE: ILR005E PLPA PAGE DATA SET FULL, Ron and Jenny Hawkins
      • Re: ILR005E PLPA PAGE DATA SET FULL, Jim Mulder
      • Re: ILR005E PLPA PAGE DATA SET FULL, Edward E. Jaffe
      • Re: ILR005E PLPA PAGE DATA SET FULL, Greg Dyck
  • RE: ILR005E PLPA PAGE DATA SET FULL, Dean Montevago
  • Re: ILR005E PLPA PAGE DATA SET FULL, Tom Russell
  • Re: ILR005E PLPA PAGE DATA SET FULL, Vernooy, C.P. - SPLXM
  • Re: ILR005E PLPA PAGE DATA SET FULL, Vernooy, C.P. - SPLXM
  • Re: ILR005E PLPA PAGE DATA SET FULL, Vernooy, C.P. - SPLXM
  • Re: ILR005E PLPA PAGE DATA SET FULL, Vernooy, C.P. - SPLXM
  • Re: ILR005E PLPA PAGE DATA SET FULL, DASDBill2
    • RE: ILR005E PLPA PAGE DATA SET FULL, Ron and Jenny Hawkins
  • RE: ILR005E PLPA PAGE DATA SET FULL, Jon Brock
  • Re: ILR005E PLPA PAGE DATA SET FULL, David Alcock
  • Re: ILR005E PLPA PAGE DATA SET FULL, Vernooy, C.P. - SPLXM
  • RE: ILR005E PLPA PAGE DATA SET FULL, Gibney, David Allen,Jr
  • RE: ILR005E PLPA PAGE DATA SET FULL, Craddock, Chris
  • Re: ILR005E PLPA PAGE DATA SET FULL, DASDBill2
• SRDF comands, Mehrdad Rastegar
  • Re: SRDF comands, Bruce Black
• AW: AW: InfoPrint Printway worked buy no real paper received, Sun Biao
• AMBLIST utility, mary george
  • RE: AMBLIST utility, Paul Gillis
  • Re: AMBLIST utility, ibm-main
    • Re: AMBLIST utility, mary george
    • Re: AMBLIST utility, Dave Salt
  • Re: AMBLIST utility, Ed Gould
  • <Possible follow-ups>
  • RE: AMBLIST utility, Stocker, Herman
• AHU FÜSUN ERCAN is out of the office., AHU FUSUN ERCAN
• AW: InfoPrint Printway worked buy no real paper received, Sun Biao
  • <Possible follow-ups>
  • AW: InfoPrint Printway worked buy no real paper received, Sun Biao
  • Re: AW: InfoPrint Printway worked buy no real paper received, Yan Ying
• InfoPrint Printway worked buy no real paper received, Yan Ying
  • <Possible follow-ups>
  • Re: InfoPrint Printway worked buy no real paper received, Efinnell15
  • Re: InfoPrint Printway worked buy no real paper received, Yan Ying
  • Re: InfoPrint Printway worked buy no real paper received, Yan Ying
• (none), Hank Oerlemans
• CICSPLEX support for DTP/APPC, Vijaykumar Niranjan
• 3174's, Ted MacNEIL
  • Re: 3174's, David Andrews
  • RE: 3174's, Bruce boda
  • Re: 3174's, David Wade
    • Re: 3174's, Mike Ross
  • Re: 3174's, news.new
  • Re: 3174's, R.S.
    • Re: 3174's, Edward E. Jaffe
      • Re: 3174's, R.S.
  • <Possible follow-ups>
  • Re: 3174's, Ted MacNEIL
    • Re: 3174's, David Andrews
  • Re: 3174's, Efinnell15
    • Re: 3174's, Edward E. Jaffe
      • Re: 3174's, Richard Peurifoy
      • Re: 3174's, Shmuel Metz , Seymour J.
      • Re: 3174's, Shmuel Metz , Seymour J.
  • RE: 3174's, Bob Shannon
  • Re: 3174's, MikeMaylone
  • RE: 3174's, Pommier, Rex R.
  • RE: 3174's, Pommier, Rex R.
  • Re: 3174's, Michael Ross
  • RE: 3174's, Hal Merritt
• New zOS dump analyzer product, John Mycroft
• Re: Mistaken Identity - TSOID switch, Alan . C . Field
  • <Possible follow-ups>
  • RE: Mistaken Identity - TSOID switch, Chase, John
    • Re: Mistaken Identity - TSOID switch, Jeffrey . Deaver
      • Re: Mistaken Identity - TSOID switch, Edward E. Jaffe
• Thomas Watson Jr. 6th Most Influential Businessman, Timothy Sipples
  • <Possible follow-ups>
  • Re: Thomas Watson Jr. 6th Most Influential Businessman, Efinnell15
• AW: How to access return codes of previous jobsteps, Thomas . Ramseier
  • Re: AW: How to access return codes of previous jobsteps, Edward E. Jaffe
  • <Possible follow-ups>
  • AW: How to access return codes of previous jobsteps, Thomas . Ramseier
  • AW: How to access return codes of previous jobsteps, Thomas . Ramseier
• How to access return codes of previous jobsteps, Beate . Kawelke
  • Betr.: How to access return codes of previous jobsteps, G. van Arnhem
  • <Possible follow-ups>
  • RE: How to access return codes of previous jobsteps, turner, mark
  • RE: How to access return codes of previous jobsteps, Rob Scott
  • RE: How to access return codes of previous jobsteps, DOMINGUEZ MARTIN, ANGEL LUIS
  • Re: How to access return codes of previous jobsteps, Mark Zelden
    • Re: How to access return codes of previous jobsteps, Edward E. Jaffe
  • RE: How to access return codes of previous jobsteps, turner, mark
  • How to access return codes of previous jobsteps, Thomas . Ramseier
    • Re: How to access return codes of previous jobsteps, Edward E. Jaffe
  • RE: How to access return codes of previous jobsteps, Rob Scott
• mf-study, Ted MacNEIL
• copy of uncataloged pds', jieryn
  • <Possible follow-ups>
  • Fw: copy of uncataloged pds', ibm-main
  • Re: copy of uncataloged pds', Arthur T.
• re: New IBM Mainframes Due this week?, Ed Gould
• Re: Supported interface to set/retrieve TCBUSER field NON-authorized?, "Robert A. Rosenberg"
• Bryan Childs/Poughkeepsie/IBM is out of the office., Bryan Childs
• Newbie doubt about Supervised State, De La Fuente Seivane, Victor
  • RE: Newbie doubt about Supervised State, Charles Mills
  • Re: Newbie doubt about Supervised State, Shmuel Metz , Seymour J.
  • Re: Newbie doubt about Supervised State, R.S.
  • <Possible follow-ups>
  • Re: Newbie doubt about Supervised State, DASDBill2
  • RE: Newbie doubt about Supervised State, Hal Merritt
    • RE: Newbie doubt about Supervised State, Paul Hanrahan
  • RE: Newbie doubt about Supervised State, Craddock, Chris
    • RE: Newbie doubt about Supervised State, Wayne Driscoll
  • RE: Newbie doubt about Supervised State, De La Fuente Seivane, Victor
    • Re: Newbie doubt about Supervised State, R.S.
    • Re: Newbie doubt about Supervised State, Walt Farrell
    • Re: Newbie doubt about Supervised State, Shmuel Metz , Seymour J.
  • RE: Newbie doubt about Supervised State, Schiradin,Roland HG-Dir itb-db/dc
  • RE: Newbie doubt about Supervised State, Peter Pfaffner
    • Re: Newbie doubt about Supervised State, David Andrews
      • Re: Newbie doubt about Supervised State, R.S.
  • RE: Newbie doubt about Supervised State, Schiradin,Roland HG-Dir itb-db/dc
  • RE: Newbie doubt about Supervised State, De La Fuente Seivane, Victor
  • RE: Newbie doubt about Supervised State, Chase, John
    • Re: Newbie doubt about Supervised State, R.S.
• segprof, printdude1968@xxxxxxxxx
• SMP/E Upgrade to 3.3 Gone Bad., Howard Rifkind
  • Re: SMP/E Upgrade to 3.3 Gone Bad., Edward E. Jaffe
  • Re: SMP/E Upgrade to 3.3 Gone Bad., Thomas Conley
  • Re: SMP/E Upgrade to 3.3 Gone Bad., Shmuel Metz , Seymour J.
  • <Possible follow-ups>
  • RE: SMP/E Upgrade to 3.3 Gone Bad., Imbriale, Donald , Exchange
  • Re: SMP/E Upgrade to 3.3 Gone Bad., Efinnell15
  • RE: SMP/E Upgrade to 3.3 Gone Bad., Richards.Bob
  • RE: SMP/E Upgrade to 3.3 Gone Bad., McKown, John
  • Re: SMP/E Upgrade to 3.3 Gone Bad., john gilmore
    • Re: SMP/E Upgrade to 3.3 Gone Bad., Howard Rifkind
      • Re: SMP/E Upgrade to 3.3 Gone Bad., Thomas Conley
      • Re: SMP/E Upgrade to 3.3 Gone Bad., ibm-main
      • Re: SMP/E Upgrade to 3.3 Gone Bad., Howard Rifkind
      • Re: SMP/E Upgrade to 3.3 Gone Bad., Edward E. Jaffe
      • Re: SMP/E Upgrade to 3.3 Gone Bad., Shmuel Metz , Seymour J.
      • Re: SMP/E Upgrade to 3.3 Gone Bad., Shmuel Metz , Seymour J.
  • Re: SMP/E Upgrade to 3.3 Gone Bad., Efinnell15
  • Re: SMP/E Upgrade to 3.3 Gone Bad., Efinnell15
• COBOL APAR OQ83744 & Compiler Options, Ben Alford
• TSO Unallocate Dataset., Howard Rifkind
  • Re: TSO Unallocate Dataset., Mark Jacobs
  • Re: TSO Unallocate Dataset., Shmuel Metz , Seymour J.
  • <Possible follow-ups>
  • RE: TSO Unallocate Dataset., Farley, Peter x23353
    • Re: TSO Unallocate Dataset., Howard Rifkind
  • Re: TSO Unallocate Dataset., rkuebbin
  • RE: TSO Unallocate Dataset., Richards.Bob
  • Re: TSO Unallocate Dataset., gilmap
  • Re: TSO Unallocate Dataset., Ted MacNEIL
    • Re: TSO Unallocate Dataset., Howard Rifkind
  • RE: TSO Unallocate Dataset., Taddei, Cathy
    • Basic questions on ibm-main (wasTSO Unallocate Dataset.), Conway, Steven F
    • Re: TSO Unallocate Dataset., Howard Rifkind
  • Re: TSO Unallocate Dataset., Ted MacNEIL
  • RE: TSO Unallocate Dataset., Chiam, Susan Mee-Shia
  • Re: TSO Unallocate Dataset., gilmap
    • Re: TSO Unallocate Dataset./ISRDDN, Alan . C . Field
  • Re: TSO Unallocate Dataset., Phil King
  • RE: TSO Unallocate Dataset., Richards.Bob
    • Re: TSO Unallocate Dataset., ibm-main
  • RE: TSO Unallocate Dataset., Richards.Bob
  • RE: TSO Unallocate Dataset., Richards.Bob
  • RE: TSO Unallocate Dataset., Chiam, Susan Mee-Shia
  • Re: TSO Unallocate Dataset., Mark Thomen
    • Re: TSO Unallocate Dataset., Howard Rifkind
  • RE: TSO Unallocate Dataset., Chase, John
    • Re: TSO Unallocate Dataset., Edward E. Jaffe
  • Re: TSO Unallocate Dataset., Efinnell15
  • Re: TSO Unallocate Dataset., Efinnell15
  • Re: TSO Unallocate Dataset., Mark Thomen
    • Re: TSO Unallocate Dataset., Edward E. Jaffe
      • Mistaken Identity - TSOID switch, Jeffrey . Deaver
      • Re: Mistaken Identity - TSOID switch, Edward E. Jaffe
      • Re: Mistaken Identity - TSOID switch, Ron van der Zande
      • Re: Mistaken Identity - TSOID switch, Ron van der Zande
      • Re: TSO Unallocate Dataset., Shmuel Metz , Seymour J.
    • Re: TSO Unallocate Dataset., Howard Rifkind
  • RE: TSO Unallocate Dataset., Webster, Chris
    • Re: TSO Unallocate Dataset., Ed Gould
  • Re: TSO Unallocate Dataset., Mark Thomen
  • RE: TSO Unallocate Dataset., Robinson, James
    • Re: TSO Unallocate Dataset., Shmuel Metz , Seymour J.
  • Re: TSO Unallocate Dataset., Mark Thomen
  • Re: TSO Unallocate Dataset., David Alcock
  • Re: TSO Unallocate Dataset., gilmap
• ADMINISTRIVIA: Off Topic Posts, Darren Evans-Young
• RSVNONR again, R.S.
  • <Possible follow-ups>
  • RE: RSVNONR again, Rob Scott
  • RE: RSVNONR again, mf-system
  • RE: RSVNONR again, Rob Scott
    • Re: RSVNONR again, Gil Peleg
  • RSVNONR again, Peter Pfaffner
    • Re: RSVNONR again, R.S.
  • Re: RSVNONR again, Vernooy, C.P. - SPLXM
• MVS Systems' Opportunities - Need your Help, kstewart@xxxxxxxxxxxxx
• Region requested by MQBroker, DMR-Qualitas Outsourcing
  • Re: Region requested by MQBroker, DMR-Qualitas Outsourcing
  • <Possible follow-ups>
  • Re: Region requested by MQBroker, Mark Zelden
• JES2 Cold Start (was Re: NEW IBM Mainframes), Mark Zelden
  • <Possible follow-ups>
  • Re: JES2 Cold Start (was Re: NEW IBM Mainframes), Vernooy, C.P. - SPLXM
• RE: Supported interface to set/retrieve TCBUSER field NON-authori zed?, Craddock, Chris
  • <Possible follow-ups>
  • RE: Supported interface to set/retrieve TCBUSER field NON-authori zed?, Farley, Peter x23353
  • re: supported interface to set/retrieve TCBUSER field NON-authori zed?, john gilmore
  • RE: supported interface to set/retrieve TCBUSER field NON-authori zed?, McKown, John
    • Re: supported interface to set/retrieve TCBUSER field NON-authori zed?, Don Poitras
    • Re: supported interface to set/retrieve TCBUSER field NON-authori zed?, Shmuel Metz , Seymour J.
  • Re: supported interface to set/retrieve TCBUSER field NON-authori zed?, john gilmore
• VSAM browser, Natasa Savinc
  • Re: VSAM browser, John P Kalinich
  • Re: VSAM browser, R.S.
  • <Possible follow-ups>
  • Re: VSAM browser, Mark Zelden
  • RE: VSAM browser, Greg Shirey
    • Re: VSAM browser, John P Kalinich
      • Re: VSAM browser, R.S.
  • RE: VSAM browser, Greg Shirey
  • Re: VSAM browser, Natasa Savinc
• Accessin system symbolics from assembler, Bauer, Bobby , NIH/CIT
  • RE: Accessin system symbolics from assembler, Gary Green
  • <Possible follow-ups>
  • RE: Accessin system symbolics from assembler, Bauer, Bobby , NIH/CIT
  • RE: Accessin system symbolics from assembler, Rob Scott
  • Re: Accessin system symbolics from assembler, Mark Zelden
• RSVNONR -DB2, William Ball
  • RE: RSVNONR -DB2, Wayne Driscoll
    • Re: RSVNONR -DB2, Jim Mulder
      • RE: RSVNONR -DB2, Wayne Driscoll
  • <Possible follow-ups>
  • Re: RSVNONR -DB2, Ted MacNEIL
  • RE: RSVNONR -DB2, Imbriale, Donald , Exchange
    • Re: RSVNONR -DB2, William Ball
  • Re: RSVNONR -DB2, Efinnell15
    • RE: RSVNONR -DB2, Isaac Yassin
  • RE: RSVNONR -DB2, Craddock, Chris
  • Re: RSVNONR -DB2, Ted MacNEIL
    • Re: RSVNONR -DB2, R.S.
      • Re: RSVNONR -DB2, Shmuel Metz , Seymour J.
  • RE: RSVNONR -DB2, Craddock, Chris
  • Re: RSVNONR -DB2, Ted MacNEIL
  • RE: RSVNONR -DB2, Rob Scott
    • Re: RSVNONR -DB2, ibm-main
  • RE: RSVNONR -DB2, Rob Scott
  • Re: RSVNONR -DB2, Vernooy, C.P. - SPLXM
    • Re: RSVNONR -DB2, Edward E. Jaffe
      • Re: [IBM-MAIN] RSVNONR -DB2, Jay Maynard
      • Re: RSVNONR -DB2, Shmuel Metz , Seymour J.
  • Re: RSVNONR -DB2, Ted MacNEIL
    • Re: RSVNONR -DB2, R.S.
  • Re: RSVNONR -DB2, Mark Zelden
    • Align MF & Open backups?, Jeffrey . Deaver
  • Re: RSVNONR -DB2, Ted MacNEIL
  • RE: RSVNONR -DB2, Bob Shannon
    • Re: [IBM-MAIN] RSVNONR -DB2, Jay Maynard
      • Re: RSVNONR -DB2, Edward E. Jaffe
      • Re: [IBM-MAIN] RSVNONR -DB2, Jay Maynard
      • Re: RSVNONR -DB2, Edward E. Jaffe
      • Re: RSVNONR -DB2, Shmuel Metz , Seymour J.
      • Re: RSVNONR -DB2, R.S.
  • RE: RSVNONR -DB2, Jon Brock
  • Re: RSVNONR -DB2, Mark Zelden
  • RE: RSVNONR -DB2, Bob Shannon
  • RE: RSVNONR -DB2, Jon Brock
  • Re: RSVNONR -DB2, Vernooy, C.P. - SPLXM
  • RE: RSVNONR -DB2, Bob Shannon
    • Re: RSVNONR -DB2, Ed Gould
  • RE: RSVNONR -DB2, McKown, John
  • Re: RSVNONR -DB2, DASDBill2
  • RE: RSVNONR -DB2, Jon Brock
  • Re: RSVNONR -DB2, DASDBill2
  • RE: RSVNONR -DB2, Rob Scott
  • Re: RSVNONR -DB2, Ted MacNEIL
  • RSVNONR -DB2, Peter Pfaffner
  • RE: RSVNONR -DB2, Schiradin,Roland HG-Dir itb-db/dc
• SMF records, Chiam, Susan Mee-Shia
  • Betr.: SMF records, G. van Arnhem
  • <Possible follow-ups>
  • Re: SMF records, Vernooy, C.P. - SPLXM
  • RE: SMF records, Chiam, Susan Mee-Shia
• System completion code FCD, mary george
  • Re: System completion code FCD, Jim McAlpine
  • Re: System completion code FCD, mary george
    • Re: System completion code FCD, ibm-main
  • <Possible follow-ups>
  • Re: System completion code FCD, Vernooy, C.P. - SPLXM
    • Re: System completion code FCD, mary george
  • Re: System completion code FCD, Efinnell15
  • RE: System completion code FCD, Imbriale, Donald , Exchange
• Quiescing VSAM RLS data sets, IBroussard
  • <Possible follow-ups>
  • Re: Quiescing VSAM RLS data sets, Mark Thomen
• NEW IBM Mainframes This week?, Ed Gould
  • Re: NEW IBM Mainframes This week?, Tom Grieve
    • Re: NEW IBM Mainframes This week?, Birger Heede
    • Re: NEW IBM Mainframes This week?, John Eells
  • Re: NEW IBM Mainframes This week?, Birger Heede
  • <Possible follow-ups>
  • Re: NEW IBM Mainframes This week?, Vernooy, C.P. - SPLXM
    • Re: NEW IBM Mainframes This week?, Birger Heede
  • Re: NEW IBM Mainframes This week?, DASDBill2
  • Re: NEW IBM Mainframes This week?, Vernooy, C.P. - SPLXM
  • Re: NEW IBM Mainframes This week?, Vernooy, C.P. - SPLXM
• RE: TLAs - was summit entirely ..., brad taylor
• Re: TLAs - was summit else entirely, john gilmore
  • <Possible follow-ups>
  • RE: TLAs - was summit else entirely, Chase, John
    • Re: TLAs - was summit else entirely, Anne & Lynn Wheeler
  • Re: TLAs - was summit else entirely, Mark Zelden
    • RE: TLAs - was summit else entirely, Ray Mullins
• Re: MP3000 ICA cable to CISCO, August . Carideo
  • <Possible follow-ups>
  • RE: MP3000 ICA cable to CISCO, Greg Shirey
• Re: It was his turn to be "beamed" up... :(, Efinnell15
  • <Possible follow-ups>
  • Re: It was his turn to be "beamed" up... :(, DASDBill2
  • Re: It was his turn to be "beamed" up... :(, KTu2112593
  • Re: It was his turn to be "beamed" up... :(, Efinnell15
    • Re: It was his turn to be "beamed" up... :(, Graeme Gibson
    • Re: It was his turn to be "beamed" up... :(, Ed Gould
  • Re: It was his turn to be "beamed" up... :(, Ted MacNEIL
    • RE: It was his turn to be "beamed" up... :(, Gary Green
  • Re: It was his turn to be "beamed" up... :(, Efinnell15
• Re: MCAT cache hits, DMR-Qualitas Outsourcing
  • <Possible follow-ups>
  • Re: MCAT cache hits, Mark Thomen
• IEBGENER and SDB, Walter Marguccio
  • Re: IEBGENER and SDB, martin_kline
    • Re: IEBGENER and SDB, Ed Long
      • It was his turn to be "beamed" up... :(, Gary Green
  • Re: IEBGENER and SDB, R.S.
    • Re: IEBGENER and SDB, Thomas Conley
      • Re: IEBGENER and SDB, Ed Gould
      • Re: IEBGENER and SDB, R.S.
  • Re: IEBGENER and SDB, Bruce Black
    • FICON and CTC, Marian Gasparovic
      • Re: FICON and CTC, Marian Gasparovic
      • Re: FICON and CTC, R.S.
      • Re: FICON and CTC, ibm-main
    • Re: IEBGENER and SDB, R.S.
  • <Possible follow-ups>
  • IEBGENER and SDB, Walter Marguccio
    • Re: IEBGENER and SDB, R.S.
• Migration to a new processor 2086, D-Arbigny Pierre-Andre
  • <Possible follow-ups>
  • Re: Migration to a new processor 2086, Natarajan Mohan
  • RE: Migration to a new processor 2086, Hal Merritt
  • Migration to a new processor 2086, John_Mattson
• EDT and Token, D-Arbigny Pierre-Andre
  • <Possible follow-ups>
  • RE: EDT and Token, McKown, John
• Re: TLAs - was summit else entirely ..., Ted MacNEIL
  • RE: TLAs - was summit else entirely ..., Charles Mills
  • <Possible follow-ups>
  • RE: TLAs - was summit else entirely ..., Craddock, Chris
  • Re: TLAs - was summit else entirely ..., Ted MacNEIL
  • Re: TLAs - was summit else entirely ..., Howard Brazee
  • Re: TLAs - was summit else entirely ..., Ted MacNEIL
  • Re: TLAs - was summit else entirely ..., Ted MacNEIL
    • Re: TLAs - was summit else entirely ..., Edward E. Jaffe
  • Re: TLAs - was summit else entirely ..., Ted MacNEIL
    • Re: TLAs - was summit else entirely ..., Edward E. Jaffe
  • Re: TLAs - was summit else entirely ..., Ted MacNEIL
    • Re: TLAs - was summit else entirely ..., Edward E. Jaffe
  • Re: TLAs - was summit else entirely ..., DASDBill2
  • RE: TLAs - was summit else entirely ..., Richards.Bob
  • RE: TLAs - was summit else entirely ..., Richards.Bob
    • Re: TLAs - was summit else entirely ..., Edward E. Jaffe
  • RE: TLAs - was summit else entirely ..., Rob Scott
  • RE: TLAs - was summit else entirely ..., Chase, John
  • Re: TLAs - was summit else entirely ..., Ted MacNEIL
• Delete a Record depending on the actuell Date; JCL DFSORT, Norbert
• Using WSED for HLASM development, Beate . Kawelke
  • Re: Using WSED for HLASM development, Thomas David Rivers
  • <Possible follow-ups>
  • Re: Using WSED for HLASM development, Rob Wunderlich
  • RE: Using WSED for HLASM development, McKown, John
    • Re: Using WSED for HLASM development, Dave Salt
  • Re: Using WSED for HLASM development, Timothy Sipples
  • RE: Using WSED for HLASM development, McKown, John
• Re: Displaying USS couple data sets information, Barbara Nitz
• IRDFSD service, Schiradin,Roland HG-Dir itb-db/dc
• Workload License Charges & IRD Seminar in Milwaukee, Al Sherkow
• Displaying USS couple data sets information, Mark Yuhas
• Defined Capacity vs. Capping, Ken . Porowski
  • Re: Defined Capacity vs. Capping, Shane Ginnane
    • RE: Defined Capacity vs. Capping, Paul Hanrahan
      • Re: Defined Capacity vs. Capping, Shane Ginnane
  • Re: Defined Capacity vs. Capping, Gil Peleg
  • <Possible follow-ups>
  • Re: Defined Capacity vs. Capping, Ted MacNEIL
  • Re: Defined Capacity vs. Capping, Al Sherkow
  • Re: Defined Capacity vs. Capping, Al Sherkow
• CBT Tape file 104 JRP, Richard Pinion
• ZDASD Response for Carlos Alberto Bodra, Bruce boda
• Measuring CPU time under USS in a "C" program, Jackson, Scott
  • Re: Measuring CPU time under USS in a "C" program, Gil Peleg
• The secret to multi-volume, non-SMS, DASD allocations?, Steve_Grimes
  • Re: The secret to multi-volume, non-SMS, DASD allocations?, Ed Gould
    • Re: The secret to multi-volume, non-SMS, DASD allocations?, Steve_Grimes
  • Re: The secret to multi-volume, non-SMS, DASD allocations?, willie bunter
    • Re: The secret to multi-volume, non-SMS, DASD allocations?, Steve_Grimes
    • Re: The secret to multi-volume, non-SMS, DASD allocations?, R.S.
      • Re: The secret to multi-volume, non-SMS, DASD allocations?, Steve_Grimes
    • Re: The secret to multi-volume, non-SMS, DASD allocations?, Gerhard Postpischil
      • Re: The secret to multi-volume, non-SMS, DASD allocations?, R.S.
  • <Possible follow-ups>
  • RE: The secret to multi-volume, non-SMS, DASD allocations?, Richards.Bob
    • Re: The secret to multi-volume, non-SMS, DASD allocations?, Steve_Grimes
  • Re: The secret to multi-volume, non-SMS, DASD allocations?, rkuebbin
  • Re: The secret to multi-volume, non-SMS, DASD allocations?, Ted MacNEIL
  • RE: The secret to multi-volume, non-SMS, DASD allocations?, Richards.Bob
  • RE: The secret to multi-volume, non-SMS, DASD allocations?, Raymond Noal
• Re: JES2 and Abend S722, Ed Gould
• External Time Source - 9037 RISC UNIX, Gabe Torres
  • Re: External Time Source - 9037 RISC UNIX, Alan . C . Field
    • Re: External Time Source - 9037 RISC UNIX, JO . Skip . Robinson
  • <Possible follow-ups>
  • Re: External Time Source - 9037 RISC UNIX, gilmap
  • RE: External Time Source - 9037 RISC UNIX, Gabe Torres
• RiP/EIGRP mainframe migration, Philip Miscione
  • Re: RiP/EIGRP mainframe migration, John S. Giltner, Jr.
  • <Possible follow-ups>
  • Re: RiP/EIGRP mainframe migration, Timothy Sipples
  • RE: RiP/EIGRP mainframe migration, Schramm, Rob
• RE: [IBM-MAIN] capacity of largest drive, Ken . Porowski
  • <Possible follow-ups>
  • Re: [IBM-MAIN] capacity of largest drive, Vernooy, C.P. - SPLXM
• Secure FTP on z/OS, Neal Eckhardt
  • Re: Secure FTP on z/OS, John S. Giltner, Jr.
  • Re: Secure FTP on z/OS, Neal Eckhardt
  • <Possible follow-ups>
  • RE: Secure FTP on z/OS, Gibney, David Allen,Jr
  • RE: Secure FTP on z/OS, Hal Merritt
• capacity of largest drive, Steve Comstock
  • Re: capacity of largest drive, R.S.
    • Re: capacity of largest drive, Shmuel Metz , Seymour J.
    • Re: capacity of largest drive, Shmuel Metz , Seymour J.
  • Re: capacity of largest drive, John P Kalinich
    • Re: capacity of largest drive, Steve Comstock
      • Re: capacity of largest drive, John P Kalinich
    • Re: capacity of largest drive, Shmuel Metz , Seymour J.
  • Re: capacity of largest drive, John Eells
    • Re: capacity of largest drive, Steve Comstock
      • Re: capacity of largest drive, R.S.
      • Re: capacity of largest drive, Jeffrey . Deaver
      • Re: capacity of largest drive, gerard46
  • Re: capacity of largest drive, Shmuel Metz , Seymour J.
  • <Possible follow-ups>
  • RE: capacity of largest drive, Richards.Bob
    • Re: capacity of largest drive, Shmuel Metz , Seymour J.
  • RE: capacity of largest drive, McKown, John
  • Re: capacity of largest drive, Lutz Hamann
  • RE: capacity of largest drive, Rob Scott
  • Re: capacity of largest drive, DASDBill2
    • Re: capacity of largest drive, Bruce Black
      • Re: capacity of largest drive, Chris Langford
      • Re: capacity of largest drive, Bruce Black
  • Re: capacity of largest drive, Vernooy, C.P. - SPLXM
  • Re: capacity of largest drive, Ted MacNEIL
  • Re: capacity of largest drive, DASDBill2
  • RE: capacity of largest drive, McKown, John
  • Re: capacity of largest drive, jbaker314
    • Re: capacity of largest drive, R.S.
      • RE: capacity of largest drive, John P Baker
      • Re: capacity of largest drive, R.S.
      • Re: capacity of largest drive, Bruce Black
      • RE: capacity of largest drive, Ray Mullins
      • Re: capacity of largest drive, Ed Gould
      • Re: capacity of largest drive, Bruce Black
  • Re: capacity of largest drive, DASDBill2
  • RE: capacity of largest drive, Blaicher, Chris
    • Re: capacity of largest drive, Clark Morris
  • Re: capacity of largest drive, Vernooy, C.P. - SPLXM
  • Re: capacity of largest drive, Ted MacNEIL
  • RE: capacity of largest drive, Compton, John
    • TLAs - was summit else entirely ..., ibm-main
      • Re: TLAs - was summit else entirely ..., john . ticic . extern
      • Re: TLAs - was summit else entirely ..., ibm-main
  • Re: capacity of largest drive, Ted MacNEIL
  • Re: capacity of largest drive, Vernooy, C.P. - SPLXM
  • RE: capacity of largest drive, Chase, John
  • Re: capacity of largest drive, Ted MacNEIL
  • Re: capacity of largest drive, Bruce Black
  • Re: capacity of largest drive, DASDBill2
  • Re: capacity of largest drive, jbaker314
  • Re: capacity of largest drive, gilmap
  • RE: capacity of largest drive, McKown, John
  • Re: capacity of largest drive, jbaker314
  • RE: capacity of largest drive, Chase, John
    • RE: capacity of largest drive, Ron and Jenny Hawkins
    • Re: capacity of largest drive, Ed Gould
  • Re: capacity of largest drive, DASDBill2
    • RE: capacity of largest drive, John P Baker
  • Re: capacity of largest drive, Vernooy, C.P. - SPLXM
    • Re: capacity of largest drive, R.S.
  • Re: capacity of largest drive, gilmap
• STAE/ESTAE, mary george
  • RE: STAE/ESTAE, Wayne Driscoll
    • Re: STAE/ESTAE, mary george
      • Re: STAE/ESTAE, Binyamin Dissen
  • <Possible follow-ups>
  • Re: STAE/ESTAE, Ted MacNEIL
  • Re: STAE/ESTAE, Mark Zelden
  • RE: STAE/ESTAE, Craddock, Chris
    • Re: STAE/ESTAE, Rolf Ernst
  • RE: STAE/ESTAE, Craddock, Chris
  • Re: STAE/ESTAE, DASDBill2
    • Re: STAE/ESTAE, mary george
  • RE: STAE/ESTAE, Rob Scott
  • Re: STAE/ESTAE, David Alcock
    • Re: STAE/ESTAE, Edward E. Jaffe
  • Re: STAE/ESTAE, Peter Relson
• Re: IXG601I loss of data, Barbara Nitz
• User experiences TAPE/COPY, Lieven Borgs
  • Re: User experiences TAPE/COPY, Bruce Black
  • RE: User experiences TAPE/COPY, Don Bolton
  • <Possible follow-ups>
  • Re: User experiences TAPE/COPY, Mark Zelden
• IXG601I loss of data, Julian Zhu
• The clamor begins for IBM to give up the code for OS/2, Ed Gould
  • <Possible follow-ups>
  • Re: The clamor begins for IBM to give up the code for OS/2, Efinnell15
    • Re: The clamor begins for IBM to give up the code for OS/2, Ed Gould
      • Re: The clamor begins for IBM to give up the code for OS/2, David Andrews
      • Re: The clamor begins for IBM to give up the code for OS/2, Shmuel Metz , Seymour J.
  • Re: The clamor begins for IBM to give up the code for OS/2, Paul Gilmartin
    • Re: The clamor begins for IBM to give up the code for OS/2, Steve Comstock
    • Re: The clamor begins for IBM to give up the code for OS/2, David Andrews
      • Re: The clamor begins for IBM to give up the code for OS/2, Ed Gould
      • Re: The clamor begins for IBM to give up the code for OS/2, Shmuel Metz , Seymour J.
      • Re: The clamor begins for IBM to give up the code for OS/2, Leonard Woren
      • Re: The clamor begins for IBM to give up the code for OS/2, Shmuel Metz , Seymour J.
      • Re: The clamor begins for IBM to give up the code for OS/2, R.S.
  • Re: The clamor begins for IBM to give up the code for OS/2, Efinnell15
  • RE: The clamor begins for IBM to give up the code for OS/2, McKown, John
  • Re: The clamor begins for IBM to give up the code for OS/2, Ted MacNEIL
  • RE: The clamor begins for IBM to give up the code for OS/2, Jon Brock
  • Re: The clamor begins for IBM to give up the code for OS/2, Scott Rowe
  • Re: The clamor begins for IBM to give up the code for OS/2, Efinnell15
  • Re: The clamor begins for IBM to give up the code for OS/2, gilmap
  • Re: The clamor begins for IBM to give up the code for OS/2, gilmap
  • Re: The clamor begins for IBM to give up the code for OS/2, Scott Rowe
  • Re: The clamor begins for IBM to give up the code for OS/2, Efinnell15
  • Re: The clamor begins for IBM to give up the code for OS/2, Scott Rowe
  • Re: The clamor begins for IBM to give up the code for OS/2, Efinnell15
  • Re: The clamor begins for IBM to give up the code for OS/2, Scott Rowe
  • Re: The clamor begins for IBM to give up the code for OS/2, Efinnell15
  • Re: The clamor begins for IBM to give up the code for OS/2, Scott Rowe
  • Re: The clamor begins for IBM to give up the code for OS/2, DASDBill2
  • Re: The clamor begins for IBM to give up the code for OS/2, Efinnell15
    • Re: The clamor begins for IBM to give up the code for OS/2, Ed Gould
      • Re: The clamor begins for IBM to give up the code for OS/2, Edward E. Jaffe
      • Re: The clamor begins for IBM to give up the code for OS/2, Ed Gould
      • Re: The clamor begins for IBM to give up the code for OS/2, R.S.
  • Re: The clamor begins for IBM to give up the code for OS/2, Scott Rowe
  • Re: The clamor begins for IBM to give up the code for OS/2, Efinnell15
  • RE: The clamor begins for IBM to give up the code for OS/2, Gibney, David Allen,Jr
  • Re: The clamor begins for IBM to give up the code for OS/2, Scott Rowe
  • Re: The clamor begins for IBM to give up the code for OS/2, Scott Rowe
  • Re: The clamor begins for IBM to give up the code for OS/2, Howard Brazee
  • Re: The clamor begins for IBM to give up the code for OS/2, Efinnell15
  • Re: The clamor begins for IBM to give up the code for OS/2, Scott Rowe
  • RE: The clamor begins for IBM to give up the code for OS/2, Hal Merritt
  • Re: The clamor begins for IBM to give up the code for OS/2, Howard Brazee
    • RE: The clamor begins for IBM to give up the code for OS/2, Ron and Jenny Hawkins
  • Re: The clamor begins for IBM to give up the code for OS/2, Efinnell15
  • Re: The clamor begins for IBM to give up the code for OS/2, Scott Rowe
  • Re: The clamor begins for IBM to give up the code for OS/2, Scott Rowe
  • Re: The clamor begins for IBM to give up the code for OS/2, Efinnell15
  • Re: The clamor begins for IBM to give up the code for OS/2, Scott Rowe
• VLF Trimming - how much is good?, Fred . Schmidt
  • <Possible follow-ups>
  • Re: VLF Trimming - how much is good?, DMR-Qualitas Outsourcing
  • Re: VLF Trimming - how much is good?, Fred Schmidt
• CARLES ARIS REDO/CAIXA01 está ausente de la oficina., caris
• RE: [IBM-MAIN] AW: Debug for z/OS, Ken . Porowski
  • <Possible follow-ups>
  • RE: [IBM-MAIN] AW: Debug for z/OS, Ken . Porowski
    • Re: [IBM-MAIN] AW: Debug for z/OS, Eric Bielefeld
• Structured field definition, Dan Ponta
  • Re: Structured field definition, Edward E. Jaffe
  • <Possible follow-ups>
  • RE: Structured field definition, Chase, John
• AW: Debug for z/OS, Schiradin,Roland HG-Dir itb-db/dc
  • <Possible follow-ups>
  • AW: Debug for z/OS, Schiradin,Roland HG-Dir itb-db/dc
  • Re: AW: Debug for z/OS, Efinnell15
  • RE: AW: Debug for z/OS, Larry Kraus
  • RE: AW: Debug for z/OS, Chase, John
  • Fw: AW: Debug for z/OS, Bill Klein
• RE: [IBM-MAIN] Debug for z/OS, Ken . Porowski
  • <Possible follow-ups>
  • RE: [IBM-MAIN] Debug for z/OS, Ken . Porowski
• Debug for z/OS, Richards.Bob
  • Re: Debug for z/OS, Shmuel Metz , Seymour J.
  • Re: Debug for z/OS, Tom Longfellow
  • <Possible follow-ups>
  • RE: Debug for z/OS, Chase, John
  • RE: Debug for z/OS, Richards.Bob
  • RE: Debug for z/OS, Schiradin,Roland HG-Dir itb-db/dc
  • RE: Debug for z/OS, Pommier, Rex R.
  • RE: Debug for z/OS, Chase, John
  • RE: Debug for z/OS, Chase, John
  • RE: Debug for z/OS, Pommier, Rex R.
• RE: Question on XSC IPSF utility, Imbriale, Donald , Exchange
  • RES: Question on XSC IPSF utility, geraldo barbosa
  • <Possible follow-ups>
  • Re: Question on XSC IPSF utility, Shmuel Metz , Seymour J.
• Question: ISPF - XSC utilities, geraldo barbosa
• [SMS] testing new SCDS configuration, Neil Duffee
  • <Possible follow-ups>
  • [SMS] testing new SCDS configuration, Richards.Bob
  • RE: [SMS] testing new SCDS configuration, Knutson, Sam
• HCD OS options for 3592, Johnston, Robert E
  • Re: HCD OS options for 3592, R.S.
    • Re: HCD OS options for 3592, Cyber
  • <Possible follow-ups>
  • RE: HCD OS options for 3592, McKown, John
  • RE: HCD OS options for 3592, Johnston, Robert E
  • Re: HCD OS options for 3592, Efinnell15
• HSM backup copy retention, Perryman, Brian
  • Re: HSM backup copy retention, pauls2272
  • <Possible follow-ups>
  • RE: HSM backup copy retention, Scott Barry
• Question on LU6.2 trace - Request Header flags, Mauri Kanter
  • RE: Question on LU6.2 trace - Request Header flags, Paul Hanrahan
  • Re: Question on LU6.2 trace - Request Header flags, Shmuel Metz , Seymour J.
  • <Possible follow-ups>
  • RE: Question on LU6.2 trace - Request Header flags, Chase, John
  • Re: Question on LU6.2 trace - Request Header flags, Mauri Kanter
  • RE: Question on LU6.2 trace - Request Header flags, Chase, John
  • Re: Question on LU6.2 trace - Request Header flags, Mauri Kanter
    • Question on XSC IPSF utility, geraldo barbosa
• EMC dasd question, awhite
  • RE: EMC dasd question, Ron and Jenny H