Table of contents:

• *NOTICE* TMON/CICS Message Changes (2 messages)
• 10,000 DIGEST lines is too much (17 messages)
• 2007 Conference (2 messages)
• A DB2 List Question (3 messages)
• ACF2 Generated SSL Certificates (2 messages)
• AOR, what TOR? (12 messages)
• ASREXIT (5 messages)
• ASSEMBLER INSTRUCTION "JE" (4 messages)
• AW: AW: AW: Access RACF Info ++ sorry!
• AW: AW: Access RACF Info (3 messages)
• AW: Access RACF Info (4 messages)
• AW: Exec Cics Link and Cobol dynamic call
• AW: measure task cpu time consumption
• Access RACF Info (7 messages)
• Anyone know how....... (4 messages)
• Are there any well regarded CICS certifications ?
• Auto Install Model Problem . . . (2 messages)
• Bruce Lin/Dallas/IBM is out of the office.
• Bruce S Dennis/Nationwide/NWIE is out of the office.
• CA-View and alternate screen sizes
• CA/IDEAL & CTS 3.1 (2 messages)
• CATS package and using APPC
• CICS AS400 DB2 and iSeries
• CICS Forward Recovery (2 messages)
• CICS SOAP message compression
• CICS Time Out Value (3 messages)
• CICS Users join Webcast on Storage Violations
• CICS V2.3 conversion (9 messages)
• CICS V4.1 to CICS TS V3.1? (8 messages)
• CICS conversion philosophy, etc (7 messages)
• CICS, Cobol, DB2 Programmers (2 messages)
• CICS-L Digest - 18 Jul 2006 to 19 Jul 2006 (#2006-182)
• CICS-L NOMAIL (2 messages)
• CICS-RACF Doubt (2 messages)
• CICS/COBOL (or Assembler) Base64 Conversion Routine (6 messages)
• Catch inefficient code sooner, deliver quality apps faster (24 messages)
• Cedf problem (9 messages)
• Compatibility CICS/TS NOT
• Craig Nicholson is out of the office until June 25th 2006
• DFHTRAP overhead (11 messages)
• DR (was Catch inefficient code sooner, deliver quality apps faster) (2 messages)
• David Hurlbert/KC/HALLMARK is out of the office.
• Duplicate entries en Mainview files
• ENQMODEL
• EYUXD0707E Message from EYU9XDUT (6 messages)
• EZACIC01 OTE=YES/NO
• Elena Nanos/IL/HCSC is out of the office. (2 messages)
• Exec Cics Link and Cobol dynamic call
• Fabrice Jarassat/France/IBM is out of the office.
• File open (4 messages)
• Find the program/Transaction which started to this Transaction (4 messages)
• Fw: CICS V4.1 to CICS TS V3.1? (2 messages)
• Fw: Catch inefficient code sooner, deliver quality apps faster
• Fw: Fw: Fw: Program to test high CPU usage?
• Fw: Fw: Program to test high CPU usage?
• Fw: Program to test high CPU usage?
• Fw: VSAM CI Size & CICS
• Fw: Yielding Loop (5 messages)
• Fw: update timestanmp in CICS (4 messages)
• GRNAME (2 messages)
• George Potiris/ITM/DCC/DCX is out of the office. (2 messages)
• Help with trace entries (2 messages)
• Help: Precompiling variable length CICS C Source (2 messages)
• How do I find out which TOR transactions are routed to the AORs ?
• I am on vacation. Please contact Renee Bartels if you need immediate assistance.
• ISRLEMX substitution problem
• IXRJCL error installing support pack ca8i (9 messages)
• Increased MSGUSR Output Due To CICS Internal Limitation (6 messages)
• Is anyone using CICS TS 3.1's Web Services Capability? (7 messages)
• John J. Leonard/Westfield Companies is out of the office.
• Kathie Bertram is out of the office.
• Ken Taylor/RYE/US/Avon is out of the office. (2 messages)
• LUTYPE6.1 trivia?
• Lee Eshleman is out of the office.
• Manny Reyes/IL/HCSC is out of the office.
• Marina Kmet/Australia/IBM is out of the office.
• Mary McCaw/FlorhamPark/Pershing is out of the office.
• Measuring program loads. (8 messages)
• Numerous DFHLG0747I messages at CICS start-up (13 messages)
• Occasional high DISPWTT CICS-MQ Bridge (3 messages)
• Omegamon replacements (4 messages)
• Outbound http (3 messages)
• Paul Johnson is out of the office.
• Preferred way to serve up images?? (3 messages)
• Problem with DOCUMENT CREATE (2 messages)
• Program to test high CPU usage? (14 messages)
• Quesiton about CICS system log (4 messages)
• RACF commands under CICS (18 messages)
• Reply to CICS/COBOL (or Assem
• Report (3 messages)
• Robert Crawford/ORD/ALLTELCORP is out of the office. (2 messages)
• SMPE error for CICS/TS 2.2 service install (13 messages)
• SOAP Translation Problem (2 messages)
• Sean Dilmore/Endicott/IBM is out of the office.
• TSQ 16 Character names
• Tech Conference 2007 Poll results and more.
• Tony Nestoras/DS/MICORP is out of the office.
• UNSUBSCRIBE (3 messages)
• Unsubscribe
• VSAM CI Size & CICS (20 messages)
• Why use SSI in CICS? (8 messages)
• Will ' FREE=CLOSE' work for the SIT override parmlib??? (6 messages)
• Yielding Loop (25 messages)
• [From Vwall: Suspected SPAM]: Help with trace entries
• abendAPC3 (5 messages)
• cics transaction cpu collect statistics tmrcput (3 messages)
• cics web service...... (2 messages)
• cics web services (2 messages)
• cicsts23 xcf cicsts13 (mro)
• how can I find all TSQ created by the specific program? (2 messages)
• measure task cpu time consumption (9 messages)
• run plex1 or plex2 (3 messages)
• unsubscribe
• update timestanmp in CICS (4 messages)
• why I can't relase one load hold program? (3 messages)

1. *NOTICE* TMON/CICS Message Changes
   • *NOTICE* TMON/CICS Message Changes (16 lines)
     From: Rick Woods <Rick.Woods@AZDOA.GOV>
   • Re: *NOTICE* TMON/CICS Message Changes (97 lines)
     From: Gary Henderson <gary.henderson@ASG.COM>

2. 10,000 DIGEST lines is too much
   • Re: 10,000 DIGEST lines is too much (35 lines)
     From: Russell West <list0id1@PACBELL.NET>
   • Re: 10,000 DIGEST lines is too much (82 lines)
     From: Evans, Kevin R <kevin.r.evans@LMCO.COM>
   • Re: 10,000 DIGEST lines is too much (27 lines)
     From: Chase, John <jchase@USSCO.COM>
   • Re: 10,000 DIGEST lines is too much (18 lines)
     From: Rick Woods <Rick.Woods@AZDOA.GOV>
   • Re: 10,000 DIGEST lines is too much (80 lines)
     From: Joseph Fatula <jfatula@AESSUCCESS.ORG>
   • Re: 10,000 DIGEST lines is too much (37 lines)
     From: Chase, John <jchase@USSCO.COM>
   • Re: 10,000 DIGEST lines is too much (208 lines)
     From: Clark, Graham <Graham.Clark@ACS-INC.COM>
   • Re: 10,000 DIGEST lines is too much (23 lines)
     From: Chase, John <jchase@USSCO.COM>
   • Re: 10,000 DIGEST lines is too much (155 lines)
     From: Evans, Kevin R <kevin.r.evans@LMCO.COM>
   • Re: 10,000 DIGEST lines is too much (16 lines)
     From: Rick Woods <Rick.Woods@AZDOA.GOV>
   • Re: 10,000 DIGEST lines is too much (43 lines)
     From: McKown, John <John.Mckown@HEALTHMARKETS.COM>
   • Re: 10,000 DIGEST lines is too much (38 lines)
     From: Evans, Kevin R <kevin.r.evans@LMCO.COM>
   • Re: 10,000 DIGEST lines is too much (35 lines)
     From: Rick Woods <Rick.Woods@AZDOA.GOV>
   • Re: 10,000 DIGEST lines is too much (69 lines)
     From: McKown, John <John.Mckown@HEALTHMARKETS.COM>
   • Re: 10,000 DIGEST lines is too much (40 lines)
     From: Joseph Fatula <jfatula@AESSUCCESS.ORG>
   • Re: 10,000 DIGEST lines is too much (23 lines)
     From: Chase, John <jchase@USSCO.COM>
   • Re: 10,000 DIGEST lines is too much (19 lines)
     From: Evans, Kevin R <kevin.r.evans@LMCO.COM>

3. 2007 Conference
   • Re: 2007 Conference (95 lines)
     From: CICS_Infobase/Systems/Philadelphia/Fiserv%FISERVTS@FISERV.COM
   • Re: 2007 Conference (29 lines)
     From: PCS <pcs305@YAHOO.COM>

4. A DB2 List Question
   • A DB2 List Question (36 lines)
     From: Sergio Lima <sergiocics@YAHOO.COM.BR>
   • Re: A DB2 List Question (22 lines)
     From: PCS <pcs305@YAHOO.COM>
   • Re: A DB2 List Question (46 lines)
     From: Sergio Lima <sergiocics@YAHOO.COM.BR>

5. ACF2 Generated SSL Certificates
   • ACF2 Generated SSL Certificates (22 lines)
     From: Grinsell, Don <dgrinsell@MT.GOV>
   • Re: ACF2 Generated SSL Certificates (43 lines)
     From: Grinsell, Don <dgrinsell@MT.GOV>

6. AOR, what TOR?
   • AOR, what TOR? (16 lines)
     From: Frank Swarbrick <frank.swarbrick@EFIRSTBANK.COM>
   • Re: AOR, what TOR? (171 lines)
     From: Michael Norred <mnorred@TSYS.COM>
   • Re: AOR, what TOR? (40 lines)
     From: Jim Anglim <Jim.Anglim@DARBYGROUP.COM>
   • Re: AOR, what TOR? (36 lines)
     From: wobconsult@sprynet.com <wobconsult@SPRYNET.COM>
   • Re: AOR, what TOR? (48 lines)
     From: Frank Swarbrick <frank.swarbrick@EFIRSTBANK.COM>
   • Re: AOR, what TOR? (66 lines)
     From: Frank Swarbrick <frank.swarbrick@EFIRSTBANK.COM>
   • Re: AOR, what TOR? (89 lines)
     From: Jim Anglim <Jim.Anglim@DARBYGROUP.COM>
   • Re: AOR, what TOR? (20 lines)
     From: Chase, John <jchase@USSCO.COM>
   • Re: AOR, what TOR? (43 lines)
     From: Frank Swarbrick <frank.swarbrick@EFIRSTBANK.COM>
   • Re: AOR, what TOR? (74 lines)
     From: Tony Saul <generalemaillists@YAHOO.COM.AU>
   • Re: AOR, what TOR? (88 lines)
     From: Jim Anglim <Jim.Anglim@DARBYGROUP.COM>
   • Re: AOR, what TOR? (31 lines)
     From: Frank Swarbrick <frank.swarbrick@EFIRSTBANK.COM>

7. ASREXIT
   • ASREXIT (53 lines)
     From: fmorote@BN.COM.PE
   • Re: ASREXIT (128 lines)
     From: Chase, John <jchase@USSCO.COM>
   • Re: ASREXIT (184 lines)
     From: fmorote@BN.COM.PE
   • Re: ASREXIT (141 lines)
     From: Chase, John <jchase@USSCO.COM>
   • Re: ASREXIT (42 lines)
     From: Barnard, John <John_Barnard@BMC.COM>

8. ASSEMBLER INSTRUCTION "JE"
   • ASSEMBLER INSTRUCTION "JE" (40 lines)
     From: Briggs, Arlyn <Arlyn.Briggs@UMB.COM>
   • Re: ASSEMBLER INSTRUCTION "JE" (96 lines)
     From: Farley, Peter x23353 <Peter_Farley@ADP.COM>
   • Re: ASSEMBLER INSTRUCTION "JE" (30 lines)
     From: Edward Jaffe <edjaffe@PHOENIXSOFTWARE.COM>
   • Re: ASSEMBLER INSTRUCTION "JE" (47 lines)
     From: Farley, Peter x23353 <Peter_Farley@ADP.COM>

9. AW: AW: AW: Access RACF Info ++ sorry!
   • AW: AW: AW: Access RACF Info ++ sorry! (224 lines)
     From: McBurnie, Carl <Carl.McBurnie@COMMERZBANK.COM>

10. AW: AW: Access RACF Info
    • AW: AW: Access RACF Info (154 lines)
      From: McBurnie, Carl <Carl.McBurnie@COMMERZBANK.COM>
    • AW: AW: Access RACF Info (129 lines)
      From: McBurnie, Carl <Carl.McBurnie@COMMERZBANK.COM>
    • Re: AW: AW: Access RACF Info (103 lines)
      From: Baugh, Steve <Steve.Baugh@ANPAC.COM>

11. AW: Access RACF Info
    • AW: Access RACF Info (246 lines)
      From: Mc Burnie, Carl <Carl.McBurnie@COMMERZBANK.COM>
    • Re: AW: Access RACF Info (114 lines)
      From: Roland Schiradin <roland@SCHIRADIN.DE>
    • Re: AW: Access RACF Info (88 lines)
      From: Chase, John <jchase@USSCO.COM>
    • AW: Access RACF Info (244 lines)
      From: McBurnie, Carl <Carl.McBurnie@COMMERZBANK.COM>

12. AW: Exec Cics Link and Cobol dynamic call
    • AW: Exec Cics Link and Cobol dynamic call (252 lines)
      From: Mc Burnie, Carl <Carl.McBurnie@COMMERZBANK.COM>

13. AW: measure task cpu time consumption
    • AW: measure task cpu time consumption (29 lines)
      From: McBurnie, Carl <Carl.McBurnie@COMMERZBANK.COM>

14. Access RACF Info
    • Access RACF Info (119 lines)
      From: Baugh, Steve <Steve.Baugh@ANPAC.COM>
    • Re: Access RACF Info (36 lines)
      From: Ian Deeley <ian_deeley@UK.IBM.COM>
    • Re: Access RACF Info (44 lines)
      From: wobconsult@sprynet.com <wobconsult@SPRYNET.COM>
    • Re: Access RACF Info (156 lines)
      From: Chase, John <jchase@USSCO.COM>
    • Re: Access RACF Info (60 lines)
      From: Baugh, Steve <Steve.Baugh@ANPAC.COM>
    • Re: Access RACF Info (50 lines)
      From: Chase, John <jchase@USSCO.COM>
    • Re: Access RACF Info (186 lines)
      From: Schiradin,Roland HG-Dir itb-db/dc <SchiradinR@ALTE-LEIPZIGER.DE>

15. Anyone know how.......
    • Anyone know how....... (137 lines)
      From: Schneck.Glenn <Glenn.Schneck@SUNTRUST.COM>
    • Re: Anyone know how....... (121 lines)
      From: Ira Broussard <IBroussard@AOL.COM>
    • Re: Anyone know how....... (150 lines)
      From: Schneck.Glenn <Glenn.Schneck@SUNTRUST.COM>
    • Re: Anyone know how....... (38 lines)
      From: Rick Woods <Rick.Woods@AZDOA.GOV>

16. Are there any well regarded CICS certifications ?
    • Are there any well regarded CICS certifications ? (18 lines)
      From: Jon Bathmaker <JBathmaker@CSIHOME.COM>

17. Auto Install Model Problem . . .
    • Auto Install Model Problem . . . (38 lines)
      From: Jon Bathmaker <JBathmaker@CSIHOME.COM>
    • Re: Auto Install Model Problem . . . (58 lines)
      From: Barkow, Eileen <EBarkow@DOITT.NYC.GOV>

18. Bruce Lin/Dallas/IBM is out of the office.
    • Bruce Lin/Dallas/IBM is out of the office. (13 lines)
      From: Bruce Lin <blin@US.IBM.COM>

19. Bruce S Dennis/Nationwide/NWIE is out of the office.
    • Bruce S Dennis/Nationwide/NWIE is out of the office. (12 lines)
      From: Bruce Dennis <DENNISB2@NATIONWIDE.COM>

20. CA-View and alternate screen sizes
    • CA-View and alternate screen sizes (26 lines)
      From: Chase, John <jchase@USSCO.COM>

21. CA/IDEAL & CTS 3.1
    • CA/IDEAL & CTS 3.1 (20 lines)
      From: Scott Trost <TrostS@SCHNEIDER.COM>
    • Re: CA/IDEAL & CTS 3.1 (53 lines)
      From: Scott Trost <TrostS@SCHNEIDER.COM>

22. CATS package and using APPC
    • CATS package and using APPC (35 lines)
      From: james.nagy@HIGHMARK.COM

23. CICS AS400 DB2 and iSeries
    • CICS AS400 DB2 and iSeries (49 lines)
      From: Michael Potter <pottmi@GMAIL.COM>

24. CICS Forward Recovery
    • CICS Forward Recovery (22 lines)
      From: Klavon John R <klavon.jr@MELLON.COM>
    • Re: CICS Forward Recovery (54 lines)
      From: Kevin Cogley <KCOGLEY@HOUSTON.RR.COM>

25. CICS SOAP message compression
    • Re: CICS SOAP message compression (16 lines)
      From: Jordan, Bobby <BoJordan@GEICO.COM>

26. CICS Time Out Value
    • CICS Time Out Value (33 lines)
      From: Howard Rifkind <cics_l@YAHOO.COM>
    • Re: CICS Time Out Value (109 lines)
      From: Chase, John <jchase@USSCO.COM>
    • Re: CICS Time Out Value (53 lines)
      From: Howard Rifkind <cics_l@YAHOO.COM>

27. CICS Users join Webcast on Storage Violations
    • CICS Users join Webcast on Storage Violations (50 lines)
      From: Kathie D Bertram <kbertram@US.IBM.COM>

28. CICS V2.3 conversion
    • CICS V2.3 conversion (14 lines)
      From: Rick Woods <Rick.Woods@AZDOA.GOV>
    • Re: CICS V2.3 conversion (38 lines)
      From: Mullen, Patrick <Patrick.Mullen@GWL.CA>
    • Re: CICS V2.3 conversion (30 lines)
      From: Chase, John <jchase@USSCO.COM>
    • Re: CICS V2.3 conversion (48 lines)
      From: Jordan, Bobby <BoJordan@GEICO.COM>
    • Re: CICS V2.3 conversion (28 lines)
      From: wobconsult@sprynet.com <wobconsult@SPRYNET.COM>
    • Re: CICS V2.3 conversion (27 lines)
      From: Rick Woods <Rick.Woods@AZDOA.GOV>
    • Re: CICS V2.3 conversion (29 lines)
      From: John Hamman <JHamman@BCBSMS.COM>
    • Re: CICS V2.3 conversion (47 lines)
      From: Rick Woods <Rick.Woods@AZDOA.GOV>
    • Re: CICS V2.3 conversion (57 lines)
      From: Mullen, Patrick <Patrick.Mullen@GWL.CA>

29. CICS V4.1 to CICS TS V3.1?
    • CICS V4.1 to CICS TS V3.1? (53 lines)
      From: Vinson Lee <vlee@SDCCD.EDU>
    • Re: CICS V4.1 to CICS TS V3.1? (139 lines)
      From: Grinsell, Don <dgrinsell@MT.GOV>
    • Re: CICS V4.1 to CICS TS V3.1? (230 lines)
      From: Ward, David <david.ward@WAMU.NET>
    • Re: CICS V4.1 to CICS TS V3.1? (30 lines)
      From: Roland Schiradin <roland@SCHIRADIN.DE>
    • Re: CICS V4.1 to CICS TS V3.1? (40 lines)
      From: PCS <pcs305@YAHOO.COM>
    • Re: CICS V4.1 to CICS TS V3.1? (210 lines)
      From: Clark, Graham <Graham.Clark@ACS-INC.COM>
    • Re: CICS V4.1 to CICS TS V3.1? (37 lines)
      From: Vinson Lee <vlee@SDCCD.EDU>
    • Re: CICS V4.1 to CICS TS V3.1? (156 lines)
      From: Pat Mihalec <Pat_Mihalec@RUSH.EDU>

30. CICS conversion philosophy, etc
    • CICS conversion philosophy, etc (19 lines)
      From: Rick Woods <Rick.Woods@AZDOA.GOV>
    • Re: CICS conversion philosophy, etc (28 lines)
      From: Chase, John <jchase@USSCO.COM>
    • Re: CICS conversion philosophy, etc (47 lines)
      From: Mike Giaquinto <giaquint@WELLSFARGO.COM>
    • Re: CICS conversion philosophy, etc (114 lines)
      From: Richard A. Green <ragreen@GFB.ORG>
    • Re: CICS conversion philosophy, etc (69 lines)
      From: Rick Woods <Rick.Woods@AZDOA.GOV>
    • Re: CICS conversion philosophy, etc (104 lines)
      From: Francis ANDRE <francis.andre@EASYNET.FR>
    • Re: CICS conversion philosophy, etc (22 lines)
      From: Rick Woods <Rick.Woods@AZDOA.GOV>

31. CICS, Cobol, DB2 Programmers
    • CICS, Cobol, DB2 Programmers (50 lines)
      From: Robin Marsh <palladian1@SBCGLOBAL.NET>
    • Re: CICS, Cobol, DB2 Programmers (35 lines)
      From: wobconsult@sprynet.com <wobconsult@SPRYNET.COM>

32. CICS-L Digest - 18 Jul 2006 to 19 Jul 2006 (#2006-182)
    • Re: CICS-L Digest - 18 Jul 2006 to 19 Jul 2006 (#2006-182) (147 lines)
      From: Dean Grobowsky <dgrobows@CA.IBM.COM>

33. CICS-L NOMAIL
    • CICS-L NOMAIL (41 lines)
      From: ANDERSON Margaret * DAS IRMD GGDC <Margaret.Anderson@STATE.OR.US>
    • Re: CICS-L NOMAIL (27 lines)
      From: wobconsult@sprynet.com <wobconsult@SPRYNET.COM>

34. CICS-RACF Doubt
    • Re: CICS-RACF Doubt (319 lines)
      From: Sabater Frau, Pedro G. <psabater@BANCAMARCH.ES>
    • Re: CICS-RACF Doubt (138 lines)
      From: Derek Scrivens <derek.scrivens@TNT.COM>

35. CICS/COBOL (or Assembler) Base64 Conversion Routine
    • CICS/COBOL (or Assembler) Base64 Conversion Routine (93 lines)
      From: Wayne.Myers@BBH.COM
    • Re: CICS/COBOL (or Assembler) Base64 Conversion Routine (189 lines)
      From: ANDERSON Margaret * DAS IRMD GGDC <Margaret.Anderson@STATE.OR.US>
    • Re: CICS/COBOL (or Assembler) Base64 Conversion Routine (86 lines)
      From: Tony Thigpen <tony@VSE2PDF.COM>
    • Re: CICS/COBOL (or Assembler) Base64 Conversion Routine (101 lines)
      From: Barkow, Eileen <EBarkow@DOITT.NYC.GOV>
    • Re: CICS/COBOL (or Assembler) Base64 Conversion Routine (28 lines)
      From: PCS <pcs305@YAHOO.COM>
    • Re: CICS/COBOL (or Assembler) Base64 Conversion Routine (112 lines)
      From: Evans, Kevin R <kevin.r.evans@LMCO.COM>

36. Catch inefficient code sooner, deliver quality apps faster
    • Catch inefficient code sooner, deliver quality apps faster (281 lines)
      From: Galambos, Robert <Robert.Galambos@COMPUWARE.COM>
    • Re: Catch inefficient code sooner, deliver quality apps faster (20 lines)
      From: Rick Woods <Rick.Woods@AZDOA.GOV>
    • Re: Catch inefficient code sooner, deliver quality apps faster (39 lines)
      From: BOND Victor A <Victor.A.BOND@ODOT.STATE.OR.US>
    • Re: Catch inefficient code sooner, deliver quality apps faster (24 lines)
      From: Grinsell, Don <dgrinsell@MT.GOV>
    • Re: Catch inefficient code sooner, deliver quality apps faster (49 lines)
      From: Rick Woods <Rick.Woods@AZDOA.GOV>
    • Re: Catch inefficient code sooner, deliver quality apps faster (22 lines)
      From: BOND Victor A <Victor.A.BOND@ODOT.STATE.OR.US>
    • Re: Catch inefficient code sooner, deliver quality apps faster (68 lines)
      From: Barnard, John <John_Barnard@BMC.COM>
    • Re: Catch inefficient code sooner, deliver quality apps faster (88 lines)
      From: Gary Henderson <gary.henderson@ASG.COM>
    • Re: Catch inefficient code sooner, deliver quality apps faster (99 lines)
      From: Barnard, John <John_Barnard@BMC.COM>
    • Re: Catch inefficient code sooner, deliver quality apps faster (123 lines)
      From: Robin Marsh <palladian1@SBCGLOBAL.NET>
    • Re: Catch inefficient code sooner, deliver quality apps faster (78 lines)
      From: wobconsult@sprynet.com <wobconsult@SPRYNET.COM>
    • Re: Catch inefficient code sooner, deliver quality apps faster (22 lines)
      From: Rick Woods <Rick.Woods@AZDOA.GOV>
    • Re: Catch inefficient code sooner, deliver quality apps faster (25 lines)
      From: Ralph Robison <ralph_robison@COMPUWARE.COM>
    • Re: Catch inefficient code sooner, deliver quality apps faster (35 lines)
      From: Graham Hobbs <ghobbs@SYMPATICO.CA>
    • Re: Catch inefficient code sooner, deliver quality apps faster (99 lines)
      From: Havelock, Glenn A <Glenn.Havelock@CA.COM>
    • Re: Catch inefficient code sooner, deliver quality apps faster (24 lines)
      From: Chase, John <jchase@USSCO.COM>
    • Re: Catch inefficient code sooner, deliver quality apps faster (37 lines)
      From: Weiss, Mark <Mark.Weiss@COMPUWARE.COM>
    • Re: Catch inefficient code sooner, deliver quality apps faster (41 lines)
      From: Rick Woods <Rick.Woods@AZDOA.GOV>
    • Re: Catch inefficient code sooner, deliver quality apps faster (199 lines)
      From: Bruce Baxter <Bruce_Baxter@TAX.STATE.NY.US>
    • Re: Catch inefficient code sooner, deliver quality apps faster (334 lines)
      From: McKown, John <John.Mckown@HEALTHMARKETS.COM>
    • Re: Catch inefficient code sooner, deliver quality apps faster (63 lines)
      From: george bern <george_bern@YAHOO.COM>
    • Re: Catch inefficient code sooner, deliver quality apps faster (19 lines)
      From: Rick Woods <Rick.Woods@AZDOA.GOV>
    • Re: Catch inefficient code sooner, deliver quality apps faster (71 lines)
      From: Rico Juinio <ricojuinio@GMAIL.COM>
    • Re: Catch inefficient code sooner, deliver quality apps faster (99 lines)
      From: Prakash subramanian <sm.prakash@GMAIL.COM>

37. Cedf problem
    • Cedf problem (37 lines)
      From: Luis Ponce Melero <lpmelero@YAHOO.ES>
    • Re: Cedf problem (54 lines)
      From: Jordan, Bobby <BoJordan@GEICO.COM>
    • Re: Cedf problem (20 lines)
      From: Chase, John <jchase@USSCO.COM>
    • Re: Cedf problem (31 lines)
      From: Stephen M. Wiegand <swiegand@NEO.RR.COM>
    • Re: Cedf problem (55 lines)
      From: Jordan, Bobby <BoJordan@GEICO.COM>
    • Re: Cedf problem (91 lines)
      From: Lee Eshleman <leshlema@AESSUCCESS.ORG>
    • Re: Cedf problem (44 lines)
      From: Farley, Peter x23353 <Peter_Farley@ADP.COM>
    • Re: Cedf problem (68 lines)
      From: wobconsult@sprynet.com <wobconsult@SPRYNET.COM>
    • Re: Cedf problem (153 lines)
      From: Robert Zenuk <Robzenuk@AOL.COM>

38. Compatibility CICS/TS NOT
    • Compatibility CICS/TS NOT (31 lines)
      From: Martin <martin@PI-SYSPROG.DE>

39. Craig Nicholson is out of the office until June 25th 2006
    • Craig Nicholson is out of the office until June 25th 2006 (26 lines)
      From: marion_c._nicholson@HUD.GOV

40. DFHTRAP overhead
    • DFHTRAP overhead (20 lines)
      From: Francois LE MANER <francois.lemaner@FREE.FR>
    • Re: DFHTRAP overhead (34 lines)
      From: Samson, Roger <Roger.Samson@OA.MO.GOV>
    • Re: DFHTRAP overhead (48 lines)
      From: Barnard, John <John_Barnard@BMC.COM>
    • Re: DFHTRAP overhead (29 lines)
      From: Martin <martin@PI-SYSPROG.DE>
    • Re: DFHTRAP overhead (14 lines)
      From: Francois LE MANER <francois.lemaner@FREE.FR>
    • Re: DFHTRAP overhead (39 lines)
      From: Briggs, Arlyn <Arlyn.Briggs@UMB.COM>
    • Re: DFHTRAP overhead (13 lines)
      From: Francois LE MANER <francois.lemaner@FREE.FR>
    • Re: DFHTRAP overhead (93 lines)
      From: Carol Sutfin <csutfin@AMSOUTH.COM>
    • Re: DFHTRAP overhead (106 lines)
      From: SUE FINKELSTEIN <SFINKEL@PLANNING.NYC.GOV>
    • Re: DFHTRAP overhead (10 lines)
      From: Francois LE MANER <francois.lemaner@FREE.FR>
    • Re: DFHTRAP overhead (23 lines)
      From: Roland Schiradin <roland@SCHIRADIN.DE>

41. DR (was Catch inefficient code sooner, deliver quality apps faster)
    • DR (was Catch inefficient code sooner, deliver quality apps faster) (384 lines)
      From: Bruce Baxter <Bruce_Baxter@TAX.STATE.NY.US>
    • Re: DR (was Catch inefficient code sooner, deliver quality apps faster) (667 lines)
      From: Evans, Kevin R <kevin.r.evans@LMCO.COM>

42. David Hurlbert/KC/HALLMARK is out of the office.
    • David Hurlbert/KC/HALLMARK is out of the office. (20 lines)
      From: David Hurlbert <dhurlb1@HALLMARK.COM>

43. Duplicate entries en Mainview files
    • Duplicate entries en Mainview files (45 lines)
      From: Francois LE MANER <francois.lemaner@FREE.FR>

44. ENQMODEL
    • ENQMODEL (54 lines)
      From: Gaffney, Dave <Dave.Gaffney@CRA-ARC.GC.CA>

45. EYUXD0707E Message from EYU9XDUT
    • EYUXD0707E Message from EYU9XDUT (53 lines)
      From: Darwin Nash <IBM@DARWINNASH.COM>
    • Re: EYUXD0707E Message from EYU9XDUT (121 lines)
      From: Chase, John <jchase@USSCO.COM>
    • Re: EYUXD0707E Message from EYU9XDUT (108 lines)
      From: Schiradin,Roland HG-Dir itb-db/dc <SchiradinR@ALTE-LEIPZIGER.DE>
    • Re: EYUXD0707E Message from EYU9XDUT (86 lines)
      From: Darwin Nash <IBM@DARWINNASH.COM>
    • Re: EYUXD0707E Message from EYU9XDUT (107 lines)
      From: Darwin Nash <IBM@DARWINNASH.COM>
    • Re: EYUXD0707E Message from EYU9XDUT (82 lines)
      From: Schiradin,Roland HG-Dir itb-db/dc <SchiradinR@ALTE-LEIPZIGER.DE>

46. EZACIC01 OTE=YES/NO
    • EZACIC01 OTE=YES/NO (25 lines)
      From: Schiradin,Roland HG-Dir itb-db/dc <SchiradinR@ALTE-LEIPZIGER.DE>

47. Elena Nanos/IL/HCSC is out of the office.
    • Elena Nanos/IL/HCSC is out of the office. (27 lines)
      From: Elena Nanos <Elena_Nanos@BCBSIL.COM>
    • Elena Nanos/IL/HCSC is out of the office. (28 lines)
      From: Elena Nanos <Elena_Nanos@BCBSIL.COM>

48. Exec Cics Link and Cobol dynamic call
    • Exec Cics Link and Cobol dynamic call (229 lines)
      From: Reiner Schmidt <RSchmidt@VHV.DE>

49. Fabrice Jarassat/France/IBM is out of the office.
    • Fabrice Jarassat/France/IBM is out of the office. (12 lines)
      From: Fabrice Jarassat <fabrice.jarassat@FR.IBM.COM>

50. File open
    • File open (20 lines)
      From: Aaron Holland <aholland@AWGINC.COM>
    • Re: File open (157 lines)
      From: Clark, Graham <Graham.Clark@ACS-INC.COM>
    • Re: File open (111 lines)
      From: Aaron Holland <aholland@AWGINC.COM>
    • Re: File open (29 lines)
      From: Chase, John <jchase@USSCO.COM>

51. Find the program/Transaction which started to this Transaction
    • Find the program/Transaction which started to this Transaction (213 lines)
      From: Petluri, Srinivasa <Srinivasa.Petluri@FMR.COM>
    • Re: Find the program/Transaction which started to this Transaction (54 lines)
      From: Tony Saul <generalemaillists@YAHOO.COM.AU>
    • Re: Find the program/Transaction which started to this Transaction (252 lines)
      From: Chase, John <jchase@USSCO.COM>
    • Re: Find the program/Transaction which started to this Transaction (33 lines)
      From: Chase, John <jchase@USSCO.COM>

52. Fw: CICS V4.1 to CICS TS V3.1?
    • Fw: CICS V4.1 to CICS TS V3.1? (88 lines)
      From: Joseph Fatula <jfatula@AESSUCCESS.ORG>
    • Fw: CICS V4.1 to CICS TS V3.1? (24 lines)
      From: PCS <pcs305@YAHOO.COM>

53. Fw: Catch inefficient code sooner, deliver quality apps faster
    • Fw: Catch inefficient code sooner, deliver quality apps faster (83 lines)
      From: Joseph Fatula <jfatula@AESSUCCESS.ORG>

54. Fw: Fw: Fw: Program to test high CPU usage?
    • Fw: Fw: Fw: Program to test high CPU usage? (139 lines)
      From: Joseph Fatula <jfatula@AESSUCCESS.ORG>

55. Fw: Fw: Program to test high CPU usage?
    • Fw: Fw: Program to test high CPU usage? (113 lines)
      From: Joseph Fatula <jfatula@AESSUCCESS.ORG>

56. Fw: Program to test high CPU usage?
    • Fw: Program to test high CPU usage? (80 lines)
      From: Joseph Fatula <jfatula@AESSUCCESS.ORG>

57. Fw: VSAM CI Size & CICS
    • Fw: VSAM CI Size & CICS (131 lines)
      From: Joseph Fatula <jfatula@AESSUCCESS.ORG>

58. Fw: Yielding Loop
    • Fw: Yielding Loop (124 lines)
      From: Joseph Fatula <jfatula@AESSUCCESS.ORG>
    • Re: Fw: Yielding Loop (59 lines)
      From: Frank Swarbrick <frank.swarbrick@EFIRSTBANK.COM>
    • Re: Fw: Yielding Loop (73 lines)
      From: Evans, Kevin R <kevin.r.evans@LMCO.COM>
    • Re: Fw: Yielding Loop (88 lines)
      From: Barnard, John <John_Barnard@BMC.COM>
    • Re: Fw: Yielding Loop (100 lines)
      From: Evans, Kevin R <kevin.r.evans@LMCO.COM>

59. Fw: update timestanmp in CICS
    • Fw: update timestanmp in CICS (88 lines)
      From: Joseph Fatula <jfatula@AESSUCCESS.ORG>
    • Re: Fw: update timestanmp in CICS (11 lines)
      From: Judy Ellis <jellis@AMIG.COM>
    • Re: Fw: update timestanmp in CICS (36 lines)
      From: wobconsult@sprynet.com <wobconsult@SPRYNET.COM>
    • Re: Fw: update timestanmp in CICS (79 lines)
      From: Esposito, Richard (Exchange) <RESPOSITO@BEAR.COM>

60. GRNAME
    • Re: GRNAME (277 lines)
      From: Laughton, Mark <Mark.Laughton@UK.EXPERIAN.COM>
    • Re: GRNAME (212 lines)
      From: Fernando Morote <fmorote@BN.COM.PE>

61. George Potiris/ITM/DCC/DCX is out of the office.
    • George Potiris/ITM/DCC/DCX is out of the office. (13 lines)
      From: George Potiris <gp5@DAIMLERCHRYSLER.COM>
    • George Potiris/ITM/DCC/DCX is out of the office. (13 lines)
      From: gp5@DAIMLERCHRYSLER.COM

62. Help with trace entries
    • Help with trace entries (17 lines)
      From: Rick Stetser <RICK.STETSER@MCMASTER.COM>
    • Re: Help with trace entries (34 lines)
      From: wobconsult@sprynet.com <wobconsult@SPRYNET.COM>

63. Help: Precompiling variable length CICS C Source
    • Help: Precompiling variable length CICS C Source (59 lines)
      From: Francis ANDRE <francis.andre@EASYNET.FR>
    • Re: Help: Precompiling variable length CICS C Source (35 lines)
      From: Roland Schiradin <roland@SCHIRADIN.DE>

64. How do I find out which TOR transactions are routed to the AORs ?
    • Re: How do I find out which TOR transactions are routed to the AORs ? (104 lines)
      From: Jon Bathmaker <JBathmaker@CSIHOME.COM>

65. I am on vacation. Please contact Renee Bartels if you need immediate assistance.
    • I am on vacation. Please contact Renee Bartels if you need immediate assistance. (17 lines)
      From: Patricia Procknow <pprocknow@METLIFE.COM>

66. ISRLEMX substitution problem
    • ISRLEMX substitution problem (30 lines)
      From: Thomas L. Sipusic <sipusic@GEORGETOWN.EDU>

67. IXRJCL error installing support pack ca8i
    • IXRJCL error installing support pack ca8i (264 lines)
      From: Barkow, Eileen <EBarkow@DOITT.NYC.GOV>
    • Re: IXRJCL error installing support pack ca8i (244 lines)
      From: Thomas Davis <thomas.davis@AHOLDUSA.COM>
    • Re: IXRJCL error installing support pack ca8i (548 lines)
      From: Barkow, Eileen <EBarkow@DOITT.NYC.GOV>
    • Re: IXRJCL error installing support pack ca8i (466 lines)
      From: Briggs, Arlyn <Arlyn.Briggs@UMB.COM>
    • Re: IXRJCL error installing support pack ca8i (551 lines)
      From: Barkow, Eileen <EBarkow@DOITT.NYC.GOV>
    • Re: IXRJCL error installing support pack ca8i (614 lines)
      From: Briggs, Arlyn <Arlyn.Briggs@UMB.COM>
    • Re: IXRJCL error installing support pack ca8i (739 lines)
      From: Barkow, Eileen <EBarkow@DOITT.NYC.GOV>
    • Re: IXRJCL error installing support pack ca8i (543 lines)
      From: Robert Zenuk <Robzenuk@AOL.COM>
    • Re: IXRJCL error installing support pack ca8i (818 lines)
      From: Evans, Kevin R <kevin.r.evans@LMCO.COM>

68. Increased MSGUSR Output Due To CICS Internal Limitation
    • Increased MSGUSR Output Due To CICS Internal Limitation (135 lines)
      From: Wayne.Myers@BBH.COM
    • Re: Increased MSGUSR Output Due To CICS Internal Limitation (157 lines)
      From: Chase, John <jchase@USSCO.COM>
    • Re: Increased MSGUSR Output Due To CICS Internal Limitation (312 lines)
      From: Evans, Kevin R <kevin.r.evans@LMCO.COM>
    • Re: Increased MSGUSR Output Due To CICS Internal Limitation (264 lines)
      From: Grinsell, Don <dgrinsell@MT.GOV>
    • Re: Increased MSGUSR Output Due To CICS Internal Limitation (14 lines)
      From: Ray Parham <Ray.Parham@FIRSTCITIZENS.COM>
    • Increased MSGUSR Output Due To CICS Internal Limitation (232 lines)
      From: Wayne.Myers@BBH.COM

69. Is anyone using CICS TS 3.1's Web Services Capability?
    • Is anyone using CICS TS 3.1's Web Services Capability? (63 lines)
      From: Toole, Michael <MToole@AAAMICHIGAN.COM>
    • Re: Is anyone using CICS TS 3.1's Web Services Capability? (189 lines)
      From: Schneck.Glenn <Glenn.Schneck@SUNTRUST.COM>
    • Re: Is anyone using CICS TS 3.1's Web Services Capability? (241 lines)
      From: Toole, Michael <MToole@AAAMICHIGAN.COM>
    • Re: Is anyone using CICS TS 3.1's Web Services Capability? (284 lines)
      From: Schneck.Glenn <Glenn.Schneck@SUNTRUST.COM>
    • Re: Is anyone using CICS TS 3.1's Web Services Capability? (175 lines)
      From: Rakesh Kaushika <Rakesh_Kaushika@SECURA.NET>
    • Re: Is anyone using CICS TS 3.1's Web Services Capability? (40 lines)
      From: Laughton, Mark <Mark.Laughton@UK.EXPERIAN.COM>
    • Re: Is anyone using CICS TS 3.1's Web Services Capability? (286 lines)
      From: Jordan, Bobby <BoJordan@GEICO.COM>

70. John J. Leonard/Westfield Companies is out of the office.
    • John J. Leonard/Westfield Companies is out of the office. (21 lines)
      From: John J. Leonard <JohnLeonard@WESTFIELDGRP.COM>

71. Kathie Bertram is out of the office.
    • Kathie Bertram is out of the office. (30 lines)
      From: Kathie D Bertram <kbertram@US.IBM.COM>

72. Ken Taylor/RYE/US/Avon is out of the office.
    • Ken Taylor/RYE/US/Avon is out of the office. (12 lines)
      From: Ken Taylor <Ken.Taylor@AVON.COM>
    • Ken Taylor/RYE/US/Avon is out of the office. (12 lines)
      From: Ken Taylor <Ken.Taylor@AVON.COM>

73. LUTYPE6.1 trivia?
    • LUTYPE6.1 trivia? (17 lines)
      From: Phil Sidler <phil_sidler@HOTMAIL.COM>

74. Lee Eshleman is out of the office.
    • Lee Eshleman is out of the office. (22 lines)
      From: Lee Eshleman <leshlema@AESSUCCESS.ORG>

75. Manny Reyes/IL/HCSC is out of the office.
    • Manny Reyes/IL/HCSC is out of the office. (24 lines)
      From: Manny Reyes <REYESM1@BCBSIL.COM>

76. Marina Kmet/Australia/IBM is out of the office.
    • Marina Kmet/Australia/IBM is out of the office. (14 lines)
      From: Marina Kmet <mkmet@AU1.IBM.COM>

77. Mary McCaw/FlorhamPark/Pershing is out of the office.
    • Mary McCaw/FlorhamPark/Pershing is out of the office. (12 lines)
      From: Mary McCaw <MMcCaw@PERSHING.COM>

78. Measuring program loads.
    • Measuring program loads. (94 lines)
      From: Martland, George <George.Martland@SCHWAB.COM>
    • Re: Measuring program loads. (89 lines)
      From: Ivan Gelb <ivangelb@GMAIL.COM>
    • Re: Measuring program loads. (330 lines)
      From: Knutson, Sam <SKnutson@GEICO.COM>
    • Re: Measuring program loads. (409 lines)
      From: Schiradin,Roland HG-Dir itb-db/dc <SchiradinR@ALTE-LEIPZIGER.DE>
    • Re: Measuring program loads. (166 lines)
      From: Schiradin,Roland HG-Dir itb-db/dc <SchiradinR@ALTE-LEIPZIGER.DE>
    • Re: Measuring program loads. (169 lines)
      From: Knutson, Sam <SKnutson@GEICO.COM>
    • Re: Measuring program loads. (22 lines)
      From: Roland Schiradin <roland@SCHIRADIN.DE>
    • Re: Measuring program loads. (183 lines)
      From: Thomas H Puddicombe <tpuddico@CSC.COM>

79. Numerous DFHLG0747I messages at CICS start-up
    • Numerous DFHLG0747I messages at CICS start-up (192 lines)
      From: Brunner, Eric <Eric.Brunner@ATOSORIGIN.COM>
    • Re: Numerous DFHLG0747I messages at CICS start-up (259 lines)
      From: Clark, Graham <Graham.Clark@ACS-INC.COM>
    • Re: Numerous DFHLG0747I messages at CICS start-up (283 lines)
      From: Chiam, Susan Mee-Shia <Susan.Chiam@UNISYSWEST.COM.AU>
    • Re: Numerous DFHLG0747I messages at CICS start-up (101 lines)
      From: Chase, John <jchase@USSCO.COM>
    • Re: Numerous DFHLG0747I messages at CICS start-up (35 lines)
      From: Rick Woods <Rick.Woods@AZDOA.GOV>
    • Re: Numerous DFHLG0747I messages at CICS start-up (207 lines)
      From: Bruce Baxter <Bruce_Baxter@TAX.STATE.NY.US>
    • Re: Numerous DFHLG0747I messages at CICS start-up (300 lines)
      From: Clark, Graham <Graham.Clark@ACS-INC.COM>
    • Re: Numerous DFHLG0747I messages at CICS start-up (22 lines)
      From: Chase, John <jchase@USSCO.COM>
    • Re: Numerous DFHLG0747I messages at CICS start-up (80 lines)
      From: Chase, John <jchase@USSCO.COM>
    • Re: Numerous DFHLG0747I messages at CICS start-up (154 lines)
      From: Clark, Graham <Graham.Clark@ACS-INC.COM>
    • Re: Numerous DFHLG0747I messages at CICS start-up (25 lines)
      From: Rick Woods <Rick.Woods@AZDOA.GOV>
    • Re: Numerous DFHLG0747I messages at CICS start-up (26 lines)
      From: Chase, John <jchase@USSCO.COM>
    • Re: Numerous DFHLG0747I messages at CICS start-up (28 lines)
      From: Rick Woods <Rick.Woods@AZDOA.GOV>

80. Occasional high DISPWTT CICS-MQ Bridge
    • Occasional high DISPWTT CICS-MQ Bridge (124 lines)
      From: Thomas H Puddicombe <tpuddico@CSC.COM>
    • Re: Occasional high DISPWTT CICS-MQ Bridge (141 lines)
      From: Mike Giaquinto <giaquint@WELLSFARGO.COM>
    • Re: Occasional high DISPWTT CICS-MQ Bridge (96 lines)
      From: Thomas H Puddicombe <tpuddico@CSC.COM>

81. Omegamon replacements
    • Omegamon replacements (121 lines)
      From: Rugen, Len <RugenL@MISSOURI.EDU>
    • Re: Omegamon replacements (29 lines)
      From: Rick Woods <Rick.Woods@AZDOA.GOV>
    • Re: Omegamon replacements (44 lines)
      From: Barkow, Eileen <EBarkow@DOITT.NYC.GOV>
    • Re: Omegamon replacements (24 lines)
      From: Roland Schiradin <roland@SCHIRADIN.DE>

82. Outbound http
    • Outbound http (35 lines)
      From: Florence Mare <Florence.Mare@SITA.CO.ZA>
    • Re: Outbound http (59 lines)
      From: Branson, Susanne M <susanne-branson@UIOWA.EDU>
    • Re: Outbound http (28 lines)
      From: Adam Coulthard <a.p.coulthard@UK.IBM.COM>

83. Paul Johnson is out of the office.
    • Paul Johnson is out of the office. (13 lines)
      From: Paul Johnson <paul_johnson@UK.IBM.COM>

84. Preferred way to serve up images??
    • Preferred way to serve up images?? (22 lines)
      From: Briggs, Arlyn <Arlyn.Briggs@UMB.COM>
    • Re: Preferred way to serve up images?? (46 lines)
      From: Barkow, Eileen <EBarkow@DOITT.NYC.GOV>
    • Re: Preferred way to serve up images?? (58 lines)
      From: Cesar Alberto Hyssa Luiz <cesarhluiz@UOL.COM.BR>

85. Problem with DOCUMENT CREATE
    • Problem with DOCUMENT CREATE (41 lines)
      From: Martin <martin@PI-SYSPROG.DE>
    • Problem with DOCUMENT CREATE (22 lines)
      From: Martin <martin@PI-SYSPROG.DE>

86. Program to test high CPU usage?
    • Program to test high CPU usage? (24 lines)
      From: Antonio Lopez <cicswolf63@YAHOO.COM>
    • Re: Program to test high CPU usage? (33 lines)
      From: Edward Jaffe <edjaffe@PHOENIXSOFTWARE.COM>
    • Re: Program to test high CPU usage? (31 lines)
      From: Roland Schiradin <roland@SCHIRADIN.DE>
    • Re: Program to test high CPU usage? (10 lines)
      From: Jonathan Scott <jonathan_scott@VNET.IBM.COM>
    • Re: Program to test high CPU usage? (25 lines)
      From: Antonio Lopez <cicswolf63@YAHOO.COM>
    • Re: Program to test high CPU usage? (26 lines)
      From: Gordon Keehn <gordonkeehn@NETZERO.NET>
    • Re: Program to test high CPU usage? (30 lines)
      From: Edward Jaffe <edjaffe@PHOENIXSOFTWARE.COM>
    • Re: Program to test high CPU usage? (33 lines)
      From: Chase, John <jchase@USSCO.COM>
    • Re: Program to test high CPU usage? (25 lines)
      From: Edward Jaffe <edjaffe@PHOENIXSOFTWARE.COM>
    • Re: Program to test high CPU usage? (24 lines)
      From: Chase, John <jchase@USSCO.COM>
    • Re: Program to test high CPU usage? (153 lines)
      From: Thomas H Puddicombe <tpuddico@CSC.COM>
    • Re: Program to test high CPU usage? (84 lines)
      From: Lee, Gary D. <GLEE@BSU.EDU>
    • Re: Program to test high CPU usage? (118 lines)
      From: giaquint@WELLSFARGO.COM
    • Program to test high CPU usage? (33 lines)
      From: Sarma Kappagantu <sarma_kappagantu@YAHOO.CO.IN>

87. Quesiton about CICS system log
    • Quesiton about CICS system log (24 lines)
      From: Audrey Chen <audreyc.chen@GMAIL.COM>
    • Re: Quesiton about CICS system log (102 lines)
      From: Robert Zenuk <Robzenuk@AOL.COM>
    • Re: Quesiton about CICS system log (32 lines)
      From: Chase, John <jchase@USSCO.COM>
    • Re: Quesiton about CICS system log (15 lines)
      From: Audrey Chen <audreyc.chen@GMAIL.COM>

88. RACF commands under CICS
    • RACF commands under CICS (37 lines)
      From: Sergio Lima <sergiocics@YAHOO.COM.BR>
    • Re: RACF commands under CICS (41 lines)
      From: Rick Woods <Rick.Woods@AZDOA.GOV>
    • Re: RACF commands under CICS (148 lines)
      From: Len Rugen <rugenl@MISSOURI.EDU>
    • Re: RACF commands under CICS (298 lines)
      From: Knutson, Sam <SKnutson@GEICO.COM>
    • Re: RACF commands under CICS (49 lines)
      From: Itschak Mugzach <imugzach@ISRACARD.CO.IL>
    • Re: RACF commands under CICS (199 lines)
      From: Itschak Mugzach <imugzach@ISRACARD.CO.IL>
    • Re: RACF commands under CICS (49 lines)
      From: Itschak Mugzach <imugzach@ISRACARD.CO.IL>
    • Re: RACF commands under CICS (199 lines)
      From: Itschak Mugzach <imugzach@ISRACARD.CO.IL>
    • Re: RACF commands under CICS (208 lines)
      From: Bob Horne <rhorne@US.IBM.COM>
    • Re: RACF commands under CICS (17 lines)
      From: Roland Schiradin <roland@SCHIRADIN.DE>
    • Re: RACF commands under CICS (60 lines)
      From: Sergio Lima <sergiocics@YAHOO.COM.BR>
    • Re: RACF commands under CICS (33 lines)
      From: Sergio Lima <sergiocics@YAHOO.COM.BR>
    • Re: RACF commands under CICS (210 lines)
      From: Knutson, Sam <SKnutson@GEICO.COM>
    • Re: RACF commands under CICS (80 lines)
      From: Sergio Lima <sergiocics@YAHOO.COM.BR>
    • Re: RACF commands under CICS (97 lines)
      From: Sergio Lima <sergiocics@YAHOO.COM.BR>
    • Re: RACF commands under CICS (354 lines)
      From: Bob Horne <rhorne@US.IBM.COM>
    • Re: RACF commands under CICS (105 lines)
      From: Chase, John <jchase@USSCO.COM>
    • Re: RACF commands under CICS (25 lines)
      From: Antonio Lopez <cicswolf63@YAHOO.COM>

89. Reply to CICS/COBOL (or Assem
    • Reply to CICS/COBOL (or Assem (38 lines)
      From: Dwight C Giorgis <DCGIOR@WYDSPROD.STATE.WY.US>

90. Report
    • Report (69 lines)
      From: Bahman Saeedinia <saeedinia@HOTMAIL.COM>
    • Re: Report (143 lines)
      From: Schiradin,Roland HG-Dir itb-db/dc <SchiradinR@ALTE-LEIPZIGER.DE>
    • Re: Report (105 lines)
      From: Chase, John <jchase@USSCO.COM>

91. Robert Crawford/ORD/ALLTELCORP is out of the office.
    • Robert Crawford/ORD/ALLTELCORP is out of the office. (10 lines)
      From: Robert Crawford <robert.crawford@FNF.COM>
    • Robert Crawford/ORD/ALLTELCORP is out of the office. (10 lines)
      From: Robert Crawford <robert.crawford@FNF.COM>

92. SMPE error for CICS/TS 2.2 service install
    • SMPE error for CICS/TS 2.2 service install (182 lines)
      From: Jim McAlpine <Jim.McAlpine@CEDAR.COM>
    • Re: SMPE error for CICS/TS 2.2 service install (344 lines)
      From: Barkow, Eileen <EBarkow@DOITT.NYC.GOV>
    • Re: SMPE error for CICS/TS 2.2 service install (419 lines)
      From: Jim McAlpine <Jim.McAlpine@CEDAR.COM>
    • Re: SMPE error for CICS/TS 2.2 service install (36 lines)
      From: Roland Schiradin <roland@SCHIRADIN.DE>
    • Re: SMPE error for CICS/TS 2.2 service install (757 lines)
      From: Barkow, Eileen <EBarkow@DOITT.NYC.GOV>
    • Re: SMPE error for CICS/TS 2.2 service install (23 lines)
      From: PCS <pcs305@YAHOO.COM>
    • Re: SMPE error for CICS/TS 2.2 service install (395 lines)
      From: Hill, Jerry D. <HILLJE@AAFES.COM>
    • Re: SMPE error for CICS/TS 2.2 service install (764 lines)
      From: Jim McAlpine <Jim.McAlpine@CEDAR.COM>
    • Re: SMPE error for CICS/TS 2.2 service install (470 lines)
      From: Jim McAlpine <Jim.McAlpine@CEDAR.COM>
    • Re: SMPE error for CICS/TS 2.2 service install (637 lines)
      From: Hill, Jerry D. <HILLJE@AAFES.COM>
    • Re: SMPE error for CICS/TS 2.2 service install (708 lines)
      From: Jim McAlpine <Jim.McAlpine@CEDAR.COM>
    • Re: SMPE error for CICS/TS 2.2 service install (789 lines)
      From: Schiradin,Roland HG-Dir itb-db/dc <SchiradinR@ALTE-LEIPZIGER.DE>
    • Re: SMPE error for CICS/TS 2.2 service install (903 lines)
      From: Jim McAlpine <Jim.McAlpine@CEDAR.COM>

93. SOAP Translation Problem
    • SOAP Translation Problem (33 lines)
      From: Vince Smith <vince.smith@NCSECU.ORG>
    • Re: SOAP Translation Problem (73 lines)
      From: Barkow, Eileen <EBarkow@DOITT.NYC.GOV>

94. Sean Dilmore/Endicott/IBM is out of the office.
    • Sean Dilmore/Endicott/IBM is out of the office. (12 lines)
      From: Sean Dilmore <dilmores@US.IBM.COM>

95. TSQ 16 Character names
    • Re: TSQ 16 Character names (15 lines)
      From: Anand Kumar <anand_kvk@YAHOO.COM>

96. Tech Conference 2007 Poll results and more.
    • Tech Conference 2007 Poll results and more. (42 lines)
      From: PCS <pcs305@YAHOO.COM>

97. Tony Nestoras/DS/MICORP is out of the office.
    • Tony Nestoras/DS/MICORP is out of the office. (17 lines)
      From: Tony Nestoras <Tony.Nestoras@METAVANTE.COM>

98. UNSUBSCRIBE
    • UNSUBSCRIBE (76 lines)
      From: Mamilla, Swapna (Cognizant) <Swapna.Mamilla@COGNIZANT.COM>
    • Re: UNSUBSCRIBE (30 lines)
      From: wobconsult@sprynet.com <wobconsult@SPRYNET.COM>
    • UNSUBSCRIBE (12 lines)
      From: Sreekanth Dumpa <sreekanth.dumpa@PATNI.COM>

99. Unsubscribe
    • Unsubscribe (14 lines)
      From: jigar mehta <jigarmm@YAHOO.COM>

100. VSAM CI Size & CICS
     • VSAM CI Size & CICS (95 lines)
       From: Tara Debrodt <Tara.Debrodt@FIRSTDATA.COM.AU>
     • Re: VSAM CI Size & CICS (98 lines)
       From: Derek Scrivens <derek.scrivens@TNT.COM>
     • Re: VSAM CI Size & CICS (110 lines)
       From: Chase, John <jchase@USSCO.COM>
     • Re: VSAM CI Size & CICS (202 lines)
       From: Masters, Paul1 <paul1.masters@CITIGROUP.COM>
     • Re: VSAM CI Size & CICS (194 lines)
       From: Evans, Kevin R <kevin.r.evans@LMCO.COM>
     • Re: VSAM CI Size & CICS (79 lines)
       From: McKown, John <John.Mckown@HEALTHMARKETS.COM>
     • Re: VSAM CI Size & CICS (324 lines)
       From: Clark, Graham <Graham.Clark@ACS-INC.COM>
     • Re: VSAM CI Size & CICS (140 lines)
       From: Brendan Friel <Brendan_Friel@NOTES.NTRS.COM>
     • Re: VSAM CI Size & CICS (97 lines)
       From: wobconsult@sprynet.com <wobconsult@SPRYNET.COM>
     • Re: VSAM CI Size & CICS (66 lines)
       From: Robert Zenuk <Robzenuk@AOL.COM>
     • Re: VSAM CI Size & CICS (104 lines)
       From: McKown, John <John.Mckown@HEALTHMARKETS.COM>
     • Re: VSAM CI Size & CICS (249 lines)
       From: Evans, Kevin R <kevin.r.evans@LMCO.COM>
     • Re: VSAM CI Size & CICS (155 lines)
       From: Robert Zenuk <Robzenuk@AOL.COM>
     • Re: VSAM CI Size & CICS (195 lines)
       From: Robert Zenuk <Robzenuk@AOL.COM>
     • Re: VSAM CI Size & CICS (192 lines)
       From: Tara Debrodt <Tara.Debrodt@FIRSTDATA.COM.AU>
     • Re: VSAM CI Size & CICS (437 lines)
       From: Evans, Kevin R <kevin.r.evans@LMCO.COM>
     • Re: VSAM CI Size & CICS (142 lines)
       From: Lee Eshleman <leshlema@AESSUCCESS.ORG>
     • Re: VSAM CI Size & CICS (185 lines)
       From: Evans, Kevin R <kevin.r.evans@LMCO.COM>
     • Re: VSAM CI Size & CICS (190 lines)
       From: Rick Woods <Rick.Woods@AZDOA.GOV>
     • Re: VSAM CI Size & CICS (201 lines)
       From: Evans, Kevin R <kevin.r.evans@LMCO.COM>

101. Why use SSI in CICS?
     • Why use SSI in CICS? (17 lines)
       From: scott <svetter@AMERITECH.NET>
     • Re: Why use SSI in CICS? (30 lines)
       From: Schiradin,Roland HG-Dir itb-db/dc <SchiradinR@ALTE-LEIPZIGER.DE>
     • Re: Why use SSI in CICS? (37 lines)
       From: scott <svetter@AMERITECH.NET>
     • Re: Why use SSI in CICS? (56 lines)
       From: Schiradin,Roland HG-Dir itb-db/dc <SchiradinR@ALTE-LEIPZIGER.DE>
     • Re: Why use SSI in CICS? (102 lines)
       From: Farley, Peter x23353 <Peter_Farley@ADP.COM>
     • Why use SSI in CICS? (17 lines)
       From: Jonathan Scott <jonathan_scott@VNET.IBM.COM>
     • Re: Why use SSI in CICS? (95 lines)
       From: scott <svetter@AMERITECH.NET>
     • Re: Why use SSI in CICS? (31 lines)
       From: scott <svetter@AMERITECH.NET>

102. Will ' FREE=CLOSE' work for the SIT override parmlib???
     • Will ' FREE=CLOSE' work for the SIT override parmlib??? (261 lines)
       From: George Bly <gbly@BGNET.BGSU.EDU>
     • Will ' FREE=CLOSE' work for the SIT override parmlib??? (49 lines)
       From: Joseph Fatula <jfatula@AESSUCCESS.ORG>
     • Re: Will ' FREE=CLOSE' work for the SIT override parmlib??? (290 lines)
       From: Laughton, Mark <Mark.Laughton@UK.EXPERIAN.COM>
     • Re: Will ' FREE=CLOSE' work for the SIT override parmlib??? (371 lines)
       From: Itschak Mugzach <imugzach@ISRACARD.CO.IL>
     • Re: Will ' FREE=CLOSE' work for the SIT override parmlib??? (38 lines)
       From: Roland Schiradin <roland@SCHIRADIN.DE>
     • Re: Will ' FREE=CLOSE' work for the SIT override parmlib??? (176 lines)
       From: Chase, John <jchase@USSCO.COM>

103. Yielding Loop
     • Yielding Loop (150 lines)
       From: Baugh, Steve <Steve.Baugh@ANPAC.COM>
     • Re: Yielding Loop (210 lines)
       From: giaquint@WELLSFARGO.COM
     • Re: Yielding Loop (21 lines)
       From: Jonathan Scott <jonathan_scott@VNET.IBM.COM>
     • Re: Yielding Loop (258 lines)
       From: McKown, John <John.Mckown@HEALTHMARKETS.COM>
     • Re: Yielding Loop (397 lines)
       From: Samson, Roger <Roger.Samson@OA.MO.GOV>
     • Re: Yielding Loop (61 lines)
       From: Barry Brooks <barry@CNS.UFL.EDU>
     • Re: Yielding Loop (289 lines)
       From: Evans, Kevin R <kevin.r.evans@LMCO.COM>
     • Re: Yielding Loop (188 lines)
       From: McKown, John <John.Mckown@HEALTHMARKETS.COM>
     • Re: Yielding Loop (273 lines)
       From: Evans, Kevin R <kevin.r.evans@LMCO.COM>
     • Re: Yielding Loop (79 lines)
       From: Farley, Peter x23353 <Peter_Farley@ADP.COM>
     • Re: Yielding Loop (43 lines)
       From: Schiradin,Roland HG-Dir itb-db/dc <SchiradinR@ALTE-LEIPZIGER.DE>
     • Re: Yielding Loop (59 lines)
       From: Tom Schmidt <Tom.Schmidt@OASSOFTWARE.COM>
     • Re: Yielding Loop (86 lines)
       From: Farley, Peter x23353 <Peter_Farley@ADP.COM>
     • Re: Yielding Loop (89 lines)
       From: Joseph Fatula <jfatula@AESSUCCESS.ORG>
     • Re: Yielding Loop (109 lines)
       From: Evans, Kevin R <kevin.r.evans@LMCO.COM>
     • Re: Yielding Loop (96 lines)
       From: Evans, Kevin R <kevin.r.evans@LMCO.COM>
     • Re: Yielding Loop (273 lines)
       From: Laughton, Mark <Mark.Laughton@UK.EXPERIAN.COM>
     • Re: Yielding Loop (35 lines)
       From: Rick Woods <Rick.Woods@AZDOA.GOV>
     • Re: Yielding Loop (86 lines)
       From: Gary Henderson <gary.henderson@ASG.COM>
     • Re: Yielding Loop (65 lines)
       From: Evans, Kevin R <kevin.r.evans@LMCO.COM>
     • Re: Yielding Loop (37 lines)
       From: Joseph Fatula <jfatula@AESSUCCESS.ORG>
     • Re: Yielding Loop (60 lines)
       From: Evans, Kevin R <kevin.r.evans@LMCO.COM>
     • Re: Yielding Loop (94 lines)
       From: Rick Woods <Rick.Woods@AZDOA.GOV>
     • Re: Yielding Loop (125 lines)
       From: Gary Henderson <gary.henderson@ASG.COM>
     • Re: Yielding Loop (162 lines)
       From: Gary Henderson <gary.henderson@ASG.COM>

104. [From Vwall: Suspected SPAM]: Help with trace entries
     • Re: [From Vwall: Suspected SPAM]: Help with trace entries (31 lines)
       From: Barkow, Eileen <EBarkow@DOITT.NYC.GOV>

105. abendAPC3
     • abendAPC3 (29 lines)
       From: Francois LE MANER <francois.lemaner@FREE.FR>
     • Re: abendAPC3 (284 lines)
       From: Clark, Graham <Graham.Clark@ACS-INC.COM>
     • Re: abendAPC3 (19 lines)
       From: Francois LE MANER <francois.lemaner@FREE.FR>
     • Re: abendAPC3 (56 lines)
       From: Laughton, Mark <Mark.Laughton@UK.EXPERIAN.COM>
     • Re: abendAPC3 (62 lines)
       From: Laughton, Mark <Mark.Laughton@UK.EXPERIAN.COM>

106. cics transaction cpu collect statistics tmrcput
     • cics transaction cpu collect statistics tmrcput (25 lines)
       From: Albert Delahaye <albert.delahaye@INFOCO.BE>
     • Re: cics transaction cpu collect statistics tmrcput (94 lines)
       From: Laughton, Mark <Mark.Laughton@UK.EXPERIAN.COM>
     • Re: cics transaction cpu collect statistics tmrcput (148 lines)
       From: Barkow, Eileen <EBarkow@DOITT.NYC.GOV>

107. cics web service......
     • cics web service...... (73 lines)
       From: Güven Gücüyener <qfcyric@GMAIL.COM>
     • Re: cics web service...... (73 lines)
       From: Roland Schiradin <roland@SCHIRADIN.DE>

108. cics web services
     • cics web services (59 lines)
       From: Güven Gücüyener <qfcyric@GMAIL.COM>
     • Re: cics web services (37 lines)
       From: Roland Schiradin <roland@SCHIRADIN.DE>

109. cicsts23 xcf cicsts13 (mro)
     • cicsts23 xcf cicsts13 (mro) (48 lines)
       From: Fernando Morote <fmorote@BN.COM.PE>

110. how can I find all TSQ created by the specific program?
     • how can I find all TSQ created by the specific program? (20 lines)
       From: Hu Jun <hu_jun_1@YAHOO.COM.CN>
     • Re: how can I find all TSQ created by the specific program? (34 lines)
       From: Roland Schiradin <roland@SCHIRADIN.DE>

111. measure task cpu time consumption
     • measure task cpu time consumption (14 lines)
       From: Albert Delahaye <albert.delahaye@INFOCO.BE>
     • Re: measure task cpu time consumption (19 lines)
       From: Roland Schiradin <roland@SCHIRADIN.DE>
     • Re: measure task cpu time consumption (17 lines)
       From: Rick Woods <Rick.Woods@AZDOA.GOV>
     • Re: measure task cpu time consumption (31 lines)
       From: Albert Delahaye <albert.delahaye@INFOCO.BE>
     • Re: measure task cpu time consumption (55 lines)
       From: Cesar Alberto Hyssa Luiz <cesarhluiz@UOL.COM.BR>
     • Re: measure task cpu time consumption (43 lines)
       From: Roland Schiradin <roland@SCHIRADIN.DE>
     • Re: measure task cpu time consumption (189 lines)
       From: Schiradin,Roland HG-Dir itb-db/dc <SchiradinR@ALTE-LEIPZIGER.DE>
     • Re: measure task cpu time consumption (204 lines)
       From: Albert Delahaye <albert.delahaye@INFOCO.BE>
     • Re: measure task cpu time consumption (540 lines)
       From: cesarhluiz <cesarhluiz@UOL.COM.BR>

112. run plex1 or plex2
     • run plex1 or plex2 (103 lines)
       From: Fernando Morote <fmorote@BN.COM.PE>
     • Re: run plex1 or plex2 (246 lines)
       From: McKown, John <John.Mckown@HEALTHMARKETS.COM>
     • Re: run plex1 or plex2 (263 lines)
       From: Fernando Morote <fmorote@BN.COM.PE>

113. unsubscribe
     • unsubscribe (16 lines)
       From: Kalyan Rao <kk83@DAIMLERCHRYSLER.COM>

114. update timestanmp in CICS
     • update timestanmp in CICS (23 lines)
       From: Judy Ellis <jellis@AMIG.COM>
     • Re: update timestanmp in CICS (45 lines)
       From: Jim Anglim <Jim.Anglim@DARBYGROUP.COM>
     • Re: update timestanmp in CICS (57 lines)
       From: Chase, John <jchase@USSCO.COM>
     • Re: update timestanmp in CICS (74 lines)
       From: Jim Anglim <Jim.Anglim@DARBYGROUP.COM>

115. why I can't relase one load hold program?
     • why I can't relase one load hold program? (62 lines)
       From: Hu Jun <hu_jun_1@YAHOO.COM.CN>
     • Re: why I can't relase one load hold program? (33 lines)
       From: Martin <martin@PI-SYSPROG.DE>
     • Re: why I can't relase one load hold program? (44 lines)
       From: Lluch, Juan <LluchJ@CONED.COM>