This Q&A forum allows users to post and respond to "How Do I Do ....." questions. Please do not use to report (suspected) errors - you must use your regional help desk for this. The information contained in this forum has not been validated by LANSA and, as such, LANSA cannot guarantee the accuracy of the information.
Can you tell me the difference between check out and check out Readonly?
According to Lansa documentation:
Check out is used to copy the definition of an object that is currently stored in the LANSA for i Master Repository into a Visual LANSA Slave Repository. You can check out an object as Read-only or for Update. In order to check out an object for update, you must have appropriate authority to access the object.
So if I understand correctly Check out updates the definition of the object to every Visual Lansa Slave repository while checkout read only updates the object only where it was requested ??
When you use Visual LANSA as your IDE in windows,
and your IBM as your MASTER development repository,
all the source code of your application and repository definitions are in the IBM.
If you want to be able to SEE that in Visual LANSA, you need to check out what you need
from the IBM repository to your PC.
Check out readonly, will bring stuff to your pc, but it will be only to allow you to compile it
locally, run it for test, or maybe just use it as part of other program, or coppy, etc.
You cannot make changes to it and you cannot send those changes back to the IBM. If you want to
make changes to those components, you need first to check out with UPDATE.
Make the changes, then you can perform a CHECKIN to send those components back to the IBM.
However there is probably something that I am missing here because in my setup (LANSA IDE WINDOWS - IBM MASTER), when the object (e.g. a function) is checked out read only, I can make changes to it, save it and send it via check in. The only difference that I notice is that after check out readonly the Task of the object (function/process) is empty while after check out (update) the task of the object is set to whatever task is defined in the LANSA IDE.
You should not be using dcxpgmlib or pcxuser for example as users. That would be like programming using qsecofr.
You can have your own user in the IBM, with some authorities like *JOBCTL, and the library list similar to dcxpgmlib's jobd,
Then if you are using task control, you need to configure that correctly at partition definition level, https://docs.lansa.com/15/en/lansa010/i ... 7_0025.htm
Then you need to have tasks created and have your user authorized to the task that you want to use.
