Multiple subfiles

[John Webster]

WARNING: The following response uses the word "sex". If you are in any way PC, please change this to "gender" ;-)
(BTW, we had an application where there were 5 values for sex - M, F, H, C, R)

(1) Check your data. Maybe the first 1000 records are sexless... or the sex is stored in lower case
(2) The need for qualification is explained in the Advanced PowerHouse course, but the only other place I've seen the "current file" concept discussed is the (ancient) PowerHouse PC manual. Here's the way it is explained:

IF two or more output files have a like-named record item AND the item statement for the record item does not explicitly identify the output file THEN QTP assumes the item statement is the "child" of the current file.

At the beginning of a request QTP sets the current file to blank.
When you enter an ACCESS statement, the primary file becomes the current file.
When you enter an OUTPUT statement, the specified file becomes the current file.
When you enter a SUBFILE statement, the specified subfile becomes the current file.
When you enter a DEFINE or TEMPORARY statement, PowerHouse resets the current file to blank.

In other words ALWAYS QUALIFY ALL REFERENCES TO RECORD ITEMS WITH AN "OF" QUALIFIER.

The codes? M=Mare, F=Filly, H=Horse, C=Colt, R=Rig
A rig is a horse with one undescended testicle, but this is probably more information than you need. 

----------
From: 	Thomson, Martyn EDUC:EX[SMTP:martyn.thomson@gems1.gov.bc.ca]
Sent: 	Tuesday, 26 January 1999 08:50
To: 	'POWERHOUSE Listserv'
Subject: 	RE: Multiple subfiles

> Thanks to Bob Deskin and John Penney for explaining this QTP 'feature' to
> me.
> So, the second unqualified reference to stud_sex is defaulting to the
> value in the first subfile, not the input file. 
> But there's still no output to either subfile if a sort is used (with or
> without qualification). Why is that?
> 
> ----------
> From: 	Deskin, Bob[SMTP:Bob.Deskin@Cognos.COM]
> Sent: 	January 25, 1999 9:38 AM
> To: 	'POWERHOUSE Listserv'
> Subject: 	RE: Multiple subfiles
> 
> The problem is which file the reference to STUD_SEX looks in. Try
> qualifying
> it with OF PEN_MASTER.
> 
> Bob Deskin              
> Senior Product Advisor  bob.deskin@cognos.com
> Cognos Inc.             (613) 738-1338 ext 4205 FAX: (613) 228-3149
> 3755 Riverside Drive P.O. Box 9707 Stn. T, Ottawa ON K1G 4K9 CANADA
> 
> 
> -----Original Message-----
> From: Thomson, Martyn EDUC:EX [mailto:martyn.thomson@gems1.gov.bc.ca]
> Sent: Monday, January 25, 1999 12:35 PM
> To: 'POWERHOUSE Listserv'
> Subject: Multiple subfiles
> 
> 
> Perhaps somebody could shed some light on this?  Why can I not have more
> than one subfile in a request?
> Consider the following simplified example -
> 
> run subtest
> request subtest
> set proc limit 1000
> access pen_master in pen
> subfile males keep if stud_sex='M'  &
> include stud_no of pen_master, stud_sex of pen_master
> subfile females keep if stud_sex='F'   &
> include stud_no of pen_master, stud_sex of pen_master
> build
> 
> On running this, records are written to the first subfile , but not the
> second!  If I switch the order of the subfiles - same result.  I've seen
> two
> subfiles in a request before, but outputting at different control breaks.
> If I put in a sort (say on stud_no), I don't get any output at all!  What
> is
> going on here?  I can't see anything in the QTP manual or the 7.10F4 RBF
> relating to this scenario. 
> Any help much appreciated.
> Using 7.10E1 on OpenVMS 6.1
> 
> Regards,
> Martyn Thomson
> Ministry of Education,
> B.C., Canada
> 
> 
>  
> 
> 
> = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> =
> 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.
> 
> 
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
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.