Using VEOPEN with PowerHouse on the HP-3000

Thu, 18 Mar 2004 10:22:38 -0000

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C40CD2.F001C5D0
Content-Type: text/plain;
	charset="iso-8859-1"

Walter,

If memory serves me correctly then this is a two step operation.

First you have to patch the QUIZ, QTP, QUICK and QDESIGN programs to call
VEOPEN instead of DBOPEN. Details of how to do this is as follows:

	:HELLO MANAGER.COGNOS,<group containing the PH version you want to
patch>
	:RUN VEOPEN.PUB.VESOFT,PATCH
	<enter the name of the program to be changed>
	<respond with 'V' to the Change it to call... message>

Next you will have to modify the PHRUNPROG UDC. Set the XL="" parameter in
the header to XL="VEOPENNL.PUB.VESOFT".

Remember to take a backup copy of the programs/udc before you patch/edit
them.

regards,

Robert W.Mills
Systems Development Manager
Windsong Services
(01689) 870622 x3005

Walter Murray <mailto:wmurray@midtown.net> wrote on 18 March 2004 03:06:

> 2004-03-17
> 
> Greetings,
> 
> I hope all you experts will be tolerant of this PowerHouse novice. 
> I'm 
> an old hand at the HP-3000 and MPE, but new to the wonderful world of
> Cognos software.
> 
> Can anyone share any experiences, tips, or pitfalls with using the
> VEOPEN procedure (part of SECURITY/3000 from VESOFT, Inc.), with
> PowerHouse applications?
> 
> I am in the midst of a project to eliminate IMAGE passwords that
> appear 
> in plain text in places like source code, job streams, schemas, etc.
> The goals are (1) to minimize the risk that someone looking through
> files or listings will discover a password he shouldn't know; and (2)
> to 
> make it easy to change a password without having to hunt down and
> change 
> every file that might contain that password.
> 
> I am using VEOPEN to accomplish this, and I have just about everything
> worked out except what I need to do with PowerHouse.
> 
> As I understand it (and please set me straight if I don't have this
> right), PowerHouse needs to know only one password for each IMAGE
> database, and that has to be a password that permits read and write
> access to all data sets and items.  That password appears in plain
> text 
> in the source schema, but apparently is encrypted in the compiled
> schema.  (I deduce this because I dumped a small compiled schema and
> didn't see any passwords.)
> 
> My plan is to remove the passwords from the PowerHouse schemas and
> recompile them.  According to the documentation, that will cause
> PowerHouse to use a semicolon password when calling DBOPEN, which
> normally wouldn't work, except for the creator of the database.
> 
> The trick, then, is to make sure that calls to DBOPEN from PowerHouse
> are intercepted by an XL that VESOFT provides, named
> VEOPENNL.PUB.VESOFT.  The VESOFT version of DBOPEN calls VEOPEN, when
> consults an Access Control File created by the Data Base
> Administrator. 
> If the user is authenticated, VEOPEN then gets the database password
> from the root file and passes it along in its call to the real version
> of DBOPEN.
> 
> What I need to do, then, is provide for PowerHouse programs to be
> bound 
> to VEOPENNL.PUB.VESOFT when they are loaded.
> 
> It looks as though all PowerHouse applications are invoked using a
> variety of UDCs, all of which seem to funnel through a single UDC,
> named 
> PHRUNPROG, which contains a single RUN command, which potentially
> contains a number of libraries in its XL list.  I propose simply to
> add VEOPENNL.PUB.VESOFT to the end of that list.
> 
> Is it that simple?  Will that work?  I spoke with support folks at
> both 
> VESOFT and Cognos this morning, but neither really knew anything about
> the other.  To his benefit, the Cognos support analyst invited me to
> share what I found out, to be added to their knowledge base.
> 
> Thanks for any help you can provide.  I apologize if this message is a
> great deal longer than it needs to be.
> 
> Walter, a stranger in PowerHouse paradise
> 
> Walter J. Murray
> 
> 
> = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> Mailing list: powerh-l@lists.sowder.com
> Subscribe: "subscribe" in message body to
> powerh-l-request@lists.sowder.com 
> Unsubscribe: "unsubscribe <password>" in message body to
> powerh-l-request@lists.sowder.com
> http://lists.sowder.com/mailman/listinfo/powerh-l 
> This list is closed, thus to post to the list you must be a
> subscriber. 

------_=_NextPart_001_01C40CD2.F001C5D0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>RE: Using VEOPEN with PowerHouse on the HP-3000</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Walter,</FONT>
</P>

<P><FONT SIZE=3D2>If memory serves me correctly then this is a two step =
operation.</FONT>
</P>

First you have to patch the QUIZ, QTP, QUICK and =
QDESIGN programs to call VEOPEN instead of DBOPEN. Details of how to do =
this is as follows:

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; :HELLO =
MANAGER.COGNOS,&lt;group containing the PH version you want to =
patch&gt;
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; :RUN =
VEOPEN.PUB.VESOFT,PATCH
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;enter =
the name of the program to be changed&gt;
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;respond with 'V' to the Change it to call... =
message&gt;

Next you will have to modify the PHRUNPROG UDC. Set =
the XL=3D&quot;&quot; parameter in the header to =
XL=3D&quot;VEOPENNL.PUB.VESOFT&quot;.

<P><FONT SIZE=3D2>Remember to take a backup copy of the programs/udc =
before you patch/edit them.</FONT>
</P>

<P><FONT SIZE=3D2>regards,</FONT>
</P>

<P><FONT SIZE=3D2>Robert W.Mills</FONT>
<BR><FONT SIZE=3D2>Systems Development Manager</FONT>
<BR><FONT SIZE=3D2>Windsong Services</FONT>
<BR><FONT SIZE=3D2>(01689) 870622 x3005</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Walter Murray &lt;<A =
HREF=3D"mailto:wmurray@midtown.net">mailto:wmurray@midtown.net</A>&gt; =
wrote on 18 March 2004 03:06:</FONT>
</P>

&gt; 2004-03-17
 &gt; 
 &gt; Greetings,
 &gt; 
 &gt; I hope all you experts will be tolerant of this =
PowerHouse novice. 
 &gt; I'm 
 &gt; an old hand at the HP-3000 and MPE, but new to =
the wonderful world of
 &gt; Cognos software.
 &gt; 
 &gt; Can anyone share any experiences, tips, or =
pitfalls with using the
 &gt; VEOPEN procedure (part of SECURITY/3000 from =
VESOFT, Inc.), with
 &gt; PowerHouse applications?
 &gt; 
 &gt; I am in the midst of a project to eliminate =
IMAGE passwords that
 &gt; appear 
 &gt; in plain text in places like source code, job =
streams, schemas, etc.
 &gt; The goals are (1) to minimize the risk that =
someone looking through
 &gt; files or listings will discover a password he =
shouldn't know; and (2)
 &gt; to 
 &gt; make it easy to change a password without =
having to hunt down and
 &gt; change 
 &gt; every file that might contain that =
password.
 &gt; 
 &gt; I am using VEOPEN to accomplish this, and I =
have just about everything
 &gt; worked out except what I need to do with =
PowerHouse.
 &gt; 
 &gt; As I understand it (and please set me straight =
if I don't have this
 &gt; right), PowerHouse needs to know only one =
password for each IMAGE
 &gt; database, and that has to be a password that =
permits read and write
 &gt; access to all data sets and items.&nbsp; That =
password appears in plain
 &gt; text 
 &gt; in the source schema, but apparently is =
encrypted in the compiled
 &gt; schema.&nbsp; (I deduce this because I dumped a =
small compiled schema and
 &gt; didn't see any passwords.)
 &gt; 
 &gt; My plan is to remove the passwords from the =
PowerHouse schemas and
 &gt; recompile them.&nbsp; According to the =
documentation, that will cause
 &gt; PowerHouse to use a semicolon password when =
calling DBOPEN, which
 &gt; normally wouldn't work, except for the creator =
of the database.
 &gt; 
 &gt; The trick, then, is to make sure that calls to =
DBOPEN from PowerHouse
 &gt; are intercepted by an XL that VESOFT provides, =
named
 &gt; VEOPENNL.PUB.VESOFT.&nbsp; The VESOFT version =
of DBOPEN calls VEOPEN, when
 &gt; consults an Access Control File created by the =
Data Base
 &gt; Administrator. 
 &gt; If the user is authenticated, VEOPEN then gets =
the database password
 &gt; from the root file and passes it along in its =
call to the real version
 &gt; of DBOPEN.
 &gt; 
 &gt; What I need to do, then, is provide for =
PowerHouse programs to be
 &gt; bound 
 &gt; to VEOPENNL.PUB.VESOFT when they are =
loaded.
 &gt; 
 &gt; It looks as though all PowerHouse applications =
are invoked using a
 &gt; variety of UDCs, all of which seem to funnel =
through a single UDC,
 &gt; named 
 &gt; PHRUNPROG, which contains a single RUN command, =
which potentially
 &gt; contains a number of libraries in its XL =
list.&nbsp; I propose simply to
 &gt; add VEOPENNL.PUB.VESOFT to the end of that =
list.
 &gt; 
 &gt; Is it that simple?&nbsp; Will that work?&nbsp; =
I spoke with support folks at
 &gt; both 
 &gt; VESOFT and Cognos this morning, but neither =
really knew anything about
 &gt; the other.&nbsp; To his benefit, the Cognos =
support analyst invited me to
 &gt; share what I found out, to be added to their =
knowledge base.
 &gt; 
 &gt; Thanks for any help you can provide.&nbsp; I =
apologize if this message is a
 &gt; great deal longer than it needs to be.
 &gt; 
 &gt; Walter, a stranger in PowerHouse =
paradise
 &gt; 
 &gt; Walter J. Murray
 &gt; 
 &gt; 
 &gt; =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =
=3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D
 &gt; Mailing list: powerh-l@lists.sowder.com
 &gt; Subscribe: &quot;subscribe&quot; in message =
body to
 &gt; powerh-l-request@lists.sowder.com 
 &gt; Unsubscribe: &quot;unsubscribe =
&lt;password&gt;&quot; in message body to
 &gt; powerh-l-request@lists.sowder.com
 &gt; <A =
HREF=3D"http://lists.sowder.com/mailman/listinfo/powerh-l" =
TARGET=3D"_blank">http://lists.sowder.com/mailman/listinfo/powerh-l</A> =

 &gt; This list is closed, thus to post to the list =
you must be a
 &gt; subscriber.

</BODY>
</HTML>
------_=_NextPart_001_01C40CD2.F001C5D0--