Re: Unix File names EKM and dates
[snip] In our case, I have turned off all AUDIT recording except for errors, and made the metadata.xml files 8 MB, [snip] Out of interest, what do you mean you made the metadata.xml files 8 MB? You don't allocate storage when you create a UNIX file. It grows as programs write to it. I've got some offline communication with Lizette and from that I conclude that even in a sysplex shared file system environment each EKM instance will need its own home directory to store such data as the metadata.xml, the audit log, the debug files. If this is correct, one will need to treat the EKM home like /etc, /var, /tmp, so there is no need to have one config file per EKM instance. It seems that all may access identically named files (symlinks as per my previous suggestion) in their respective home. -- Peter Hunkeler Credit Suisse -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Unix File names EKM and dates
Sorry, I mean that in the properties file I coded Audit.metadata.file.size = 8192 (8MB). At which time it will roll over to a new filename and start over. The only downfall of the current setup is that when the rollover file reaches max size, it reverts back to the original. Too bad they didn't set this up to just rename with a date, and start fresh. Regarding your observations about one home per instance, that is correct, there is not much to share that is not updated. One thing we did that is different than documented, is that we put up another separate copy of JAVA. Since EKM code is delivered with JAVA, in the JAVA filesystem, we wanted additional stability of only updating EKM when we chose too, and not when another PTF reloaded JAVA. Between that, and the fact that EKM requires customization in the SMPE controlled JAVA filesystem, I didn't want to go mucking about in SMPE controlled area's. So, once *could* mount the EKM instance of JAVA READ only or Shared, and then have a separate home for the configuration, and logs. Regarding your comments about no need for one config file per ekm instance that is incorrect, *assuming* you have more than one EKM server for redundancy purposes. There are settings in the config file that define how each instance talks to the other via tcpip. Dave _ Dave Jousma Assistant Vice President, Mainframe Services david.jou...@53.com 1830 East Paris, Grand Rapids, MI 49546 MD RSCB1G p 616.653.8429 f 616.653.8497 -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Hunkeler Peter (KIUK 3) Sent: Wednesday, January 21, 2009 6:39 AM To: IBM-MAIN@bama.ua.edu Subject: Re: Unix File names EKM and dates [snip] In our case, I have turned off all AUDIT recording except for errors, and made the metadata.xml files 8 MB, [snip] Out of interest, what do you mean you made the metadata.xml files 8 MB? You don't allocate storage when you create a UNIX file. It grows as programs write to it. I've got some offline communication with Lizette and from that I conclude that even in a sysplex shared file system environment each EKM instance will need its own home directory to store such data as the metadata.xml, the audit log, the debug files. If this is correct, one will need to treat the EKM home like /etc, /var, /tmp, so there is no need to have one config file per EKM instance. It seems that all may access identically named files (symlinks as per my previous suggestion) in their respective home. -- Peter Hunkeler Credit Suisse -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Unix File names EKM and dates
How would I code the EKM paramenter to include a date and time stamp? I want the process to generate a new file each time it is cycled. [snip] Audit.metadata.file.name = /EKM/ekmetc/SDH8_metafile.xml Would become Audit.metadata.file.name=/EKM/ekmetc/SYSNAME_metafile.xml Lizette, did you come to a solution yet? I admit, I'm pretty much ignorant about EKM but from a previous post I seem to remember it is startet as STC? You could add an initial step to create these files and then create a link to them so that you don't have to change the EKM configuration. Something like this: /*REXX*/ syscallsrc = syscalls(ON) if syscallsrc 0 then do say SYSCALLS environment could not be established, RC= !! syscallsrc say aborting... exit 16 end address syscall sysname = MVSVAR(SYSNAME) cdate = date(S)/* date as mmdd */ ctime = time(N) /* time as hh:mm:ss, transform to hhmmss */ ctime = left(ctime,2) !! substr(ctime,4,2) !! right(ctime,2) metafile = /EKM/ekmetc/ !! sysname !! _metafile.xml metafilelink = /EKM/ekmetc/metafile.xml debugfile = /EKM/ekmlog/ !! sysname !! _ !! cdate !! _ , !! ctime !! _debug debugfilelink = /EKM/ekmlog/debug open metafile O_CREAT+O_WRONLY 660 /* create the file using open */ close RETVAL /* then close it again*/ unlink metafilelink /* remove the old link*/ symlink metafile metafilelink /* and create the new link*/ open debugfile O_CREAT+O_WRONLY 660 /* create the file using open */ close RETVAL /* then close it again*/ unlink debugfilelink /* remove the old link*/ symlink debugfile debugfilelink /* and create the new link*/ exit 0 /*end-of-REXX*/ Store this REXX as CRESLINK in a REXX library and run it before the EKM step: //IRXJCL01 EXEC PGM=IRXJCL,PARM='CRESLINK' //SYSEXEC DD DISP=SHR,DSN=your-rexx-library-goes-here //SYSTSPRT DD SYSOUT=* You may want to add some more sophisticated error handling and possibly other files to create. But this should give you an idea. -- Peter Hunkeler Credit Suisse -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Unix File names EKM and dates
The config information will need to be changed each time the EKM STC is cycled. So, yes, I am looking at creating a pre or post REXX to alter the config file in Unix to have the names that I want. It would have been nicer if Unix provided this function or the JZOS process provided it. Lizette How would I code the EKM paramenter to include a date and time stamp? I want the process to generate a new file each time it is cycled. [snip] Audit.metadata.file.name = /EKM/ekmetc/SDH8_metafile.xml Would become Audit.metadata.file.name=/EKM/ekmetc/SYSNAME_metafile.xml Lizette, did you come to a solution yet? I admit, I'm pretty much ignorant about EKM but from a previous post I seem to remember it is startet as STC? You could add an initial step to create these files and then create a link to them so that you don't have to change the EKM configuration. Something like this: /*REXX*/ syscallsrc = syscalls(ON) if syscallsrc 0 then do say SYSCALLS environment could not be established, RC= !! syscallsrc say aborting... exit 16 end address syscall sysname = MVSVAR(SYSNAME) cdate = date(S)/* date as mmdd */ ctime = time(N) /* time as hh:mm:ss, transform to hhmmss */ ctime = left(ctime,2) !! substr(ctime,4,2) !! right(ctime,2) metafile = /EKM/ekmetc/ !! sysname !! _metafile.xml metafilelink = /EKM/ekmetc/metafile.xml debugfile = /EKM/ekmlog/ !! sysname !! _ !! cdate !! _ , !! ctime !! _debug debugfilelink = /EKM/ekmlog/debug open metafile O_CREAT+O_WRONLY 660 /* create the file using open */ close RETVAL /* then close it again*/ unlink metafilelink /* remove the old link*/ symlink metafile metafilelink /* and create the new link*/ open debugfile O_CREAT+O_WRONLY 660 /* create the file using open */ close RETVAL /* then close it again*/ unlink debugfilelink /* remove the old link*/ symlink debugfile debugfilelink /* and create the new link*/ exit 0 /*end-of-REXX*/ Store this REXX as CRESLINK in a REXX library and run it before the EKM step: //IRXJCL01 EXEC PGM=IRXJCL,PARM='CRESLINK' //SYSEXEC DD DISP=SHR,DSN=your-rexx-library-goes-here //SYSTSPRT DD SYSOUT=* You may want to add some more sophisticated error handling and possibly other files to create. But this should give you an idea. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Unix File names EKM and dates
The config information will need to be changed each time the EKM STC is cycled. Apart from the filenames you already posted, what else do you need to change in the config file? If it is only filenames so they point to the current files, this is exactly what symbolic links are good for. You can keep the filenames the program refers to unchanged since these are the symbolic link names. As proposed in my REXX, you then create the files with the variable names and let the symlink point to them. I just recognized that my sample REXX will only work it the /EKM directory is unique to each z/OS instance and that this probably is not the case. You'd need to change the symlink names so these are different for different instances..h... this would require a different config file for each EKM instance. Do the EKM instances share the config file? Is it specified in the JCL? If so, you can use system symbolics to point to different (but constant) config files for each EKM instance. -- Peter Hunkeler Credit Suisse -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Unix File names EKM and dates
Peter, No for now it is just the file names inside the Unix Config file for EKM that I want to change. At this time, all of our unix files are unique per LPAR for EKM. I will be working on setting up a SYSPLEX ROOT in my Unix so we can look at unix file sharing closer. As well as automove for our mount points. Lizette -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Hunkeler Peter (KIUK 3) Sent: Tuesday, January 20, 2009 8:26 AM To: IBM-MAIN@bama.ua.edu Subject: Re: Unix File names EKM and dates The config information will need to be changed each time the EKM STC is cycled. Apart from the filenames you already posted, what else do you need to change in the config file? If it is only filenames so they point to the current files, this is exactly what symbolic links are good for. You can keep the filenames the program refers to unchanged since these are the symbolic link names. As proposed in my REXX, you then create the files with the variable names and let the symlink point to them. I just recognized that my sample REXX will only work it the /EKM directory is unique to each z/OS instance and that this probably is not the case. You'd need to change the symlink names so these are different for different instances..h... this would require a different config file for each EKM instance. Do the EKM instances share the config file? Is it specified in the JCL? If so, you can use system symbolics to point to different (but constant) config files for each EKM instance. -- Peter Hunkeler Credit Suisse - - For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Unix File names EKM and dates
You can modify the config file names via operator command, so a process that Peter outlined could work. I do not know if the new file names take effect immediately, or on the next cycle. So you could set something up on a daily basis. In our case, I have turned off all AUDIT recording except for errors, and made the metadata.xml files 8 MB, and after running now for almost a year, that file is only 1.5MB with 11,500 tapes worth of data in it. We backup the file systems, so I do not plan on externalizing these files. Of course, over a number of years that file will probably get too big, but then I can manually do something, in the absence of an automated process. Dave _ Dave Jousma Assistant Vice President, Mainframe Services david.jou...@53.com 1830 East Paris, Grand Rapids, MI 49546 MD RSCB1G p 616.653.8429 f 616.653.8497 -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Lizette Koehler Sent: Tuesday, January 20, 2009 8:09 AM To: IBM-MAIN@bama.ua.edu Subject: Re: Unix File names EKM and dates The config information will need to be changed each time the EKM STC is cycled. So, yes, I am looking at creating a pre or post REXX to alter the config file in Unix to have the names that I want. It would have been nicer if Unix provided this function or the JZOS process provided it. This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Unix File names EKM and dates
How would I code the EKM paramenter to include a date and time stamp? I want the process to generate a new file each time it is cycled. Or is that not something I can do with EKM? I would also like to make the system name symbolic as well. I have been reading my EKM and UNIX manuals but cannot seem to put my finger on whether this can be done or how it can be done. Audit.metadata.file.name = /EKM/ekmetc/SDH8_metafile.xml Would becomde Audit.metadata.file.name=/EKM/ekmetc/SYSNAME_metafile.xml debug.output.file = /EKM/ekmlog/debug Would becomde debug.output.file=/EKM/ekmlog/SYSNAME_date_time_debug Audit.handler.file.name = SDH8_audit.log Would becomde Audit.handler.file.name = SYSNAME_date_time_audit.log Lizette -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Unix File names EKM and dates
Lizette Koehler wrote: How would I code the EKM paramenter to include a date and time stamp? I want the process to generate a new file each time it is cycled. Or is that not something I can do with EKM? I would also like to make the system name symbolic as well. I have been reading my EKM and UNIX manuals but cannot seem to put my finger on whether this can be done or how it can be done. Audit.metadata.file.name = /EKM/ekmetc/SDH8_metafile.xml Would becomde Audit.metadata.file.name=/EKM/ekmetc/SYSNAME_metafile.xml debug.output.file = /EKM/ekmlog/debug Would becomde debug.output.file=/EKM/ekmlog/SYSNAME_date_time_debug Audit.handler.file.name = SDH8_audit.log Would becomde Audit.handler.file.name = SYSNAME_date_time_audit.log Lizette -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html If you can't do it with EKM facilities, can you use your automation package to copy the old logs out to whatever files you desire before it starts the new instance of EKM? -- Mark Jacobs Time Customer Service Tampa, FL I hate a song that makes you think that you are not any good. I hate a song that makes you think that you are just born to lose. Bound to lose. No good to nobody. No good for nothing. Because you are too old or too young or too fat or too slim too ugly or too this or too that. Songs that run you down or poke fun at you on account of your bad luck or hard traveling. I am out to fight those songs to my very last breath of air and my last drop of blood. I am out to sing songs that will prove to you that this is your world and that if it has hit you pretty hard and knocked you for a dozen loops, no matter what color, what size you are, how you are built. I am out to sing the songs that make you take pride in yourself and in your work. Woody Guthrie -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
