If you have PER-3:
d bear
HCPCDH6164E PER-3 hardware facility is not installed
Are you saying that some code that shoulld have called the pipeline by
CMSCALL actually did a branch and link? If so, let it call EXEC2 and
APAR that. Last I looked (admittedly some thirty years ago) EXEC2
EXECCOMM trashes all registers except R14 (it is certainly entitled to
do that). I learnt to be very wary of branching to EXECCOMM.
Or is the problem that the Pipeline's save area has been trashed? Might
it be branched to in 64-bit mode?
I did run the regression test when "they" built z/CMS originally.
On 25/06/14 11:39, Jonathan Scott wrote:
I get the same error (except for a different address).
The 0C1 occurs when a PIPE command is issued via the C system()
interface EDCSYSCM, which issues a CMSCALL. On return to
EDCSYSCM, the base register has been changed (and so have the
other registers) causing a wild branch. The command D BEAR is
very useful for tracking down wild branches!
Jonathan Scott
Glenn Knickerbocker wrote:
We're getting ready for the new level of PL/X and learned the compiler
only runs in z/CMS. This means, of course, testing out everything else
that needs to be used along with it in z/CMS. Here's a wacky one: The
v2r4 levels of the PL/X compiler abend in z/CMS if the uplevel Pipelines
is loaded.
DMSABE148T System abend 0C1 called from 0FE2F88C reason code 00000000
Figuring out whose fault this is is way beyond me. Oddly, loading the
product Pipelines with the PUSH option is sufficient to work around the
problem.
,R
