Powerhouse screen failing to set value on detail record
Thurston, Alan JTST:EX
Alan.Thurston at gov.bc.ca
Wed Jan 25 11:34:37 CST 2017
Thanks Nicolas,
This seems to have done the trick. Way to simple!
Thanks!
Alan Thurston (Independent Contractor)
Working for the Ministry of Jobs, Tourism and Skills Training, and Responsible for Labour
250-882-4623 (cell)
From: nicholas.arniakos at externe.bnpparibas.com [mailto:nicholas.arniakos at externe.bnpparibas.com]
Sent: Tuesday, January 24, 2017 10:40 PM
To: Thurston, Alan JTST:EX
Cc: powerh-l at lists.sowder.com; powerh-l-bounces+nicholas.arniakos=bnpparibas.com at lists.sowder.com
Subject: Re: Powerhouse screen failing to set value on detail record
Good morning
Try to change the sequence of the PUT commands in update procedure in the loop. First HEARING_DATE then MEETING.
Regards, Nicholas
[Inactive hide details for Alan.Thurston---24/01/2017 20:45:36---A high level view of the business is that a CASE may have a HEA]Alan.Thurston---24/01/2017 20:45:36---A high level view of the business is that a CASE may have a HEARING. The hearing may happen over sev
Powerhouse screen failing to set value on detail record
(Internet)
Alan.Thurston
To:
powerh-l
24/01/2017 20:45
Sent by : powerh-l-bounces+nicholas.arniakos=bnpparibas.com at lists.sowder.com<mailto:powerh-l-bounces+nicholas.arniakos=bnpparibas.com at lists.sowder.com>
________________________________
A high level view of the business is that a CASE may have a HEARING. The hearing may happen over several days (HEARING_DATE) and on each of those dates there will be a MEETING.
The MEETING record has an attribute HRG_ID which stores the HRG_ID of the HEARING_DATE.
HRG_ID of the HEARING_DATE is the primary key and always has a correct value.
HRG_ID of the MEETING is meant to store the same value as HRG_ID of the HEARING_DATE.
I have a screen that includes the following files. This is the original source for the screen. The "item HRG_ID of MEETING" line under the file MEETING statement is the only place that HRG_ID of MEETING is given a value. Prior to migrating to Itanium this worked as expected.
file CASE_HEARING in LRBDB primary
access via CASE_ID using T_CASE_ID2
access via CASE_ID using CASE_ID request CASE_ID
access via CASE_ID, HRG_ID using T_CASE_ID, T_HRG_ID
item UPD_BY of CASE_HEARING final &
upshift(getsystemval("LRB_USER",logical,"LNM$JOB")) &
if alteredrecord of CASE_HEARING
item UPD_DTE of CASE_HEARING final sysdate if alteredrecord of CASE_HEARING
file HEARING_DATE in LRBDB detail occurs 9
access via HRG_ID using HRG_ID of CASE_HEARING &
orderby HRG_ACTUAL_DTE descending
select if &
(HRG_ACTUAL_DTE of HEARING_DATE >= CONSOLIDATION_DTE of CASE_HEARING &
and HRG_ACTUAL_DTE of HEARING_DATE <= WITHDRAWAL_DTE of CASE_HEARING) or &
(HRG_ACTUAL_DTE of HEARING_DATE >= CONSOLIDATION_DTE of CASE_HEARING &
and WITHDRAWAL_DTE of CASE_HEARING = 0) or &
CONSOLIDATION_DTE of CASE_HEARING = 0
item HRG_ID of HEARING_DATE final HRG_ID of CASE_HEARING
item UPD_BY of HEARING_DATE final &
upshift(getsystemval("LRB_USER",logical,"LNM$JOB")) &
if alteredrecord of HEARING_DATE
item UPD_DTE of HEARING_DATE final sysdate if alteredrecord of HEARING_DATE
file MEETING in LRBDB secondary occurs with HEARING_DATE
access via HRG_ID using HRG_ID of HEARING_DATE
item HRG_ID of MEETING final HRG_ID of HEARING_DATE <-------------- not working
item MTG_DTE of MEETING final HRG_ACTUAL_DTE of HEARING_DATE
item MTG_NAME of MEETING final HRG_NAME of HEARING
item MTG_START_TIME of MEETING final HRG_START_TIME of HEARING_DATE
item UPD_BY of MEETING final &
upshift(getsystemval("LRB_USER",logical,"LNM$JOB")) &
if alteredrecord of MEETING
item UPD_DTE of MEETING final sysdate if alteredrecord of MEETING
select if MTG_DTE of MEETING = HRG_ACTUAL_DTE of HEARING_DATE and &
MTG_START_TIME of MEETING = HRG_START_TIME of HEARING_DATE
After the move to Itanium this is no longer working consistently, sometimes does, more often does not, even with the same data entry sequence
I've tried a number of statements like "let HRG_ID of MEETING = HRG_ID of HEARING_DATE" at various points.
I went so far as to hard code the update procedure:
procedure update
begin
put HEARING
put CASE_HEARING
for HEARING_DATE
begin
let HRG_ID of MEETING = HRG_ID of HEARING
info = "Before PUT: HRG_ID of MEETING = " + ascii(HRG_ID of MEETING) now resp
put MEETING
put HEARING_DATE
info = "After PUT: HRG_ID of MEETING = " + ascii(HRG_ID of MEETING) now resp
end
end
The first info shows the expected correct HRG_ID. After the "put MEETING" the info statements shows a HRG_ID of 0 which is what gets stored in the database.
There are no database triggers than impact HRG_ID of MEETING
Any ideas as to how I could fix this?
Thanks!
Alan Thurston (Independent Contractor)
Working for the Ministry of Jobs, Tourism and Skills Training, and Responsible for Labour
250-882-4623 (cell)
--
= = = = = = = = = = = = = = = = = = = = = = = = = = = =
Mailing list: powerh-l at lists.sowder.com<mailto:powerh-l at lists.sowder.com>
Subscribe: 'subscribe' in message body to powerh-l-request at lists.sowder.com<mailto:powerh-l-request at lists.sowder.com>
Unsubscribe: 'unsubscribe <password>' in message body to powerh-l-request at lists.sowder.com<mailto: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.
This message and any attachments (the "message") is
intended solely for the intended addressees and is confidential.
If you receive this message in error,or are not the intended recipient(s),
please delete it and any copies from your systems and immediately notify
the sender. Any unauthorized view, use that does not comply with its purpose,
dissemination or disclosure, either whole or partial, is prohibited. Since the internet
cannot guarantee the integrity of this message which may not be reliable, BNP PARIBAS
(and its subsidiaries) shall not be liable for the message if modified, changed or falsified.
Do not print this message unless it is necessary,consider the environment.
----------------------------------------------------------------------------------------------------------------------------------
Ce message et toutes les pieces jointes (ci-apres le "message")
sont etablis a l'intention exclusive de ses destinataires et sont confidentiels.
Si vous recevez ce message par erreur ou s'il ne vous est pas destine,
merci de le detruire ainsi que toute copie de votre systeme et d'en avertir
immediatement l'expediteur. Toute lecture non autorisee, toute utilisation de
ce message qui n'est pas conforme a sa destination, toute diffusion ou toute
publication, totale ou partielle, est interdite. L'Internet ne permettant pas d'assurer
l'integrite de ce message electronique susceptible d'alteration, BNP Paribas
(et ses filiales) decline(nt) toute responsabilite au titre de ce message dans l'hypothese
ou il aurait ete modifie, deforme ou falsifie.
N'imprimez ce message que si necessaire, pensez a l'environnement.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sowder.com/pipermail/powerh-l/attachments/20170125/0e744af3/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 105 bytes
Desc: image001.gif
URL: <http://lists.sowder.com/pipermail/powerh-l/attachments/20170125/0e744af3/attachment-0001.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 168 bytes
Desc: image002.png
URL: <http://lists.sowder.com/pipermail/powerh-l/attachments/20170125/0e744af3/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 166 bytes
Desc: image003.png
URL: <http://lists.sowder.com/pipermail/powerh-l/attachments/20170125/0e744af3/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 167 bytes
Desc: image004.png
URL: <http://lists.sowder.com/pipermail/powerh-l/attachments/20170125/0e744af3/attachment-0007.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 168 bytes
Desc: image005.png
URL: <http://lists.sowder.com/pipermail/powerh-l/attachments/20170125/0e744af3/attachment-0008.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.png
Type: image/png
Size: 168 bytes
Desc: image006.png
URL: <http://lists.sowder.com/pipermail/powerh-l/attachments/20170125/0e744af3/attachment-0009.png>
More information about the powerh-l
mailing list