Lizette,
It seems that the behavior I described is the expected behavior
for the console
service if either BPX.CONSOLE is not defined or it is defined but the
caller does not have the
proper permissions. At my shop, BPX.CONSOLE is not defined so I receive
the BPXM023I message
with the callers ID prefixed to the message. This behavior is described
in
UNIX System Services Programming: Assembler Callable Services under the
discussion of the _console service.
I added the BPX.CONSOLE profile on my sandbox system and restarted EKM and
got the messages in the form
you did. The solution for you would seem to be to either remove the
profile or the EKM server IDs access to it.
Jim
"Lizette Koehler <stars...@mindspring.com> wrote on 01/01/2009 09:36:46"
> Date: Thu, 1 Jan 2009 09:30:46 -0500
> From: Lizette Koehler <stars...@mindspring.com>
> Subject: Re: Shell Scripts in EKM
>
> Yes we are running JZOS batch loader and EKM as an STC. However, we
have no
> BPXM023I messages. Only the text of the messages. I have asked IBM
about
> this and they indicated it has to do with the BPX.CONSOLE profile. How
is
> yours set for EKM STC? Is EKM STC in the access list?
>
> Lizette
>
>
> > -----Original Message-----
> > From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On
> Behalf Of
> > Jim Holloway
> > Sent: Thursday, January 01, 2009 9:23 AM
> > To: IBM-MAIN@bama.ua.edu
> > Subject: Re: Shell Scripts in EKM
> >
> > Are you running the EKM Server under MVS with JZOS batch loader? While
I
> > agree
> > with you both concerning the lousy messaging, running the EKM Server
as a
> > started
> > task with the batch loader modifies the message enough for automation
(we
> > use BMC)
> > to pickup on the fact that EKM is up and available.
> >
> > When we start EKM we get the following:
> >
> > 08363 02:52:24.47 STC09716 000A0294 BPXM023I (EKMSERV) Processing
> > 08363 02:52:24.47 STC09716 00000090 BPXM023I (EKMSERV) Server is
started
> >
> > 08363 02:52:24.47 STC09716 000A0294 BPXM023I (EKMSERV) Server is
running.
> > TCP port: 3801, SSL port: 5443
> > 08363 02:52:24.47 STC09716 000A0294 BPXM023I (EKMSERV) Server is
running.
> > TCP port: 3801, SSL port: 5443
> >
> > We key off the BPXM023I message looking for EKMSERV
> >
> >
> > Jim Holloway - MetLife
> >
> >
> > "Hunkeler Peter (KIUK 3)" wrote on 12/31/2008 10:41:13 +0100
> > >
> > > Date: Wed, 31 Dec 2008 10:41:13 +0100
> > > From: "Hunkeler Peter (KIUK 3)"
<peter.hunke...@credit-suisse.com>
> > > Subject: Re: Shell Scripts in EKM
> > >
> > > >The reason is our EMK server on z/OS V1.9 does not
> > > >have any message IDs, so all we get is the following text:
> > > >
> > > >Server is running. TCP port: 3801, SSL port: 1443
> > >
> > > Seems like inacceptable behaviour for a software to be run
> > > on z/OS. I'd try to open a PMR requesting identifiable messages.
> > >
> > > --
> > > Peter Hunkeler
> > > Credit Suisse
> >
> > >
> > > Date: Wed, 31 Dec 2008 05:40:33 -0500
> > > From: Lizette Koehler <stars...@mindspring.com>
> > > Subject: Re: Shell Scripts in EKM
> > >
> > > I have already done that. A requirements hasw been accepted. But
with
> > > ported applications I am not sure how long it will take for IBM to
> > action
> > > this. Not enough z/OS Users or tape encryption to put pressure on
> > sooner
> > > than later.
> > >
> > > So in the meantime, I am hoping a shell script could be created that
> > will
> > > give us the message we need for automation.
> > >
> > > Lizette
> >
The information contained in this message may be CONFIDENTIAL and is for the
intended addressee only. Any unauthorized use, dissemination of the
information, or copying of this message is prohibited. If you are not the
intended addressee, please notify the sender immediately and delete this
message.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
