I need to identify within the Lawson notes on a CTP what tasks/pts we already have in production and what tasks/pts will actually be changed in production on install of this CTP.
I was hoping I could download the notes into a CSV file and create a database against which I could perform future searches for this purpose. I haven't found a nice way to download the Lawson CTP notes in any kind of a friendly way. Any suggestions?
Does anyone out there have a process for this already? I am looking for a targeted QA approach for onesy/twosy CTPs that must be installed. We want to know what has changed in this CTP from what we have in production.
Thanks, Tammy
I think the preview you speak of only tells me what components changed. How do you tie the components to a task/pt? Many of the tasks/pts in the notes for a patch do not reference a component.
If I figure out a fairly easy way to download and parse the CTP notes, I will post it here.
Hey!
That's more than I have now. Is this delta_readme file an output of the preview? Can you share the command to cause this report to be generated. We are in UNIX fyi.
Thanks,
Tammy
Hi Tammy,
Like Greg I use the preview option and then view the preview.log file in the directory /law1/lawson//Admin/. The preview log will give you a listing of what will change, any Database modifcations, etc.
Greg and Jim,
Our preview.log file only has the component versions listed.
Greg, is there an option on the command you provided that causes the task differences to be listed in addition to the component version changes? I ask because I think we have been running the preview without a parameter needed to generate the level of detail you referenced above.
Ok Greg, sorry to be so persistant but I just want to be sure I have this right.
I opened our last preview.log file and right after the component version listing I see what is listed below. If the patch introduced any changes, you are saying those change notes should show up under say....Know modifications section?
################################ End of PATCH44085.preview preview
# KEY TO SUMMARY: # M indicates local modifications detected. # m indicates local modifications possible, unable to determine. # NL indicates you are not licensed for this file. # + indicates a new file.
Database patches - None.
Known modifications - None.
Possible modifications - None.
Run Srgen - No.
Program Compiles - None.
Tammy: No, not in the preview.log file. Look for a file that exists in your CTP staging directory (which could be anywhere) for a file called something like 8.0.3_patch_48232.delta_readme.html You could do something like the following to find the files find / -name *delta_readme.html If you do this from the root user or from someone with root authority, this should bring back lots of file names. You'd have to look in each of those files to find the detail that I'm talking about.
Thanks Greg and John!
I am going to check on our AMT version and go from there. If I still have questions, I will let you know. Your help is greatly appreciated!
Once I have this figured out, I will post again so we can all have closure!
Happy Friday Greg and John!
Eureka! We have the correct version of AMT and we found the delta files! Thank you for your guidance on this. I am such a happier camper now.
It's in the Lawson doc. Simply use perl $GENDIR/bin/lawappinstall preview product_line versionfiledir Cheers, -Greg
Then you can look for changes in the preview.log file.