Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucbvax!DLRVMGO.BITNET!RZ7Y
From: RZ7Y@DLRVMGO.BITNET ("Jens Schleusener +49  709-2493", 551)
Newsgroups: comp.lang.asm370
Subject: (none)
Message-ID: <8906211938.AA19149@jade.berkeley.edu>
Date: 21 Jun 89 19:37:58 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: IBM 370 Assembly Programming Discussion List <ASM370%UCF1VM.bitnet@jade.berkeley.edu>
Distribution: inet
Organization: The Internet
Lines: 21
X-Unparsable-Date: Wed, 21 Jun 89 17:00:13 MEZ

Subject:       Return to CMS after PER breakpoint

In order to debug a new faulty crashing program normally I use the PER
command to stop execution at certain events.
After a stop the CP environment is entered and I use the DISPLAY command
to look at several relevant components to find out the error reason.
After that I use the BEGIN command to resume execution.
But if I found the error reason I often don't like to resume execution
because the program runs certainly into a terrible crash.

Is there another more elegant possibility in that situation to stop the
program and come back to CMS than a gigantic IPL CMS ?

Thanks in advance

Jens

P.S.: Using the DISPLAY command with the T as letter prefix allows
      a storage dump also with EBCDIC translation. But unfortunately
      only upper case letters are shown. Is there a possibility or
      utility to show also lower case letters (within CP environment) ?