Re: Huge LASTING GLOBALV file for DB/2 servers
The only problem with this (WRT the DB2 servers) is this ONLY executes when CMS is IPL'd. In my shop, that might mean MONTHS between cleanups of the GLOBALV's. :( There is an SQM CMS command, but it can't execute CMS commands in the DB machine while DB2 is running. Michael Coffin, President MC Consulting Company, Inc. 57 Tamarack Drive Stoughton, Massachusetts 02072 Voice: (781) 344-9837FAX: (781) 344-7683 [EMAIL PROTECTED] www.mccci.com http://www.mccci.com/ We employ aggressive SPAM filters. If you cannot reply or send email to mccci.com go to www.mccci.com/spamblockremove.php Click here to help fight http://www.spamabuse.org/images/anti-spam.gif the war on Spam! Report an unsolicited commercial email or a spamming organization. -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Stracka, James (GTI) Sent: Thursday, December 21, 2006 3:27 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Huge LASTING GLOBALV file for DB/2 servers See line number 173 of SYSPROF EXEC: 'GLOBALV INIT' -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Mike Walter Sent: Thursday, December 21, 2006 3:23 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Huge LASTING GLOBALV file for DB/2 servers Last I knew, SYSPROF EXEC, which is by default executed during an IPL of CMS, does **not** issue a GLOBALV INIT. That came as a surprise to me in the mid-1980's when a developer reported that their LASTING GLOBALV and even SESSION GLOBALVs were not being cleared. I solved that here by installing a local PROFCMS EXEC, which is called from all our supported (i.e.: remove it an you are unsupported here) user's PROFILE EXECs. That keep most of our local requirements out of SYSPROF EXEC, where changes at release boundaries have sometimes proved to be challenging. Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. Stracka, James (GTI) [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 12/21/2006 01:45 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: Huge LASTING GLOBALV file for DB/2 servers Ed, LASTING GLOBALV is normally cleared of duplicate entries at IPL CMS time. For them not to be cleared, could there be undisplayed characters making them unique? An Explicit GLOBALV INIT should also clear the duplicates. Other than that, the duplicates could be being created by the SQL SVM itself in some sort of loop. Jim -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Ed Zell Sent: Thursday, December 21, 2006 2:02 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Huge LASTING GLOBALV file for DB/2 servers We are running DB/2 for VM 7.4 on z/VM 4.4 at service level 0501. Today I noticed that the LASTING GLOBALV file on all three of my servers is HUGE. (SQLPROD's is 47,000+ lines and 276 blocks) It is full of the same settings over and over again. For example: SQL/DS DBNAMESQLPROD SQL/DS RELEASE;7.4.0 SQL/DS WORKUNITYES SQL/DS QRYBLKSIZE8 SQL/DS PROTOCOLAUTO In the PROFILE EXEC of the machine, we do SQLINIT DBNAME(SQLPROD) PROTOCOL(AUTO) which I understand will set up these variable in LASTING GLOBALV. This particular virtual machine is shut down each night before 2nd shift and logged off and then back on so the PROFILE and SQLINIT do get executed at least once a day. In looking at the LASTING GLOBALV file, there are many lines with SQL/DS RELEASE;7.1.0 and SQL/DS RELEASE;7.4.0 so that tells me this has been going on a long time and I am just now noticing it. We did convert from 7.1 to 7.4 in October of 2006 but it appears to have been growing like this since we installed z/VM 4.4 back in October of 2005 (although I can't be certain). Has anyone else seen something similar to this by chance? I am wondering if this is related to SQLINIT and is a DB/2 problem or if it is a problem with GLOBALV ... SETP. Any thoughts would be appreciated. Thanks. Ed Zell Illinois Mutual Life Insurance (309) 674-8255 x-107 . CONFIDENTIAL NOTICE: This communication, including any attachments, is intended only for the use of the individual or entity to which it is addressed and contains information which may be confidential. If you are not the intended recipient, any distribution or copying of this communication is strictly prohibited. If you have received this communication in error, notify the sender immediately, delete the communication and destroy all copies. Thank you for your compliance. If you are not an intended recipient of this e
Re: Huge LASTING GLOBALV file for DB/2 servers
Just to help me understand DB2 better, could you explain why you have a S QLINIT in the PROFILE EXEC of your server? I thought that was only for clients to issue. On Thu, 21 Dec 2006 13:01:34 -0600, Ed Zell [EMAIL PROTECTED] w rote: We are running DB/2 for VM 7.4 on z/VM 4.4 at service level 0501. Today I noticed that the LASTING GLOBALV file on all three of my servers is HUGE. (SQLPROD's is 47,000+ lines and 276 blocks) It is full of the same settings over and over again. For example: SQL/DS DBNAMESQLPROD SQL/DS RELEASE;7.4.0 SQL/DS WORKUNITYES SQL/DS QRYBLKSIZE8 SQL/DS PROTOCOLAUTO In the PROFILE EXEC of the machine, we do SQLINIT DBNAME(SQLPROD) PROTOCOL(AUTO) which I understand will set up these variable in LASTING GLOBALV. This particular virtual machine is shut down each night before 2nd shift and logged off and then back on so the PROFILE and SQLINIT do get executed at least once a day. In looking at the LASTING GLOBALV file, there are many lines with SQL/DS RELEASE;7.1.0 and SQL/DS RELEASE;7.4.0 so that tells me this has been going on a long time and I am just now noticing it. We did convert from 7.1 to 7.4 in October of 2006 but it appears to have been growing like this since we installed z/VM 4.4 back in October of 2005 (although I can't be certain). Has anyone else seen something similar to this by chance? I am wondering if this is related to SQLINIT and is a DB/2 problem or if it is a problem with GLOBALV ... SETP. Any thoughts would be appreciated. Thanks. Ed Zell Illinois Mutual Life Insurance (309) 674-8255 x-107 . CONFIDENTIAL NOTICE: This communication, including any attachments, is intended only for the use of the individual or entity to which it is addressed and contains information which may be confidential. If you are not the intended recipient, any distribution or copying of this communication is strictly prohibited. If you have received this communic ation in error, notify the sender immediately, delete the communication and destroy all copies. Than k you for your compliance. = == =
Re: Huge LASTING GLOBALV file for DB/2 servers
We've been running DB/2 for VM since Release 6.1. We're currently on DB/2 7.3 under z/VM 4.4. Our current LASTING GLOBALV is 137 lines long for SQLPROD, and it doesn't have any duplicates in it. We do not have the SQLINIT step in our PROFILE EXEC for any of the databases. We also do not log the databases off very frequently. However, they do get logged off enough that at least some duplicate entries should have occurred if that were the cause. On my personal 191 disk, I don't have any duplicate entries, either. I issue multiple SQLINIT commands each day, switching between various databases. However, I do not issue the command through my PROFILE EXEC. I'm not a systems programmer, so we've about reached the limits of my knowledge. :-) Nora Graves [EMAIL PROTECTED] Main IRS, Room 6513 (202) 622-6735 -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Ed Zell Sent: Thursday, December 21, 2006 2:02 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Huge LASTING GLOBALV file for DB/2 servers We are running DB/2 for VM 7.4 on z/VM 4.4 at service level 0501. Today I noticed that the LASTING GLOBALV file on all three of my servers is HUGE. (SQLPROD's is 47,000+ lines and 276 blocks) It is full of the same settings over and over again. For example: SQL/DS DBNAMESQLPROD SQL/DS RELEASE;7.4.0 SQL/DS WORKUNITYES SQL/DS QRYBLKSIZE8 SQL/DS PROTOCOLAUTO In the PROFILE EXEC of the machine, we do SQLINIT DBNAME(SQLPROD) PROTOCOL(AUTO) which I understand will set up these variable in LASTING GLOBALV. This particular virtual machine is shut down each night before 2nd shift and logged off and then back on so the PROFILE and SQLINIT do get executed at least once a day. In looking at the LASTING GLOBALV file, there are many lines with SQL/DS RELEASE;7.1.0 and SQL/DS RELEASE;7.4.0 so that tells me this has been going on a long time and I am just now noticing it. We did convert from 7.1 to 7.4 in October of 2006 but it appears to have been growing like this since we installed z/VM 4.4 back in October of 2005 (although I can't be certain). Has anyone else seen something similar to this by chance? I am wondering if this is related to SQLINIT and is a DB/2 problem or if it is a problem with GLOBALV ... SETP. Any thoughts would be appreciated. Thanks. Ed Zell Illinois Mutual Life Insurance (309) 674-8255 x-107 . CONFIDENTIAL NOTICE: This communication, including any attachments, is intended only for the use of the individual or entity to which it is addressed and contains information which may be confidential. If you are not the intended recipient, any distribution or copying of this communication is strictly prohibited. If you have received this communication in error, notify the sender immediately, delete the communication and destroy all copies. Thank you for your compliance.
Re: Huge LASTING GLOBALV file for DB/2 servers
Ed, LASTING GLOBALV is normally cleared of duplicate entries at IPL CMS time. For them not to be cleared, could there be undisplayed characters making them unique? An Explicit GLOBALV INIT should also clear the duplicates. Other than that, the duplicates could be being created by the SQL SVM itself in some sort of loop. Jim -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Ed Zell Sent: Thursday, December 21, 2006 2:02 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Huge LASTING GLOBALV file for DB/2 servers We are running DB/2 for VM 7.4 on z/VM 4.4 at service level 0501. Today I noticed that the LASTING GLOBALV file on all three of my servers is HUGE. (SQLPROD's is 47,000+ lines and 276 blocks) It is full of the same settings over and over again. For example: SQL/DS DBNAMESQLPROD SQL/DS RELEASE;7.4.0 SQL/DS WORKUNITYES SQL/DS QRYBLKSIZE8 SQL/DS PROTOCOLAUTO In the PROFILE EXEC of the machine, we do SQLINIT DBNAME(SQLPROD) PROTOCOL(AUTO) which I understand will set up these variable in LASTING GLOBALV. This particular virtual machine is shut down each night before 2nd shift and logged off and then back on so the PROFILE and SQLINIT do get executed at least once a day. In looking at the LASTING GLOBALV file, there are many lines with SQL/DS RELEASE;7.1.0 and SQL/DS RELEASE;7.4.0 so that tells me this has been going on a long time and I am just now noticing it. We did convert from 7.1 to 7.4 in October of 2006 but it appears to have been growing like this since we installed z/VM 4.4 back in October of 2005 (although I can't be certain). Has anyone else seen something similar to this by chance? I am wondering if this is related to SQLINIT and is a DB/2 problem or if it is a problem with GLOBALV ... SETP. Any thoughts would be appreciated. Thanks. Ed Zell Illinois Mutual Life Insurance (309) 674-8255 x-107 . CONFIDENTIAL NOTICE: This communication, including any attachments, is intended only for the use of the individual or entity to which it is addressed and contains information which may be confidential. If you are not the intended recipient, any distribution or copying of this communication is strictly prohibited. If you have received this communication in error, notify the sender immediately, delete the communication and destroy all copies. Thank you for your compliance. If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/
Re: Huge LASTING GLOBALV file for DB/2 servers
I am surprized. but indeed, each time a GLOBALV SETP or PUTP is issued, it is written in LASTING GLOBALV, even if the value is the same as before. So yes indeed a careless use of SETP/PUTP can cause huge LASTING GLOBALV files. But, GLOBALV INIT is supposed to cleanup the file, removing all but the last settting for each variable. And as far as I know, a GLOBALV INIT is done by the SYSPROF EXEC, but also the very first time GLOBALV is used. And you say your server is restarted every day, so cleanup should be done. Unless: the server would have its A-disk R/O when GLOBALV INIT is done, or, the A-disk is changed after the GLOBALV INIT (I obtained a fix precisely for this problem in the the DGTSRVxx servers of DFSMS). Beware: don't place GLOBALV INIT commands everywhere: it not only reads/cleans the LASTING GLOBALV A file, but also wipes out all GLOBALV variables that are saved in storage only. Kris, IBM Belgium, VM customer support The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU wrote on 2006-12-21 20:01:34: We are running DB/2 for VM 7.4 on z/VM 4.4 at service level 0501. Today I noticed that the LASTING GLOBALV file on all three of my servers is HUGE. (SQLPROD's is 47,000+ lines and 276 blocks) It is full of the same settings over and over again. For example: SQL/DS DBNAMESQLPROD SQL/DS RELEASE;7.4.0 SQL/DS WORKUNITYES SQL/DS QRYBLKSIZE8 SQL/DS PROTOCOLAUTO In the PROFILE EXEC of the machine, we do SQLINIT DBNAME(SQLPROD) PROTOCOL(AUTO) which I understand will set up these variable in LASTING GLOBALV. This particular virtual machine is shut down each night before 2nd shift and logged off and then back on so the PROFILE and SQLINIT do get executed at least once a day. In looking at the LASTING GLOBALV file, there are many lines with SQL/DS RELEASE;7.1.0 and SQL/DS RELEASE;7.4.0 so that tells me this has been going on a long time and I am just now noticing it. We did convert from 7.1 to 7.4 in October of 2006 but it appears to have been growing like this since we installed z/VM 4.4 back in October of 2005 (although I can't be certain). Has anyone else seen something similar to this by chance? I am wondering if this is related to SQLINIT and is a DB/2 problem or if it is a problem with GLOBALV ... SETP. Any thoughts would be appreciated. Thanks. Ed Zell Illinois Mutual Life Insurance (309) 674-8255 x-107 . CONFIDENTIAL NOTICE: This communication, including any attachments, is intended only for the use of the individual or entity to which it is addressed and contains information which may be confidential. If you are not the intended recipient, any distribution or copying of this communication is strictly prohibited. If you have received this communication in error, notify the sender immediately, delete the communication and destroy all copies. Thank you for your compliance.
Re: Huge LASTING GLOBALV file for DB/2 servers
Last I knew, SYSPROF EXEC, which is by default executed during an IPL of CMS, does **not** issue a GLOBALV INIT. That came as a surprise to me in the mid-1980's when a developer reported that their LASTING GLOBALV and even SESSION GLOBALVs were not being cleared. I solved that here by installing a local PROFCMS EXEC, which is called from all our supported (i.e.: remove it an you are unsupported here) user's PROFILE EXECs. That keep most of our local requirements out of SYSPROF EXEC, where changes at release boundaries have sometimes proved to be challenging. Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. Stracka, James (GTI) [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 12/21/2006 01:45 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: Huge LASTING GLOBALV file for DB/2 servers Ed, LASTING GLOBALV is normally cleared of duplicate entries at IPL CMS time. For them not to be cleared, could there be undisplayed characters making them unique? An Explicit GLOBALV INIT should also clear the duplicates. Other than that, the duplicates could be being created by the SQL SVM itself in some sort of loop. Jim -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Ed Zell Sent: Thursday, December 21, 2006 2:02 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Huge LASTING GLOBALV file for DB/2 servers We are running DB/2 for VM 7.4 on z/VM 4.4 at service level 0501. Today I noticed that the LASTING GLOBALV file on all three of my servers is HUGE. (SQLPROD's is 47,000+ lines and 276 blocks) It is full of the same settings over and over again. For example: SQL/DS DBNAMESQLPROD SQL/DS RELEASE;7.4.0 SQL/DS WORKUNITYES SQL/DS QRYBLKSIZE8 SQL/DS PROTOCOLAUTO In the PROFILE EXEC of the machine, we do SQLINIT DBNAME(SQLPROD) PROTOCOL(AUTO) which I understand will set up these variable in LASTING GLOBALV. This particular virtual machine is shut down each night before 2nd shift and logged off and then back on so the PROFILE and SQLINIT do get executed at least once a day. In looking at the LASTING GLOBALV file, there are many lines with SQL/DS RELEASE;7.1.0 and SQL/DS RELEASE;7.4.0 so that tells me this has been going on a long time and I am just now noticing it. We did convert from 7.1 to 7.4 in October of 2006 but it appears to have been growing like this since we installed z/VM 4.4 back in October of 2005 (although I can't be certain). Has anyone else seen something similar to this by chance? I am wondering if this is related to SQLINIT and is a DB/2 problem or if it is a problem with GLOBALV ... SETP. Any thoughts would be appreciated. Thanks. Ed Zell Illinois Mutual Life Insurance (309) 674-8255 x-107 . CONFIDENTIAL NOTICE: This communication, including any attachments, is intended only for the use of the individual or entity to which it is addressed and contains information which may be confidential. If you are not the intended recipient, any distribution or copying of this communication is strictly prohibited. If you have received this communication in error, notify the sender immediately, delete the communication and destroy all copies. Thank you for your compliance. If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited.
Re: Huge LASTING GLOBALV file for DB/2 servers
Unless: the server would have its A-disk R/O when GLOBALV INIT is done, or, the A-disk is changed after the GLOBALV INIT (I obtained a fix precisely for this problem in the the DGTSRVxx servers of DFSMS). Kris, IBM Belgium, VM customer support Kris, That's it. The 191 disk for my DB/2 servers is a R/O disk that contains common EXEC's and startup parm files that are shared by all my servers. One of the first things the PROFILE EXEC does is: 'REL A' 'ACC 199 A'/* read/write work A disk for DB/2 */ 'ACC 191 B/A' but by then SYSPROF / GLOBALV INIT has already run and didn't do anything because of the read only disk. After looking at LASTING GLOBALV in more detail, there are 2600+ copies of the variables (18 lines each so 47,000+ total lines). That means this has been going on FOR YEARS !! I guess I either: 1) Remove SQLINIT from the startup EXEC or 2) Do a GLOBALV INIT after getting the 199 as a read/write A disk Thanks so much for your quick response. I just LOVE THIS LIST Happy Holidays to everyone from us here in Peoria, Illinois, USA. Ed Zell (309) 674-8255 x-107 [EMAIL PROTECTED] . CONFIDENTIAL NOTICE: This communication, including any attachments, is intended only for the use of the individual or entity to which it is addressed and contains information which may be confidential. If you are not the intended recipient, any distribution or copying of this communication is strictly prohibited. If you have received this communication in error, notify the sender immediately, delete the communication and destroy all copies. Thank you for your compliance.
Re: Huge LASTING GLOBALV file for DB/2 servers
See line number 173 of SYSPROF EXEC: 'GLOBALV INIT' -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Mike Walter Sent: Thursday, December 21, 2006 3:23 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Huge LASTING GLOBALV file for DB/2 servers Last I knew, SYSPROF EXEC, which is by default executed during an IPL of CMS, does **not** issue a GLOBALV INIT. That came as a surprise to me in the mid-1980's when a developer reported that their LASTING GLOBALV and even SESSION GLOBALVs were not being cleared. I solved that here by installing a local PROFCMS EXEC, which is called from all our supported (i.e.: remove it an you are unsupported here) user's PROFILE EXECs. That keep most of our local requirements out of SYSPROF EXEC, where changes at release boundaries have sometimes proved to be challenging. Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. Stracka, James (GTI) [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 12/21/2006 01:45 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: Huge LASTING GLOBALV file for DB/2 servers Ed, LASTING GLOBALV is normally cleared of duplicate entries at IPL CMS time. For them not to be cleared, could there be undisplayed characters making them unique? An Explicit GLOBALV INIT should also clear the duplicates. Other than that, the duplicates could be being created by the SQL SVM itself in some sort of loop. Jim -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Ed Zell Sent: Thursday, December 21, 2006 2:02 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Huge LASTING GLOBALV file for DB/2 servers We are running DB/2 for VM 7.4 on z/VM 4.4 at service level 0501. Today I noticed that the LASTING GLOBALV file on all three of my servers is HUGE. (SQLPROD's is 47,000+ lines and 276 blocks) It is full of the same settings over and over again. For example: SQL/DS DBNAMESQLPROD SQL/DS RELEASE;7.4.0 SQL/DS WORKUNITYES SQL/DS QRYBLKSIZE8 SQL/DS PROTOCOLAUTO In the PROFILE EXEC of the machine, we do SQLINIT DBNAME(SQLPROD) PROTOCOL(AUTO) which I understand will set up these variable in LASTING GLOBALV. This particular virtual machine is shut down each night before 2nd shift and logged off and then back on so the PROFILE and SQLINIT do get executed at least once a day. In looking at the LASTING GLOBALV file, there are many lines with SQL/DS RELEASE;7.1.0 and SQL/DS RELEASE;7.4.0 so that tells me this has been going on a long time and I am just now noticing it. We did convert from 7.1 to 7.4 in October of 2006 but it appears to have been growing like this since we installed z/VM 4.4 back in October of 2005 (although I can't be certain). Has anyone else seen something similar to this by chance? I am wondering if this is related to SQLINIT and is a DB/2 problem or if it is a problem with GLOBALV ... SETP. Any thoughts would be appreciated. Thanks. Ed Zell Illinois Mutual Life Insurance (309) 674-8255 x-107 . CONFIDENTIAL NOTICE: This communication, including any attachments, is intended only for the use of the individual or entity to which it is addressed and contains information which may be confidential. If you are not the intended recipient, any distribution or copying of this communication is strictly prohibited. If you have received this communication in error, notify the sender immediately, delete the communication and destroy all copies. Thank you for your compliance. If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ _ The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message
Huge LASTING GLOBALV file for DB/2 servers
We are running DB/2 for VM 7.4 on z/VM 4.4 at service level 0501. Today I noticed that the LASTING GLOBALV file on all three of my servers is HUGE. (SQLPROD's is 47,000+ lines and 276 blocks) It is full of the same settings over and over again. For example: SQL/DS DBNAMESQLPROD SQL/DS RELEASE;7.4.0 SQL/DS WORKUNITYES SQL/DS QRYBLKSIZE8 SQL/DS PROTOCOLAUTO In the PROFILE EXEC of the machine, we do SQLINIT DBNAME(SQLPROD) PROTOCOL(AUTO) which I understand will set up these variable in LASTING GLOBALV. This particular virtual machine is shut down each night before 2nd shift and logged off and then back on so the PROFILE and SQLINIT do get executed at least once a day. In looking at the LASTING GLOBALV file, there are many lines with SQL/DS RELEASE;7.1.0 and SQL/DS RELEASE;7.4.0 so that tells me this has been going on a long time and I am just now noticing it. We did convert from 7.1 to 7.4 in October of 2006 but it appears to have been growing like this since we installed z/VM 4.4 back in October of 2005 (although I can't be certain). Has anyone else seen something similar to this by chance? I am wondering if this is related to SQLINIT and is a DB/2 problem or if it is a problem with GLOBALV ... SETP. Any thoughts would be appreciated. Thanks. Ed Zell Illinois Mutual Life Insurance (309) 674-8255 x-107 . CONFIDENTIAL NOTICE: This communication, including any attachments, is intended only for the use of the individual or entity to which it is addressed and contains information which may be confidential. If you are not the intended recipient, any distribution or copying of this communication is strictly prohibited. If you have received this communication in error, notify the sender immediately, delete the communication and destroy all copies. Thank you for your compliance.
Re: Huge LASTING GLOBALV file for DB/2 servers
Do you by any chance run CA's VM:DB/Suite or IBM's Control Center with your DB2 databases? JR JR (Steven) Imler CA Senior Software Engineer Tel: +1 703 708 3479 Fax: +1 703 708 3267 [EMAIL PROTECTED] -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Ed Zell Sent: Thursday, December 21, 2006 02:02 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Huge LASTING GLOBALV file for DB/2 servers We are running DB/2 for VM 7.4 on z/VM 4.4 at service level 0501. Today I noticed that the LASTING GLOBALV file on all three of my servers is HUGE. (SQLPROD's is 47,000+ lines and 276 blocks) It is full of the same settings over and over again. For example: SQL/DS DBNAMESQLPROD SQL/DS RELEASE;7.4.0 SQL/DS WORKUNITYES SQL/DS QRYBLKSIZE8 SQL/DS PROTOCOLAUTO In the PROFILE EXEC of the machine, we do SQLINIT DBNAME(SQLPROD) PROTOCOL(AUTO) which I understand will set up these variable in LASTING GLOBALV. This particular virtual machine is shut down each night before 2nd shift and logged off and then back on so the PROFILE and SQLINIT do get executed at least once a day. In looking at the LASTING GLOBALV file, there are many lines with SQL/DS RELEASE;7.1.0 and SQL/DS RELEASE;7.4.0 so that tells me this has been going on a long time and I am just now noticing it. We did convert from 7.1 to 7.4 in October of 2006 but it appears to have been growing like this since we installed z/VM 4.4 back in October of 2005 (although I can't be certain). Has anyone else seen something similar to this by chance? I am wondering if this is related to SQLINIT and is a DB/2 problem or if it is a problem with GLOBALV ... SETP. Any thoughts would be appreciated. Thanks. Ed Zell Illinois Mutual Life Insurance (309) 674-8255 x-107 . CONFIDENTIAL NOTICE: This communication, including any attachments, is intended only for the use of the individual or entity to which it is addressed and contains information which may be confidential. If you are not the intended recipient, any distribution or copying of this communication is strictly prohibited. If you have received this communication in error, notify the sender immediately, delete the communication and destroy all copies. Thank you for your compliance.
Re: Huge LASTING GLOBALV file for DB/2 servers
Do you by any chance run CA's VM:DB/Suite or IBM's Control Center with your DB2 databases? JR Hi JR, No, everything is roll yer own here. We have been running since the late 1980's (SQL/DS 2.1 if I remember correctly). At that time there were no cool tools like the ones you mentioned. I wrote quite a few utilities for the VSE side and a menu system for the VM side to make it easy for Operations to do SQL stuff. They weren't very elegant, but they did their job. I am proud to say most of them still run today with little or no changes as the new releases come along. The code is pretty scary to look at, but hey, I was wet behind the ears back then :) Ed Zell Illinois Mutual Life (309) 674-8255 x-107 . CONFIDENTIAL NOTICE: This communication, including any attachments, is intended only for the use of the individual or entity to which it is addressed and contains information which may be confidential. If you are not the intended recipient, any distribution or copying of this communication is strictly prohibited. If you have received this communication in error, notify the sender immediately, delete the communication and destroy all copies. Thank you for your compliance.
