Submit a PC Export Run to Batch
When option 7 to Export has been entered beside an existing list that has a Target System Type of PC, this screen is displayed.
|
DC@P620015 Check Objects Out to a PC Platform
List XXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Specify WIN Usage as R or M, also for M, the Check Out Task & PC Name
Default : Usage/Task PC Name
_ _________ __________
Object Type Description Usage/Task PC Name
AUTHOR FIELD AUTHOR _ ________ _____________
DEM_ FIELD ##GENERIC NAME## _ ________ _____________
DEPTAB FILE Department code table _ ________ _____________
PSL FILE ##GENERIC NAME## _ ________ _____________
ORDERS PROCESS Order Processes _ ________ _____________
PSL PROCESS ##GENERIC NAME## _ ________ _____________
RECEIVE FUNCTION Receive Orders _ ________ _____________
*MTXTDEM MLTVAR ##GENERIC NAME## _ ________ _____________
FRPRT05 TEMPLATE Drill Down Summary _ ________ _____________
LD TEMPLATE ##GENERIC NAME## _ ________ _____________
Fnn=Help Fnn=Exit Fnn=Cancel Fnn=Messages
|
|
The Check Objects Out to a PC Platform screen requests use, task and PC name information about the objects to be exported.
Default: Usage/Task/PC Name
The Usage, task and PC Name that will apply to objects that are unspecified.
Usage/Task/PC Name
The Usage may be R = Read-Only or M = Modify for each object to be exported. A valid Task ID and PC Name must be specified for Usage Modify, but is not required for Usage Read-Only.
Press Enter when complete and the Submit Export to Batch screen is displayed.
|
DC@P620002 Submit Export to Batch
List : XXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Submit this job to batch . . . . . . . . . . . . YES
Using Job name . . . . . . . . . . . . . . . . . LANSAEXP
Job description . . . . . . . . . . . . . . *LIBL/QBATCH
Job queue . . . . . . . . . . . . . . . . . *JOBD
Output queue . . . . . . . . . . . . . . . *LIBL/QPRINT
Fnn=Help Fnn=Exit Fnn=Cancel Fnn=Messages
|
|
This export run confirmation screen requests details of the actual export job which will run in batch. The details required to successfully run the export job are found in:
Submit This Job
Using Job Name
Job Description
Job Queue
Output Queue
If you are transfering objects between multilingual machines, please refer to Handling Multilingual Text in the LANSA Multilingual Application Design Guide.