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_01C28B01.4C56CBA0
Content-Type: text/plain;
charset="iso-8859-1"
Hi Ole,
>From the look of your run command statement, your original solution was on a
unix machine? The unix shell is quite nice in that it supports redirection
of standard input using the '<' character, but as you can see, windows
doesn't have all the same functionality as unix.
Why not put the parameters into environment variables using the SETSYSTEMVAL
function from your screen, then read them into your report using the
GETSYSTEMVAL function? That should work on both unix and windows, and you
wouldn't need to declare a file in your screen or on the access statement of
your report.
The only point worth mention is that these functions return a boolean, so
need to be used within an if-then-else construct [if setsystemval(...) etc].
In your screen, a procedure can be used for this, and in the report use
defined items.
Best regards,
Mark Fry
Mark.Fry@Cognos.com
-----Original Message-----
From: Ole Hansen [mailto:oh@scanconsult.dk]
Sent: 13 November 2002 09:44
To: PowerHouse Listserver
Subject: Transfer of parameters in Axiant reports/qtp-runs
Hi!
I am trying to execute a report from an Axiant screen. The report requires a
parameter, e.g. :
access sometable
choose keyitem parm prompt "Enter key : "
In PowerHouse we put the value of 'keyitem' (and values for any other
prompted items) in a flat file, and runs the report through a run command :
run command "quiz auto=compiledreport < flatparameterfile"
If we try the same in Axiant, we get the following run time error : 'Invalid
or unrecognized keyword in program arguments : (<)'.
I do not want the user to be prompted by Axiant for the value of 'keyitem',
since this is just an arbitrary number, unknown to the user.
My present work-around is to have a local, user specific (XBASE-file) with
the value of keyitem, and the report modified as follows :
access xbasefile link xbasefileline to keyitem of sometable
This works satisfactorily for report with a choose parameter, but if other
parameters is to be transferred, the following is required :
access xbasefile link xbasefileline to keyitem of sometable &
link to record 1 of otherxbasefile
&
link to record 2 of otherxbasefile alias record2
define parm1 char*10 = xbasefileline of otherxbasefile
define parm2 char*10 = xbasefileline of record2
.... and this is of course not very efficient
Mange hilsner / With kind regards
Ole Hansen
===========================================================
E-mail: oh@scanconsult.dk Cell Phone: +45 4040 1150
===========================================================
ScanConsult IT-Partners ApS Voice : +45 8738 7474
Jegstrupvej 96A Fax : +45 8738 7475
DK-8361 Hasselager Support : support@scanconsult.dk
Denmark Sales : sales@scanconsult.dk
http://www.scanconsult.dk
= ParaSuite : A Suite of Air Cargo Handling solutions =
= ParaSafe : A Suite of IT-Security solutions =
= Partners : Hewlett-Packard, Cognos, Microsoft and more =
= = = = = = = = = = = = = = = = = = = = = = = = = = = =
Mailing list: powerh-l@lists.swau.edu
Subscribe: "subscribe" in message body to powerh-l-request@lists.swau.edu
Unsubscribe: "unsubscribe" in message body to
powerh-l-request@lists.swau.edu
http://lists.swau.edu/mailman/listinfo/powerh-l
This list is closed, thus to post to the list you must be a subscriber.
This message may contain privileged and/or confidential information. If you
have received this e-mail in error or are not the intended recipient, you
may not use, copy, disseminate or distribute it; do not open any
attachments, delete it immediately from your system and notify the sender
promptly by e-mail that you have done so. Thank you.
------_=_NextPart_001_01C28B01.4C56CBA0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
RE: Transfer of parameters in Axiant reports/qtp-runs
Hi Ole,
From the look of your run command statement, your =
original solution was on a unix machine? The unix shell is quite =
nice in that it supports redirection of standard input using the '<' =
character, but as you can see, windows doesn't have all the same =
functionality as unix.
Why not put the parameters into environment variables =
using the SETSYSTEMVAL function from your screen, then read them into =
your report using the GETSYSTEMVAL function? That should work on =
both unix and windows, and you wouldn't need to declare a file in your =
screen or on the access statement of your report.
The only point worth mention is that these functions =
return a boolean, so need to be used within an if-then-else construct =
[if setsystemval(...) etc]. In your screen, a procedure can be =
used for this, and in the report use defined items.
Best regards,
Mark Fry
Mark.Fry@Cognos.com
-----Original Message-----
From: Ole Hansen [mailto:oh@scanconsult.dk]
Sent: 13 November 2002 09:44
To: PowerHouse Listserver
Subject: Transfer of parameters in Axiant =
reports/qtp-runs
Hi!
I am trying to execute a report from an Axiant =
screen. The report requires a parameter, e.g. :
access sometable
choose keyitem parm prompt "Enter key : " =
In PowerHouse we put the value of 'keyitem' (and =
values for any other prompted items) in a flat file, and runs the =
report through a run command :
run command "quiz auto=3Dcompiledreport < =
flatparameterfile"
If we try the same in Axiant, we get the following =
run time error : 'Invalid or unrecognized keyword in program arguments =
: (<)'.
I do not want the user to be prompted by Axiant for =
the value of 'keyitem', since this is just an arbitrary number, unknown =
to the user.
My present work-around is to have a local, user =
specific (XBASE-file) with the value of keyitem, and the report =
modified as follows :
access xbasefile link xbasefileline to keyitem of =
sometable
This works satisfactorily for report with a choose =
parameter, but if other parameters is to be transferred, the following =
is required :
access xbasefile link xbasefileline to keyitem of =
sometable &
&nb=
sp; &nb=
sp; link to record 1 of =
otherxbasefile &nbs=
p; =
&
&nb=
sp; &nb=
sp; link to record 2 of otherxbasefile alias record2 =
define parm1 char*10 =3D xbasefileline of =
otherxbasefile
define parm2 char*10 =3D xbasefileline of =
record2
.... and this is of course not very efficient
Mange hilsner / With kind regards
Ole Hansen
=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=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=3D=3D=3D
E-mail: =
oh@scanconsult.dk Cell =
Phone: +45 4040 1150
=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=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=3D=3D=3D
ScanConsult IT-Partners =
ApS Voice : =
+45 8738 7474
Jegstrupvej =
96A &nb=
sp; =
Fax : +45 8738 7475
DK-8361 =
Hasselager Support : =
support@scanconsult.dk
Denmark &n=
bsp; =
Sales : sales@scanconsult.dk
&nb=
sp; http://www.scanconsult.dk &=
nbsp; =
=3D ParaSuite : A Suite of Air Cargo Handling =
solutions =3D
=3D ParaSafe : A Suite of IT-Security =
solutions =
=3D
=3D Partners : Hewlett-Packard, Cognos, =
Microsoft and more =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 =3D
Mailing list: powerh-l@lists.swau.edu
Subscribe: "subscribe" in message body to =
powerh-l-request@lists.swau.edu
Unsubscribe: "unsubscribe" in message body =
to powerh-l-request@lists.swau.edu
http://lists.swau.edu/mailman/listinfo/powerh-l
This list is closed, thus to post to the list you =
must be a subscriber.
This message may contain privileged and/or =
confidential information. If you have received this e-mail in =
error or are not the intended recipient, you may not use, copy, =
disseminate or distribute it; do not open any attachments, delete it =
immediately from your system and notify the sender promptly by e-mail =
that you have done so. Thank you.
------_=_NextPart_001_01C28B01.4C56CBA0--