[U2] Fault type is 11. Layer type is BASIC run machine.
I’m getting the following error message: CRITICAL ERROR! Notify the system administrator. Abnormal termination of UniVerse. Fault type is 11. Layer type is BASIC run machine. Fault occurred in BASIC program IM.BUILD.NEW.COLD.WRK at address 228. I ran the IM.BUILD.NEW.COLD.WRK program in the DEBUG mode and found out that the error pops up when it executes the following line of code: WRITE COLD.TEXT ON COLD.WRK, COLD.WRK.ID THEN I found out the COLD.WRK is a TYPE 19 file. The COLD.WRK.ID is set to cold13-1.txt. I can use the PICK EDitor and view the txt file without a problem. The COLD.TEXT record is 53,486,974 bytes in size. I’ve opened up the permissions to the COLD.WRK file via chmod 777. I’ve also had additional space allocated. I am working on a system with Universe version 10.0.14 and AIX version 5.2.0.0. I appreciate your help, Jeff Colvin ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Fault type is 11. Layer type is BASIC run machine.
Can you write a record (anything) on the COLD.WRK file with the editor? I'd try another id, then that one itself? If not, have you checked not only for space but inodes being available on that filesystem? df -i on most 'nixes though AIX isn't in my usual repertoire... Also, does that record (file) actually exist already? If so, check the perms on the file itself. Those will override the directories if they're tighter. Robert Robert F. Porter, MCSE, CCNA, ZCE Lead Sr. Programmer / Analyst Laboratory Information Services Ochsner Health System This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful. Jeff Colvin jeff.col...@hotmail.com 1/18/2011 10:00 AM I’m getting the following error message: CRITICAL ERROR! Notify the system administrator. Abnormal termination of UniVerse. Fault type is 11. Layer type is BASIC run machine. Fault occurred in BASIC program IM.BUILD.NEW.COLD.WRK at address 228. I ran the IM.BUILD.NEW.COLD.WRK program in the DEBUG mode and found out that the error pops up when it executes the following line of code: WRITE COLD.TEXT ON COLD.WRK, COLD.WRK.ID THEN I found out the COLD.WRK is a TYPE 19 file. The COLD.WRK.ID is set to cold13-1.txt. I can use the PICK EDitor and view the txt file without a problem. The COLD.TEXT record is 53,486,974 bytes in size. I’ve opened up the permissions to the COLD.WRK file via chmod 777. I’ve also had additional space allocated. I am working on a system with Universe version 10.0.14 and AIX version 5.2.0.0. I appreciate your help, Jeff Colvin ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Fault type is 11. Layer type is BASIC run machine.
The first think that comes to mind (other than holy cow, he's writing a 54Meg record?), since you have apparently already considered disk space in the file system is inode availability. Jeff Colvin wrote: I’m getting the following error message: CRITICAL ERROR! Notify the system administrator. Abnormal termination of UniVerse. Fault type is 11. Layer type is BASIC run machine. Fault occurred in BASIC program IM.BUILD.NEW.COLD.WRK at address 228. I ran the IM.BUILD.NEW.COLD.WRK program in the DEBUG mode and found out that the error pops up when it executes the following line of code: WRITE COLD.TEXT ON COLD.WRK, COLD.WRK.ID THEN I found out the COLD.WRK is a TYPE 19 file. The COLD.WRK.ID is set to cold13-1.txt. I can use the PICK EDitor and view the txt file without a problem. The COLD.TEXT record is 53,486,974 bytes in size. I’ve opened up the permissions to the COLD.WRK file via chmod 777. I’ve also had additional space allocated. I am working on a system with Universe version 10.0.14 and AIX version 5.2.0.0. I appreciate your help, Jeff Colvin ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users -- Jeff Schasny - Denver, Co, USA jschasny at gmail dot com ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Fault type is 11. Layer type is BASIC run machine.
You're writing a 53MB sequential file in a single write. There are Universe config directives that you could tweak, but given that you're creating a text file within a directory I'd probably tweak the app to use OPENSEQ/WRITESEQ/CLOSESEQ code instead. That'll get rid of your crash and almost certainly make the app run faster. On 1/18/2011 11:00 AM, Jeff Colvin wrote: I’m getting the following error message: CRITICAL ERROR! Notify the system administrator. Abnormal termination of UniVerse. Fault type is 11. Layer type is BASIC run machine. Fault occurred in BASIC program IM.BUILD.NEW.COLD.WRK at address 228. I ran the IM.BUILD.NEW.COLD.WRK program in the DEBUG mode and found out that the error pops up when it executes the following line of code: WRITE COLD.TEXT ON COLD.WRK, COLD.WRK.ID THEN I found out the COLD.WRK is a TYPE 19 file. The COLD.WRK.ID is set to cold13-1.txt. I can use the PICK EDitor and view the txt file without a problem. The COLD.TEXT record is 53,486,974 bytes in size. I’ve opened up the permissions to the COLD.WRK file via chmod 777. I’ve also had additional space allocated. I am working on a system with Universe version 10.0.14 and AIX version 5.2.0.0. I appreciate your help, ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Fault type is 11. Layer type is BASIC run machine.
It sounds like you are blowing the memory stack with such a large item. With type 19 files you will want to do WRITESEQ so that it writes each individual line out keeping your memory intact. -Dan -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Jeff Colvin Sent: Tuesday, January 18, 2011 11:01 AM To: u2-users@listserver.u2ug.org Subject: [U2] Fault type is 11. Layer type is BASIC run machine. I’m getting the following error message: CRITICAL ERROR! Notify the system administrator. Abnormal termination of UniVerse. Fault type is 11. Layer type is BASIC run machine. Fault occurred in BASIC program IM.BUILD.NEW.COLD.WRK at address 228. I ran the IM.BUILD.NEW.COLD.WRK program in the DEBUG mode and found out that the error pops up when it executes the following line of code: WRITE COLD.TEXT ON COLD.WRK, COLD.WRK.ID THEN I found out the COLD.WRK is a TYPE 19 file. The COLD.WRK.ID is set to cold13-1.txt. I can use the PICK EDitor and view the txt file without a problem. The COLD.TEXT record is 53,486,974 bytes in size. I’ve opened up the permissions to the COLD.WRK file via chmod 777. I’ve also had additional space allocated. I am working on a system with Universe version 10.0.14 and AIX version 5.2.0.0. I appreciate your help, Jeff Colvin ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Fault type is 11. Layer type is BASIC run machine.
Are you accessing the file with the Sequential Access commands (Openseq, Readseq etc) ? If so, ensure you are doing a closeseq in the program. -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Jeff Colvin Sent: 18 January 2011 16:01 To: u2-users@listserver.u2ug.org Subject: [U2] Fault type is 11. Layer type is BASIC run machine. I’m getting the following error message: CRITICAL ERROR! Notify the system administrator. Abnormal termination of UniVerse. Fault type is 11. Layer type is BASIC run machine. Fault occurred in BASIC program IM.BUILD.NEW.COLD.WRK at address 228. I ran the IM.BUILD.NEW.COLD.WRK program in the DEBUG mode and found out that the error pops up when it executes the following line of code: WRITE COLD.TEXT ON COLD.WRK, COLD.WRK.ID THEN I found out the COLD.WRK is a TYPE 19 file. The COLD.WRK.ID is set to cold13-1.txt. I can use the PICK EDitor and view the txt file without a problem. The COLD.TEXT record is 53,486,974 bytes in size. I’ve opened up the permissions to the COLD.WRK file via chmod 777. I’ve also had additional space allocated. I am working on a system with Universe version 10.0.14 and AIX version 5.2.0.0. I appreciate your help, Jeff Colvin ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
[U2] [AD] New product mvLynx 2SQL is FusionWare's upgrade path for mv2SQL
[AD] New product mvLynx 2SQL is our upgrade path for mv2SQL. http://www.fwic.net/Products/MultiValueProducts/FusionWaremvLynx2SQL.aspx?s=lrd=20110118c=1 Robert Houben CTO FusionWare Integration Corp. p: 604-777-4254 x158 m:604-219-8394 f: 604-608-5544 http://www.fwic.net LinkedIn http://www.linkedin.com/company/fusionware-integration-corp.?trk=fc_badge Twitter http://www.twitter.com/fusionwareint FaceBookhttp://www.facebook.com/#!/pages/New-Westminster-BC/FusionWare-Integration-Corp/115116258510923 ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
[U2] Upgrading to latest UV/UD PE / Windows
A while back I posted a blog with details about upgrading Universe and Unidata. A lot of people found it to be helpful. nospamNebula-RnD.com/blog/tech/mv/2008/09/u2upgrade1.html (please remove 'nospam') I am now about to upgrade once again, just to ensure I have the very latest [ and greatest? ;) ]. I have specific questions about this endeavor: 1) Can anyone at Rocket confirm changes in the Universe 10.3.x installers which invalidate any statements I made about 10.2? Similarly for Unidata 7.2.7 vs 7.2.0. 2) What is the process for renewing PE licenses? Is there a prompt from the installer? Do we need to fill out some website form? Send an email? I don't think I've done this since the IBMRocket change. 3) Rather than installing an entire 600MB Clients for Windows package, is there a base package that can be obtained with just Uniadmin and UO support? 4) Please see issues with the Clients package documented in the blog, and comment if any of that is no longer accurate. 5) Is there a UVPE/Win v11? 6) Are there any other caveats or words of advice for minor upgrades like this? Final note for Rocket. On the download page the Expires date for UVPE shows 11 Nov Feb 2011. http://www.rocketsoftware.com/u2/resources/downloads I'll be happy to blog this experience like I did last time. Thanks! Tony Gravagno Nebula Research and Development TG@ remove.pleaseNebula-RnD.com Nebula RD sells mv.NET and other Pick/MultiValue products worldwide, and provides related development services remove.pleaseNebula-RnD.com/blog Visit PickWiki.com! Contribute! http://Twitter.com/TonyGravagno ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
[U2] LIST.READU - clear lock table ?
So great -- LIST.READU shows you some information ... but how do you clear these locks Active Record Locks: Device Inode Netnode Userno Lmode Pid Login Id Item-ID. 2621441 328100 50 4 RUS1970666 2621441 328100 48 30 RUS1970676 2621441 328100 44885 31 RUS1970557 = PID kill what ?? clear ?? 26214417866190 36393 31 RU448659~VG.6 2621441 328100 82 32 RUS1970438 When I try to kill 44885 as reported by Userno Unix says no such user. clear.locks only looks at your current login session. Any suggestions ? UV 9.6 and Aix 5.2 Garry L. Smith ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
[U2] LIST.READU - RELEASE (done)
I guess the command RELEASE clears the UV lock table --- So great -- LIST.READU shows you some information ... but how do you clear these locks Active Record Locks: Device Inode Netnode Userno Lmode Pid Login Id Item-ID. 2621441 328100 50 4 RUS1970666 2621441 328100 48 30 RUS1970676 2621441 328100 44885 31 RUS1970557 = PID kill what ?? clear ?? 26214417866190 36393 31 RU448659~VG.6 2621441 328100 82 32 RUS1970438 When I try to kill 44885 as reported by Userno Unix says no such user. clear.locks only looks at your current login session. Any suggestions ? UV 9.6 and Aix 5.2 Garry L. Smith ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] LIST.READU - clear lock table ?
LOGOUT 44885 Norm :) On Tue, Jan 18, 2011 at 7:26 PM, Garry Smith gar...@charlesmcmurray.com wrote: So great -- LIST.READU shows you some information ... but how do you clear these locks Active Record Locks: Device Inode Netnode Userno Lmode Pid Login Id Item-ID. 2621441 32810 0 50 4 RU S1970666 2621441 32810 0 48 30 RU S1970676 2621441 32810 0 44885 31 RU S1970557 = PID kill what ?? clear ?? 2621441 786619 0 36393 31 RU 448659~VG.6 2621441 32810 0 82 32 RU S1970438 When I try to kill 44885 as reported by Userno Unix says no such user. clear.locks only looks at your current login session. Any suggestions ? UV 9.6 and Aix 5.2 Garry L. Smith ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] LIST.READU - clear lock table ?
Sorry let me just elaborate a little on that last message. We are a small company so this might not be applicable to you. The one or two times a year where I get someone calling me about a lock I do a LISTU to see who it is and then call them and ask them to hurry it along because someone else is needing that record. When I can't get in touch with them then it almost always is someone who opened a record then left for lunch or got pulled into a meeting, so i just log them off. On Tue, Jan 18, 2011 at 7:26 PM, Garry Smith gar...@charlesmcmurray.com wrote: So great -- LIST.READU shows you some information ... but how do you clear these locks Active Record Locks: Device Inode Netnode Userno Lmode Pid Login Id Item-ID. 2621441 32810 0 50 4 RU S1970666 2621441 32810 0 48 30 RU S1970676 2621441 32810 0 44885 31 RU S1970557 = PID kill what ?? clear ?? 2621441 786619 0 36393 31 RU 448659~VG.6 2621441 32810 0 82 32 RU S1970438 When I try to kill 44885 as reported by Userno Unix says no such user. clear.locks only looks at your current login session. Any suggestions ? UV 9.6 and Aix 5.2 Garry L. Smith ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] LIST.READU - RELEASE (done)
Try the UNLOCK command. Also, I recommend you use LIST.READU EVERY to see all locks held. Usage: UNLOCK USER xxx ALL or UNLOCK INODE ALL (or similar if I recall the syntax. (Copy entries mentioned above from the UV account VOC file, if not present) NEVER use UNLOCK ALL...unless you wish to potentially wreak havoc on your system. ;-) The UV Deadlock daemon does periodic clean-ups of locks for dead and deadlocked processes - check it's log fie in the UV account to see if it released these locks. FYI: This is wealth of archived emails for U2-Users email list with lots of UV specific info you can Google or use the likes of Mail-archive to search... such as this posting: http://www.mail-archive.com/u2-users@listserver.u2ug.org/msg03438.html It's quite helpful...as it is impossible to remember all this stuff! -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Garry Smith Sent: Wednesday, 19 January 2011 11:55 AM To: U2 Users List Subject: [U2] LIST.READU - RELEASE (done) I guess the command RELEASE clears the UV lock table --- So great -- LIST.READU shows you some information ... but how do you clear these locks Active Record Locks: Device Inode Netnode Userno Lmode Pid Login Id Item-ID. 2621441 328100 50 4 RUS1970666 2621441 328100 48 30 RUS1970676 2621441 328100 44885 31 RUS1970557 = PID kill what ?? clear ?? 26214417866190 36393 31 RU448659~VG.6 2621441 328100 82 32 RUS1970438 When I try to kill 44885 as reported by Userno Unix says no such user. clear.locks only looks at your current login session. Any suggestions ? UV 9.6 and Aix 5.2 Garry L. Smith ** IMPORTANT MESSAGE * This e-mail message is intended only for the addressee(s) and contains information which may be confidential. If you are not the intended recipient please advise the sender by return email, do not use or disclose the contents, and delete the message and any attachments from your system. Unless specifically indicated, this email does not constitute formal advice or commitment by the sender or the Commonwealth Bank of Australia (ABN 48 123 123 124) or its subsidiaries. We can be contacted through our web site: commbank.com.au. If you no longer wish to receive commercial electronic messages from us, please reply to this e-mail by typing Unsubscribe in the subject line. ** ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] LIST.READU - clear lock table ?
Hi Garry,
Look the statement UNLOCK
--- snip from HELP UNLOCK
Use UNLOCK to clear file, group, and update record locks.
You must be a UniVerse Administrator logged in to the uniVerse account to
execute UNLOCK.
SYNTAX
UNLOCK [NODE node] [USER user.number]
[FILE pathname | [DEVICE device.number]
[INODE i.node.number]] [GROUP group.address]
[RECORD record.ID]
{FILELOCK | GROUPLOCK | READULOCK | READLLOCK | ALL}
Sample regarding your LIST.READU ;
if you want to unlock the record S1970557 use : UNLOCK INODE 32810 RECORD
S1970557 READULOCK
if you want to unlock all locks of userno 31 use : UNLOCK USER 31 ALL
warning, use LIST.READU EVERY to see all locks levels and eventually the locks
waiters when you get a deadlock condition.
manu
-Message d'origine-
De : u2-users-boun...@listserver.u2ug.org [mailto:u2-users-
boun...@listserver.u2ug.org] De la part de Garry Smith
Envoyé : mercredi 19 janvier 2011 01:27
À : U2 Users List
Objet : [U2] LIST.READU - clear lock table ?
So great -- LIST.READU shows you some information ... but how do you clear
these locks Active Record Locks:
Device Inode Netnode Userno Lmode Pid Login Id
Item-ID.
2621441 328100 50 4 RUS1970666
2621441 328100 48 30 RUS1970676
2621441 328100 44885 31 RUS1970557
= PID kill what ?? clear ??
26214417866190 36393 31 RU448659~VG.6
2621441 328100 82 32 RUS1970438
When I try to kill 44885 as reported by Userno Unix says no such user.
clear.locks only looks at your current login session. Any suggestions ?
UV 9.6 and Aix 5.2
Garry L. Smith
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users
