batch file problem
Michel Adam
michel.adam at gmail.com
Fri Jun 8 13:10:38 CDT 2012
I am reminded again that humour doesn't travel well by email.
I was using the word 'feature' in the Microsoft sense of 'a bug that has been documented' :-)
The list of unresolved defects you could access on the defect tracking system is exactly what I was after. You mentioned it may be accessible by customers. That would work. How do I get access ?
m.
Envoyé de mon iFun
Le 2012-06-08 à 11:35, Bob Deskin <Bob.Deskin at ca.ibm.com> a écrit :
> There is no such list other than what's in the defect tracking system. I
> believe that there is customer web access. There are two issues here. The
> first is whether a feature works as documented and the other is whether
> the feature works as designed. Ideally, the two are the same but they may
> not be for a variety of reasons. I would suggest that 99%+ features work
> as documented and designed. For the remainder, there is a percentage where
> the example is incorrect or misleading. And there is a smaller percentage
> where the product does not work as per the example. This is one of those
> cases.
>
> As to why it has gone this long without being corrected, I don't know.
>
> Bob
>
>
>
> From: Michel Adam <michel.adam at gmail.com>
> To: Bob Deskin/Ottawa/IBM at IBMCA,
> Cc: ken weiland <ken_weiland at yahoo.com>, "powerh-l at lists.sowder.com"
> <powerh-l at lists.sowder.com>
> Date: 2012-06-08 01:06 PM
> Subject: Re: batch file problem
> Sent by: powerh-l-bounces+bob.deskin=ca.ibm.com at lists.sowder.com
>
>
>
> As one of the 'rem-ed' out line indicated, that had been my early
> approach. I was trying to minimize the changes to the code, which would
> have been possible to a greater extent had this 'feature' not been a
> feature :-(
>
> Which brings to mind the next question, Bob:
>
> Is there a list of unresolved 'features' for PH that you could share?
>
> We could then have a list of codearound for those.
>
> It would certainly save time knowing what is a feature ...
>
> m.
>
> Envoyé de mon iFun
>
> Le 2012-06-08 à 08:24, Bob Deskin <Bob.Deskin at ca.ibm.com> a écrit :
>
>> From a variety of inputs and my own testing, the example in the manual
>> does not work.
>>
>> There are a couple of suggested approaches. Both require putting the
>> responses into a file. Then you can target that file as the input source
>
>> when prompting using < or you can use the parmfile program parameter.
>>
>> Bob
>>
>>
>>
>> From: Michel Adam <michel.adam at gmail.com>
>> To: ken weiland <ken_weiland at yahoo.com>,
>> Cc: powerh-l at lists.sowder.com
>> Date: 2012-06-07 07:40 PM
>> Subject: Re: batch file problem
>> Sent by: powerh-l-bounces+bob.deskin=ca.ibm.com at lists.sowder.com
>>
>>
>>
>>
>> Nope. the blank line is actually not needed, since there are exactly as
>> many individual values supplied as are prompted.
>>
>> Simplifying, the following does not work:
>>
>> Created a batch file, xyz.bat, and tried it:
>>
>> C:\FOAMbin>type xyz.bat
>> QTP
>> ; comment
>> E
>>
>> C:\FOAMbin>xyz.bat
>>
>> C:\FOAMbin>QTP
>> IBM(R) Cognos(R) PowerHouse(R) 4GL 8.41G - QTP
>> (C) Copyright IBM Corp. 1982, 2010
>>
>>> e ; I am typing the 'e' manually, since QTP is just waiting with a '>'
>
>> prompt
>>
>> C:\FOAMbin>comment
>> 'comment' is not recognized as an internal or external command,
>> operable program or batch file.
>>
>> C:\FOAMbin>E
>> 'E' is not recognized as an internal or external command,
>> operable program or batch file.
>>
>> C:\FOAMbin>
>>
>> Michel
>>
>>
>>
>>
>> On Thu, Jun 7, 2012 at 5:09 PM, ken weiland <ken_weiland at yahoo.com>
> wrote:
>>
>> in your example you are doing the following
>> I have done a lot of mbatch qtp and quiz files with no problems
>>
>> if seems you are calling a quiz routine inside a qtp routine
>> then means you would need 2 exits are the end
>> c:
>>> cd \foambin
>>> rem QTP auto=C:\FOAMbin\XFSPR20D < %PHTEMP%\FFSPARAM.dat
>> -- calling qtp at this point
>>> QTP
>>> execute C:\FOAMbin\XFSPR20D
>>> 02
>>> @
>>> @
>>> @
>>>
>> -- calling quiz at this point but have not exited the qtp process
>>> execute C:\FOAMbin\XFSPR20Z
>>
>> this exits the quiz process that was started
>>> exit
>>
>> -- you are calling a quiz routine while still withing the qtp call
>>> QUIZ auto=C:\FOAMbin\XFSZR20Z
>> -- your are now back to qtp routine
>>
>> -- question why are you running XFSPR20Z twice?
>>
>>
>> let know if my thinking is correct
>> - you commented out the qtp auto that would have started qtp and shut it
>
>> down after it ran
>> and now call qtp manually
>> thus you have to add an exit qtp
>>
>> it looks like the batch stream is not correct
>> qtp auto...
>> quiz auto ...
>>
>> or
>>
>> qtp
>> execute ....
>> exit
>>
>> quiz
>> execute ...
>> exit
>>
>> or
>>
>> qtp
>> execute .....
>>
>> quiz
>> execute ....
>> exit
>>
>> exit
>>
>>
>>
>>
>>
>>
>> --
>> = = = = = = = = = = = = = = = = = = = = = = = = = = = =
>> Mailing list: powerh-l at lists.sowder.com
>> Subscribe: 'subscribe' in message body to
>> powerh-l-request at lists.sowder.com
>> Unsubscribe: 'unsubscribe <password>' in message body to
>> powerh-l-request at 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.
>> Add 'site:lists.sowder.com powerh-l' to your search terms to search the
>> list archive at Google.
>>
>
> --
> = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> Mailing list: powerh-l at lists.sowder.com
> Subscribe: 'subscribe' in message body to
> powerh-l-request at lists.sowder.com
> Unsubscribe: 'unsubscribe <password>' in message body to
> powerh-l-request at 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.
> Add 'site:lists.sowder.com powerh-l' to your search terms to search the
> list archive at Google.
>
More information about the powerh-l
mailing list