CTP Analysis

 22 Replies
 0 Subscribed to this topic
 27 Subscribed to this forum
Sort:
Author
Messages
Tammy
Basic Member Send Private Message
Posts: 11
Basic Member

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

Greg Moeller
Veteran Member Send Private Message
Posts: 1498
Veteran Member
Good question, Tammy.
The only way that I've been able to do this previously is to download the actual CTP's and run them in preview mode. This will create a delta_readme.htm file with actually what it did to your system.
I'd like a good way to parse that file, too, but haven't been able to dedicate any time to finding a way.
Tammy
Basic Member Send Private Message
Posts: 11
Basic Member

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.

Greg Moeller
Veteran Member Send Private Message
Posts: 1498
Veteran Member
Just as an example, I have a delta_readme file from ctp 48232.

It lists in section 4.0 in this format
Task #
PT# Description

Programs/Processes Impacted

Testing Considerations:


Task #
PT # Description
.
.
.
Greg Moeller
Veteran Member Send Private Message
Posts: 1498
Veteran Member
That didn't transfer exactly as I entered it, but I think you can get the picture.
Tammy
Basic Member Send Private Message
Posts: 11
Basic Member

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

Deleted User
New Member Send Private Message
Posts: 0
New Member

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 Moeller
Veteran Member Send Private Message
Posts: 1498
Veteran Member
Sure, from the command line -

1) Source your env variables (If needed)
. cv

2) un-tar the CTP file
tar -xvf .tar

3) run lawappinstall
perl $GENDIR/bin/lawappinstall preview .
Greg Moeller
Veteran Member Send Private Message
Posts: 1498
Veteran Member
Again that didn't transfer exactly as I entered it. If you need more help, just ask.
Tammy
Basic Member Send Private Message
Posts: 11
Basic Member

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.

Tammy

 

Greg Moeller
Veteran Member Send Private Message
Posts: 1498
Veteran Member
It actually is a separate file created in the directory that the ctp was installed from called (in this case) 8.0.3_patch_48232.delta_readme.html

You'd have to parse that file in order to see the detail that I am mentioning. And there will be a different file for each of the CTP's that you install.
Greg Moeller
Veteran Member Send Private Message
Posts: 1498
Veteran Member
To answer your previous question Tammy, no options are required on the command. You just need to look at a different file than the preview.log file.
Tammy
Basic Member Send Private Message
Posts: 11
Basic Member

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?

Tammy

################################ 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.

 

Greg Moeller
Veteran Member Send Private Message
Posts: 1498
Veteran Member

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.

John Henley
Send Private Message
Posts: 3351
Tammy,, do you know what version of the AMT you have? It's possible that you're on an older version that didn't have the tasks feature. Also, when the AMT that supported tasks was installed, there was a one-time post-install step that was required to load the initial tasks (see http://support.lawson.com...TInfo/AMTx8Info.htm)
Thanks for using the LawsonGuru.com forums!
John
Tammy
Basic Member Send Private Message
Posts: 11
Basic Member

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!

Tammy

Tammy
Basic Member Send Private Message
Posts: 11
Basic Member

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.

Tammy

Greg Moeller
Veteran Member Send Private Message
Posts: 1498
Veteran Member
Glad that John and I were able to help you!
Good luck!
-Greg
StephenV
Basic Member Send Private Message
Posts: 20
Basic Member
Hi Folks,
How can I run the CTP in preview mode? Do you know the command? I have the documentation from Lawson to install the CTP's (which I've done) but I think for future if I can preview any information it would help considerably. We ran into some problems where some objects were updated that we hadn't counted on.
Thanks!
Stephen
Greg Moeller
Veteran Member Send Private Message
Posts: 1498
Veteran Member

It's in the Lawson doc. Simply use
perl $GENDIR/bin/lawappinstall preview product_line versionfiledir

Cheers,
-Greg

Greg Moeller
Veteran Member Send Private Message
Posts: 1498
Veteran Member

Then you can look for changes in the preview.log file.

StephenV
Basic Member Send Private Message
Posts: 20
Basic Member
Great! Thanks Greg.
Deleted User
New Member Send Private Message
Posts: 0
New Member
To tag onto this thread..we have two libraries/files that the AMT has marked with M meaning that it detects a customization. We cannot see where we have customized these two libraries at all. Is this normal?