Re: [Hardhats-members] Another GTM error
It sure does. Another possibility, though one I had not expected, is that the template you are using has some navigation built into it leading to an unanticipated loop. From within Menu Manager, you can get the option name by typing ??. Once you know the option name, you can look up the routine or template name in the OPTION file, If it's a routine, it will typically invoke an input template by setting DR equal to something like [TEMPLATE_NAME] and call ^DIE (I know, it's a terrible name, but DI is the Fileman namespace and E stands for edit.) Setting D0 equal to the internal entry number of the template, you can D ^DIET (another interesting name!) to get a textual representation of the template contents -- or, of course, you can edit it within Fileman, or just include computed values in the output of a Fileman inquiry. === Gregory Woodhouse [EMAIL PROTECTED] The whole of science is nothing more than a refinement of everyday thinking. -- Albert Einstein On May 31, 2005, at 9:11 PM, Bhaskar, KS wrote: This confirms that it was not a database structural integrity issue, but rather a database content issue. -- Bhaskar -Original Message- From:[EMAIL PROTECTED] on behalf of Usha Sent:Tue 5/31/2005 11:38 PM To:hardhats-members@lists.sourceforge.net Cc: Subject:Re: [Hardhats-members] Another GTM error I tried the mupip integ when the problem startted, bu no errors were reported. But I have been able to overcome the problem, for the time being, by installing a KIDS patch of the correct NEW PERSON file. Thanks Usha winmail.dat --- This SF.Net email is sponsored by Yahoo. Introducing Yahoo! Search Developer Network - Create apps using Yahoo! Search APIs Find out how you can build Yahoo! directly into your own Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005 ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
Re: [Hardhats-members] Another GTM error
Generally, this kind of problem requires looking at data structures rather than code tracing. You often need to look only a little bit at the code to find the relevant variables and then use ZWRITE or other tools to view the data values. Looping like Usha reports generally comes from a stepping algorithm that trips over a non-canonic number where a canonic number was assumed. For example: s test(ted,1.1)=,test(ben,.01)=,test(joe,1.0)=,name= f n=0:0 s name=$o(test(name)) q:name= d . f i=0:0 s i=$o(test(name,i)) q:'i s n=n+1 w !,n,?5,name,?10,i q:n9 It may be too late now to see the data that caused the problem, but what do you get from ZWRITE ^DD(200,B,*)? Kevin wrote: The only thing I can think to figure this out would be to trace through the code step by step. And what a dark prospect this is! You can step through using Serenji (best), or I have a bare-bones debugger for using with only GT.M if you are interested. Kevin --- Usha [EMAIL PROTECTED] wrote: After executing the command on the GT.M prompt, I deleted the LABEL Certification. Now when I try to get the list of all the fields of NEW PERSON file, after listing some fields, BOARD ELIGIBLE is displayed infinitely. This is the list of fields in the NEW PERSON file from the DATA DICTIONARY option. .01 NAME .111 STREET ADDRESS 1 .112 STREET ADDRESS 2 .113 STREET ADDRESS 3 .114 CITY .115 STATE .116 ZIP CODE .1211TEMPORARY ADDRESS 1 .1212TEMPORARY ADDRESS 2 .1213TEMPORARY ADDRESS 3 .1214TEMPORARY CITY .1215TEMPORARY STATE .1216TEMPORARY ZIP CODE .1217START DATE OF TEMP ADDRES .1218END DATE OF TEMP ADDRESS .131 PHONE (HOME) .132 OFFICE PHONE .133 PHONE #3 .134 PHONE #4 .135 COMMERCIAL PHONE .136 FAX NUMBER .137 VOICE PAGER .138 DIGITAL PAGER .141 ROOM .151 EMAIL ADDRESS 1INITIAL 2ACCESS CODE 2.1 Want to edit ACCESS CODE (Y/N) 2.2 DATE ACCESS CODE LAST CHANGED 3FILE MANAGER ACCESS CODE 4SEX 5DOB 7DISUSER 7.2 VERIFY CODE never expires 8TITLE 9SSN 9.2 TERMINATION DATE 9.21 DELETE ALL MAIL ACCESS 9.22 DELETE KEYS AT TERMINATION 9.3 TERMINAL TYPE LAST USED 9.4 Termination Reason 10 ALIAS 10.1 NAME COMPONENTS 10.6 DEGREE 11 VERIFY CODE 11.1 Want to edit VERIFY CODE (Y/N) 11.2 DATE VERIFY CODE LAST CHANGED 11.6 ALLOW ARA ACCESS 11.7 ARA VALUE 12.1 CURRENT DEGREE LEVEL 12.2 PROGRAM OF STUDY 12.3 LAST TRAINING YEAR 13 NICK NAME 14 PAC 14.9 HINQ EMPLOYEE NUMBER 15 PROHIBITED TIMES FOR SIGN-ON 16 DIVISION 19 DELEGATE OF 19.1 DELEGATION DATE 19.2 DELEGATION LEVEL 19.4 ALERT DATE/TIME 19.5 DELEGATED OPTIONS 19.6 ALLOWABLE NEW MENU PREFIX 19.8 MENU TEMPLATE 20 UCI 20.1 DATE E-SIG LAST CHANGED 20.2 SIGNATURE BLOCK PRINTED NAME 20.3 SIGNATURE BLOCK TITLE 20.4 ELECTRONIC SIGNATURE CODE 28 MAIL CODE 29 SERVICE/SECTION 30 DATE ENTERED 31 CREATOR 31.1 FILE RANGE 31.2 TEXT TERMINATOR 31.3 PREFERRED EDITOR 32 ACCESSIBLE FILE 41 ALLOWED TO USE SPOOLER 41.1 MULTI-DEVICE DESPOOLING 41.2 CAN MAKE INTO A MAIL MESSAGE 50.1 KEY DELEGATION LEVEL 51 KEYS 52 DELEGATED KEYS 53.1 AUTHORIZED TO WRITE MED ORDERS 53.2 DEA# 53.3 VA# 53.4 INACTIVE DATE 53.5 PROVIDER CLASS 53.6 PROVIDER TYPE 53.7 REQUIRES COSIGNER 53.8 USUAL COSIGNER 53.9 REMARKS 53.91NON-VA PRESCRIBER 53.92TAX ID 53.93EXCLUSIONARY CHECK PERFORMED 53.94DATE EXCLUSIONARY LIST CHECKED 53.95ON EXCLUSIONARY LIST 53.96EXCLUSIONARY CHECKED BY 54.1 LICENSING STATE 54.2 STATE ISSUING DEA NUMBER 70 STAFF REVIEW REQUIRED 71 ALLOW VERIFYING OF OTHERS 72 RAD/NUC MED CLASSIFICATION 73 RAD/NUC MED INACTIVE DATE 74 RAD/NUC MED LOCATION ACCESS 101.01RESTRICT PATIENT SELECTION 101.02PATIENT SELECTION LIST 101.13CPRS TAB 125 PROBLEM LIST PRIMARY VIEW
Re: [Hardhats-members] Another GTM error
,B,PROFESSIONAL ORGANIZATION,747.7)= ^DD(200,B,PROGRAM OF STUDY,12.2)= ^DD(200,B,PROHIBITED TIMES FOR SIGN-ON,15)= ^DD(200,B,PROVIDER CLASS,53.5)= ^DD(200,B,PROVIDER KEY,8932.001)= ^DD(200,B,PROVIDER TYPE,53.6)= ^DD(200,B,RAD/NUC MED CLASSIFICATION,72)= ^DD(200,B,RAD/NUC MED INACTIVE DATE,73)= ^DD(200,B,RAD/NUC MED LOCATION ACCESS,74)= ^DD(200,B,RANK,910.2)= ^DD(200,B,RECOMMENDATION SIGNATURES,747.31)= ^DD(200,B,REMARKS,53.9)=1 ^DD(200,B,RENEW DATE,747.113)= ^DD(200,B,REQUIRES COSIGNER,53.7)= ^DD(200,B,RESERVED,200.08)= ^DD(200,B,RESTRICT PATIENT SELECTION,101.01)= ^DD(200,B,RESULTS OF QUERY ?,747.39)= ^DD(200,B,ROOM,.141)= ^DD(200,B,SCHOOL ATTENDED,747.34)= ^DD(200,B,SECONDARY MENU OPTIONS,203)= ^DD(200,B,SERVICE,747.1)= ^DD(200,B,SERVICE COMPUTATION DATE,747.22)= ^DD(200,B,SERVICE/SECTION,29)= ^DD(200,B,SEX,4)= ^DD(200,B,SIGNATURE BLOCK PRINTED NAME,20.2)= ^DD(200,B,SIGNATURE BLOCK TITLE,20.3)= ^DD(200,B,SOCIAL WORKER ?,654)= ^DD(200,B,SOCIAL WORKER'S NUMBER,654.2)= ^DD(200,B,SPECIALTY,747.111)= ^DD(200,B,SPELLING EXCEPTION DICTIONARY,8983.5)= ^DD(200,B,SSN,9)= ^DD(200,B,STAFF REVIEW REQUIRED,70)= ^DD(200,B,START DATE OF TEMP ADDRES,.1217)= ^DD(200,B,STARTUP DEFAULT,201.2)= ^DD(200,B,STATE,.115)= ^DD(200,B,STATE ISSUING DEA NUMBER,54.2)= ^DD(200,B,STREET ADDRESS 1,.111)= ^DD(200,B,STREET ADDRESS 2,.112)= ^DD(200,B,STREET ADDRESS 3,.113)= ^DD(200,B,SUPPLY EMPLOYEE,400)= ^DD(200,B,SURROGATE,654.3)= ^DD(200,B,TAX ID,53.92)= ^DD(200,B,TEMPORARY ADDRESS 1,.1211)= ^DD(200,B,TEMPORARY ADDRESS 2,.1212)= ^DD(200,B,TEMPORARY ADDRESS 3,.1213)= ^DD(200,B,TEMPORARY CITY,.1214)= ^DD(200,B,TEMPORARY STATE,.1215)= ^DD(200,B,TEMPORARY ZIP CODE,.1216)= ^DD(200,B,TERMINAL TYPE LAST USED,9.3)= ^DD(200,B,TERMINATION DATE,9.2)= ^DD(200,B,TEXT TERMINATOR,31.2)= ^DD(200,B,TIMED READ (# OF SECONDS),200.1)= ^DD(200,B,TIMEFRAME TO RENEW PRIVILEGES?,747.25)= ^DD(200,B,TIMESTAMP,203.1)= ^DD(200,B,TITLE,8)= ^DD(200,B,TOTAL MINUTES USING LM WP,8983.17)= ^DD(200,B,TYPE OF APPOINTMENT,747.3)= ^DD(200,B,TYPE-AHEAD,200.09)= ^DD(200,B,Termination Reason,9.4)= ^DD(200,B,UCI,20)= ^DD(200,B,USUAL COSIGNER,53.8)= ^DD(200,B,VA CAUTIONARY LIST CHECKED?,747.42)= ^DD(200,B,VA Person Identification Code,9000)=1 ^DD(200,B,VA#,53.3)= ^DD(200,B,VAF 10-2850 COMPLETION (Y/N),747.9)= ^DD(200,B,VAF 10-2850 LICENSE DATA (Y/N),747.15)= ^DD(200,B,VAF 10-2850 SIGNED/COS (Y/N),747.14)= ^DD(200,B,VERIFY CODE,11)= ^DD(200,B,VERIFY CODE,11.1)=1 ^DD(200,B,VERIFY CODE never expires,7.2)= ^DD(200,B,VISITED FROM,8910)= ^DD(200,B,VOICE PAGER,.137)= ^DD(200,B,VPID,9000)= ^DD(200,B,Want to edit ACCESS CODE (Y/N),2.1)= ^DD(200,B,Want to edit VERIFY CODE (Y/N),11.1)= ^DD(200,B,XUS Active User,202.03)= ^DD(200,B,XUS Logon Attempt Count,202.02)= ^DD(200,B,ZIP CODE,.116)= GTM Usha - Original Message - From: Jim Self [EMAIL PROTECTED] To: hardhats-members@lists.sourceforge.net Sent: Thursday, June 02, 2005 3:18 AM Subject: Re: [Hardhats-members] Another GTM error Generally, this kind of problem requires looking at data structures rather than code tracing. You often need to look only a little bit at the code to find the relevant variables and then use ZWRITE or other tools to view the data values. Looping like Usha reports generally comes from a stepping algorithm that trips over a non-canonic number where a canonic number was assumed. For example: s test(ted,1.1)=,test(ben,.01)=,test(joe,1.0)=,name= f n=0:0 s name=$o(test(name)) q:name= d . f i=0:0 s i=$o(test(name,i)) q:'i s n=n+1 w !,n,?5,name,?10,i q:n9 It may be too late now to see the data that caused the problem, but what do you get from ZWRITE ^DD(200,B,*)? --- This SF.Net email is sponsored by Yahoo. Introducing Yahoo! Search Developer Network - Create apps using Yahoo! Search APIs Find out how you can build Yahoo! directly into your own Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005 ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
Re: [Hardhats-members] Another GTM error
,PERTINENT CLINICAL INFORMATION,747.32)= ^DD(200,B,PGY assigned,8932.21)= ^DD(200,B,PGYear,8932.2)= ^DD(200,B,PHONE #3,.133)= ^DD(200,B,PHONE #4,.134)= ^DD(200,B,PHONE (HOME),.131)= ^DD(200,B,PLACE OF BIRTH,747.41)= ^DD(200,B,POSITION/TITLE,654.15)= ^DD(200,B,PREFERRED EDITOR,31.3)= ^DD(200,B,PRIMARY DEGREE,747.33)= ^DD(200,B,PRIMARY MENU OPTION,201)= ^DD(200,B,PRIMARY WINDOW,201.1)= ^DD(200,B,PROBLEM LIST PRIMARY VIEW,125)= ^DD(200,B,PROBLEM SELECTION LIST,125.1)= ^DD(200,B,PROFESSIONAL ORGANIZATION,747.7)= ^DD(200,B,PROGRAM OF STUDY,12.2)= ^DD(200,B,PROHIBITED TIMES FOR SIGN-ON,15)= ^DD(200,B,PROVIDER CLASS,53.5)= ^DD(200,B,PROVIDER KEY,8932.001)= ^DD(200,B,PROVIDER TYPE,53.6)= ^DD(200,B,RAD/NUC MED CLASSIFICATION,72)= ^DD(200,B,RAD/NUC MED INACTIVE DATE,73)= ^DD(200,B,RAD/NUC MED LOCATION ACCESS,74)= ^DD(200,B,RANK,910.2)= ^DD(200,B,RECOMMENDATION SIGNATURES,747.31)= ^DD(200,B,REMARKS,53.9)=1 ^DD(200,B,RENEW DATE,747.113)= ^DD(200,B,REQUIRES COSIGNER,53.7)= ^DD(200,B,RESERVED,200.08)= ^DD(200,B,RESTRICT PATIENT SELECTION,101.01)= ^DD(200,B,RESULTS OF QUERY ?,747.39)= ^DD(200,B,ROOM,.141)= ^DD(200,B,SCHOOL ATTENDED,747.34)= ^DD(200,B,SECONDARY MENU OPTIONS,203)= ^DD(200,B,SERVICE,747.1)= ^DD(200,B,SERVICE COMPUTATION DATE,747.22)= ^DD(200,B,SERVICE/SECTION,29)= ^DD(200,B,SEX,4)= ^DD(200,B,SIGNATURE BLOCK PRINTED NAME,20.2)= ^DD(200,B,SIGNATURE BLOCK TITLE,20.3)= ^DD(200,B,SOCIAL WORKER ?,654)= ^DD(200,B,SOCIAL WORKER'S NUMBER,654.2)= ^DD(200,B,SPECIALTY,747.111)= ^DD(200,B,SPELLING EXCEPTION DICTIONARY,8983.5)= ^DD(200,B,SSN,9)= ^DD(200,B,STAFF REVIEW REQUIRED,70)= ^DD(200,B,START DATE OF TEMP ADDRES,.1217)= ^DD(200,B,STARTUP DEFAULT,201.2)= ^DD(200,B,STATE,.115)= ^DD(200,B,STATE ISSUING DEA NUMBER,54.2)= ^DD(200,B,STREET ADDRESS 1,.111)= ^DD(200,B,STREET ADDRESS 2,.112)= ^DD(200,B,STREET ADDRESS 3,.113)= ^DD(200,B,SUPPLY EMPLOYEE,400)= ^DD(200,B,SURROGATE,654.3)= ^DD(200,B,TAX ID,53.92)= ^DD(200,B,TEMPORARY ADDRESS 1,.1211)= ^DD(200,B,TEMPORARY ADDRESS 2,.1212)= ^DD(200,B,TEMPORARY ADDRESS 3,.1213)= ^DD(200,B,TEMPORARY CITY,.1214)= ^DD(200,B,TEMPORARY STATE,.1215)= ^DD(200,B,TEMPORARY ZIP CODE,.1216)= ^DD(200,B,TERMINAL TYPE LAST USED,9.3)= ^DD(200,B,TERMINATION DATE,9.2)= ^DD(200,B,TEXT TERMINATOR,31.2)= ^DD(200,B,TIMED READ (# OF SECONDS),200.1)= ^DD(200,B,TIMEFRAME TO RENEW PRIVILEGES?,747.25)= ^DD(200,B,TIMESTAMP,203.1)= ^DD(200,B,TITLE,8)= ^DD(200,B,TOTAL MINUTES USING LM WP,8983.17)= ^DD(200,B,TYPE OF APPOINTMENT,747.3)= ^DD(200,B,TYPE-AHEAD,200.09)= ^DD(200,B,Termination Reason,9.4)= ^DD(200,B,UCI,20)= ^DD(200,B,USUAL COSIGNER,53.8)= ^DD(200,B,VA CAUTIONARY LIST CHECKED?,747.42)= ^DD(200,B,VA Person Identification Code,9000)=1 ^DD(200,B,VA#,53.3)= ^DD(200,B,VAF 10-2850 COMPLETION (Y/N),747.9)= ^DD(200,B,VAF 10-2850 LICENSE DATA (Y/N),747.15)= ^DD(200,B,VAF 10-2850 SIGNED/COS (Y/N),747.14)= ^DD(200,B,VERIFY CODE,11)= ^DD(200,B,VERIFY CODE,11.1)=1 ^DD(200,B,VERIFY CODE never expires,7.2)= ^DD(200,B,VISITED FROM,8910)= ^DD(200,B,VOICE PAGER,.137)= ^DD(200,B,VPID,9000)= ^DD(200,B,Want to edit ACCESS CODE (Y/N),2.1)= ^DD(200,B,Want to edit VERIFY CODE (Y/N),11.1)= ^DD(200,B,XUS Active User,202.03)= ^DD(200,B,XUS Logon Attempt Count,202.02)= ^DD(200,B,ZIP CODE,.116)= GTM Usha - Original Message - From: Jim Self [EMAIL PROTECTED] To: hardhats-members@lists.sourceforge.net Sent: Thursday, June 02, 2005 3:18 AM Subject: Re: [Hardhats-members] Another GTM error Generally, this kind of problem requires looking at data structures rather than code tracing. You often need to look only a little bit at the code to find the relevant variables and then use ZWRITE or other tools to view the data values. Looping like Usha reports generally comes from a stepping algorithm that trips over a non-canonic number where a canonic number was assumed. For example: s test(ted,1.1)=,test(ben,.01)=,test(joe,1.0) =,name= f n=0:0 s name=$o(test(name)) q:name= d . f i=0:0 s i=$o(test(name,i)) q:'i s n=n+1 w !,n,?5,name,?10,i q:n9 It may be too late now to see the data that caused the problem, but what do you get from ZWRITE ^DD(200,B,*)? --- This SF.Net email is sponsored by Yahoo. Introducing Yahoo! Search Developer Network - Create apps using Yahoo! Search APIs Find out how you can build Yahoo! directly into your own Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg- q22005 ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members --- This SF.Net email is sponsored by Yahoo. Introducing Yahoo! Search Developer Network - Create apps using Yahoo! Search APIs Find out how you can build Yahoo! directly into your own Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
Re: [Hardhats-members] Another GTM error
If database structural integrity is suspect, a mupip integ is the recommended next step. If integrity of content is suspect, then some other means will need to be found. -- Bhaskar Greg Woodhouse wrote: That's very srange. At some level, Fileman is just $ORDERing through a global. Could there be a corruption at the global level? --- This SF.Net email is sponsored by Yahoo. Introducing Yahoo! Search Developer Network - Create apps using Yahoo! Search APIs Find out how you can build Yahoo! directly into your own Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005 ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
RE: [Hardhats-members] Another GTM error
This confirms that it was not a database structural integrity issue, but rather a database content issue. -- Bhaskar -Original Message- From: [EMAIL PROTECTED] on behalf of Usha Sent: Tue 5/31/2005 11:38 PM To: hardhats-members@lists.sourceforge.net Cc: Subject:Re: [Hardhats-members] Another GTM error I tried the mupip integ when the problem startted, bu no errors were reported. But I have been able to overcome the problem, for the time being, by installing a KIDS patch of the correct NEW PERSON file. Thanks Usha winmail.dat
Re: [Hardhats-members] Another GTM error
The only thing I can think to figure this out would be to trace through the code step by step. And what a dark prospect this is! You can step through using Serenji (best), or I have a bare-bones debugger for using with only GT.M if you are interested. Kevin --- Usha [EMAIL PROTECTED] wrote: After executing the command on the GT.M prompt, I deleted the LABEL Certification. Now when I try to get the list of all the fields of NEW PERSON file, after listing some fields, BOARD ELIGIBLE is displayed infinitely. This is the list of fields in the NEW PERSON file from the DATA DICTIONARY option. .01 NAME .111 STREET ADDRESS 1 .112 STREET ADDRESS 2 .113 STREET ADDRESS 3 .114 CITY .115 STATE .116 ZIP CODE .1211TEMPORARY ADDRESS 1 .1212TEMPORARY ADDRESS 2 .1213TEMPORARY ADDRESS 3 .1214TEMPORARY CITY .1215TEMPORARY STATE .1216TEMPORARY ZIP CODE .1217START DATE OF TEMP ADDRES .1218END DATE OF TEMP ADDRESS .131 PHONE (HOME) .132 OFFICE PHONE .133 PHONE #3 .134 PHONE #4 .135 COMMERCIAL PHONE .136 FAX NUMBER .137 VOICE PAGER .138 DIGITAL PAGER .141 ROOM .151 EMAIL ADDRESS 1INITIAL 2ACCESS CODE 2.1 Want to edit ACCESS CODE (Y/N) 2.2 DATE ACCESS CODE LAST CHANGED 3FILE MANAGER ACCESS CODE 4SEX 5DOB 7DISUSER 7.2 VERIFY CODE never expires 8TITLE 9SSN 9.2 TERMINATION DATE 9.21 DELETE ALL MAIL ACCESS 9.22 DELETE KEYS AT TERMINATION 9.3 TERMINAL TYPE LAST USED 9.4 Termination Reason 10 ALIAS 10.1 NAME COMPONENTS 10.6 DEGREE 11 VERIFY CODE 11.1 Want to edit VERIFY CODE (Y/N) 11.2 DATE VERIFY CODE LAST CHANGED 11.6 ALLOW ARA ACCESS 11.7 ARA VALUE 12.1 CURRENT DEGREE LEVEL 12.2 PROGRAM OF STUDY 12.3 LAST TRAINING YEAR 13 NICK NAME 14 PAC 14.9 HINQ EMPLOYEE NUMBER 15 PROHIBITED TIMES FOR SIGN-ON 16 DIVISION 19 DELEGATE OF 19.1 DELEGATION DATE 19.2 DELEGATION LEVEL 19.4 ALERT DATE/TIME 19.5 DELEGATED OPTIONS 19.6 ALLOWABLE NEW MENU PREFIX 19.8 MENU TEMPLATE 20 UCI 20.1 DATE E-SIG LAST CHANGED 20.2 SIGNATURE BLOCK PRINTED NAME 20.3 SIGNATURE BLOCK TITLE 20.4 ELECTRONIC SIGNATURE CODE 28 MAIL CODE 29 SERVICE/SECTION 30 DATE ENTERED 31 CREATOR 31.1 FILE RANGE 31.2 TEXT TERMINATOR 31.3 PREFERRED EDITOR 32 ACCESSIBLE FILE 41 ALLOWED TO USE SPOOLER 41.1 MULTI-DEVICE DESPOOLING 41.2 CAN MAKE INTO A MAIL MESSAGE 50.1 KEY DELEGATION LEVEL 51 KEYS 52 DELEGATED KEYS 53.1 AUTHORIZED TO WRITE MED ORDERS 53.2 DEA# 53.3 VA# 53.4 INACTIVE DATE 53.5 PROVIDER CLASS 53.6 PROVIDER TYPE 53.7 REQUIRES COSIGNER 53.8 USUAL COSIGNER 53.9 REMARKS 53.91NON-VA PRESCRIBER 53.92TAX ID 53.93EXCLUSIONARY CHECK PERFORMED 53.94DATE EXCLUSIONARY LIST CHECKED 53.95ON EXCLUSIONARY LIST 53.96EXCLUSIONARY CHECKED BY 54.1 LICENSING STATE 54.2 STATE ISSUING DEA NUMBER 70 STAFF REVIEW REQUIRED 71 ALLOW VERIFYING OF OTHERS 72 RAD/NUC MED CLASSIFICATION 73 RAD/NUC MED INACTIVE DATE 74 RAD/NUC MED LOCATION ACCESS 101.01RESTRICT PATIENT SELECTION 101.02PATIENT SELECTION LIST 101.13CPRS TAB 125 PROBLEM LIST PRIMARY VIEW 125.1PROBLEM SELECTION LIST 200.04MULTIPLE SIGN-ON 200.05ASK DEVICE TYPE AT SIGN-ON 200.06AUTO MENU 200.07LANGUAGE 200.08RESERVED 200.09TYPE-AHEAD 200.1TIMED READ (# OF SECONDS) 200.11ALWAYS SHOW SECONDARIES 200.18AUTO SIGN-ON 200.19MULTIPLE SIGN-ON LIMIT 201 PRIMARY MENU OPTION 201.1PRIMARY WINDOW 201.2STARTUP DEFAULT 202 LAST SIGN-ON DATE/TIME 202.02XUS Logon Attempt Count 202.03XUS Active User 202.04Entry Last Edit Date 202.1LAST OPTION ACCESSED 202.2
Re: [Hardhats-members] Another GTM error
That's very srange. At some level, Fileman is just $ORDERing through a global. Could there be a corruption at the global level? --- Usha [EMAIL PROTECTED] wrote: After executing the command on the GT.M prompt, I deleted the LABEL Certification. Now when I try to get the list of all the fields of NEW PERSON file, after listing some fields, BOARD ELIGIBLE is displayed infinitely. This is the list of fields in the NEW PERSON file from the DATA DICTIONARY option. .01 NAME .111 STREET ADDRESS 1 .112 STREET ADDRESS 2 .113 STREET ADDRESS 3 .114 CITY .115 STATE .116 ZIP CODE .1211TEMPORARY ADDRESS 1 .1212TEMPORARY ADDRESS 2 .1213TEMPORARY ADDRESS 3 .1214TEMPORARY CITY .1215TEMPORARY STATE .1216TEMPORARY ZIP CODE .1217START DATE OF TEMP ADDRES .1218END DATE OF TEMP ADDRESS .131 PHONE (HOME) .132 OFFICE PHONE .133 PHONE #3 .134 PHONE #4 .135 COMMERCIAL PHONE .136 FAX NUMBER .137 VOICE PAGER .138 DIGITAL PAGER .141 ROOM .151 EMAIL ADDRESS 1INITIAL 2ACCESS CODE 2.1 Want to edit ACCESS CODE (Y/N) 2.2 DATE ACCESS CODE LAST CHANGED 3FILE MANAGER ACCESS CODE 4SEX 5DOB 7DISUSER 7.2 VERIFY CODE never expires 8TITLE 9SSN 9.2 TERMINATION DATE 9.21 DELETE ALL MAIL ACCESS 9.22 DELETE KEYS AT TERMINATION 9.3 TERMINAL TYPE LAST USED 9.4 Termination Reason 10 ALIAS 10.1 NAME COMPONENTS 10.6 DEGREE 11 VERIFY CODE 11.1 Want to edit VERIFY CODE (Y/N) 11.2 DATE VERIFY CODE LAST CHANGED 11.6 ALLOW ARA ACCESS 11.7 ARA VALUE 12.1 CURRENT DEGREE LEVEL 12.2 PROGRAM OF STUDY 12.3 LAST TRAINING YEAR 13 NICK NAME 14 PAC 14.9 HINQ EMPLOYEE NUMBER 15 PROHIBITED TIMES FOR SIGN-ON 16 DIVISION 19 DELEGATE OF 19.1 DELEGATION DATE 19.2 DELEGATION LEVEL 19.4 ALERT DATE/TIME 19.5 DELEGATED OPTIONS 19.6 ALLOWABLE NEW MENU PREFIX 19.8 MENU TEMPLATE 20 UCI 20.1 DATE E-SIG LAST CHANGED 20.2 SIGNATURE BLOCK PRINTED NAME 20.3 SIGNATURE BLOCK TITLE 20.4 ELECTRONIC SIGNATURE CODE 28 MAIL CODE 29 SERVICE/SECTION 30 DATE ENTERED 31 CREATOR 31.1 FILE RANGE 31.2 TEXT TERMINATOR 31.3 PREFERRED EDITOR 32 ACCESSIBLE FILE 41 ALLOWED TO USE SPOOLER 41.1 MULTI-DEVICE DESPOOLING 41.2 CAN MAKE INTO A MAIL MESSAGE 50.1 KEY DELEGATION LEVEL 51 KEYS 52 DELEGATED KEYS 53.1 AUTHORIZED TO WRITE MED ORDERS 53.2 DEA# 53.3 VA# 53.4 INACTIVE DATE 53.5 PROVIDER CLASS 53.6 PROVIDER TYPE 53.7 REQUIRES COSIGNER 53.8 USUAL COSIGNER 53.9 REMARKS 53.91NON-VA PRESCRIBER 53.92TAX ID 53.93EXCLUSIONARY CHECK PERFORMED 53.94DATE EXCLUSIONARY LIST CHECKED 53.95ON EXCLUSIONARY LIST 53.96EXCLUSIONARY CHECKED BY 54.1 LICENSING STATE 54.2 STATE ISSUING DEA NUMBER 70 STAFF REVIEW REQUIRED 71 ALLOW VERIFYING OF OTHERS 72 RAD/NUC MED CLASSIFICATION 73 RAD/NUC MED INACTIVE DATE 74 RAD/NUC MED LOCATION ACCESS 101.01RESTRICT PATIENT SELECTION 101.02PATIENT SELECTION LIST 101.13CPRS TAB 125 PROBLEM LIST PRIMARY VIEW 125.1PROBLEM SELECTION LIST 200.04MULTIPLE SIGN-ON 200.05ASK DEVICE TYPE AT SIGN-ON 200.06AUTO MENU 200.07LANGUAGE 200.08RESERVED 200.09TYPE-AHEAD 200.1TIMED READ (# OF SECONDS) 200.11ALWAYS SHOW SECONDARIES 200.18AUTO SIGN-ON 200.19MULTIPLE SIGN-ON LIMIT 201 PRIMARY MENU OPTION 201.1PRIMARY WINDOW 201.2STARTUP DEFAULT 202 LAST SIGN-ON DATE/TIME 202.02XUS Logon Attempt Count 202.03XUS Active User 202.04Entry Last Edit Date 202.1LAST OPTION ACCESSED 202.2LAST OPTION MAIN MENU 203 SECONDARY MENU OPTIONS 203.1TIMESTAMP 400 SUPPLY EMPLOYEE 450
Re: [Hardhats-members] Another GTM error
Certification and Board eligibility are all wrapped up together in the practitioner world and I would suggest that you try to find out how to put the certification back in rather than how to take the eligibility back out. The pointer to the undefined file is also present in the Board Eligible data dictionary, so this appears to be a feature instead of an error. I submit that file will need to be put in eventually, so all the more reason to put things in, not take them out. On Monday 30 May 2005 12:01 pm, Kevin Toppenberg wrote: The only thing I can think to figure this out would be to trace through the code step by step. And what a dark prospect this is! You can step through using Serenji (best), or I have a bare-bones debugger for using with only GT.M if you are interested. Kevin --- Usha [EMAIL PROTECTED] wrote: After executing the command on the GT.M prompt, I deleted the LABEL Certification. Now when I try to get the list of all the fields of NEW PERSON file, after listing some fields, BOARD ELIGIBLE is displayed infinitely. This is the list of fields in the NEW PERSON file from the DATA DICTIONARY option. .01 NAME .111 STREET ADDRESS 1 .112 STREET ADDRESS 2 .113 STREET ADDRESS 3 .114 CITY .115 STATE .116 ZIP CODE .1211TEMPORARY ADDRESS 1 .1212TEMPORARY ADDRESS 2 .1213TEMPORARY ADDRESS 3 .1214TEMPORARY CITY .1215TEMPORARY STATE .1216TEMPORARY ZIP CODE .1217START DATE OF TEMP ADDRES .1218END DATE OF TEMP ADDRESS .131 PHONE (HOME) .132 OFFICE PHONE .133 PHONE #3 .134 PHONE #4 .135 COMMERCIAL PHONE .136 FAX NUMBER .137 VOICE PAGER .138 DIGITAL PAGER .141 ROOM .151 EMAIL ADDRESS 1INITIAL 2ACCESS CODE 2.1 Want to edit ACCESS CODE (Y/N) 2.2 DATE ACCESS CODE LAST CHANGED 3FILE MANAGER ACCESS CODE 4SEX 5DOB 7DISUSER 7.2 VERIFY CODE never expires 8TITLE 9SSN 9.2 TERMINATION DATE 9.21 DELETE ALL MAIL ACCESS 9.22 DELETE KEYS AT TERMINATION 9.3 TERMINAL TYPE LAST USED 9.4 Termination Reason 10 ALIAS 10.1 NAME COMPONENTS 10.6 DEGREE 11 VERIFY CODE 11.1 Want to edit VERIFY CODE (Y/N) 11.2 DATE VERIFY CODE LAST CHANGED 11.6 ALLOW ARA ACCESS 11.7 ARA VALUE 12.1 CURRENT DEGREE LEVEL 12.2 PROGRAM OF STUDY 12.3 LAST TRAINING YEAR 13 NICK NAME 14 PAC 14.9 HINQ EMPLOYEE NUMBER 15 PROHIBITED TIMES FOR SIGN-ON 16 DIVISION 19 DELEGATE OF 19.1 DELEGATION DATE 19.2 DELEGATION LEVEL 19.4 ALERT DATE/TIME 19.5 DELEGATED OPTIONS 19.6 ALLOWABLE NEW MENU PREFIX 19.8 MENU TEMPLATE 20 UCI 20.1 DATE E-SIG LAST CHANGED 20.2 SIGNATURE BLOCK PRINTED NAME 20.3 SIGNATURE BLOCK TITLE 20.4 ELECTRONIC SIGNATURE CODE 28 MAIL CODE 29 SERVICE/SECTION 30 DATE ENTERED 31 CREATOR 31.1 FILE RANGE 31.2 TEXT TERMINATOR 31.3 PREFERRED EDITOR 32 ACCESSIBLE FILE 41 ALLOWED TO USE SPOOLER 41.1 MULTI-DEVICE DESPOOLING 41.2 CAN MAKE INTO A MAIL MESSAGE 50.1 KEY DELEGATION LEVEL 51 KEYS 52 DELEGATED KEYS 53.1 AUTHORIZED TO WRITE MED ORDERS 53.2 DEA# 53.3 VA# 53.4 INACTIVE DATE 53.5 PROVIDER CLASS 53.6 PROVIDER TYPE 53.7 REQUIRES COSIGNER 53.8 USUAL COSIGNER 53.9 REMARKS 53.91NON-VA PRESCRIBER 53.92TAX ID 53.93EXCLUSIONARY CHECK PERFORMED 53.94DATE EXCLUSIONARY LIST CHECKED 53.95ON EXCLUSIONARY LIST 53.96EXCLUSIONARY CHECKED BY 54.1 LICENSING STATE 54.2 STATE ISSUING DEA NUMBER 70 STAFF REVIEW REQUIRED 71 ALLOW VERIFYING OF OTHERS 72 RAD/NUC MED CLASSIFICATION 73 RAD/NUC MED INACTIVE DATE 74 RAD/NUC MED LOCATION ACCESS 101.01RESTRICT PATIENT SELECTION 101.02PATIENT SELECTION LIST 101.13CPRS TAB 125 PROBLEM LIST PRIMARY VIEW 125.1
Re: [Hardhats-members] Another GTM error
After executing the command on the GT.M prompt, I deleted the LABEL Certification. Now when I try to get the list of all the fields of NEW PERSON file, after listing some fields, BOARD ELIGIBLE is displayed infinitely. This is the list of fields in the NEW PERSON file from the DATA DICTIONARY option. .01 NAME .111 STREET ADDRESS 1 .112 STREET ADDRESS 2 .113 STREET ADDRESS 3 .114 CITY .115 STATE .116 ZIP CODE .1211TEMPORARY ADDRESS 1 .1212TEMPORARY ADDRESS 2 .1213TEMPORARY ADDRESS 3 .1214TEMPORARY CITY .1215TEMPORARY STATE .1216TEMPORARY ZIP CODE .1217START DATE OF TEMP ADDRES .1218END DATE OF TEMP ADDRESS .131 PHONE (HOME) .132 OFFICE PHONE .133 PHONE #3 .134 PHONE #4 .135 COMMERCIAL PHONE .136 FAX NUMBER .137 VOICE PAGER .138 DIGITAL PAGER .141 ROOM .151 EMAIL ADDRESS 1INITIAL 2ACCESS CODE 2.1 Want to edit ACCESS CODE (Y/N) 2.2 DATE ACCESS CODE LAST CHANGED 3FILE MANAGER ACCESS CODE 4SEX 5DOB 7DISUSER 7.2 VERIFY CODE never expires 8TITLE 9SSN 9.2 TERMINATION DATE 9.21 DELETE ALL MAIL ACCESS 9.22 DELETE KEYS AT TERMINATION 9.3 TERMINAL TYPE LAST USED 9.4 Termination Reason 10 ALIAS 10.1 NAME COMPONENTS 10.6 DEGREE 11 VERIFY CODE 11.1 Want to edit VERIFY CODE (Y/N) 11.2 DATE VERIFY CODE LAST CHANGED 11.6 ALLOW ARA ACCESS 11.7 ARA VALUE 12.1 CURRENT DEGREE LEVEL 12.2 PROGRAM OF STUDY 12.3 LAST TRAINING YEAR 13 NICK NAME 14 PAC 14.9 HINQ EMPLOYEE NUMBER 15 PROHIBITED TIMES FOR SIGN-ON 16 DIVISION 19 DELEGATE OF 19.1 DELEGATION DATE 19.2 DELEGATION LEVEL 19.4 ALERT DATE/TIME 19.5 DELEGATED OPTIONS 19.6 ALLOWABLE NEW MENU PREFIX 19.8 MENU TEMPLATE 20 UCI 20.1 DATE E-SIG LAST CHANGED 20.2 SIGNATURE BLOCK PRINTED NAME 20.3 SIGNATURE BLOCK TITLE 20.4 ELECTRONIC SIGNATURE CODE 28 MAIL CODE 29 SERVICE/SECTION 30 DATE ENTERED 31 CREATOR 31.1 FILE RANGE 31.2 TEXT TERMINATOR 31.3 PREFERRED EDITOR 32 ACCESSIBLE FILE 41 ALLOWED TO USE SPOOLER 41.1 MULTI-DEVICE DESPOOLING 41.2 CAN MAKE INTO A MAIL MESSAGE 50.1 KEY DELEGATION LEVEL 51 KEYS 52 DELEGATED KEYS 53.1 AUTHORIZED TO WRITE MED ORDERS 53.2 DEA# 53.3 VA# 53.4 INACTIVE DATE 53.5 PROVIDER CLASS 53.6 PROVIDER TYPE 53.7 REQUIRES COSIGNER 53.8 USUAL COSIGNER 53.9 REMARKS 53.91NON-VA PRESCRIBER 53.92TAX ID 53.93EXCLUSIONARY CHECK PERFORMED 53.94DATE EXCLUSIONARY LIST CHECKED 53.95ON EXCLUSIONARY LIST 53.96EXCLUSIONARY CHECKED BY 54.1 LICENSING STATE 54.2 STATE ISSUING DEA NUMBER 70 STAFF REVIEW REQUIRED 71 ALLOW VERIFYING OF OTHERS 72 RAD/NUC MED CLASSIFICATION 73 RAD/NUC MED INACTIVE DATE 74 RAD/NUC MED LOCATION ACCESS 101.01RESTRICT PATIENT SELECTION 101.02PATIENT SELECTION LIST 101.13CPRS TAB 125 PROBLEM LIST PRIMARY VIEW 125.1PROBLEM SELECTION LIST 200.04MULTIPLE SIGN-ON 200.05ASK DEVICE TYPE AT SIGN-ON 200.06AUTO MENU 200.07LANGUAGE 200.08RESERVED 200.09TYPE-AHEAD 200.1TIMED READ (# OF SECONDS) 200.11ALWAYS SHOW SECONDARIES 200.18AUTO SIGN-ON 200.19MULTIPLE SIGN-ON LIMIT 201 PRIMARY MENU OPTION 201.1PRIMARY WINDOW 201.2STARTUP DEFAULT 202 LAST SIGN-ON DATE/TIME 202.02XUS Logon Attempt Count 202.03XUS Active User 202.04Entry Last Edit Date 202.1LAST OPTION ACCESSED 202.2LAST OPTION MAIN MENU 203 SECONDARY MENU OPTIONS 203.1TIMESTAMP 400 SUPPLY EMPLOYEE 450 PAID EMPLOYEE 500 NETWORK ADDRESS 654 SOCIAL WORKER ? 654.1IMMEDIATE SUPERVISOR 654.15POSITION/TITLE 654.2SOCIAL WORKER'S NUMBER 654.3SURROGATE 720 DMMS UNITS 747.1SERVICE 747.11APPOINTMENT
Re: [Hardhats-members] Another GTM error
Frankly, I am not sure, at least at here in the US, that you will want to remove the certification field. It is becoming of increasing importance to physicians and maybe others as well as boards require recertification and employers require recertification for continued employment. In fact, I would not be surprised if that whole section were beefed up to include links to business rules to flag people whose certifications are not up to date. On Friday 27 May 2005 12:52 am, Usha wrote: I tried to modify file attributes to remove CERTIFICATION field, but Select OPTION: 4 MODIFY FILE ATTRIBUTES Do you want to use the screen-mode version? YES// NO MODIFY WHAT FILE: NEW PERSON// Select FIELD: 747.5 CERTIFICATION And the system hangs... Is there any other way? Usha - Original Message - From: Cameron Schlehuber [EMAIL PROTECTED] To: hardhats-members@lists.sourceforge.net Sent: Thursday, May 26, 2005 10:14 PM Subject: RE: [Hardhats-members] Another GTM error Since it appears there is nothing in the sub-file at 200.07475 in the DD (as you indicated in your other response where you did ZWR ^DD(200.07475,*)) and the CERTIFICATION field (which represents the column for that table) thinks the DD should be there, I think that's what's actually leading to the error you have. And since the field is no longer being used for anything, I suggest you simply use FM's Modify option, select file 200 then field 747.5 and delete it by entering @ at the Name prompt. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Usha Sent: Wednesday, May 25, 2005 9:29 PM To: hardhats-members@lists.sourceforge.net Subject: Re: [Hardhats-members] Another GTM error When I look at my DATA DICTIONARY entry, this is what I get GTMd Q^DI VA FileMan 22.0 Select OPTION: 8 DATA DICTIONARY UTILITIES Select DATA DICTIONARY UTILITY OPTION: 1 LIST FILE ATTRIBUTES START WITH WHAT FILE: NEW PERSON// GO TO WHAT FILE: NEW PERSON// Select SUB-FILE: Select LISTING FORMAT: STANDARD// Start with field: FIRST// CERTIFICATION Go to field: STANDARD DATA DICTIONARY #200 -- NEW PERSON FILE MAY 26,[EMAIL PROTECTED]:54:31 PAGE 1 STORED IN ^VA(200, (150 ENTRIES) SITE: HUIVISTA3 UCI: ROU,ROU (VERSION 8.0) DATA NAME GLOBALDATA ELEMENT TITLE LOCATION TYPE --- - --- 200,747.5 CERTIFICATION QAR2;0 POINTER Multiple #200.07475 DESCRIPTION: This field allows you to enter specialties in which the practitioner is Board Certified. 200,747.6 BOARD ELIGIBLE QAR4;0 POINTER Multiple #200.07476 (Add New Entry without Asking) DESCRIPTION: If this applicant is eligible to complete specialty board exams, enter the area of specialty. 200.07476,2 VERIFICATION 0;3 SET '1' FOR LETTER FROM TRAINING DIRECTOR; '2' FOR LETTER FROM SPECIALTY BOARD; ... Is it that my global is corrupted? How can I rectify it? Regards Usha - Original Message - From: Nancy Anthracite [EMAIL PROTECTED] To: hardhats-members@lists.sourceforge.net Sent: Wednesday, May 25, 2005 5:00 PM Subject: Re: [Hardhats-members] Another GTM error I would like to know how to chase this down for future reference. Am I on the right track and now what? How do I find out more about IOSL? This is what I did so far: I found the 32nd line after the tag WR in the routine DDSU.m. the line with the WR tag is 126. The lines below are 149-159 and there were no line wraps above to screw things up that I could see. It seems that WR+32 is probably line 157, so WR+32 must count the line with WR as 1, correct? W DDH(A0,A4) I $D(DDH(ID)) D S:$D(DUOUT) DIY=U . N DDD,DIY,DDSID . S DDSID=DDH(ID) . S:$D(DDH(ID,1))#2 DDSID(1)=DDH(ID,1) . N DDH . S:$D(DDSID(1))#2 DDH(ID,1)=DDSID(1) K DDSID(1) . S Y=A4 . S:$D(DDS) DDQ=$S(DY(IOSL-1):IOSL-1,1:DY)_U_$X . X DDSID Q IOSL is not newed and is used early in the routine,and gives me a value, so I assume it is the undefined global variable. This is immediately after I started up with D P^DI, which I think wipes the local variables, correct? GTMW IOSL 24 I asked for that section in the global, I think. GTMZWR ^DD(200.07475,.01,0) ^DD(200.07475,.01,0)=CERTIFICATION^MP747.9'^QA(747.9,^0;1^Q Then I looked in the Data Dictionary: ** Select OPTION: 8 DATA DICTIONARY UTILITIES Select DATA DICTIONARY UTILITY OPTION: ^ Select OPTION: ^ GTMD Q^DI VA
RE: [Hardhats-members] Another GTM error
Since it appears there is nothing in the sub-file at 200.07475 in the DD (as you indicated in your other response where you did ZWR ^DD(200.07475,*)) and the CERTIFICATION field (which represents the column for that table) thinks the DD should be there, I think that's what's actually leading to the error you have. And since the field is no longer being used for anything, I suggest you simply use FM's Modify option, select file 200 then field 747.5 and delete it by entering @ at the Name prompt. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Usha Sent: Wednesday, May 25, 2005 9:29 PM To: hardhats-members@lists.sourceforge.net Subject: Re: [Hardhats-members] Another GTM error When I look at my DATA DICTIONARY entry, this is what I get GTMd Q^DI VA FileMan 22.0 Select OPTION: 8 DATA DICTIONARY UTILITIES Select DATA DICTIONARY UTILITY OPTION: 1 LIST FILE ATTRIBUTES START WITH WHAT FILE: NEW PERSON// GO TO WHAT FILE: NEW PERSON// Select SUB-FILE: Select LISTING FORMAT: STANDARD// Start with field: FIRST// CERTIFICATION Go to field: STANDARD DATA DICTIONARY #200 -- NEW PERSON FILE MAY 26,[EMAIL PROTECTED]:54:31 PAGE 1 STORED IN ^VA(200, (150 ENTRIES) SITE: HUIVISTA3 UCI: ROU,ROU (VERSION 8.0) DATA NAME GLOBALDATA ELEMENT TITLE LOCATION TYPE --- 200,747.5 CERTIFICATION QAR2;0 POINTER Multiple #200.07475 DESCRIPTION: This field allows you to enter specialties in which the practitioner is Board Certified. 200,747.6 BOARD ELIGIBLE QAR4;0 POINTER Multiple #200.07476 (Add New Entry without Asking) DESCRIPTION: If this applicant is eligible to complete specialty board exams, enter the area of specialty. 200.07476,2 VERIFICATION 0;3 SET '1' FOR LETTER FROM TRAINING DIRECTOR; '2' FOR LETTER FROM SPECIALTY BOARD; ... Is it that my global is corrupted? How can I rectify it? Regards Usha - Original Message - From: Nancy Anthracite [EMAIL PROTECTED] To: hardhats-members@lists.sourceforge.net Sent: Wednesday, May 25, 2005 5:00 PM Subject: Re: [Hardhats-members] Another GTM error I would like to know how to chase this down for future reference. Am I on the right track and now what? How do I find out more about IOSL? This is what I did so far: I found the 32nd line after the tag WR in the routine DDSU.m. the line with the WR tag is 126. The lines below are 149-159 and there were no line wraps above to screw things up that I could see. It seems that WR+32 is probably line 157, so WR+32 must count the line with WR as 1, correct? W DDH(A0,A4) I $D(DDH(ID)) D S:$D(DUOUT) DIY=U . N DDD,DIY,DDSID . S DDSID=DDH(ID) . S:$D(DDH(ID,1))#2 DDSID(1)=DDH(ID,1) . N DDH . S:$D(DDSID(1))#2 DDH(ID,1)=DDSID(1) K DDSID(1) . S Y=A4 . S:$D(DDS) DDQ=$S(DY(IOSL-1):IOSL-1,1:DY)_U_$X . X DDSID Q IOSL is not newed and is used early in the routine,and gives me a value, so I assume it is the undefined global variable. This is immediately after I started up with D P^DI, which I think wipes the local variables, correct? GTMW IOSL 24 I asked for that section in the global, I think. GTMZWR ^DD(200.07475,.01,0) ^DD(200.07475,.01,0)=CERTIFICATION^MP747.9'^QA(747.9,^0;1^Q Then I looked in the Data Dictionary: ** Select OPTION: 8 DATA DICTIONARY UTILITIES Select DATA DICTIONARY UTILITY OPTION: ^ Select OPTION: ^ GTMD Q^DI VA FileMan 22.0 Select OPTION: 8 DATA DICTIONARY UTILITIES Select DATA DICTIONARY UTILITY OPTION: 1 LIST FILE ATTRIBUTES START WITH WHAT FILE: NEW PERSON// GO TO WHAT FILE: NEW PERSON// Select SUB-FILE: Select LISTING FORMAT: STANDARD// Start with field: FIRST// Certification Go to field: DEVICE: TELNET STANDARD DATA DICTIONARY #200 -- NEW PERSON FILE MAY 25,[EMAIL PROTECTED]:04:05 PAGE 1 STORED IN ^VA(200, (1154 ENTRIES) SITE: CAMP MASTER UCI: VAH,ROU (VERSION 8.0) DATA NAME GLOBALDATA ELEMENT TITLE LOCATION TYPE -- - 200,747.5 CERTIFICATION QAR2;0 POINTER Multiple #200.07475 DESCRIPTION: This field allows you to enter specialties in which the practitioner is Board Certified. 200.07475,.01 CERTIFICATION 0;1 POINTER ** TO AN UNDEFINED FILE ** (Multiply asked) LAST EDITED
RE: [Hardhats-members] Another GTM error
Lloyd, Would you please send me your telephone number on a separate e-mail. Thanks, [EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Lloyd Milligan Sent: Wednesday, May 25, 2005 7:03 PM To: hardhats-members@lists.sourceforge.net Subject: Re: [Hardhats-members] Another GTM error No, but I think there is a path length limitation. Try it from a short path, if you are not already doing so. Lloyd - Original Message - From: Thurman Pedigo [EMAIL PROTECTED] To: hardhats-members@lists.sourceforge.net Sent: Wednesday, May 25, 2005 6:58 PM Subject: RE: [Hardhats-members] Another GTM error Is there a special folder to place a KIDS build/transport? I am having problems getting VistA to find a KIDS upgrade. The system is VistA running on Cache with Win2K server. Thanks, thurman -Original Message- From: [EMAIL PROTECTED] [mailto:hardhats- [EMAIL PROTECTED] On Behalf Of Cameron Schlehuber Sent: Wednesday, May 25, 2005 2:46 PM To: hardhats-members@lists.sourceforge.net Subject: RE: [Hardhats-members] Another GTM error One can manually reconstruct things, but it's usually safer (and less labor if a lot is missing) to create a KIDS build from a reliable account for just the components involved then import it. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kevin Toppenberg Sent: Wednesday, May 25, 2005 1:33 PM To: hardhats-members@lists.sourceforge.net Subject: RE: [Hardhats-members] Another GTM error My question, looking at this, is how to go about fixing such a problem. I assume a node was blown away somehow. Would it have to be manually reconstructed? Kevin --- Cameron Schlehuber [EMAIL PROTECTED] wrote: Actually, pointing to missing files won't cause the problem reported here. Fileman does tolerate that. Having data at ^DD(200.07475,.01,nn but not at ^DD(200.07475,.01,0) WILL cause such errors. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gregory Woodhouse Sent: Wednesday, May 25, 2005 5:55 AM To: hardhats-members@lists.sourceforge.net Subject: Re: [Hardhats-members] Another GTM error Fileman is resilient against quite a few potential errors, but pointing to files not in the DD is not one of them. === Gregory Woodhouse [EMAIL PROTECTED] A practical man is a man who practices the errors of his forefathers. -- Benjamin Disraeli On May 25, 2005, at 5:45 AM, Gregory Woodhouse wrote: Yes, you're on the right track. IOSL is one of a number of documented Kernel variables that you can read about in the online documentation. This one is screen length, and is ultimately a value set by the device handler based on the DEVICE file. It is unrelated to the problem here. Notice that this is an invalid pointer, and without looking too closely, I'd guess that the problem here was an attempt to dereference it. === Gregory Woodhouse [EMAIL PROTECTED] The whole of science is nothing more than a refinement of everyday thinking. -- Albert Einstein --- This SF.Net email is sponsored by Yahoo. Introducing Yahoo! Search Developer Network - Create apps using Yahoo! Search APIs Find out how you can build Yahoo! directly into your own Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005 ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members --- SF.Net email is sponsored by: GoToMeeting - the easiest way to collaborate online with coworkers and clients while avoiding the high cost of travel and communications. There is no equipment to buy and you can meet as often as you want. Try it free.http://ads.osdn.com/?ad_id=7402alloc_id=16135op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --- SF.Net email is sponsored by: GoToMeeting - the easiest way to collaborate online with coworkers and clients while avoiding the high cost of travel and communications. There is no equipment to buy and you can meet as often as you want. Try it free.http://ads.osdn.com/?ad_id=7402alloc_id=16135op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists
Re: [Hardhats-members] Another GTM error
I tried to modify file attributes to remove CERTIFICATION field, but Select OPTION: 4 MODIFY FILE ATTRIBUTES Do you want to use the screen-mode version? YES// NO MODIFY WHAT FILE: NEW PERSON// Select FIELD: 747.5 CERTIFICATION And the system hangs... Is there any other way? Usha - Original Message - From: Cameron Schlehuber [EMAIL PROTECTED] To: hardhats-members@lists.sourceforge.net Sent: Thursday, May 26, 2005 10:14 PM Subject: RE: [Hardhats-members] Another GTM error Since it appears there is nothing in the sub-file at 200.07475 in the DD (as you indicated in your other response where you did ZWR ^DD(200.07475,*)) and the CERTIFICATION field (which represents the column for that table) thinks the DD should be there, I think that's what's actually leading to the error you have. And since the field is no longer being used for anything, I suggest you simply use FM's Modify option, select file 200 then field 747.5 and delete it by entering @ at the Name prompt. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Usha Sent: Wednesday, May 25, 2005 9:29 PM To: hardhats-members@lists.sourceforge.net Subject: Re: [Hardhats-members] Another GTM error When I look at my DATA DICTIONARY entry, this is what I get GTMd Q^DI VA FileMan 22.0 Select OPTION: 8 DATA DICTIONARY UTILITIES Select DATA DICTIONARY UTILITY OPTION: 1 LIST FILE ATTRIBUTES START WITH WHAT FILE: NEW PERSON// GO TO WHAT FILE: NEW PERSON// Select SUB-FILE: Select LISTING FORMAT: STANDARD// Start with field: FIRST// CERTIFICATION Go to field: STANDARD DATA DICTIONARY #200 -- NEW PERSON FILE MAY 26,[EMAIL PROTECTED]:54:31 PAGE 1 STORED IN ^VA(200, (150 ENTRIES) SITE: HUIVISTA3 UCI: ROU,ROU (VERSION 8.0) DATA NAME GLOBALDATA ELEMENT TITLE LOCATION TYPE --- 200,747.5 CERTIFICATION QAR2;0 POINTER Multiple #200.07475 DESCRIPTION: This field allows you to enter specialties in which the practitioner is Board Certified. 200,747.6 BOARD ELIGIBLE QAR4;0 POINTER Multiple #200.07476 (Add New Entry without Asking) DESCRIPTION: If this applicant is eligible to complete specialty board exams, enter the area of specialty. 200.07476,2 VERIFICATION 0;3 SET '1' FOR LETTER FROM TRAINING DIRECTOR; '2' FOR LETTER FROM SPECIALTY BOARD; ... Is it that my global is corrupted? How can I rectify it? Regards Usha - Original Message - From: Nancy Anthracite [EMAIL PROTECTED] To: hardhats-members@lists.sourceforge.net Sent: Wednesday, May 25, 2005 5:00 PM Subject: Re: [Hardhats-members] Another GTM error I would like to know how to chase this down for future reference. Am I on the right track and now what? How do I find out more about IOSL? This is what I did so far: I found the 32nd line after the tag WR in the routine DDSU.m. the line with the WR tag is 126. The lines below are 149-159 and there were no line wraps above to screw things up that I could see. It seems that WR+32 is probably line 157, so WR+32 must count the line with WR as 1, correct? W DDH(A0,A4) I $D(DDH(ID)) D S:$D(DUOUT) DIY=U . N DDD,DIY,DDSID . S DDSID=DDH(ID) . S:$D(DDH(ID,1))#2 DDSID(1)=DDH(ID,1) . N DDH . S:$D(DDSID(1))#2 DDH(ID,1)=DDSID(1) K DDSID(1) . S Y=A4 . S:$D(DDS) DDQ=$S(DY(IOSL-1):IOSL-1,1:DY)_U_$X . X DDSID Q IOSL is not newed and is used early in the routine,and gives me a value, so I assume it is the undefined global variable. This is immediately after I started up with D P^DI, which I think wipes the local variables, correct? GTMW IOSL 24 I asked for that section in the global, I think. GTMZWR ^DD(200.07475,.01,0) ^DD(200.07475,.01,0)=CERTIFICATION^MP747.9'^QA(747.9,^0;1^Q Then I looked in the Data Dictionary: ** Select OPTION: 8 DATA DICTIONARY UTILITIES Select DATA DICTIONARY UTILITY OPTION: ^ Select OPTION: ^ GTMD Q^DI VA FileMan 22.0 Select OPTION: 8 DATA DICTIONARY UTILITIES Select DATA DICTIONARY UTILITY OPTION: 1 LIST FILE ATTRIBUTES START WITH WHAT FILE: NEW PERSON// GO TO WHAT FILE: NEW PERSON// Select SUB-FILE: Select LISTING FORMAT: STANDARD// Start with field: FIRST// Certification Go to field: DEVICE: TELNET STANDARD DATA DICTIONARY #200 -- NEW PERSON FILE MAY 25,[EMAIL PROTECTED]:04:05 PAGE 1 STORED IN ^VA(200, (1154 ENTRIES) SITE: CAMP MASTER UCI: VAH,ROU (VERSION 8.0) DATA NAME GLOBALDATA ELEMENT
Re: [Hardhats-members] Another GTM error
I would like to know how to chase this down for future reference. Am I on the right track and now what? How do I find out more about IOSL? This is what I did so far: I found the 32nd line after the tag WR in the routine DDSU.m. the line with the WR tag is 126. The lines below are 149-159 and there were no line wraps above to screw things up that I could see. It seems that WR+32 is probably line 157, so WR+32 must count the line with WR as 1, correct? W DDH(A0,A4) I $D(DDH(ID)) D S:$D(DUOUT) DIY=U . N DDD,DIY,DDSID . S DDSID=DDH(ID) . S:$D(DDH(ID,1))#2 DDSID(1)=DDH(ID,1) . N DDH . S:$D(DDSID(1))#2 DDH(ID,1)=DDSID(1) K DDSID(1) . S Y=A4 . S:$D(DDS) DDQ=$S(DY(IOSL-1):IOSL-1,1:DY)_U_$X . X DDSID Q IOSL is not newed and is used early in the routine,and gives me a value, so I assume it is the undefined global variable. This is immediately after I started up with D P^DI, which I think wipes the local variables, correct? GTMW IOSL 24 I asked for that section in the global, I think. GTMZWR ^DD(200.07475,.01,0) ^DD(200.07475,.01,0)=CERTIFICATION^MP747.9'^QA(747.9,^0;1^Q Then I looked in the Data Dictionary: ** Select OPTION: 8 DATA DICTIONARY UTILITIES Select DATA DICTIONARY UTILITY OPTION: ^ Select OPTION: ^ GTMD Q^DI VA FileMan 22.0 Select OPTION: 8 DATA DICTIONARY UTILITIES Select DATA DICTIONARY UTILITY OPTION: 1 LIST FILE ATTRIBUTES START WITH WHAT FILE: NEW PERSON// GO TO WHAT FILE: NEW PERSON// Select SUB-FILE: Select LISTING FORMAT: STANDARD// Start with field: FIRST// Certification Go to field: DEVICE: TELNET STANDARD DATA DICTIONARY #200 -- NEW PERSON FILE MAY 25,[EMAIL PROTECTED]:04:05 PAGE 1 STORED IN ^VA(200, (1154 ENTRIES) SITE: CAMP MASTER UCI: VAH,ROU (VERSION 8.0) DATA NAME GLOBALDATA ELEMENT TITLE LOCATION TYPE --- 200,747.5 CERTIFICATION QAR2;0 POINTER Multiple #200.07475 DESCRIPTION: This field allows you to enter specialties in which the practitioner is Board Certified. 200.07475,.01 CERTIFICATION 0;1 POINTER ** TO AN UNDEFINED FILE ** (Multiply asked) LAST EDITED: FEB 01, 1991 HELP-PROMPT: Enter the specialties in which the practitioner is Board Certified. DESCRIPTION: This field allows you to enter specialties in which the practitioner is Board Certified. CROSS-REFERENCE: 200.07475^B 1)= S ^VA(200,DA(1),QAR2,B, $E(X,1,30),DA)= 2)= K ^VA(200,DA(1),QAR2,B,$E(X,1,30),DA) 200.07475,1 DATE 0;2 DATE INPUT TRANSFORM:S %DT=E D IN^QARVER1,^%DT S X=Y K:Y1 X NOTES: --CAN'T BE ALTERED EXCEPT BY PROGRAMMER On Wednesday 25 May 2005 05:15 am, Usha wrote: Hi While listing the fields of NEW PERSON file from FileMan, the following is displayed 747.5CERTIFICATION%GTM-E-GVUNDEF, Global variable undefined: ^DD(200.07475,.01,0) At M source location WR+32^DDSU Can anyone help? Regards Usha -- Nancy Anthracite --- This SF.Net email is sponsored by Yahoo. Introducing Yahoo! Search Developer Network - Create apps using Yahoo! Search APIs Find out how you can build Yahoo! directly into your own Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005 ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
Re: [Hardhats-members] Another GTM error
Nancy; The IO* symbols are setup by the ^%ZIS routines. The values are determined by the device selected. Sorry, but I have to run right now. Best wishes; Chris - Original Message - From: Nancy Anthracite [EMAIL PROTECTED] To: hardhats-members@lists.sourceforge.net Sent: Wednesday, May 25, 2005 4:30 AM Subject: Re: [Hardhats-members] Another GTM error I would like to know how to chase this down for future reference. Am I on the right track and now what? How do I find out more about IOSL? This is what I did so far: I found the 32nd line after the tag WR in the routine DDSU.m. the line with the WR tag is 126. The lines below are 149-159 and there were no line wraps above to screw things up that I could see. It seems that WR+32 is probably line 157, so WR+32 must count the line with WR as 1, correct? W DDH(A0,A4) I $D(DDH(ID)) D S:$D(DUOUT) DIY=U . N DDD,DIY,DDSID . S DDSID=DDH(ID) . S:$D(DDH(ID,1))#2 DDSID(1)=DDH(ID,1) . N DDH . S:$D(DDSID(1))#2 DDH(ID,1)=DDSID(1) K DDSID(1) . S Y=A4 . S:$D(DDS) DDQ=$S(DY(IOSL-1):IOSL-1,1:DY)_U_$X . X DDSID Q IOSL is not newed and is used early in the routine,and gives me a value, so I assume it is the undefined global variable. This is immediately after I started up with D P^DI, which I think wipes the local variables, correct? GTMW IOSL 24 I asked for that section in the global, I think. GTMZWR ^DD(200.07475,.01,0) ^DD(200.07475,.01,0)=CERTIFICATION^MP747.9'^QA(747.9,^0;1^Q Then I looked in the Data Dictionary: ** Select OPTION: 8 DATA DICTIONARY UTILITIES Select DATA DICTIONARY UTILITY OPTION: ^ Select OPTION: ^ GTMD Q^DI VA FileMan 22.0 Select OPTION: 8 DATA DICTIONARY UTILITIES Select DATA DICTIONARY UTILITY OPTION: 1 LIST FILE ATTRIBUTES START WITH WHAT FILE: NEW PERSON// GO TO WHAT FILE: NEW PERSON// Select SUB-FILE: Select LISTING FORMAT: STANDARD// Start with field: FIRST// Certification Go to field: DEVICE: TELNET STANDARD DATA DICTIONARY #200 -- NEW PERSON FILE MAY 25,[EMAIL PROTECTED]:04:05 PAGE 1 STORED IN ^VA(200, (1154 ENTRIES) SITE: CAMP MASTER UCI: VAH,ROU (VERSION 8.0) DATA NAME GLOBALDATA ELEMENT TITLE LOCATION TYPE -- - 200,747.5 CERTIFICATION QAR2;0 POINTER Multiple #200.07475 DESCRIPTION: This field allows you to enter specialties in which the practitioner is Board Certified. 200.07475,.01 CERTIFICATION 0;1 POINTER ** TO AN UNDEFINED FILE ** (Multiply asked) LAST EDITED: FEB 01, 1991 HELP-PROMPT: Enter the specialties in which the practitioner is Board Certified. DESCRIPTION: This field allows you to enter specialties in which the practitioner is Board Certified. CROSS-REFERENCE: 200.07475^B 1)= S ^VA(200,DA(1),QAR2,B, $E(X,1,30),DA)= 2)= K ^VA(200,DA(1),QAR2,B,$E(X,1,30),DA) 200.07475,1 DATE 0;2 DATE INPUT TRANSFORM:S %DT=E D IN^QARVER1,^%DT S X=Y K:Y1 X NOTES: --CAN'T BE ALTERED EXCEPT BY PROGRAMMER On Wednesday 25 May 2005 05:15 am, Usha wrote: Hi While listing the fields of NEW PERSON file from FileMan, the following is displayed 747.5CERTIFICATION%GTM-E-GVUNDEF, Global variable undefined: ^DD(200.07475,.01,0) At M source location WR+32^DDSU Can anyone help? Regards Usha -- Nancy Anthracite --- This SF.Net email is sponsored by Yahoo. Introducing Yahoo! Search Developer Network - Create apps using Yahoo! Search APIs Find out how you can build Yahoo! directly into your own Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005 ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members --- This SF.Net email is sponsored by Yahoo. Introducing Yahoo! Search Developer Network - Create apps using Yahoo! Search APIs Find out how you can build Yahoo! directly into your own Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005 ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
Re: [Hardhats-members] Another GTM error
Fileman is resilient against quite a few potential errors, but pointing to files not in the DD is not one of them. === Gregory Woodhouse [EMAIL PROTECTED] A practical man is a man who practices the errors of his forefathers. -- Benjamin Disraeli On May 25, 2005, at 5:45 AM, Gregory Woodhouse wrote: Yes, you're on the right track. IOSL is one of a number of documented Kernel variables that you can read about in the online documentation. This one is screen length, and is ultimately a value set by the device handler based on the DEVICE file. It is unrelated to the problem here. Notice that this is an invalid pointer, and without looking too closely, I'd guess that the problem here was an attempt to dereference it. === Gregory Woodhouse [EMAIL PROTECTED] The whole of science is nothing more than a refinement of everyday thinking. -- Albert Einstein --- This SF.Net email is sponsored by Yahoo. Introducing Yahoo! Search Developer Network - Create apps using Yahoo! Search APIs Find out how you can build Yahoo! directly into your own Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005 ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
Re: [Hardhats-members] Another GTM error
FWIW, I think you (Nancy) did a pretty good job of picking up on the relevant details. It might be useful to think of it this way: Kernel keeps track of session specific state (such as characteristics of the current output device) using various standard variables in the process symbol table. Particularly famous variables include DUZ (who's signed in) and the IO* variables. In this case, the issue with IOSL was secondary (having to do with checking to see if the error message will fit on the current screen/page). A good technique (if the error is logged in the error trap) is to look at the stack dump, so that you can trace your way back to the ultimate source of the trouble. --- [EMAIL PROTECTED] wrote: I would like to know how to chase this down for future reference. Am I on the right track and now what? How do I find out more about IOSL? This is what I did so far: I found the 32nd line after the tag WR in the routine DDSU.m. the line with the WR tag is 126. The lines below are 149-159 and there were no line wraps above to screw things up that I could see. It seems that WR+32 is probably line 157, so WR+32 must count the line with WR as 1, correct? Nancy, WR+32 is the line 32 lines later than WR. (WR counts as WR+0) to see the line directly, you can just type: MUMPS WRITE $TEXT(WR+32^DDSU),! . X DDSID which explains the headache, since it is an Xecute command on the local variable DDSID (which gets changed at run-time). As you can see in your code fragment below, the variable IOSL (Input-Output-Screen-Length) is only referenced on line WR+31 if the variable DDS is defined, either with sub-nodes, or a value itself. $D(DDS)= 1 , 10 or 11 (Self, SubnodesOnly, Self+Subnodes) This kind of problem is hard to debug, since it depends on the late-bound value of a variable. Usually, the only way to find out the problem is to use the ZWRITE DDSID command immediately after you see the error. W DDH(A0,A4) I $D(DDH(ID)) D S:$D(DUOUT) DIY=U . N DDD,DIY,DDSID . S DDSID=DDH(ID) . S:$D(DDH(ID,1))#2 DDSID(1)=DDH(ID,1) . N DDH . S:$D(DDSID(1))#2 DDH(ID,1)=DDSID(1) K DDSID(1) . S Y=A4 . S:$D(DDS) DDQ=$S(DY(IOSL-1):IOSL-1,1:DY)_U_$X . X DDSID Q IOSL is not newed and is used early in the routine,and gives me a value, so I assume it is the undefined global variable. This is immediately after I started up with D P^DI, which I think wipes the local variables, correct? GTMW IOSL 24 I asked for that section in the global, I think. GTMZWR ^DD(200.07475,.01,0) ^DD(200.07475,.01,0)=CERTIFICATION^MP747.9'^QA(747.9,^0;1^Q Then I looked in the Data Dictionary: ** Select OPTION: 8 DATA DICTIONARY UTILITIES Select DATA DICTIONARY UTILITY OPTION: ^ Select OPTION: ^ GTMD Q^DI VA FileMan 22.0 Select OPTION: 8 DATA DICTIONARY UTILITIES Select DATA DICTIONARY UTILITY OPTION: 1 LIST FILE ATTRIBUTES START WITH WHAT FILE: NEW PERSON// GO TO WHAT FILE: NEW PERSON// Select SUB-FILE: Select LISTING FORMAT: STANDARD// Start with field: FIRST// Certification Go to field: DEVICE: TELNET STANDARD DATA DICTIONARY #200 -- NEW PERSON FILE MAY 25,[EMAIL PROTECTED]:04:05 PAGE 1 STORED IN ^VA(200, (1154 ENTRIES) SITE: CAMP MASTER UCI: VAH,ROU (VERSION 8.0) DATA NAME GLOBALDATA ELEMENT TITLE LOCATION TYPE --- 200,747.5 CERTIFICATION QAR2;0 POINTER Multiple #200.07475 DESCRIPTION: This field allows you to enter specialties in which the practitioner is Board Certified. 200.07475,.01 CERTIFICATION 0;1 POINTER ** TO AN UNDEFINED FILE ** (Multiply asked) LAST EDITED: FEB 01, 1991 HELP-PROMPT: Enter the specialties in which the practitioner is Board Certified. DESCRIPTION: This field allows you to enter specialties in which the practitioner is Board Certified. CROSS-REFERENCE: 200.07475^B 1)= S ^VA(200,DA(1),QAR2,B, $E(X,1,30),DA)= 2)= K ^VA(200,DA(1),QAR2,B,$E(X,1,30),DA) 200.07475,1 DATE 0;2 DATE INPUT TRANSFORM:S %DT=E D IN^QARVER1,^%DT S X=Y K:Y1 X NOTES: --CAN'T BE ALTERED EXCEPT BY PROGRAMMER On Wednesday 25 May 2005 05:15 am, Usha wrote: Hi While listing the fields of NEW PERSON file from
Re: [Hardhats-members] Another GTM error
Frankly, I am very glad I asked this question because it is revealing of more than just my ignorance. How do you dump the stack? And the error trap your refer to is the one seen in D ^XTER? On Wednesday 25 May 2005 10:23 am, Greg Woodhouse wrote: FWIW, I think you (Nancy) did a pretty good job of picking up on the relevant details. It might be useful to think of it this way: Kernel keeps track of session specific state (such as characteristics of the current output device) using various standard variables in the process symbol table. Particularly famous variables include DUZ (who's signed in) and the IO* variables. In this case, the issue with IOSL was secondary (having to do with checking to see if the error message will fit on the current screen/page). A good technique (if the error is logged in the error trap) is to look at the stack dump, so that you can trace your way back to the ultimate source of the trouble. --- [EMAIL PROTECTED] wrote: I would like to know how to chase this down for future reference. Am I on the right track and now what? How do I find out more about IOSL? This is what I did so far: I found the 32nd line after the tag WR in the routine DDSU.m. the line with the WR tag is 126. The lines below are 149-159 and there were no line wraps above to screw things up that I could see. It seems that WR+32 is probably line 157, so WR+32 must count the line with WR as 1, correct? Nancy, WR+32 is the line 32 lines later than WR. (WR counts as WR+0) to see the line directly, you can just type: MUMPS WRITE $TEXT(WR+32^DDSU),! . X DDSID which explains the headache, since it is an Xecute command on the local variable DDSID (which gets changed at run-time). As you can see in your code fragment below, the variable IOSL (Input-Output-Screen-Length) is only referenced on line WR+31 if the variable DDS is defined, either with sub-nodes, or a value itself. $D(DDS)= 1 , 10 or 11 (Self, SubnodesOnly, Self+Subnodes) This kind of problem is hard to debug, since it depends on the late-bound value of a variable. Usually, the only way to find out the problem is to use the ZWRITE DDSID command immediately after you see the error. W DDH(A0,A4) I $D(DDH(ID)) D S:$D(DUOUT) DIY=U . N DDD,DIY,DDSID . S DDSID=DDH(ID) . S:$D(DDH(ID,1))#2 DDSID(1)=DDH(ID,1) . N DDH . S:$D(DDSID(1))#2 DDH(ID,1)=DDSID(1) K DDSID(1) . S Y=A4 . S:$D(DDS) DDQ=$S(DY(IOSL-1):IOSL-1,1:DY)_U_$X . X DDSID Q IOSL is not newed and is used early in the routine,and gives me a value, so I assume it is the undefined global variable. This is immediately after I started up with D P^DI, which I think wipes the local variables, correct? GTMW IOSL 24 I asked for that section in the global, I think. GTMZWR ^DD(200.07475,.01,0) ^DD(200.07475,.01,0)=CERTIFICATION^MP747.9'^QA(747.9,^0;1^Q Then I looked in the Data Dictionary: ** Select OPTION: 8 DATA DICTIONARY UTILITIES Select DATA DICTIONARY UTILITY OPTION: ^ Select OPTION: ^ GTMD Q^DI VA FileMan 22.0 Select OPTION: 8 DATA DICTIONARY UTILITIES Select DATA DICTIONARY UTILITY OPTION: 1 LIST FILE ATTRIBUTES START WITH WHAT FILE: NEW PERSON// GO TO WHAT FILE: NEW PERSON// Select SUB-FILE: Select LISTING FORMAT: STANDARD// Start with field: FIRST// Certification Go to field: DEVICE: TELNET STANDARD DATA DICTIONARY #200 -- NEW PERSON FILE MAY 25,[EMAIL PROTECTED]:04:05 PAGE 1 STORED IN ^VA(200, (1154 ENTRIES) SITE: CAMP MASTER UCI: VAH,ROU (VERSION 8.0) DATA NAME GLOBALDATA ELEMENT TITLE LOCATION TYPE --- 200,747.5 CERTIFICATION QAR2;0 POINTER Multiple #200.07475 DESCRIPTION: This field allows you to enter specialties in which the practitioner is Board Certified. 200.07475,.01 CERTIFICATION 0;1 POINTER ** TO AN UNDEFINED FILE ** (Multiply asked) LAST EDITED: FEB 01, 1991 HELP-PROMPT: Enter the specialties in which the practitioner is Board Certified. DESCRIPTION: This field allows you to enter specialties in which the practitioner is Board Certified. CROSS-REFERENCE: 200.07475^B 1)= S ^VA(200,DA(1),QAR2,B, $E(X,1,30),DA)= 2)= K
RE: [Hardhats-members] Another GTM error
Of course you're right. --- Cameron Schlehuber [EMAIL PROTECTED] wrote: Actually, pointing to missing files won't cause the problem reported here. Fileman does tolerate that. Having data at ^DD(200.07475,.01,nn but not at ^DD(200.07475,.01,0) WILL cause such errors. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gregory Woodhouse Sent: Wednesday, May 25, 2005 5:55 AM To: hardhats-members@lists.sourceforge.net Subject: Re: [Hardhats-members] Another GTM error Fileman is resilient against quite a few potential errors, but pointing to files not in the DD is not one of them. === Gregory Woodhouse [EMAIL PROTECTED] A practical man is a man who practices the errors of his forefathers. -- Benjamin Disraeli On May 25, 2005, at 5:45 AM, Gregory Woodhouse wrote: Yes, you're on the right track. IOSL is one of a number of documented Kernel variables that you can read about in the online documentation. This one is screen length, and is ultimately a value set by the device handler based on the DEVICE file. It is unrelated to the problem here. Notice that this is an invalid pointer, and without looking too closely, I'd guess that the problem here was an attempt to dereference it. === Gregory Woodhouse [EMAIL PROTECTED] The whole of science is nothing more than a refinement of everyday thinking. -- Albert Einstein --- This SF.Net email is sponsored by Yahoo. Introducing Yahoo! Search Developer Network - Create apps using Yahoo! Search APIs Find out how you can build Yahoo! directly into your own Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005 ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members --- SF.Net email is sponsored by: GoToMeeting - the easiest way to collaborate online with coworkers and clients while avoiding the high cost of travel and communications. There is no equipment to buy and you can meet as often as you want. Try it free.http://ads.osdn.com/?ad_id=7402alloc_id=16135op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members A practical man is a man who practices the errors of his forefathers. --Benjamin Disraeli Greg Woodhouse [EMAIL PROTECTED] [EMAIL PROTECTED] --- SF.Net email is sponsored by: GoToMeeting - the easiest way to collaborate online with coworkers and clients while avoiding the high cost of travel and communications. There is no equipment to buy and you can meet as often as you want. Try it free.http://ads.osdn.com/?ad_id=7402alloc_id=16135op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
RE: [Hardhats-members] Another GTM error
Nothing at that node, but I think the node in question was at: ^DD(200.07475, -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nancy Anthracite Sent: Wednesday, May 25, 2005 9:48 AM To: hardhats-members@lists.sourceforge.net Subject: Re: [Hardhats-members] Another GTM error So does this tell me that in my installation I have nothing? GTMD ^%G Output device: terminal: List ^DD(200.0745,.01,*) List ^ On Wednesday 25 May 2005 12:31 pm, Cameron Schlehuber wrote: Actually, pointing to missing files won't cause the problem reported here. Fileman does tolerate that. Having data at ^DD(200.07475,.01,nn but not at ^DD(200.07475,.01,0) WILL cause such errors. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gregory Woodhouse Sent: Wednesday, May 25, 2005 5:55 AM To: hardhats-members@lists.sourceforge.net Subject: Re: [Hardhats-members] Another GTM error Fileman is resilient against quite a few potential errors, but pointing to files not in the DD is not one of them. === Gregory Woodhouse [EMAIL PROTECTED] A practical man is a man who practices the errors of his forefathers. -- Benjamin Disraeli On May 25, 2005, at 5:45 AM, Gregory Woodhouse wrote: Yes, you're on the right track. IOSL is one of a number of documented Kernel variables that you can read about in the online documentation. This one is screen length, and is ultimately a value set by the device handler based on the DEVICE file. It is unrelated to the problem here. Notice that this is an invalid pointer, and without looking too closely, I'd guess that the problem here was an attempt to dereference it. === Gregory Woodhouse [EMAIL PROTECTED] The whole of science is nothing more than a refinement of everyday thinking. -- Albert Einstein --- This SF.Net email is sponsored by Yahoo. Introducing Yahoo! Search Developer Network - Create apps using Yahoo! Search APIs Find out how you can build Yahoo! directly into your own Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005 ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members --- SF.Net email is sponsored by: GoToMeeting - the easiest way to collaborate online with coworkers and clients while avoiding the high cost of travel and communications. There is no equipment to buy and you can meet as often as you want. Try it free.http://ads.osdn.com/?ad_id=7402alloc_id=16135op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members -- Nancy Anthracite --- SF.Net email is sponsored by: GoToMeeting - the easiest way to collaborate online with coworkers and clients while avoiding the high cost of travel and communications. There is no equipment to buy and you can meet as often as you want. Try it free.http://ads.osdn.com/?ad_id=7402alloc_id=16135op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members --- SF.Net email is sponsored by: GoToMeeting - the easiest way to collaborate online with coworkers and clients while avoiding the high cost of travel and communications. There is no equipment to buy and you can meet as often as you want. Try it free.http://ads.osdn.com/?ad_idt02alloc_id135op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
Re: [Hardhats-members] Another GTM error
Nancy, Take a look, also, at a quick summary of debugging commands I compiled for GTM here: http://openforum.worldvista.org/~forum/index.php?title=Debugging_with_GT.M It doesn't answer your qestion about dumping the stack (I can't remember how to do that either right now), but it gives other helpful tips. Kevin --- Nancy Anthracite [EMAIL PROTECTED] wrote: Frankly, I am very glad I asked this question because it is revealing of more than just my ignorance. How do you dump the stack? And the error trap your refer to is the one seen in D ^XTER? On Wednesday 25 May 2005 10:23 am, Greg Woodhouse wrote: FWIW, I think you (Nancy) did a pretty good job of picking up on the relevant details. It might be useful to think of it this way: Kernel keeps track of session specific state (such as characteristics of the current output device) using various standard variables in the process symbol table. Particularly famous variables include DUZ (who's signed in) and the IO* variables. In this case, the issue with IOSL was secondary (having to do with checking to see if the error message will fit on the current screen/page). A good technique (if the error is logged in the error trap) is to look at the stack dump, so that you can trace your way back to the ultimate source of the trouble. --- [EMAIL PROTECTED] wrote: I would like to know how to chase this down for future reference. Am I on the right track and now what? How do I find out more about IOSL? This is what I did so far: I found the 32nd line after the tag WR in the routine DDSU.m. the line with the WR tag is 126. The lines below are 149-159 and there were no line wraps above to screw things up that I could see. It seems that WR+32 is probably line 157, so WR+32 must count the line with WR as 1, correct? Nancy, WR+32 is the line 32 lines later than WR. (WR counts as WR+0) to see the line directly, you can just type: MUMPS WRITE $TEXT(WR+32^DDSU),! . X DDSID which explains the headache, since it is an Xecute command on the local variable DDSID (which gets changed at run-time). As you can see in your code fragment below, the variable IOSL (Input-Output-Screen-Length) is only referenced on line WR+31 if the variable DDS is defined, either with sub-nodes, or a value itself. $D(DDS)= 1 , 10 or 11 (Self, SubnodesOnly, Self+Subnodes) This kind of problem is hard to debug, since it depends on the late-bound value of a variable. Usually, the only way to find out the problem is to use the ZWRITE DDSID command immediately after you see the error. W DDH(A0,A4) I $D(DDH(ID)) D S:$D(DUOUT) DIY=U . N DDD,DIY,DDSID . S DDSID=DDH(ID) . S:$D(DDH(ID,1))#2 DDSID(1)=DDH(ID,1) . N DDH . S:$D(DDSID(1))#2 DDH(ID,1)=DDSID(1) K DDSID(1) . S Y=A4 . S:$D(DDS) DDQ=$S(DY(IOSL-1):IOSL-1,1:DY)_U_$X . X DDSID Q IOSL is not newed and is used early in the routine,and gives me a value, so I assume it is the undefined global variable. This is immediately after I started up with D P^DI, which I think wipes the local variables, correct? GTMW IOSL 24 I asked for that section in the global, I think. GTMZWR ^DD(200.07475,.01,0) ^DD(200.07475,.01,0)=CERTIFICATION^MP747.9'^QA(747.9,^0;1^Q Then I looked in the Data Dictionary: ** Select OPTION: 8 DATA DICTIONARY UTILITIES Select DATA DICTIONARY UTILITY OPTION: ^ Select OPTION: ^ GTMD Q^DI VA FileMan 22.0 Select OPTION: 8 DATA DICTIONARY UTILITIES Select DATA DICTIONARY UTILITY OPTION: 1 LIST FILE ATTRIBUTES START WITH WHAT FILE: NEW PERSON// GO TO WHAT FILE: NEW PERSON// Select SUB-FILE: Select LISTING FORMAT: STANDARD// Start with field: FIRST// Certification Go to field: DEVICE: TELNET STANDARD DATA DICTIONARY #200 -- NEW PERSON FILE MAY 25,[EMAIL PROTECTED]:04:05 PAGE 1 STORED IN ^VA(200, (1154 ENTRIES) SITE: CAMP MASTER UCI: VAH,ROU (VERSION 8.0) DATA NAME GLOBAL DATA ELEMENT TITLE LOCATION TYPE --- 200,747.5 CERTIFICATION QAR2;0 POINTER Multiple #200.07475 DESCRIPTION: This field allows you to enter specialties in which the practitioner is Board Certified. 200.07475,.01 CERTIFICATION 0;1 POINTER ** TO AN UNDEFINED FILE ** (Multiply asked) LAST EDITED: FEB 01, 1991
RE: [Hardhats-members] Another GTM error
One can manually reconstruct things, but it's usually safer (and less labor if a lot is missing) to create a KIDS build from a reliable account for just the components involved then import it. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kevin Toppenberg Sent: Wednesday, May 25, 2005 1:33 PM To: hardhats-members@lists.sourceforge.net Subject: RE: [Hardhats-members] Another GTM error My question, looking at this, is how to go about fixing such a problem. I assume a node was blown away somehow. Would it have to be manually reconstructed? Kevin --- Cameron Schlehuber [EMAIL PROTECTED] wrote: Actually, pointing to missing files won't cause the problem reported here. Fileman does tolerate that. Having data at ^DD(200.07475,.01,nn but not at ^DD(200.07475,.01,0) WILL cause such errors. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gregory Woodhouse Sent: Wednesday, May 25, 2005 5:55 AM To: hardhats-members@lists.sourceforge.net Subject: Re: [Hardhats-members] Another GTM error Fileman is resilient against quite a few potential errors, but pointing to files not in the DD is not one of them. === Gregory Woodhouse [EMAIL PROTECTED] A practical man is a man who practices the errors of his forefathers. -- Benjamin Disraeli On May 25, 2005, at 5:45 AM, Gregory Woodhouse wrote: Yes, you're on the right track. IOSL is one of a number of documented Kernel variables that you can read about in the online documentation. This one is screen length, and is ultimately a value set by the device handler based on the DEVICE file. It is unrelated to the problem here. Notice that this is an invalid pointer, and without looking too closely, I'd guess that the problem here was an attempt to dereference it. === Gregory Woodhouse [EMAIL PROTECTED] The whole of science is nothing more than a refinement of everyday thinking. -- Albert Einstein --- This SF.Net email is sponsored by Yahoo. Introducing Yahoo! Search Developer Network - Create apps using Yahoo! Search APIs Find out how you can build Yahoo! directly into your own Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005 ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members --- SF.Net email is sponsored by: GoToMeeting - the easiest way to collaborate online with coworkers and clients while avoiding the high cost of travel and communications. There is no equipment to buy and you can meet as often as you want. Try it free.http://ads.osdn.com/?ad_id=7402alloc_id=16135op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --- SF.Net email is sponsored by: GoToMeeting - the easiest way to collaborate online with coworkers and clients while avoiding the high cost of travel and communications. There is no equipment to buy and you can meet as often as you want. Try it free.http://ads.osdn.com/?ad_id=7402alloc_id=16135op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members --- SF.Net email is sponsored by: GoToMeeting - the easiest way to collaborate online with coworkers and clients while avoiding the high cost of travel and communications. There is no equipment to buy and you can meet as often as you want. Try it free.http://ads.osdn.com/?ad_idt02alloc_id135op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
Re: [Hardhats-members] Another GTM error
Dumb. Dumb. Dumb. OK, here it is again. GTMZWR ^DD(200.07475,.01,*) ^DD(200.07475,.01,0)=CERTIFICATION^MP747.9'^QA(747.9,^0;1^Q ^DD(200.07475,.01,1,0)=^.1 ^DD(200.07475,.01,1,1,0)=200.07475^B ^DD(200.07475,.01,1,1,1)=S ^VA(200,DA(1),QAR2,B,$E(X,1,30),DA)= ^DD(200.07475,.01,1,1,2)=K ^VA(200,DA(1),QAR2,B,$E(X,1,30),DA) ^DD(200.07475,.01,3)=Enter the specialties in which the practitioner is BoardCertified. ^DD(200.07475,.01,21,0)=^^4^4^2910410^^ ^DD(200.07475,.01,21,1,0)=This field allows you to enter specialties in which the practitioner is ^DD(200.07475,.01,21,2,0)=Board Certified. ^DD(200.07475,.01,21,3,0)= ^DD(200.07475,.01,21,4,0)= ^DD(200.07475,.01,DT)=2910201 After having seen the data dictionary and all, I thought I would like to see what it looked like when I tried to enter something here. It was just dumb luck there was something wrong here as well. This is from the VA Demo. Select OPTION: 1 ENTER OR EDIT FILE ENTRIES INPUT TO WHAT FILE: NEW PERSON// EDIT WHICH FIELD: ALL// CertIFICATION(multiple) EDIT WHICH CERTIFICATION SUB-FIELD: ALL// THEN EDIT FIELD: Select NEW PERSON NAME: `138 MANAGER,SYSTEM SM RCR Select CERTIFICATION: Internal Medicine ?? Select CERTIFICATION: ?? You may enter a new CERTIFICATION, if you wish This field allows you to enter specialties in which the practitioner is Board Certified. Pointed-to File does not exist! Select CERTIFICATION: On Wednesday 25 May 2005 01:03 pm, Cameron Schlehuber wrote: Nothing at that node, but I think the node in question was at: ^DD(200.07475, -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nancy Anthracite Sent: Wednesday, May 25, 2005 9:48 AM To: hardhats-members@lists.sourceforge.net Subject: Re: [Hardhats-members] Another GTM error So does this tell me that in my installation I have nothing? GTMD ^%G Output device: terminal: List ^DD(200.0745,.01,*) List ^ On Wednesday 25 May 2005 12:31 pm, Cameron Schlehuber wrote: Actually, pointing to missing files won't cause the problem reported here. Fileman does tolerate that. Having data at ^DD(200.07475,.01,nn but not at ^DD(200.07475,.01,0) WILL cause such errors. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gregory Woodhouse Sent: Wednesday, May 25, 2005 5:55 AM To: hardhats-members@lists.sourceforge.net Subject: Re: [Hardhats-members] Another GTM error Fileman is resilient against quite a few potential errors, but pointing to files not in the DD is not one of them. === Gregory Woodhouse [EMAIL PROTECTED] A practical man is a man who practices the errors of his forefathers. -- Benjamin Disraeli On May 25, 2005, at 5:45 AM, Gregory Woodhouse wrote: Yes, you're on the right track. IOSL is one of a number of documented Kernel variables that you can read about in the online documentation. This one is screen length, and is ultimately a value set by the device handler based on the DEVICE file. It is unrelated to the problem here. Notice that this is an invalid pointer, and without looking too closely, I'd guess that the problem here was an attempt to dereference it. === Gregory Woodhouse [EMAIL PROTECTED] The whole of science is nothing more than a refinement of everyday thinking. -- Albert Einstein --- This SF.Net email is sponsored by Yahoo. Introducing Yahoo! Search Developer Network - Create apps using Yahoo! Search APIs Find out how you can build Yahoo! directly into your own Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005 ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members --- SF.Net email is sponsored by: GoToMeeting - the easiest way to collaborate online with coworkers and clients while avoiding the high cost of travel and communications. There is no equipment to buy and you can meet as often as you want. Try it free.http://ads.osdn.com/?ad_id=7402alloc_id=16135op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members -- Nancy Anthracite --- SF.Net email is sponsored by: GoToMeeting - the easiest way to collaborate online with coworkers and clients while avoiding the high cost of travel and communications. There is no equipment to buy and you can meet as often as you want. Try it free.http://ads.osdn.com/?ad_id=7402alloc_id=16135op=click ___ Hardhats-members mailing list Hardhats
RE: [Hardhats-members] Another GTM error
That's how FM is supposed to work! It doesn't throw you into the error trap, just gives you a gentle notice that a file is missing. I've logged a request to have the fields removed in the NEW PERSON file that are pointing to old files that have been removed. (When those files were removed, the developers responsible should have arranged for the cleanup in file 200, too. The system is just so forgiving though!) A patch will be forthcoming in a month or two. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nancy Anthracite Sent: Wednesday, May 25, 2005 11:06 AM To: hardhats-members@lists.sourceforge.net Subject: Re: [Hardhats-members] Another GTM error Dumb. Dumb. Dumb. OK, here it is again. GTMZWR ^DD(200.07475,.01,*) ^DD(200.07475,.01,0)=CERTIFICATION^MP747.9'^QA(747.9,^0;1^Q ^DD(200.07475,.01,1,0)=^.1 ^DD(200.07475,.01,1,1,0)=200.07475^B ^DD(200.07475,.01,1,1,1)=S ^VA(200,DA(1),QAR2,B,$E(X,1,30),DA)= ^DD(200.07475,.01,1,1,2)=K ^VA(200,DA(1),QAR2,B,$E(X,1,30),DA) ^DD(200.07475,.01,3)=Enter the specialties in which the practitioner is BoardCertified. ^DD(200.07475,.01,21,0)=^^4^4^2910410^^ ^DD(200.07475,.01,21,1,0)=This field allows you to enter specialties in which the practitioner is ^DD(200.07475,.01,21,2,0)=Board Certified. ^DD(200.07475,.01,21,3,0)= ^DD(200.07475,.01,21,4,0)= ^DD(200.07475,.01,DT)=2910201 After having seen the data dictionary and all, I thought I would like to see what it looked like when I tried to enter something here. It was just dumb luck there was something wrong here as well. This is from the VA Demo. Select OPTION: 1 ENTER OR EDIT FILE ENTRIES INPUT TO WHAT FILE: NEW PERSON// EDIT WHICH FIELD: ALL// CertIFICATION(multiple) EDIT WHICH CERTIFICATION SUB-FIELD: ALL// THEN EDIT FIELD: Select NEW PERSON NAME: `138 MANAGER,SYSTEM SM RCR Select CERTIFICATION: Internal Medicine ?? Select CERTIFICATION: ?? You may enter a new CERTIFICATION, if you wish This field allows you to enter specialties in which the practitioner is Board Certified. Pointed-to File does not exist! Select CERTIFICATION: On Wednesday 25 May 2005 01:03 pm, Cameron Schlehuber wrote: Nothing at that node, but I think the node in question was at: ^DD(200.07475, -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nancy Anthracite Sent: Wednesday, May 25, 2005 9:48 AM To: hardhats-members@lists.sourceforge.net Subject: Re: [Hardhats-members] Another GTM error So does this tell me that in my installation I have nothing? GTMD ^%G Output device: terminal: List ^DD(200.0745,.01,*) List ^ On Wednesday 25 May 2005 12:31 pm, Cameron Schlehuber wrote: Actually, pointing to missing files won't cause the problem reported here. Fileman does tolerate that. Having data at ^DD(200.07475,.01,nn but not at ^DD(200.07475,.01,0) WILL cause such errors. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gregory Woodhouse Sent: Wednesday, May 25, 2005 5:55 AM To: hardhats-members@lists.sourceforge.net Subject: Re: [Hardhats-members] Another GTM error Fileman is resilient against quite a few potential errors, but pointing to files not in the DD is not one of them. === Gregory Woodhouse [EMAIL PROTECTED] A practical man is a man who practices the errors of his forefathers. -- Benjamin Disraeli On May 25, 2005, at 5:45 AM, Gregory Woodhouse wrote: Yes, you're on the right track. IOSL is one of a number of documented Kernel variables that you can read about in the online documentation. This one is screen length, and is ultimately a value set by the device handler based on the DEVICE file. It is unrelated to the problem here. Notice that this is an invalid pointer, and without looking too closely, I'd guess that the problem here was an attempt to dereference it. === Gregory Woodhouse [EMAIL PROTECTED] The whole of science is nothing more than a refinement of everyday thinking. -- Albert Einstein --- This SF.Net email is sponsored by Yahoo. Introducing Yahoo! Search Developer Network - Create apps using Yahoo! Search APIs Find out how you can build Yahoo! directly into your own Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005 ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members --- SF.Net email is sponsored by: GoToMeeting - the easiest way to collaborate online with coworkers and clients while avoiding the high cost of travel and communications. There is no equipment to buy and you can meet as often as you want. Try it free.http
Re: [Hardhats-members] Another GTM error
No, but I think there is a path length limitation. Try it from a short path, if you are not already doing so. Lloyd - Original Message - From: Thurman Pedigo [EMAIL PROTECTED] To: hardhats-members@lists.sourceforge.net Sent: Wednesday, May 25, 2005 6:58 PM Subject: RE: [Hardhats-members] Another GTM error Is there a special folder to place a KIDS build/transport? I am having problems getting VistA to find a KIDS upgrade. The system is VistA running on Cache with Win2K server. Thanks, thurman -Original Message- From: [EMAIL PROTECTED] [mailto:hardhats- [EMAIL PROTECTED] On Behalf Of Cameron Schlehuber Sent: Wednesday, May 25, 2005 2:46 PM To: hardhats-members@lists.sourceforge.net Subject: RE: [Hardhats-members] Another GTM error One can manually reconstruct things, but it's usually safer (and less labor if a lot is missing) to create a KIDS build from a reliable account for just the components involved then import it. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kevin Toppenberg Sent: Wednesday, May 25, 2005 1:33 PM To: hardhats-members@lists.sourceforge.net Subject: RE: [Hardhats-members] Another GTM error My question, looking at this, is how to go about fixing such a problem. I assume a node was blown away somehow. Would it have to be manually reconstructed? Kevin --- Cameron Schlehuber [EMAIL PROTECTED] wrote: Actually, pointing to missing files won't cause the problem reported here. Fileman does tolerate that. Having data at ^DD(200.07475,.01,nn but not at ^DD(200.07475,.01,0) WILL cause such errors. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gregory Woodhouse Sent: Wednesday, May 25, 2005 5:55 AM To: hardhats-members@lists.sourceforge.net Subject: Re: [Hardhats-members] Another GTM error Fileman is resilient against quite a few potential errors, but pointing to files not in the DD is not one of them. === Gregory Woodhouse [EMAIL PROTECTED] A practical man is a man who practices the errors of his forefathers. -- Benjamin Disraeli On May 25, 2005, at 5:45 AM, Gregory Woodhouse wrote: Yes, you're on the right track. IOSL is one of a number of documented Kernel variables that you can read about in the online documentation. This one is screen length, and is ultimately a value set by the device handler based on the DEVICE file. It is unrelated to the problem here. Notice that this is an invalid pointer, and without looking too closely, I'd guess that the problem here was an attempt to dereference it. === Gregory Woodhouse [EMAIL PROTECTED] The whole of science is nothing more than a refinement of everyday thinking. -- Albert Einstein --- This SF.Net email is sponsored by Yahoo. Introducing Yahoo! Search Developer Network - Create apps using Yahoo! Search APIs Find out how you can build Yahoo! directly into your own Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005 ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members --- SF.Net email is sponsored by: GoToMeeting - the easiest way to collaborate online with coworkers and clients while avoiding the high cost of travel and communications. There is no equipment to buy and you can meet as often as you want. Try it free.http://ads.osdn.com/?ad_id=7402alloc_id=16135op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --- SF.Net email is sponsored by: GoToMeeting - the easiest way to collaborate online with coworkers and clients while avoiding the high cost of travel and communications. There is no equipment to buy and you can meet as often as you want. Try it free.http://ads.osdn.com/?ad_id=7402alloc_id=16135op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members --- SF.Net email is sponsored by: GoToMeeting - the easiest way to collaborate online with coworkers and clients while avoiding the high cost of travel and communications. There is no equipment to buy and you can meet as often as you want. Try it free.http://ads.osdn.com/?ad_idt02alloc_id135op=ick ___ Hardhats-members mailing list Hardhats-members
RE: [Hardhats-members] Another GTM error
Sorry for jumping in, in the middle, but could someone please help me stop getting double posts before I have to check into an AA program? Thanks. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Lloyd Milligan Sent: Wednesday, May 25, 2005 8:03 PM To: hardhats-members@lists.sourceforge.net Subject: Re: [Hardhats-members] Another GTM error No, but I think there is a path length limitation. Try it from a short path, if you are not already doing so. Lloyd - Original Message - From: Thurman Pedigo [EMAIL PROTECTED] To: hardhats-members@lists.sourceforge.net Sent: Wednesday, May 25, 2005 6:58 PM Subject: RE: [Hardhats-members] Another GTM error Is there a special folder to place a KIDS build/transport? I am having problems getting VistA to find a KIDS upgrade. The system is VistA running on Cache with Win2K server. Thanks, thurman -Original Message- From: [EMAIL PROTECTED] [mailto:hardhats- [EMAIL PROTECTED] On Behalf Of Cameron Schlehuber Sent: Wednesday, May 25, 2005 2:46 PM To: hardhats-members@lists.sourceforge.net Subject: RE: [Hardhats-members] Another GTM error One can manually reconstruct things, but it's usually safer (and less labor if a lot is missing) to create a KIDS build from a reliable account for just the components involved then import it. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kevin Toppenberg Sent: Wednesday, May 25, 2005 1:33 PM To: hardhats-members@lists.sourceforge.net Subject: RE: [Hardhats-members] Another GTM error My question, looking at this, is how to go about fixing such a problem. I assume a node was blown away somehow. Would it have to be manually reconstructed? Kevin --- Cameron Schlehuber [EMAIL PROTECTED] wrote: Actually, pointing to missing files won't cause the problem reported here. Fileman does tolerate that. Having data at ^DD(200.07475,.01,nn but not at ^DD(200.07475,.01,0) WILL cause such errors. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gregory Woodhouse Sent: Wednesday, May 25, 2005 5:55 AM To: hardhats-members@lists.sourceforge.net Subject: Re: [Hardhats-members] Another GTM error Fileman is resilient against quite a few potential errors, but pointing to files not in the DD is not one of them. === Gregory Woodhouse [EMAIL PROTECTED] A practical man is a man who practices the errors of his forefathers. -- Benjamin Disraeli On May 25, 2005, at 5:45 AM, Gregory Woodhouse wrote: Yes, you're on the right track. IOSL is one of a number of documented Kernel variables that you can read about in the online documentation. This one is screen length, and is ultimately a value set by the device handler based on the DEVICE file. It is unrelated to the problem here. Notice that this is an invalid pointer, and without looking too closely, I'd guess that the problem here was an attempt to dereference it. === Gregory Woodhouse [EMAIL PROTECTED] The whole of science is nothing more than a refinement of everyday thinking. -- Albert Einstein --- This SF.Net email is sponsored by Yahoo. Introducing Yahoo! Search Developer Network - Create apps using Yahoo! Search APIs Find out how you can build Yahoo! directly into your own Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005 ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members --- SF.Net email is sponsored by: GoToMeeting - the easiest way to collaborate online with coworkers and clients while avoiding the high cost of travel and communications. There is no equipment to buy and you can meet as often as you want. Try it free.http://ads.osdn.com/?ad_id=7402alloc_id=16135op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --- SF.Net email is sponsored by: GoToMeeting - the easiest way to collaborate online with coworkers and clients while avoiding the high cost of travel and communications. There is no equipment to buy and you can meet as often as you want. Try it free.http://ads.osdn.com/?ad_id=7402alloc_id=16135op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net
Re: [Hardhats-members] Another GTM error
Nice! Thanks. On Wednesday 25 May 2005 04:24 pm, Kevin Toppenberg wrote: Nancy, Take a look, also, at a quick summary of debugging commands I compiled for GTM here: http://openforum.worldvista.org/~forum/index.php?title=Debugging_with_GT.M It doesn't answer your qestion about dumping the stack (I can't remember how to do that either right now), but it gives other helpful tips. Kevin --- Nancy Anthracite [EMAIL PROTECTED] wrote: Frankly, I am very glad I asked this question because it is revealing of more than just my ignorance. How do you dump the stack? And the error trap your refer to is the one seen in D ^XTER? On Wednesday 25 May 2005 10:23 am, Greg Woodhouse wrote: FWIW, I think you (Nancy) did a pretty good job of picking up on the relevant details. It might be useful to think of it this way: Kernel keeps track of session specific state (such as characteristics of the current output device) using various standard variables in the process symbol table. Particularly famous variables include DUZ (who's signed in) and the IO* variables. In this case, the issue with IOSL was secondary (having to do with checking to see if the error message will fit on the current screen/page). A good technique (if the error is logged in the error trap) is to look at the stack dump, so that you can trace your way back to the ultimate source of the trouble. --- [EMAIL PROTECTED] wrote: I would like to know how to chase this down for future reference. Am I on the right track and now what? How do I find out more about IOSL? This is what I did so far: I found the 32nd line after the tag WR in the routine DDSU.m. the line with the WR tag is 126. The lines below are 149-159 and there were no line wraps above to screw things up that I could see. It seems that WR+32 is probably line 157, so WR+32 must count the line with WR as 1, correct? Nancy, WR+32 is the line 32 lines later than WR. (WR counts as WR+0) to see the line directly, you can just type: MUMPS WRITE $TEXT(WR+32^DDSU),! . X DDSID which explains the headache, since it is an Xecute command on the local variable DDSID (which gets changed at run-time). As you can see in your code fragment below, the variable IOSL (Input-Output-Screen-Length) is only referenced on line WR+31 if the variable DDS is defined, either with sub-nodes, or a value itself. $D(DDS)= 1 , 10 or 11 (Self, SubnodesOnly, Self+Subnodes) This kind of problem is hard to debug, since it depends on the late-bound value of a variable. Usually, the only way to find out the problem is to use the ZWRITE DDSID command immediately after you see the error. W DDH(A0,A4) I $D(DDH(ID)) D S:$D(DUOUT) DIY=U . N DDD,DIY,DDSID . S DDSID=DDH(ID) . S:$D(DDH(ID,1))#2 DDSID(1)=DDH(ID,1) . N DDH . S:$D(DDSID(1))#2 DDH(ID,1)=DDSID(1) K DDSID(1) . S Y=A4 . S:$D(DDS) DDQ=$S(DY(IOSL-1):IOSL-1,1:DY)_U_$X . X DDSID Q IOSL is not newed and is used early in the routine,and gives me a value, so I assume it is the undefined global variable. This is immediately after I started up with D P^DI, which I think wipes the local variables, correct? GTMW IOSL 24 I asked for that section in the global, I think. GTMZWR ^DD(200.07475,.01,0) ^DD(200.07475,.01,0)=CERTIFICATION^MP747.9'^QA(747.9,^0;1^Q Then I looked in the Data Dictionary: ** Select OPTION: 8 DATA DICTIONARY UTILITIES Select DATA DICTIONARY UTILITY OPTION: ^ Select OPTION: ^ GTMD Q^DI VA FileMan 22.0 Select OPTION: 8 DATA DICTIONARY UTILITIES Select DATA DICTIONARY UTILITY OPTION: 1 LIST FILE ATTRIBUTES START WITH WHAT FILE: NEW PERSON// GO TO WHAT FILE: NEW PERSON// Select SUB-FILE: Select LISTING FORMAT: STANDARD// Start with field: FIRST// Certification Go to field: DEVICE: TELNET STANDARD DATA DICTIONARY #200 -- NEW PERSON FILE MAY 25,[EMAIL PROTECTED]:04:05 PAGE 1 STORED IN ^VA(200, (1154 ENTRIES) SITE: CAMP MASTER UCI: VAH,ROU (VERSION 8.0) DATA NAME GLOBAL DATA ELEMENT TITLE LOCATION TYPE --- 200,747.5 CERTIFICATION QAR2;0 POINTER Multiple #200.07475 DESCRIPTION: This field allows you to enter specialties in
RE: [Hardhats-members] Another GTM error
ZSHOW (which defaults to ZSHOW S to dump the stack - there are several options of things to show). Regards -- Bhaskar -Original Message- From: [EMAIL PROTECTED] on behalf of Nancy Anthracite Sent: Wed 5/25/2005 11:38 AM To: hardhats-members@lists.sourceforge.net Cc: Subject:Re: [Hardhats-members] Another GTM error Frankly, I am very glad I asked this question because it is revealing of more than just my ignorance. How do you dump the stack? And the error trap your refer to is the one seen in D ^XTER? winmail.dat
Re: [Hardhats-members] Another GTM error
Cameron's suggestion of re-installing the file from a KIDS build is probably your safest course. === Gregory Woodhouse [EMAIL PROTECTED] A practical man is a man who practices the errors of his forefathers. -- Benjamin Disraeli On May 25, 2005, at 9:29 PM, Usha wrote: When I look at my DATA DICTIONARY entry, this is what I get GTMd Q^DI VA FileMan 22.0 Select OPTION: 8 DATA DICTIONARY UTILITIES Select DATA DICTIONARY UTILITY OPTION: 1 LIST FILE ATTRIBUTES START WITH WHAT FILE: NEW PERSON// GO TO WHAT FILE: NEW PERSON// Select SUB-FILE: Select LISTING FORMAT: STANDARD// Start with field: FIRST// CERTIFICATION Go to field: STANDARD DATA DICTIONARY #200 -- NEW PERSON FILE MAY 26,[EMAIL PROTECTED]:54:31 PAGE 1 STORED IN ^VA(200, (150 ENTRIES) SITE: HUIVISTA3 UCI: ROU,ROU (VERSION 8.0) DATA NAME GLOBALDATA ELEMENT TITLE LOCATION TYPE -- -- --- 200,747.5 CERTIFICATION QAR2;0 POINTER Multiple #200.07475 DESCRIPTION: This field allows you to enter specialties in which the practitioner is Board Certified. 200,747.6 BOARD ELIGIBLE QAR4;0 POINTER Multiple #200.07476 (Add New Entry without Asking) DESCRIPTION: If this applicant is eligible to complete specialty board exams, enter the area of specialty. 200.07476,2 VERIFICATION 0;3 SET '1' FOR LETTER FROM TRAINING DIRECTOR; '2' FOR LETTER FROM SPECIALTY BOARD; ... Is it that my global is corrupted? How can I rectify it? Regards Usha - Original Message - From: Nancy Anthracite [EMAIL PROTECTED] To: hardhats-members@lists.sourceforge.net Sent: Wednesday, May 25, 2005 5:00 PM Subject: Re: [Hardhats-members] Another GTM error I would like to know how to chase this down for future reference. Am I on the right track and now what? How do I find out more about IOSL? This is what I did so far: I found the 32nd line after the tag WR in the routine DDSU.m. the line with the WR tag is 126. The lines below are 149-159 and there were no line wraps above to screw things up that I could see. It seems that WR+32 is probably line 157, so WR+32 must count the line with WR as 1, correct? W DDH(A0,A4) I $D(DDH(ID)) D S:$D(DUOUT) DIY=U . N DDD,DIY,DDSID . S DDSID=DDH(ID) . S:$D(DDH(ID,1))#2 DDSID(1)=DDH(ID,1) . N DDH . S:$D(DDSID(1))#2 DDH(ID,1)=DDSID(1) K DDSID(1) . S Y=A4 . S:$D(DDS) DDQ=$S(DY(IOSL-1):IOSL-1,1:DY)_U_$X . X DDSID Q IOSL is not newed and is used early in the routine,and gives me a value, so I assume it is the undefined global variable. This is immediately after I started up with D P^DI, which I think wipes the local variables, correct? GTMW IOSL 24 I asked for that section in the global, I think. GTMZWR ^DD(200.07475,.01,0) ^DD(200.07475,.01,0)=CERTIFICATION^MP747.9'^QA(747.9,^0;1^Q Then I looked in the Data Dictionary: ** Select OPTION: 8 DATA DICTIONARY UTILITIES Select DATA DICTIONARY UTILITY OPTION: ^ Select OPTION: ^ GTMD Q^DI VA FileMan 22.0 Select OPTION: 8 DATA DICTIONARY UTILITIES Select DATA DICTIONARY UTILITY OPTION: 1 LIST FILE ATTRIBUTES START WITH WHAT FILE: NEW PERSON// GO TO WHAT FILE: NEW PERSON// Select SUB-FILE: Select LISTING FORMAT: STANDARD// Start with field: FIRST// Certification Go to field: DEVICE: TELNET STANDARD DATA DICTIONARY #200 -- NEW PERSON FILE MAY 25,[EMAIL PROTECTED]:04:05 PAGE 1 STORED IN ^VA(200, (1154 ENTRIES) SITE: CAMP MASTER UCI: VAH,ROU (VERSION 8.0) DATA NAME GLOBALDATA ELEMENT TITLE LOCATION TYPE - - - 200,747.5 CERTIFICATION QAR2;0 POINTER Multiple #200.07475 DESCRIPTION: This field allows you to enter specialties in which the practitioner is Board Certified. 200.07475,.01 CERTIFICATION 0;1 POINTER ** TO AN UNDEFINED FILE ** (Multiply asked) LAST EDITED: FEB 01, 1991 HELP-PROMPT: Enter the specialties in which the practitioner is Board Certified. DESCRIPTION: This field allows you to enter specialties in which the practitioner is Board Certified. CROSS-REFERENCE: 200.07475^B 1)= S ^VA
Re: [Hardhats-members] Another GTM error
The command shows no output GTMZWR ^DD(200.07475,*) GTM Usha - Original Message - From: Chris Richardson To: hardhats-members@lists.sourceforge.net Sent: Wednesday, May 25, 2005 6:25 PM Subject: Re: [Hardhats-members] Another GTM error Usha; What you see there is an error message that there was an attempt to access the data dictionary, at a subfile of file 200, the first field of this subfile, but it seems to be missing. The error has occurred in routine, DDSU (Data Dictionary Setup, I would guess without actually looking), at line, WR+32. It looks like not all of your data dictionary (^DD)is present. Try this and see if there is anything there; ZWR ^DD(200.07475,*) Best wishes; Chris - Original Message - From: Usha To: hardhats-members@lists.sourceforge.net Sent: Wednesday, May 25, 2005 2:15 AM Subject: [Hardhats-members] Another GTM error Hi While listing the fields of NEW PERSON file from FileMan, the following is displayed 747.5 CERTIFICATION%GTM-E-GVUNDEF, Global variable undefined: ^DD(200.07475,.01,0) At M source location WR+32^DDSU Can anyone help? Regards Usha
Re: [Hardhats-members] Another GTM error
GTMD ^XTER In response to the DATE prompt you can enter: 'S' to specify text to be matched in error or routine name No error logged on 5/26/2005 Which date? t-1 1 error logged on 5/25/2005 1) (UNDEF)PLBS+3^IMRUTST 10:14:31 ROU,ROU 5106 0 No screened error Usha - Original Message - From: Nancy Anthracite [EMAIL PROTECTED] To: hardhats-members@lists.sourceforge.net Sent: Wednesday, May 25, 2005 9:08 PM Subject: Re: [Hardhats-members] Another GTM error Frankly, I am very glad I asked this question because it is revealing of more than just my ignorance. How do you dump the stack? And the error trap your refer to is the one seen in D ^XTER? On Wednesday 25 May 2005 10:23 am, Greg Woodhouse wrote: FWIW, I think you (Nancy) did a pretty good job of picking up on the relevant details. It might be useful to think of it this way: Kernel keeps track of session specific state (such as characteristics of the current output device) using various standard variables in the process symbol table. Particularly famous variables include DUZ (who's signed in) and the IO* variables. In this case, the issue with IOSL was secondary (having to do with checking to see if the error message will fit on the current screen/page). A good technique (if the error is logged in the error trap) is to look at the stack dump, so that you can trace your way back to the ultimate source of the trouble. --- [EMAIL PROTECTED] wrote: I would like to know how to chase this down for future reference. Am I on the right track and now what? How do I find out more about IOSL? This is what I did so far: I found the 32nd line after the tag WR in the routine DDSU.m. the line with the WR tag is 126. The lines below are 149-159 and there were no line wraps above to screw things up that I could see. It seems that WR+32 is probably line 157, so WR+32 must count the line with WR as 1, correct? Nancy, WR+32 is the line 32 lines later than WR. (WR counts as WR+0) to see the line directly, you can just type: MUMPS WRITE $TEXT(WR+32^DDSU),! . X DDSID which explains the headache, since it is an Xecute command on the local variable DDSID (which gets changed at run-time). As you can see in your code fragment below, the variable IOSL (Input-Output-Screen-Length) is only referenced on line WR+31 if the variable DDS is defined, either with sub-nodes, or a value itself. $D(DDS)= 1 , 10 or 11 (Self, SubnodesOnly, Self+Subnodes) This kind of problem is hard to debug, since it depends on the late-bound value of a variable. Usually, the only way to find out the problem is to use the ZWRITE DDSID command immediately after you see the error. W DDH(A0,A4) I $D(DDH(ID)) D S:$D(DUOUT) DIY=U . N DDD,DIY,DDSID . S DDSID=DDH(ID) . S:$D(DDH(ID,1))#2 DDSID(1)=DDH(ID,1) . N DDH . S:$D(DDSID(1))#2 DDH(ID,1)=DDSID(1) K DDSID(1) . S Y=A4 . S:$D(DDS) DDQ=$S(DY(IOSL-1):IOSL-1,1:DY)_U_$X . X DDSID Q IOSL is not newed and is used early in the routine,and gives me a value, so I assume it is the undefined global variable. This is immediately after I started up with D P^DI, which I think wipes the local variables, correct? GTMW IOSL 24 I asked for that section in the global, I think. GTMZWR ^DD(200.07475,.01,0) ^DD(200.07475,.01,0)=CERTIFICATION^MP747.9'^QA(747.9,^0;1^Q Then I looked in the Data Dictionary: ** Select OPTION: 8 DATA DICTIONARY UTILITIES Select DATA DICTIONARY UTILITY OPTION: ^ Select OPTION: ^ GTMD Q^DI VA FileMan 22.0 Select OPTION: 8 DATA DICTIONARY UTILITIES Select DATA DICTIONARY UTILITY OPTION: 1 LIST FILE ATTRIBUTES START WITH WHAT FILE: NEW PERSON// GO TO WHAT FILE: NEW PERSON// Select SUB-FILE: Select LISTING FORMAT: STANDARD// Start with field: FIRST// Certification Go to field: DEVICE: TELNET STANDARD DATA DICTIONARY #200 -- NEW PERSON FILE MAY 25,[EMAIL PROTECTED]:04:05 PAGE 1 STORED IN ^VA(200, (1154 ENTRIES) SITE: CAMP MASTER UCI: VAH,ROU (VERSION 8.0) DATA NAME GLOBALDATA ELEMENT TITLE LOCATION TYPE -- - 200,747.5 CERTIFICATION QAR2;0 POINTER Multiple #200.07475 DESCRIPTION: This field allows you to enter specialties in which the practitioner is Board Certified. 200.07475,.01 CERTIFICATION 0;1 POINTER ** TO AN UNDEFINED FILE
