I'd say these messages are coming out of the ALLUSERS EXEC. Looks like
the exec is written in REXX but executing as an EXEC or EXEC2. It is not
recognizing the comments statements as comment. Check the first line of
ALLUSERS it has to be a REXX comment. 

Also, I haven't modified a lot of SYSPROF stuff. Might check the
restrictions imposed on it.  


Bob Bates
Enterprise Hosting Services - Enterprise Virtualization - z/VM and
z/Linux 

w. (972) 753-5967
c. (214) 907-5071

"This message may contain confidential and/or privileged information.
If you are not the addressee or authorized to receive this for the
addressee, you must not use, copy, disclose, or take any action based on
this message or any information herein.  If you have received this
message in error, please advise the sender immediately by reply e-mail
and delete this message.  Thank you for your cooperation."



-----Original Message-----
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Dusha, Cecelia CIV WHS/ITMD
Sent: Friday, November 23, 2007 10:39 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: SYSPROF Modification

Hello,

I have modified the SYSPROF EXEC to execute SYSEXIT EXEC on the IFL.  
This set up is working on the general engine, so I am puzzled as to why
this problem is occurring on the IFL...

SYSPROF EXEC:
If batch = 'no'          /*If this is not batch machine      */
  Then Do           /*Handle first command, and PROFILE EXEC */
    If gotfirst = 'yes'  /*Was a first command entered?      */
      Then Push usr_cmd  /*Yes, execute command after profile*/
    If noprof = 'no'      /*Should we look for PROFILE EXEC? */
      Then Do             /*Look on first disk we accessed   */
        'EXEC SYSEXIT'    /*Site specific data           (cd)*/
        'ESTATE PROFILE EXEC ' mdisk_mode                      
        ...

SYSEXIT EXEC:
/* SYSEXIT EXEC                                                   */
'CP LINK MAINT 31A 131A RR'        /* Get the local programs disk */   
'ACCESS 131A X/X'                                                      
'EXEC ALLUSERS'                   /* Call EXEC with local commands */ 


When I go to execute SYSEXIT from a logged on userid:
sysexit                                                               
DASD 131A LINKED R/O; R/W BY MAINT                                    
DMSACC724I 131A replaces X (131A)                                     
DMSACP723I X (131A) R/O                                               
/* This exec contains commands to be invoked for all users at logon */
DMSOPN062E Invalid character / in fileid /* MODULE                    
+++ R(-0004) +++                                                      
/* time just before the PROFILE EXEC executes It is called via the */ 
DMSOPN062E Invalid character / in fileid /* MODULE                    
+++ R(-0004) +++                                                      
/* SYSEXIT EXEC out of the SYSPROF EXEC. */                           
DMSOPN062E Invalid character / in fileid /* MODULE                    
+++ R(-0004) +++                                                      
'CP LINK MAINT 319 1319 RR' /* Get the program products disk */       
DMSOPN062E Invalid character ' in fileid 'CP MODULE                   
+++ R(-0004) +++                                                      
'ACCESS 1319 P/P'                                                     
DMSOPN062E Invalid character ' in fileid 'ACCESS MODULE               
+++ R(-0004) +++                                                      
'VMFCLEA                                                              
DMSOPN062E Invalid character ' in fileid 'VMFCLEA MODULE              
+++ R(-0004) +++                                     
'TYPE LOGON MESSAGE X'                               
DMSOPN062E Invalid character ' in fileid 'TYPE MODULE
+++ R(-0004) +++                                     
'Q LOG'                                              
DMSOPN062E Invalid character ' in fileid 'Q MODULE   
+++ R(-0004) +++                                     
Ready; T=0.01/0.01 11:33:59                          

At first I thought it was because I had changed SYSPROF EXEC and it was
stored in one of the shared segments.  I resaved all of the shared
segments on the IFL, but this problem continues.

Hopefully someone one can provide some insite into this problem.

Thank you.

Cecelia Dusha
  

Reply via email to