Found the problem. CMSINST LSEGMAP loads from the 490 disk... I should not take short cuts... I should have followed the local modification procedures to implement this.
But the steps I followed worked on the other zVM 5.1 system... The modified code is on the 190 disk and when I saved the segments, the modified code was picked up - even though CMSINST LSEGMAP point to the 490 disk... Thanks. Cecelia Dusha -----Original Message----- From: Dusha, Cecelia Ms. WHS/ITMD Sent: Friday, August 04, 2006 9:33 AM To: 'The IBM z/VM Operating System' Subject: RE: SYSPROF I realized this reads as if this is a coding problem... SYSPROF EXEC does invoke the userid's PROFILE EXEC which is the next statement... It just does not execute the modification... Thanks. Cecelia Dusha -----Original Message----- From: Dusha, Cecelia Ms. WHS/ITMD Sent: Friday, August 04, 2006 8:48 AM To: 'The IBM z/VM Operating System' Subject: SYSPROF Hello, I need to modify SYSPROF EXEC. On my vanilla zVM 5.1 system, I successfully implemented this change. On the test system I am building for the customers I am experiencing problems. The SYSPROF EXEC on MAINT 190 disk has the modification. I have resaved ALL of the cms segments (CMSFILES, SVM, CMSVMLIB, CMSPIPES, INSTSEG, HELPSEG, GUICSLIB, NLSUCENG, NLSGER, NLSKANJI, NLSAMENG, SCEE, SCEEX). I think the only one that needed to be resaved was INSTSEG, but being that didn't work - I saved them all. I even put a trace into the region where the modification exists to ensure it was passing through that code and that it was picking up my modified copy... But it isn't executing this portion of the code. The modification consists of 1 line preceding the ESTATE PROFILE EXEC statement, before it invokes the userid's PROFILE EXEC. As I said, these same steps worked on my vanilla zVM 5.1. These same steps are not functioning on the merged system for a customer test environment... Please advice. Thank you. Cecelia Dusha
