QTP question.

Joe Boyle atla38 at dsl.pipex.com
Mon Aug 29 13:14:47 CDT 2005 

for some reason I had it in my mind's eye that the subfile link WAS
optional; probably because that would complicate things even more :)

Regards, Joe.



-----Original Message-----
From: Darren Reely [mailto:darren.reely at latticesemi.com] 
Sent: 29 August 2005 19:11
To: Joe Boyle
Cc: 'Syed Shahul Hameed Mustaffa'; powerh-l at lists.sowder.com
Subject: Re: QTP question.

Considering there is no OPTION on any of the linked files, the two 
should return the equivalent rows. To prove it to your self Syed, run 
the two queries agaist your MPEIX system.

Darren


Joe Boyle wrote:
> the 2nd version will retrieve only as many rows as there are matched from
> the subfile, whereas the first version will retrieve all rows in the
> statement below for which there exists a record in the subfile, 
> 
> access   COW_LOC_D  IN CWDB                          &
>          link UNIT_NO to UNIT_NO of UNIT_M  IN CWDB  &
>          link CLD_COMPUTER_NO to CLD_COMPUTER_NO of COW_D IN CWDB &
> 
> Regards, Joe.
> 
> 
> 
> -----Original Message-----
> From: powerh-l-bounces+atla38=dsl.pipex.com at lists.sowder.com
> [mailto:powerh-l-bounces+atla38=dsl.pipex.com at lists.sowder.com] On Behalf
Of
> Syed Shahul Hameed Mustaffa
> Sent: 28 August 2005 15:02
> To: Deskin, Bob
> Cc: Joe Boyle; powerh-l at lists.sowder.com
> Subject: Re: QTP question.
> 
> Dear Joe, Bob,
> 
> As I'm coming from RDBMS background, I do not understand everything
> word for word.
> 
> I very sincerely appreciate your help and efforts in helping me out.
> 
> Pls. give me some explanation about the following two ACCESS statements.
>
----------------------------------------------------------------------------
> -----------------------------------
> (1) access   COW_LOC_D  IN CWDB                          &
>          link UNIT_NO to UNIT_NO of UNIT_M  IN CWDB  &
>          link CLD_COMPUTER_NO to CLD_COMPUTER_NO of COW_D IN CWDB &
>          link CLD_COMPUTER_NO to COMPUTER_NO  of
*$UEV_SUBFILE_PATH\CW877SF1
> 
> (2) access *$UEV_SUBFILE_PATH\CW877SF1 link COMPUTER_NO        &
>         to CLD_COMPUTER_NO of cow_loc_d in cwdb  &
>         link unit_no of cow_loc_d to unit_no of unit_m in cwdb	  &
>         link cld_computer_no of cow_loc_d to cld_computer_no of cow_d	 in
> cwdb
>
----------------------------------------------------------------------------
> ------------------------------------
> I have re-written (1) like (2). However, I do not understand the
> effect of my change.
> As advised by Bob, I've made the subfile as the primary file. Can you
> please point out if there is anything in (2) that'll change the
> meaning of (1).
> 
> Best Regards,
> SYED.
> On 8/28/05, Deskin, Bob <Bob.Deskin at cognos.com> wrote:
> 
>>Two corrections:
>>
>>First, PowerHouse still recognizes XBASE, however it does not use it for
> 
> indexed subfiles.
> 
>>Second, XBASE is not native to Windows, however it is free to use (as far
> 
> as I know) and is somewhat limited compared to other indexed file systems.
> 
>>It is this last point that prompted us to provide support for a more
> 
> complete indexed file system. Axiant has always had problems with indexed
> files and indexed subfiles because of the limitations of XBASE compared
with
> KSAM and C-ISAM. We knew this would be a problem for people migrating.
> Obviously we expect many of our customers to migrate to Windows from MPE
but
> we also have a number of people migrating from OpenVMS as well as looking
at
> Windows as an option to UNIX (for smaller systems). For all of these
reasons
> we decided to provide a more complete indexed file system and DISAM was
the
> one selected at the time (probably about 3-4 years back considering
> development time, beta testing, etc, etc).
> 
>>Bob
>>
>>-----Original Message-----
>>From: Joe Boyle [mailto:atla38 at dsl.pipex.com]
>>Sent: August 28, 2005 5:58 AM
>>To: Deskin, Bob; 'Syed Shahul Hameed Mustaffa'
>>Cc: powerh-l at lists.sowder.com
>>Subject: RE: QTP question.
>>
>>
>>Typically developers have indexed file access so they don't need to use
>>direct access.
>>
>>As cognos no longer recognize the windows XBASE format ( why is that ? ),
>>which is presumably that OS's native indexed file system, so using direct
>>access to subfiles will be used more often - probably.
>>
>>Regards, Joe.
>>
>>
>>-----Original Message-----
>>From: powerh-l-bounces+atla38=dsl.pipex.com at lists.sowder.com
>>[mailto:powerh-l-bounces+atla38=dsl.pipex.com at lists.sowder.com] On Behalf
> 
> Of
> 
>>Deskin, Bob
>>Sent: 28 August 2005 02:47
>>To: Syed Shahul Hameed Mustaffa; atla38 at dsl.pipex.com
>>Cc: powerh-l at lists.sowder.com
>>Subject: RE: QTP question.
>>
>>A non-indexed subfile can be linked using the record number. However, in
>>practise this is typically used only for a single record file. An
>>alternative is to put enough data in the subfile so that it can be used as
>>the driver for the linkage, i.e. the primary file in the ACCESS.
>>
>>Bob
>>
>>-----Original Message-----
>>From: Syed Shahul Hameed Mustaffa [mailto:sshahulgm at gmail.com]
>>Sent: August 27, 2005 12:08 PM
>>To: atla38 at dsl.pipex.com; Deskin, Bob
>>Cc: powerh-l at lists.sowder.com
>>Subject: Re: QTP question.
>>
>>
>>Dear Joe, Bob,
>>
>>If I remove the index keyword, then, I could not use the subfile in
>>the subsequent requests to link with other tables. Am I correct?
>>
>>Regards,
>>SYED
>>
>>On 8/26/05, Joe Boyle <atla38 at dsl.pipex.com> wrote:
>>
>>>I can see that Bob's option is the easiest to implement, but you could
>>>always implement the direct access method to subfiles; the disadvantage
> 
> is
> 
>>>that this will only work for single segment numeric indexes.
>>>
>>>The access syntax for this approach would be as follows,
>>>
>>>'link to record COMPUTER_NO of *$UEV_SUBFILE_PATH\CW877SF1'
>>>
>>>but there would be no pre-sorting capabilities as is the case when
>>
>>accessing
>>
>>>subfiles via indexes.
>>>
>>>To use the option above you would have to create a subfile with at least
>>
>>as
>>
>>>many records as you have COMPUTER_NO's, and instead of writing the
> 
> subfile
> 
>>>from qtp, you would process a 'output update' run against the subfile
>>
>>etc...
>>
>>>Regards, Joe.
>>>
>>>
>>>
>>>-----Original Message-----
>>>From: powerh-l-bounces+atla38=dsl.pipex.com at lists.sowder.com
>>>[mailto:powerh-l-bounces+atla38=dsl.pipex.com at lists.sowder.com] On
> 
> Behalf
> 
>>Of
>>
>>>Syed Shahul Hameed Mustaffa
>>>Sent: 25 August 2005 17:33
>>>To: powerh-l at lists.sowder.com
>>>Cc: Joe Boyle
>>>Subject: QTP question.
>>>
>>>Dear Gurus,
>>>
>>>Quick Intro: I'm migrating PH/MPEIX application to AXIANT-4GL/WINDOWS.
>>>
>>>Please look at the following excerpt of code.
>>>
>>
>
;---------------------------------------------------------------------------
> 
>>>------------
>>>request Extract-Rexam-Record
>>>
>>>access REEXAM_D IN CWDB &
>>>      link COMPUTER_NO to COMPUTER_NO of EVENT_D IN CWDB
>>>
>>>choose EPISODE_TYPE "EXAM"
>>>
>>>select if CW_DATE of REEXAM_D ge RX-DATE-FR and &
>>>         CW_DATE of REEXAM_D le RX-DATE-TO and &
>>>         EVENT_ACRONYM of REEXAM_D eq EVENT_ACRONYM of EVENT_D
>>>
>>>subfile $UEV_SUBFILE_PATH\CW877SF1  KEEP include     &
>>>       COMPUTER_NO of EVENT_D,           &
>>>       EVENT_ACRONYM of EVENT_D,         &
>>>       COMMENTS of EVENT_D,              &
>>>       ED_DATE of EVENT_D,               &
>>>       CW_DATE    &
>>>      index COMPUTER_NO ;segment COMPUTER_NO  ;<---- THIS LINE
>>>
>>>request Create-Final-Subfile
>>>
>>>access   COW_LOC_D  IN CWDB                          &
>>>  link UNIT_NO to UNIT_NO of UNIT_M  IN CWDB  &
>>>  link CLD_COMPUTER_NO to CLD_COMPUTER_NO of COW_D IN CWDB &
>>> link CLD_COMPUTER_NO to COMPUTER_NO of *$UEV_SUBFILE_PATH\CW877SF1
>>>;<---- THIS LINE
>>>
>>
>
;---------------------------------------------------------------------------
> 
>>>----------
>>>
>>>The lines I have marked as THIS LINE cannot execute without a DISAM
>>
>>license.
>>
>>>How can I rewrite this code to execute without a DISAM license.
>>>
>>>I'd appreciate every effort to help me out in this issue.
>>>
>>>Best Regards,
>>>SYED.
>>>
>>>--
>>>= = = = = = = = = = = = = = = = = = = = = = = = = = = =
>>>Mailing list: powerh-l at lists.sowder.com
>>>Subscribe: "subscribe" in message body to
>>
>>powerh-l-request at lists.sowder.com
>>
>>>Unsubscribe: "unsubscribe &lt;password&gt;" 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.
>>>
>>>
>>
>>      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.
>>
>>
>>
>>--
>>= = = = = = = = = = = = = = = = = = = = = = = = = = = =
>>Mailing list: powerh-l at lists.sowder.com
>>Subscribe: "subscribe" in message body to
> 
> powerh-l-request at lists.sowder.com
> 
>>Unsubscribe: "unsubscribe &lt;password&gt;" 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.
>>
>>
>>
> 
>

More information about the powerh-l mailing list