HP MPE -- QDESIGN inside QEDIT in a job

Cummings, Ken P. KPCUMMIN@gapac.com
Thu, 15 Oct 1998 12:44:59 -0400


Allison:

Thank you so much.  That solved the problem instantly.  We appreciate it
greatly.

> ----------
> From: 	Hamilton, Allison[SMTP:Allison.Hamilton@Cognos.COM]
> Sent: 	Thursday, October 15, 1998 12:11 PM
> To: 	'PowerHouse Discussion List'; Cummings, Ken P.
> Cc: 	Dulworth, Amanda L.
> Subject: 	RE: HP MPE -- QDESIGN inside QEDIT in a job
> 
> From one of the 8.19 developers... 
> 
> By explicitly running QDESIGN instead of using the UDC, they're not
> getting
> some of the environment set up correctly.  The simplest solution is
> probably
> to set up the environment within their job before starting QEDIT.  This
> can
> be done by adding the command "SETPOWERHOUSE" to their job file.
> 
> Alternatively, they can just set up the specific variable that they're
> missing - either within the job file or in QDESIGNE.PUB.  The statement to
> do this is:
> SETVAR COGNLSTAB "COGLANG.PH819C1.COGNOS"
> Allison Hamilton
> 
> > ----------
> > From: 	Cummings, Ken P.[SMTP:KPCUMMIN@gapac.com]
> > Sent: 	Thursday, October 15, 1998 11:21 AM
> > To: 	'PowerHouse Discussion List'
> > Cc: 	Dulworth, Amanda L.
> > Subject: 	HP MPE -- QDESIGN inside QEDIT in a job
> > 
> > We have had a PUB file that we have been using for a long time with
> > version
> > 7.29.  The QDESIGNE.PUB file contains the following:
> > 
> > 	FILE PHD=OPD729.PDL
> > 	RUN QDESIGN.PH729C2.COGNOS;INFO=" "
> > 
> > We use this to overcome a limitation that prevents us from using QDESIGN
> > within QEDIT in a job.  We need to do this because we have a job that
> > recompiles all of our QUICK code using QEDIT -- we run QDESIGN within
> > QEDIT
> > to perform the compile.
> > 
> > When we try to do the same thing with version 8.19, we get the following
> > error when we try and run the PUB file:
> > 
> > 	:PRINT QDESIGNE.PUB
> > 	FILE PHD=OPD819.PDL
> > 	RUN QDESIGN.PH819C1.COGNOS;INFO=" "
> > 
> > 	:QDESIGNE
> > 
> > 	*E* The COGNLSTAB environment variable must be set.
> > 
> > Does anyone have a clue what this means and how we can circumvent or
> solve
> > the problem?
> > 
> > Thanks!
> > Ken.
> > 
> > 
> > ----------------------------------------------------------------------
> >           Ken Cummings
> >           Senior Consultant
> >           VersaComp Systems Inc.
> >           cummingsk@versacomp.com
> >           kpcummin@gapac.com
> >           404-652-6250
> > 
> > = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> =
> > =
> > Subscribe: "subscribe powerh-l" in message body to
> > majordomo@lists.swau.edu
> > Unsubscribe: "unsubscribe powerh-l" in message to
> majordomo@lists.swau.edu
> > powerh-l@lists.swau.edu is gatewayed one-way to bit.listserv.powerh-l
> > This list is closed, thus to post to the list, you must be a subscriber.
> > 
> 
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Subscribe: "subscribe powerh-l" in message body to majordomo@lists.swau.edu
Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.edu
powerh-l@lists.swau.edu is gatewayed one-way to bit.listserv.powerh-l
This list is closed, thus to post to the list, you must be a subscriber.