System Utilities Reference Guide

System Utilities Reference Guide

Version 9.0.0.xPublished May 2010

IBM i

Document Number ESURG-90A-09

Legal Notices

This content is for instructional or informational purposes only. This content may be changed orsuperseded without notice, and is not part of any Lawson product, maintenance or services warranty.

Export Notice: Pursuant to your agreement with Lawson, you are required (at your own expense) tocomply with all laws, rules, regulations, and lawful orders of any governmental body that apply to youand the products, services or information provided to you by Lawson. This obligation includes, withoutlimitation, compliance with the U.S. Foreign Corrupt Practices Act (which prohibits certain paymentsto governmental officials and political parties), U.S. export control regulations, and U.S. regulations ofinternational boycotts. Without limiting the foregoing, you may not use, distribute or export the products,services or information provided to you by Lawson except as permitted by your agreement with Lawsonand any applicable laws, rules, regulations or orders. Non-compliance with any such law, rule, regulationor order shall constitute a material breach of your agreement with Lawson.

Intellectual Property: All brand or product names mentioned herein are trademarks or registeredtrademarks of Lawson, or the respective trademark owners. This documentation is the proprietaryinformation of Lawson protected internationally under copyright and related intellectual property laws.Lawson customers or authorized Lawson business partners may use, copy, or transmit this document fortheir internal use only. Any other use or transmission requires advance written approval of Lawson.

© Copyright 2010 Lawson Software. All rights reserved.

Contents

Chapter 1 System Utilities 7analyze_stats. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7blddbdict . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8blddbvers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8bldexpfd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9bldibmddl. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9bldibmsec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11bldsecdict . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13bldxffiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13calc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16caldef . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16chkrec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16cmpdict. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17cndrpt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23cnvexp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24cnvimp .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24cnvtape. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25createprodline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26dbadmin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26dbcndusage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27dbcopy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28dbcreate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29dbdef . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29dbdoc. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29dbdump .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30dbfldusage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32dbindusage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32dbload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33dbmode .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34dbnode .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34dbrelusage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35dbreorg. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35dbreorg -G GCfile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37dbupdate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38dburf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39dbusers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40delckpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40delement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40deljobhst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41derfldrpt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42dmpappclmphr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43dmpappmsg .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43dmpappphr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44dmpdict. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44dmpdftxt. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

System Utilities Reference Guide Contents 3

dmpfldtxt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50dmplang. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51dmplapmerr. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51dmppgftxt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51dmpprodmenus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52dmprpgpi . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52dmpscrtxt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53dmpsecdict . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54dmptitle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54dmpuniveng . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55dmpunivlib . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55dmpunivmen.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55dmpunivtkn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56dmpunvhlp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56dmpunvmsg .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56dmpunvphr. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56docname .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57editda. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59expsysdb. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59fldrpt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61gendbload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61grpdef . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62hlpgen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62ibmdu.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63ilename.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63impexp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64importdb. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66integ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67jbsubmit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67jobdef. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68jobdump.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68jobinq. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69jobinteg. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69jobload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70jobprmrpt. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71jobrpt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71jobstatus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71jqdef . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72jqdflt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72jqrpt. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72jqstatus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73jqsubmit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73js . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73kndef . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74laenv . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74langdef . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74laservipc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74lashow.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75laua . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75lawcmp .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75ldappclmphr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76ldappmsg .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76ldappphr. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77ldappvallst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

4 Contents System Utilities Reference Guide

lddoctxt. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78ldhlptxt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78ldlang. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78ldprodmenus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79ldtitle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79lduniveng . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79ldunivlibs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79ldunivmenus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80ldunivtkns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80ldunvhlp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80ldunvmsg.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80ldunvphr. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81libdef . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81licsta . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81loadusers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82loan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83locdef . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83lsconfig .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83lsdump .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86lsload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87lstinvk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90lstprodatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90menurpt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91msggen .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91msgmnt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91msgrpt. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92pgftxt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93pgmdef . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93pgmdef2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94phraserpt. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94phrcnt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94prmdump.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94prmload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95proddadi. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95prtdef . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95qcompile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96qcontrol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96qstatus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97queue .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97recdef . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97recrpt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97rngdbdump .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97rpgcmp .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99rpgshell. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100rptgen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100rulerpt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101scrgen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102secdump .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102secinteg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103secload. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104setdbvers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105setnotused . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105setsfl. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105skndef . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .106

System Utilities Reference Guide Contents 5

sqldbcopy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .106srgen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108startladb. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109startlajs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109startlase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109startlatm.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109startlaw.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109startqueue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110stopjobq . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110stopladb . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110stoplajs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110stoplase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111stoplatm.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111stoplaw .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111stopqueue .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111sysdelfile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111sysdump .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112sysload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113titlerpt. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115tknsecrpt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115tmcontrol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115tokendef. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .116ujobdump .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .116ujobload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .118univver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120unvmnurpt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120updatchfile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120updatchorph . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .121upgenvgrps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .121useracc. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .122userdoc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .122vallstrpt. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123verifyibm .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123vwdblog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123workdef. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124workgen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124wtsubmit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .125

Appendix A Documentation Conventions and Support 127Utility Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127Documentation Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128Related Lawson Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131

Index 133

6 Contents System Utilities Reference Guide

Chapter 1

System Utilities

This section lists the system utilities in alphabetical order by program name.

In most cases, to view the syntax of a utility, type the utility at the Qshellcommand line or the utility plus a -u option and press Enter. The syntaxwill appear.

If you are not familiar with Lawson utility syntax documentation conventions,see "Documentation Conventions and Support" on page 127.

analyze_statsanalyze_stats Analyze Database Statistics Script

analyze_stats [-oqrV] [-d DataArea | DataID] [-p Program][-l Path]

The analyze_stats script creates a configuration file for the tables analyzed bythe report. The configuration file shows tables that you could configure forcaching and the recommended number of records to be cached. You useanalyze_stats in conjunction with the timed statistics feature.

For more information, see the Lawson Administration: Data Access guidefor your database.

Program Option Descriptiono Offline Mode. Do not connect to the database.

q Quiet Mode. Generate only the program.cfg file

r Report Mode. Generate only a report; do notgenerate a configuration file.

dDataArea|DataID

Specify a data area or data ID to analyze.

p Program Specify a program to analyze.

l Path Designate a path to the timestat files.

V Print the usage.

System Utilities Reference Guide Chapter 1 System Utilities 7

blddbdictblddbdict Build Dictionary

blddbdict [-q] productline

blddbdict -p dataarea

Create or rebuild the product line dictionary file.

CAUTION Before using the blddbdict utility, see the Lawsondatabase access manual for your database for a completedescription of building dictionary files.

Program Option Descriptionp Specifies a specific data area dictionary for location

changes only.

q Builds all data area dictionaries within a product line.

Type the above at the Qshell command line.

- or -1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type blddbdict and click

OK or press Enter.3. Type or select the following data.

Program Options See the program options listed above.

Product Line The product line you are building the dictionaryfile for.

Data area The data area you are building the dictionary filefor.

I/O Options Optional. Display the output or redirect it to a file.

4. Press Enter.

IMPORTANT If a dictionary is built and no changes are detected, youreceive the message “New Dictionary matches existing Dictionary --no change made.” If you receive this message, do not reorganize thedatabase.

blddbversblddbvers Build Database Version File

blddbvers productline [versionfile]

Builds the database version file.

8 Chapter 1 System Utilities System Utilities Reference Guide

bldexpfdbldexpfd Build Export File Description

bldexpfd productline exportfdfile [filename...]

Generate a file description for formatting an export file. It is useful for buildinguser programs to dump user database files and to import them into Lawsondatabase files. The file includes the database file field names and their sizesin a record layout format. Generate the file descriptions for the files you wantto export and put them in a COBOL program that writes the export records.

Type the above at a Qshell command line

Example Command and OutputThe following command creates a file called gltrans.fd that contains thefile description for the gltrans file in the app900 product line.

bldexpfd app900 gltrans.fd gltrans

The following example illustrates a portion of the output from this command:*************************************************************** GLTRANS-FILE ***************************************************************01 EF-GLTRANS-REC.

02 EF-FILE-NAME PIC X(10) VALUE "GLTRANS".02 EF-GLT-COMPANY PIC 9(4).02 EF-GLT-FISCAL-YEAR PIC 9(4).02 EF-GLT-ACCT-PERIOD PIC 9(2).02 EF-GLT-CONTROL-GROUP PIC 9(8).02 EF-GLT-SYSTEM PIC X(2).02 EF-GLT-JE-TYPE PIC X(1).02 EF-GLT-JE-SEQUENCE PIC 9(2).02 EF-GLT-LINE-NBR PIC 9(6).02 EF-GLT-OBJ-ID PIC 9(12).02 EF-GLT-STATUS PIC 9(1).

bldibmddlbldibmddl Build Data Definition Language

bldibmddl [-UqaoRDTIGECKBWXSV] [-u DbLoginName] [-pPassword] DataArea [SystemCode] [FileName ...]

The bldibmddl utility generates SQL statements for creating or deletingselected tables, indexes, and stored procedures. The utility can operate onspecific tables, all tables in a system code, or all tables in a product line. Itcreates Data Definition Language (DDL) text according to the highest possibleversion with the given compatibility. The definitions that generate the SQLstatements reside in the Lawson dictionary and are maintained by Lawsonutilities.

The bldibmddl utility can be run to create an output file containing the SQLstatements, or it can be run in update mode to implement changes to theSQL database objects.


Program Option DescriptionU Update; create objects in the database.

If you use the -U option, the generated SQLstatements update the IBM DB2 database definition.Otherwise, SQL statements are generated but notexecuted. If you are working with critical data, donot use the update mode without first examiningthe DDL. Instead, the preferred method is to directthe output to a file that you can examine, edit ifnecessary, and issue the command to the databasethrough a SQL utility.

q Quiet mode. Do not echo DDL to stdout.

a Positioning mode. Start at dataarea [systemcode]filename.

If you use the -a option, you can start the utility at aspecific system code or file.

o Offline Mode. Do not connect to the database

R Rebuild mode. Drop objects before creating.

If you do not specify either the -R or -D option,output is generated to create tables and indexes.

D Drop objects only.

If you do not specify either the -R or -D option,output is generated to create tables and indexes.

T Affect table objects only.

If you do not specify the -T or -I option, output isgenerated for both tables and indexes.

I Affect index objects only.

If you do not specify the -T or -I option, outputis generated for both tables and indexes. If youdo not specify either the -R or -D option, output isgenerated to create tables and indexes.

G Affect trigger objects only.

B Affect non-native objects only.

Cannot be used with -U. Requires -T or -I. Thedefault is -BTI.

E Affect text indexes only.

Requires the -I option.

C Rebuild the conditional indexes.


Program Option DescriptionK Create an additional index without a descending

column for the primary key constraint. Use thisoption if you need to replicate an IBM DB2 table thathas a descending column.

Requires the -I option. Cannot be used with the-E option.

Running bldibmddl with the -K option allows forcreation of a primary key to enable tables that havea descending column in the primary index to bereplicated. The -K option generates an additionalindex without a descending column for the primarykey constraint. The intent of the -K option is toget around the IBM DB2 limitation of not allowingprimary key constraints on indexes with one or moredescending columns. Use bldibmddl with -UIKafter you run a dbreorg (or dbcreate) to restore theoptional primary key indexes which are dropped inthe dbreorg process.

The bldibmddl utility, when used without the -Koption, also drops the optional primary key indexes.Run the utility with -UIK to restore the optionalprimary keys after the tables are rebuilt with eitherdbcreate or bldibmddl.

W Affect native view objects only.

Cannot be used with -U or any other object typeoption.

X Affect non-native view objects only.

Cannot be used with -U or any other object typeoption.

S Generate DDL into files by system codes:dbname.systemcode.ddl.

u DbLoginName The database login name to use.

p Password The password for the database login name.

V Print the utility version.

bldibmsecbldibmsec Create Security Objects in an IBM DB2 Database

bldibmsec [-UDGVq] [-u DbLoginName] [-p Password]DataArea [DatabaseService]

Checks the Lawson User Security definition to see which users have accessto which tables and generates SQL grant/revoke permission statementsbased on the dictionary.


Before you start If your system uses LAUA security, and you haveUSEOSID=TRUE set in your $LAWDIR/productline|dataarea/IBM file, andLAWSONUID=TRUE set in your ladb.cfg file, do not use the bldibmsec utility.

Before you start If your system uses Lawson Security and ResourceManagement, and you have USE_CFG_FILE and USE_PRIVILEGED_IDspecified for a database service login method, do not use the bldibmsecutility for that database service.

Option Descriptionu DbLoginName The database user login.

p Password The password for the database user.

U Update mode. Issue query directly to the database.

D Drop-only processing; revoke all permissions fromall Lawson tables for all Lawson users.

Once Lawson table-level security exists in the IBMDB2 database, generate SQL statements to removeit by running the bldibmsec utility with the drop (-D)flag.

G LAUA security only.

Generate security for groups instead of individualusers.

DataArea The data area that you want to apply security to.

DatabaseService Lawson Security only.

The name of the database service defined for yoursystem.

For each RMId, bldibmsec validates its accessto the DatabaseService. If the RMId has accessto the service, bldibmsec resolves the RMIdsdatabase login and generates the grant/revoke SQLstatement.

V Print the version.

q Do not print the commands to stdout.

Error ProcessingIf an error occurs that the bldibmsec utility cannot handle, it stopsimmediately. The commands that have executed up until that point remainin effect, but no further commands are executed. To revoke the permissionsgranted up to that point, run the utility again with the same set of options plusthe -D option. For example, if when the error occurred you were runningthe following:


bldibmsec -U dataarea

then run:

bldibmsec -DU dataarea

bldsecdictbldsecdict Build Security Dictionary

bldsecdict [-dV] dataarea|dataID

Update the security dictionary. For more information, see LawsonAdministration: LAUA Security.

Program Option Descriptiond Build directly to the active security dictionary (no

dbreorg).

V Display the version number of this utility.

bldxffilesbldxffiles Xternal Format File Builder

To build external format files for all print files:

bldxffiles -XCAPUTdp Username JobName JobStep [-lLanguage] [-v SpecVersion]

To build external format files for a single file:

bldxffiles -S[XCAPTdp] | -q | -F UserName FilePathNamePrintFileName [-l Language] [-v SpecVersion]

Enables you to build various additional files from a report programs printfiles, including CSV files that can be opened with a spreadsheet programand PDF files.

You can run this utility from a Qshell command line or by accessing aparameter form. To access the parameter form, do a form transfer tobldxffiles.

You have several main options for how to indicate which files you want built:• Specify one or more of the -C, -X, -A and -P options to generate the

CSV, XML, ADO, or PDF files.• Specify the -F option to generate only a PDF file from an input file.• Specify the -U option to generate the same type of files that were

generated by the report job when it ran originally.

NOTE You can also generate these additional files at run time by settingparameters in the report configuration files. For more information, see LawsonAdministration: Jobs and Reports.


Program Option DescriptionC Generate CSV files.

X Generate XML (.xml and .xid) files. Currently, these areused internally by Lawson Software.

A Generate the ADO files (_ado.xml, .csv and_ado_schema.xml). These are used by the OLE DBserver.

U Generate files based on the report configurationparameters currently in place.

T Include the total groups in the CSV file for any groupsset up with the $TOTOFGRP key word.

P Create PDF files from print files.

S Build files only for the path and print file specified.

F Build PDF files from the specified input file. This inputfile can be any text file, not necessarily a print file. ThePDF files are created in the current working directory ofthe user running bldxffiles.

Other than the -v option, all other options are ignoredif you use the -F option.

vSpecVersion

The output file suffix and display mode for the PDFfile. Valid SpecVersion values always start with the"PDFPRM=" prefix. Display mode values include:• _L - Normal landscape mode (default)• _P - Portrait mode• _L158 - Condensed landscape mode• _L198 - More condensed landscape mode• _L233 - Maximum condensed landscape mode

If you include the -v SpecVersion parameter, thedisplay mode value is appended to the file name.For example, if you specify -v PDFPRM=_L158 theresulting PDF file name will be InputFileName_L158.pdf

You can use -V instead of -v to see a more verboseoutput to the screen.

d Turn on XFF debugging.

l Language Specify the language to use for the generated fiiles.This assumes the language has been defined andtranslations for column headings have been providedthrough the translation utilities. For more information,see Lawson Administration: Translation.

p Create the .prop and .grp files in the print directory.Otherwise, the global .prop and .grp files in the RptMapdirectory are used. In either case, .prop and .grp filesare generated if they do not already exist or if theirtimestamps do not match the RptMap.


Program Option DescriptionUserName If you are not using the -F option, this is the name of the

user who created the print files to be converted.

If you are using the -F option, this is a placeholder only.You must specify some text for this, but it can be anycharacter.

JobName The name of the job whose print files are to beconverted.

JobStep The job step whose print files are to be converted.

FullFilePath The path to the input file, if you are using the -S or -Foption.

FileName The name of the input file, if you are using the -S or-F option.

I/O Options Optional. Display the output or redirect it to a file.(Available only through the parameter form.)

q Display the parameter wildcard usage. See below.

Parameter Wildcard Usage

You can use wildcard values in the UserName and FullFilePath parameters.The format is:

<PrefixChar><VarString>

where <PrefixChar> can be =, $, *, #, @, +, %, or !. You must use one ofthese characters as a prefix to signal that what follows is a variable string.Different prefix characters are available because not all of them work on alloperating systems. For example, you may receive an error if you use thedollar sign as a prefix character on a UNIX system.

where <VarString> can be any of the following:

String Description

LAWDIR or L $LAWDIR environment variable value.

GENDIR or G $GENDIR environment variable value.

HOME or H $HOME environment variable value.

USER or U The user name from the operating system userprofile of the person running bldxffiles.

CWD or C The current working directory.

LPU $LAWDIR/print/UserName where UserName isthe user name of the person running bldxffiles.

Examples:

bldxffiles -SC =U =LPU/jobname/1 reportfilename

bldxffiles -F $U @H filename

bldxffiles -SXC +U +C reportfilename


calccalc User Accessories Calculator

Use the calculator to perform basic mathematical operations.

To access the calculator:1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type calc and click the

OK button or press Enter.

caldefcaldef Calendar Definition

Define a calendar for keeping track of your working schedule on an electroniccalendar.

To access the Calendar Definition utility:1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type caldef and click the


chkrecchkrec Check Validity of Database Records

chkrec [-a] [-n] dataarea [filename ...]

The Check Database Records utility (chkrec) identifies bad data. chkrecscans the entire data area or any specified files. You can specify to continuechecking after finding the first bad record in a file.

chkrec produces the same output as described for online record checking.

Program Option Descriptiona Check all database file types; only Lawson database

files are checked by default.

n Go to next file after the first bad record.


- or -1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type chkrec and click the

OK button or press Enter.3. On the Check Database Records form, type or select the following data.

Field Description

ProgramOptions

See above.

Data Area Data area you want to check records for.


Field Description

Database Files Files to check.

Leave blank to check all files in the data area.


4. Press Enter.

cmpdictcmpdict Dictionary Comparison

cmpdict [-d] SourceDataArea DestinationDataArea

The Dictionary Comparison utility (cmpdict) compares the data structuresof two product line or data area dictionaries. This utility can help identifytable, field, and index definition changes made between release levels of anapplication, product line, or data area.

Program Option DescriptionSourceDataArea Specify the first data area to use in the dictionary

comparison.

DestinationDataArea Specify the second data area to use in thedictionary comparison.

d Print additional detail to stdout.

cmpdict OutputThe output of a cmpdict command can be redirected to an ascii file and thenimported into a spreadsheet. The format of the cmpdict command outputdepends on which type of database object is being compared:• "File Database Object (FILE)" on page 17• "Index Database Object (INDEX)" on page 18• "Field Database Object (FILEFIELD)" on page 19• "Index Field Database Object (INDEXFIELD)" on page 20• "Index Condition Database Object (INDEXCOND)" on page 22

File Database Object (FILE)The following example shows the columns written by cmpdict when thedatabase object being compared is a file in the database.

NOTE The first row shown in this example is not written by the utility; it isprovided for the sake of explaining the output more clearly.

SystemCode FileName Subject Action SqlName ViewAR ARISGBLK FILE DELETESY DATECOLS FILE NEWAR ARISGBLK FILE CHANGE ISVIEWHR L_HEMP FILE NONE

The following table describes the output.


Column Description Explanation

1 SystemCode The system code in which the file exists.

2 FileName The name of the file being compared betweendata areas.

3 Subject The type of database object being compared.In this case, FILE.

4 Action The type of difference in the database objectbetween the source and destination dataareas:• NEW

Indicates that the database object is newin destination data area.

• DELETE

Indicates that the database object existsin the source data area, but not in thedestination data area.

• CHANGE

Indicates that the database object isdifferent in destination data area.

• NONE

Indicates that the database object isidentical in both data areas.

5 SqlName For future implementation.

6 View If the file is a view, the phrase IsView willappear.

Index Database Object (INDEX)The following example shows the columns written by cmpdict when thedatabase object being compared is an index.


SystemCode FileName Subject Action Name SqlName UniqueAR AROITEMS INDEX DELETE AROSET10PR TIMERECORD INDEX NEW TRDSET10PR TIMERECORD INDEX CHANGE TRDSET11PR TIMERECORD INDEX PRIMARY TRDSET12




1 SystemCode The system code in which the file exists.


3 Subject The type of database object being compared.In this case, INDEX.



• DELETE


• CHANGE


• PRIMARY

Indicates that the database objectbecame the primary index in thedestination data area.


6 Unique Whether the index is unique or not.

Field Database Object (FILEFIELD)The following example shows the columns written by cmpdict when thedatabase object being compared is a field in a database file.


SC FileName Subject Action Pos Ref-Fld-Name Name Occ Type Prec ScaleAR AROITEMS FILEFIELD CHANGE DISC-PCT 3 Percent 5 5LA CKPOINT FILEFIELD CHANGE RESTART-INFO 1 AlphaLower 691 0PR TIMERECORD FILEFIELD CHANGE WAGE-AMOUNT 1 Signed 11 2AR AROITEMS FILEFIELD DELETE INVOICEHR EMPLOYEE FILEFIELD NEW AFTER ZIP COUNTRY




1 SystemCode The system code in which the field exists.


3 Subject The type of database object being compared.In this case, FILEFIELD (a field in a file).



• DELETE


• CHANGE


5 Position The location of the field in the file, when thefield is new or the change is that the fieldmoved within the file:• BEGIN

Indicates that the field is at the beginningof the file in the destination data area.

• END

Indicates that the field is at the end of thefile in the destination data area.

• AFTER

Indicates that the field follows theRef-Field-Name field in the destinationdata area.

7 Ref-Field-Name

A field used to indicate the position of anotherfield in a file.

8 Name The name of the field being compared.

9 Occ The number of times the field occurs.

10 Type The datatype of the field listed in column 8.

11 Precision The precision of the field listed in column 8.

12 Scale The scale of the field listed in column 8.

Index Field Database Object (INDEXFIELD)The following example shows the columns written by cmpdict when thedatabase object being compared is an index field.



SystemCode IndexName Subject Action Position Ref-Field-Name Name SqlName DirectionPR TRDSET6 INDEXFIELD MOVE AFTER PROCESS-GRP TIME-SEQAR AROSET1 INDEXFIELD NEW AFTER TRANS-TYPE INVOICE



1 SystemCode The system code in which the index fieldexists.

2 IndexName The name of the index being comparedbetween data areas.

3 Subject The type of database object being compared.In this case, INDEXFIELD (a index in a file).



• DELETE


• CHANGE


5 Position The location of the field in the file, when thefield is new or the change is that the fieldmoved within the file:• BEGIN

Indicates that the field is at the beginningof the file in the destination data area.

• END

Indicates that the field is at the end of thefile in the destination data area.

• AFTER

Indicates that the field follows theRef-Field-Name field in the destinationdata area.

7 Ref-Field-Name

A field used to indicate another field in theindex.

8 Name The name of the index field being compared.




10 Direction Whether the index field has changed fromascending to descending, or vice versa.

Index Condition Database Object (INDEXCOND)The following example shows the columns written by cmpdict when thedatabase object being compared is an index condition.


SystemCode IndexName Subject Action NamePR TRDSET4 INDEXCOND CHANGE SOMECONDNAME



1 SystemCode The system code in which the index conditionexists.

2 IndexName The name of the index where the conditionexists.

3 Subject The type of database object being compared.In this case, INDEXCOND (a condition in anindex).



• DELETE


• CHANGE


8 Name The name of the condition being compared.


cndrptcndrpt Condition Report

cndrpt productline [filename]

List existing rules for conditions in the specified file. For more information onconditions, see Doc for Developers: Application Development WorkbenchStandards.


- or -1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type cndrpt and click the

OK button or press Enter.3. Type or select the following data.

Field Description

Product Line Product line for the conditions.

File Name File name the conditions reside under.


4. Press Enter.


cnvexpcnvexp Convert Sequential Export File

cnvexp [-f] filename recordsize

Convert a sequential export file (typically from a mainframe computer) so ithas Return (Enter) characters. Typically, when an export file comes from amainframe, each record is a fixed length with no Return characters. To use,the file must have Return characters.

Program Option Descriptionf Output fixed-length records.


- or -1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type cnvexp and click the


Field Description

ProgramOptions

See the program option above.

Export FileName

Export the file you want to convert to include Return(Enter) characters.

Record Size Size of a record in the export file.

I/O options Optional. Display the output or redirect it to a file.

4. Press Enter.

For more information regarding copying and transferring data, seeLawson Administration: Server Setup and Maintenance.

cnvimpcnvimp Convert a Line Sequential Import File

cnvimp filename recordsize

Convert a line sequential import file to a sequential file.


- or -1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type cnvimp and click the



Field Description

Import FileName

Import the file you want to convert to a sequential file.

Record Size Size of a record in the import file.

I/O options Optional. Display the output or redirect it to a file.

4. Press Enter.

For more information, see Lawson Administration: Server Setup andMaintenance.

cnvtapecnvtape Convert Tape

cnvtape [-n] InputFile RecordSize OutputFile

Use this utility to convert a tape file to a fixed-length record file. This utility onlyworks with files defined as tape files in the Work Definition utility (workdef)..

Program Option Descriptionn End each line with a new line character.

InputFile The tape file.

RecordSize The length of each fixed-length record.

OutputFile The file containing the fixed length record.

countcount Count Records in Table

count [-d databasespace] dataarea|dataID [systemcode][filename ...]

The count utility counts the number of records in a specified database table(file).

Program Option Descriptiond databasespace Produce output for an editda directives file.

V Print the utility version.


createprodlinecreateprodline Create Product Line

createprodline [-fq] prodlinename

The createprodline utility creates a new product line.

Program Option Descriptionf Forces the creation of the product line regardless of

conditions.

q Runs the utility in quiet mode (supporesses output).

prodlinename The name for the new product line.

dbadmindbadmin ladb Administration Utility

dbadmin -idle DataAreadbadmin -idleALLdbadmin -get REUSE|DEBUG|IDLETIMEdbadmin -set REUSE|DEBUG|IDLETIME [value]dbadmin -get TIMESTATS|USERFILTER|PROGRAMFILTER|DATAAREAFILTER|TIMESTATSDIRdbadmin -set TIMESTATS|USERFILTER|PROGRAMFILTER|DATAAREAFILTER|TIMESTATSDIR [value]

Allows the administrator to change certain database configuration parameterswithout stopping the database service.

Parameter Description-idle[DataArea]

Stop the idle database drivers within a data area.

-idleALL Stop the idle database drivers for all data areas.

-get Get the current value for the ladb.cfg configurationfile variable specified by the flag following the -getparameter.

-set Set the ladb.cfg configuration file variable to thespecified value.

REUSE [value] Enable or disable reuse of idle driver connectionsby ladb.

When setting REUSE, you can specify a value. Validvalues are OFF or ON; FALSE or TRUE; 0 or 1.

DEBUG [value] Enable or disable debug mode.

When setting DEBUG, you can specify a value. Validvalues are OFF or ON; FALSE or TRUE; 0 or 1.


Parameter DescriptionIDLETIME[value]

Specify how long a database driver can be idlebefore it is stopped.

When setting IDLETIME, you can specify a valuein minutes.

TIMESTATS[value]

Enable or disable timed statistics collection.

When setting TIMESTATS, you can specify a value.Valid values are OFF or ON; FALSE or TRUE; 0or 1.

USERFILTER[value]

Specify a name of a user to monitor. If a user namehas no program listed next to it, all programs beingrun by that user are monitored.

Requires TIMESTATS set to TRUE.

NOTE If you have modified the USER_FILTERparameter with a prefix to identify auser as an operating system user(USER_FILTER=OSID:username) or a webuser (USER_FILTER=LOBS:username), you needto remove the prefix (OSID: or LOBS:) from thisparameter.

DATAAREAFILTER[value]

Specify a data area to monitor when using timedstatistics.


PROGRAMFILTER[value]

Specify a program to monitor when using timedstatistics. If the program has no user entry precedingit, all instances of this program are monitored.


TIMESTATSDIR[value]

The directory for the output files from the timedstatistics monitor. This must be an absolute path.

The default for IBM DB2 on IBM i is tmp.

dbcndusagedbcndusage Condition Usage Report

dbcndusage productline filename conditionname

List all occurrences in the database definition of the specified condition.


- or -1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type dbcndusage and

click the OK button or press Enter.


3. On the Condition Usage Report form, type or select the following data.

Field Description

Product Line Product line for the field.

File Name File name the field resides under.

Condition Name Condition name to perform the usage report on.


4. Press Enter.

For more information on conditions, see Doc for Developers: ApplicationDevelopment Workbench Standards.

dbcopydbcopy Database Copy

dbcopy [-cdEpfiRt] [-S srcdir] [-Ddestdir] sourcedataarea destinationdataarea[filename|systemcode...]dbcopy -7[-cdEpfiRt] sourcedataarea destinationdataareasourcelibrary [filename|systemcode...]dbcopy -V

The dbcopy command is used to copy data from one data area to anotherdata area. By default, the data in all the files is copied. If only the files in asystem code or specific files should be copied, list them in the command. Thefiles copied must be in both dictionaries and, unless the -c option is specified,they must have the same structure (the database columns are the same).

Program Option Descriptionc Convert data where the two files do not exactly match.

Columns in both files are copied and columns only inthe destination file are set to the default value. If thefiles are the same, no conversion is done.

d Delete the file and indexes from the destination dataarea database (if they exist), create the file in thedatabase, copy the data, and then create the indexesbefore copying.

E Exclude IsView objects in the destination.

p Precreate indexes before copying. Only use with -d.

f Fix records, if needed, while copying.

i Ignore errors while copying.

R Reject records with bad keys while copying.

t Truncate the file in the destination data area databaseprior to copying the data.

S Read source data from files in the srcdir directory.

D Write destination data to files in the destdir directory.


Program Option Description7 Copy from a 7.x Lawson Environment on IBM i. The IBM

i library containing the file(s) to copy is sourcelibrary.

V Prints the version of dbcopy.


or1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type dbcopy and click

OK or press Enter.

dbcreatedbcreate Create Database

dbcreate dataarea

Sets a flag in the repository (database definition, product line, or dataarea), making it possible to create database files corresponding to the datadictionary. The actual database files are not created until a record is writtento the file. You use dbcreate for a new product line or data area. Use theReorganize Database utility to implement dictionary changes in existingdatabase files. For more information, see the Data Access manual for yourdatabase.

dbdefdbdef Database Definition

Define the product line database. For more information, see Doc forDevelopers: Application Development Workbench.

To access the Database Definition utility:1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type dbdef and click the


dbdocdbdoc Print Data File Text

dbdoc [-eincrpw] productline systemcode [filename...]

Print data file text, listing important information about an application’s datafiles.

Program Option Descriptione Print items without document text.

i Print index only.


Program Option Descriptionn Do not print detail columns.

c Print definitions for COBOL names (default).

r Print definitions for RPG names.

p Print cover and copyright.

w Web output - HTML formatted documents.

The output directories must exist before you run dbdoc.The dbdoc utility expects the output directories to bein the current working directory. It expects a directorynamed for the product line and, within that, a directoryfor the system code. You can create the directoriesmanually in the current working directory or create themdynamically with the Print Technical Text utility (dburf)with the -w and -d options. For example:

dburf -w -d /EnvironmentDirectory/law/lawapp9/webdocs lawapp9


- or -1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type dbdoc and click the


dbdumpdbdump Dump Database File

dbdump [-dp] [-i index] dataarea|dataID filename [>flatfile]

Dump database files to standard output. You can then load the database fromthe flat file using dbload. Do not use this utility to import data into a Lawsondatabase from a non-Lawson application system. The main use for this utilityis to dump the Lawson database on one machine and load it onto another.

Unless you use the -d option, the utility truncates fields larger than 80columns (or 132 columns, with the -p option). To dump files containing fieldslarger than 80 columns, in addition to using dbdump -d, you can also userngdbdump with either the -d or -c option.

If your data files have attachments, make sure you dump both the header anddetail attachment files. They reside in the same data area as the data towhich they are attached, and they are named as follows:

L_HPrefix L_DPrefix

where the following values apply:


Value DescriptionPrefix The prefix of the data file the attachments are related to.

L_H A header attachment file. If the file name is EMPLOYEE,for example, the result is L_HEMP. The header is in thefirst 512 bytes of the attachment.

L_D The detail attachment file. This makes up the remainingbytes (up to 32,000) of the attachment.

IMPORTANT To have the system automatically dump and load theattachment files, use the expsysdb and impexp utilities.

Program Option Descriptiond Dump to a flat file. Use with the dbload utility. You can

also use this option to dump files containing fields largerthan 80 columns.

p Printer format (132 columns). Writes the output in132-column format. The default is to write the output in80-column format for online display.

i Use index (for example, -iGLMSET1). Dumps thedatabase using an index sequence. The index namemust follow the -i.


- or -1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. in the Form ID field on the Form Transfer form, type dbdump and click

the OK button or press Enter.3. Type or select the following data.

Program Options See program options above.

Dictionary Name Dictionary (data area) whose database files youwant to dump.

File Name File you want to dump.


4. Press Enter.

IMPORTANT Date, time, user name, type, utility name, and key fieldactivities of this utility are logged in the $LAWDIR/system/secadmin.logfile.


dbfldusagedbfldusage Field Usage Report

dbfldusage productline filename fieldname

List all occurrences in the database definition of the specified field.


- or -1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. in the Form ID field on the Form Transfer form, type dbfldusage and

click the OK button or press Enter.3. On the Field Usage Report form, type or select the following data.

Field Description



Field Name Field name to perform the usage report on.


4. Press Enter.

For more information about database fields, see Doc for Developers:Application Development Workbench Standards.

dbindusagedbindusage Index Usage Report

dbindusage productline filename indexname

List all occurrences in the database definition of the specified index.


- or -1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. in the Form ID field on the Form Transfer form, type dbindusage and

click the OK button or press Enter.3. On the Index Usage Report form, type or select the following data.

Field Description



Index Name Index name to perform the usage report on.


4. Press Enter.

For more information about indexes, see Doc for Developers: ApplicationDevelopment Workbench Standards.


dbloaddbload Load a Database from a Flat File

dbload [-7anrf] dataarea|dataID filename [flatfilename]

Load a flat file into a database file. The only format it accepts is dbdump -d.For more information, see "dbdump" on page 30.

Program Option Descriptiona Overwrite all duplicate records. Replaces existing

database records with duplicate records in the flat file. Ifthe flat file has multiple occurrences of a record, the lastoccurrence is stored in the database.

n Do not overwrite duplicate records. Does not replaceexisting database records with duplicate records fromthe flat file. It ignores the duplicate records in the flat file.

r Report on duplicate records that prints duplicate recordsbetween the flat file and the database. It does notreplace the existing database records.

f Do not check for existing records. Required for SQLdatabases. Writes whatever records exist in the flat file,completely overwriting the records in the database.

7 Indicates that the flat file is in Lawson 7.x format forIBM i.


- or -1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. in the Form ID field on the Form Transfer form, type dbload and click the



Product Line The dictionary (product line) you are loading theflat file to.

File Name The file you want to load. Leave blank to loadthe entire database.

Flat File Name The flat file to load database files from.


4. Press Enter.

IMPORTANT Date, time, user name, type, utility name, and key field activitiesof this utility are logged in the $LAWDIR/system/secadmin.log file.


dbmodedbmode Set or Display Database Mode

dbmode -p|s|m|n

The Set or Display Database Mode utility (dbmode) lets you view or set thedatabase user mode.

This command applies to only the Database Server (ladb), not to the IBMDB2 server.

Program Option Descriptionp Print current database mode.

s Set single-user mode. If you are the only user on thedatabase, you can specify single-user mode. No newusers are allowed to access the database.

m Set multiuser mode.

n No new database users are allowed. Prevents any newdatabase user processes from starting. Users with adatabase process running when this command is issuedcan continue to access the database.


dbnodedbnode Analyze Element Node

dbnode productline

Perform a nodal analysis of database elements. Each word in an elementis called an element node. For example, the element First-Name has twonodes: First and Name. This utility lists each database element node and theelements that use it.


- or -1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type dbnode and click the


For more information, see For more information, see Doc for Developers:Application Development Workbench Standards.


dbrelusagedbrelusage Relation Usage Report

dbrelusage productline filename relationname

List all occurrences in the database definition of the specified relation.


- or -1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. in the Form ID field on the Form Transfer form, type dbrelusage and

click the OK button or press Enter.3. On the Relation Usage Report form, type or select the following data.

Field Description



Relation Name Relation name to perform the usage report on.


4. Press Enter.

For more information about relations, see Doc for Developers: ApplicationDevelopment Workbench Standards.

dbreorgdbreorg Reorganize Database

CAUTION Before using the dbreorg utility, see the Data Accessguide for your database for a complete description of the dictionaryfile reorganization process.

dbreorg [-SCFYdin] [-W WFFile] {{-p dataarea} |Productline}dbreorg [-G [GCFile]] [-W WFFile] {{-p dataarea} |Productline}dbreorg [-lcs] {{-p dataarea} | Productline}dbreorg [-x] {{-p dataarea} | Productline}dbreorg -L Library Productline

Restart is automatic. The log file for a database reorganization is in the IFS in/EnvironmentDirectory/DB/PRODUCTLINE/reorg.hist


Program Option DescriptionC Conservative mode. This is the traditional dump and

load operation. Using the -C option, dbreorg first savesthe table’s data in a dump file before altering the table. Itis a safe mode because dbreorg can recover data usingthe dump file backup. This is the most time-consumingway of performing a dbreorg and ensures that no datais corrupted.

It is called conservative because it requires the extrastep of saving the data of the table in a dump file beforealtering the table in the database.

F Fast mode.

This mode bypasses the step of saving the table’s datain a dump file.

IMPORTANT Back up your data before runningdbreorg with this option.

S Safe mode (the default). In this mode, dbreorg firstsaves the table’s data in a dump file and then alters thetable directly in the database. If a table(s) alterationfails, dbreorg goes into Conservative mode for thefailed table and reloads from the dump file.

Y Yes. Do not prompt to continue in Fast mode (requires-F)

d No physical database exists.

i Rebuild data ID dictionary for shared data areas.

n Do not run srgen.

G GCFile Garbage collection; reorganize files specified in thegarbage collection file. The garbage collection file is alist of files to be reorganized. File names specified in thegarbage collection file are separated by a <cr> (carriagereturn character) or spaces, tabs, or commas.

When -G is specified without a garbage collection file,all files are marked for garbage collection.

W WFFile Could specify a number of work files. You must have afile to specify the work file names.

Optional. Work file to hold the database file. A work filecan be a tape device. If you do not supply a name, thedefault is $LAWDIR/productline/reorg.rwrk.

- or -

$LAWDIR/reorg.rwrk

The reorganization process dumps the database fileto a work file. It splits a single database file amongmultiple work files if a work file grows too large for the


Program Option Descriptionpartition it is in. If the file gets full, the system promptsyou for the next work file.

c Compare dictionaries showing files changed.

l List files to be reorganized.

s List number of records in the files (requires -l).

p dataarea Reorganize the specified data area. If you do not usethe -p option, specify a product line to run the reorg for.

x Print out the detail from the dbreorg.cntrl file.

L Library The library where you want the NEWIO delivery fileplaced. Use this option if you have made changesthrough the Database Definition utility (dbdef) andneed to run the split80 program after the dbreorg. Formore information, see Doc for Developers: ApplicationDevelopment Workbench Standards.

dbreorg -G GCfiledbreorg -G GCfile Garbage Collection

dbreorg [-G [GCFile]] [-W WFFile] {{-p dataarea} |Productline}

Removes deleted records from the database and compacts the files.

GCfile is the file that contains the names of other files that should havegarbage collection performed. If you do not specify GCfile, dbreorgperforms garbage collection on all files in the product line.

CAUTION Performing dbreorg -G on a full application line maybe very time consuming.

Program Option DescriptionG GCFile Garbage collection; reorganize files specified in the

garbage collection file. The garbage collection file isa list of files to be reorganized. File names specifiedin the garbage collection file are separated by any ofthe following: <cr> (carriage return character), spaces,tabs, or commas.

When -G is specified without a garbage collection file,all files are marked for garbage collection.

W WFFile Could specify a number of work files. You must have afile to specify the work file names.

Optional. Work file to hold the database file. A work filecan be a tape device. If you do not supply a name, thedefault is $LAWDIR/productline/reorg.rwrk.

- or -


Program Option Description

$LAWDIR/reorg.rwrk

The reorganization process dumps the database fileto a work file. It splits a single database file amongmultiple work files if a work file grows too large for thepartition it is in. If the file gets full, the system promptsyou for the next work file.

p dataarea Reorganize the specified data area. If you do not usethe -p option, specify a product line to run the reorg for.

dbupdatedbupdate Database Update

dbupdate [-fiR] [-I FieldDataFile] SourceDataAreaDestinationDataArea LogFile file ...dbupdate -V

The dbupdate command retrieves data records from the source data area fileusing the saved primary key in the log file; then converts, inserts, or updatesrecords in the destination data area file to match the source data area file.

If a record exists in the destination data area but is not found in the sourcedata area, then the record is deleted from the destination data area.

In order for dbupdate to process a file, the number, names, and order offields in the primary keys for the specified files in the source and destinationdata areas must match. Field types and sizes do not need to be identical, aslong as the field values can be converted.

Program Option Descriptionf Fix records, if needed, while copying.

i Ignore errors while copying.

R Reject records with bad keys while copying.

FileName The file in the destination data area that thisrow contains a default value for.

FieldName The name of a field in FileName that this rowcontains a default value for.

FieldOccurrence The number of times FieldName occurs.

FieldOccurrence must be set to 1 (one) orhigher.

FieldValue The default value you want to populateFieldName. The value must be conform tothe standard format for each field data type.Valid data types are described in the Docfor Developers: Application DevelopmentWorkbench Standards.



Expressions can be used to specifyFieldName.

SourceDataArea The data area containing the file whosevalues you want to use to update the file inthe destination data area.

DestinationDataArea The data area containing the file that you wantto update.

LogFile The file that recorded changes to thedatabase. See the Data Access guide foryour database for information about setting updatabase change logs.

file ... The name(s) of the file(s) that you want toupdate.

V Prints the version of dbcopy.


or

1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).

2. In the Form ID field on the Form Transfer form, type dbupdate and clickthe OK button or press Enter.

dburfdburf Print Technical Text

dburf [-tepcrw] [-m Module] [-d Directory] ProductLine[SystemCode] [ProgramCode...]

Print technical text, listing the updated and referenced files for a form.


- or -


2. In the Form ID field on the Form Transfer form, type dburf and click theOK button or press Enter.

3. Type or select the following data.

Program Option Descriptiont Do not print user reference text.

e Print error messages about missing document text.

p Print cover page, copyright, and form listing.

c Print definitions for COBOL names (default).

r Print definitions for RPG names.


Program Option Descriptionm Process system module only.

w Web output - HTML formatted documents.

d Directory in which to create Web output files.

dbusersdbusers View Database Processes

dbusers -n|-p|-u|-v [-d DataArea]

List the users and processes that are currently using the database.

Program Option Descriptionn List the number of users only.

p List the processes currently using the database.

u List database user numbers and process IDs.

v Verbose output, including user name, job name, andjob number.

d List information for a data area only.


delckpointdelckpoint Delete Checkpoint Records

delckpoint [-U] username jobname dataarea|dataID[jobNumber]

Delete the checkpoint records used to allow a resubmitted Needs Recoveryjob to restart where it left off. Deleting the checkpoint records has the effectof deleting the Needs Recovery job.

WARNING When running a batch update job, use delckpointwith extreme care. Running delckpoint could cause data loss orcorruption if not used appropriately. For more information, seeLawson Administration: Jobs and Reports.

Program Option DescriptionU Print usage and syntax.

delementdelement Delete Unused Elements

delement [-avil] [productline]


Delete all elements that a product line no longer uses.

Program Option Descriptiona Use all product lines.

v Verbose; print deleted elements.

i Interactive delete.

l List elements to be deleted.


- or -1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type delement and click

the OK button or press Enter.

deljobhstdeljobhst Delete Job History

deljobhst [-ckjrUvw] [-d] [-u username] [-f fromdate]todate

Delete the print files, completed job entries, and waiting job entries with anInvalid Parameter status. You can also delete individual job logs on theCompleted Jobs form, which removes the GEN database record but keepsthe physical files. For more information, see Lawson Administration: Jobsand Reports.

Program Option Descriptionc Delete Completed Job Entries Deletes completed jobs

on the Completed Jobs form and deletes the associatedjob logs from $LAWDIR/system/joblog.

k Keep Entries, Do Not Delete Produces a report listingthe job histories without deleting them.

j Delete Recurring Job Entries Deletes recurring jobentries that have passed their stop dates.

r Delete batch report files. Deletes all print files from thePrint Manager.

U Print usage and syntax. Prints the file usage and syntaxfor the selected job history.

v Verbose. Produces a report listing the verbose entries.

d Debug Messages and Verbose. Displays debugmessages and other details while the deljobhst utilityruns.

w Delete waiting job entries. Deletes the waiting jobentries on the Waiting Jobs form.


Program Option Descriptionu username Delete entries for username.

NOTE This option is not available if you are using thisutility through a LID form, rather than the command line.

f fromdate The date from which to start deleting job entries, inmmddyy format.

todate is the date to delete job entries up to, in mmddyyformat; or curdate [-nbrdays] .

NOTE If you do not use the -f fromdate option, thesystem deletes all job histories up to todate.


- or -1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type deljobhst and click


derfldrptderfldrpt Derived Field Report

derfldrpt productline [filename]

List existing rules for derived fields in the specified file.


- or -1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type derfldrpt and click

the OK button or press Enter.3. On the Derived Field Report form, type or select the following data.

Field Description

Product Line Product line for the derived fields.

File Name File with the derived fields.


4. Press Enter.


dmpappclmphrdmpappclmphr Dump Application Column Phrases

dmpappclmphr [-l language [-t]] dumpfile productline[systemcode]

Creates an ASCII text file containing all column phrases for a product line andtranslation, and stacks the column phrases for translation as seen on a form.The file includes the comment line with the maximum column translation sizeand the number of lines for the column phrase.

IMPORTANT Date, time, username, type, utility name and key field activitiesof this utility are logged in the $LAWDIR/system/secadmin.log file.

Use this utility when using ldappclmphr. For more information, see LawsonAdministration: Translation.

dmpappmsgdmpappmsg Dump Application Messages

dmpappmsg [-b] [-n] [-x] [-c Category] [-m Module] [-lLanguage [-t]] Dumpfile Productline [systemcode]

Create an ASCII text file containing application messages for a product line.

For more information, see Lawson Administration: Translation.

Program Option Descriptionb Dump blank lines for documentation generation.

n Dump non-program related messages.

x Dump only messages that are marked for translationthrough the Message Maintenance utility (msgmnt).

c Dump messages for this category. Cannot be used withthe -n option, the -m option, or a system code.

m Process system module only.

l Dump messages in this language.

t Dump non-translated messages in this language.


- or -1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type dmpappmsg and



dmpappphrdmpappphr Dump Application Phrases

dmpappphr [-l language [-t]] [-x] dumpfile productline[systemcode]

Create an ASCII text file containing all non-column phrases for a product lineand translation. The output is in alpha order and a comment line is included,indicating the minimum and maximum sizes of the space available on formsfor a given phrase. An additional line is added when dumping regular phrases(non-column) for the translator to include a short translation. No columnphrases are dumped with this utility.

Program Option Descriptionl Dump phrases in this language.

t Dump only those phrases that do not have translations.

x Dump only phrases that contain at least one alphacharacter.

Field Descriptionlanguage The language of the phrases you want to dump.

dumpfile File in which to store the application phrases.

productline Product line for which to dump phrases.

systemcode System code for which to dump phrases.




dmpdictdmpdict Dictionary Dump

dmpdict [-rdf] DictionaryName FileNamedmpdict -s[rdf] DictionaryName SystemCodedmpdict -a[rdf] DictionaryName ClassNamedmpdict -a[rcdfi] DictionaryNamedmpdict -h[a] DictionaryNamedmpdict -l[a] DictionaryNamedmpdict -[UV]

The Dictionary Dump utility (dmpdict) produces a file description from thespecified dictionary.


Program Option DescriptionDictionaryName The name of the dictionary that you want to dump a

description for. This is equivalent to a product line ordata area.

a Include all files for DictionaryName in the output.

s Include only a description of a specified systemcode (SystemCode) in the output.

c Include business class information for ClassNamein the output. For future implementation.

d Include a description of the data area and/or data IDinformation in the output.

e Include a description of elements in the output.

f Include a description of file information in the output.

h Build .c header files for the output.

i Include a description of index information in theoutput.

p Print editda directives in the output.

r Provide a raw dictionary dump.

t Include expression text in the output.

FileName A file within the specified dictionary that you want todump a description for.

U Prints the usage and syntax of this utility.

V Prints the version of this utility.

Output Examples

Dictionary DescriptionThe following example shows a sample of the output from dmpdictrelated to the dictionary.Dictionary APPS803

Stamp 1055184647nFiles 2035nSystems 50mRunFd 22096mUserFd 22232mFd 44328DictSize 6033432

Systems

System CodenFiles 0

System Code ACnFiles 171

System Code ADnFiles 6


System Code AMnFiles 82

...

Database Space DescriptionThe following example shows a sample of the output from dmpdictrelated to database space definition.Location 0

DBType (2) = OracleMachineName =Location = dattsIndLocation = idxtsCndNbr = -1BrkOutOccFlds = YesUseDateType = YesIsView = No

File DescriptionThe following example shows a sample of the output from dmpdictrelated to the file definitions.FILE ACACCTCAT

RUNFD

FileName ACACCTCATfHasAttach 0Stamp 1049140076RecSize 39nInds 3nCnds 1nIndFlds 4nCndNds 1nCndElms 1


Relation DescriptionThe following example shows a sample of the output from dmpdictrelated to relation definitions.RelFld->Fld #1

FldType 1 FT_DBFldOp 0RelNbr -1FINbr 461 BENEFICRYFldNbr 15 REL-CODE

REL #7

Name PLANRelType 0 RLT_OTOFINbr 1632 PLANIndNbr 0IsSelfRef 0DptLvl 0Required 1 RLT_REQDelRule 0 RLT_DELIGNOREDnOccurs 1nFlds 3CndNbr -1

Index DescriptionThe following example shows a sample of the output from dmpdictrelated to database file indexes.Index AAXSET2

IsDuplicate 0IsKeyChg 0Size 5nFlds 1CndNbr 0

INDFLD #0

IsDesc 0Type 0 ALPHASize 5Offset 0


Condition DescriptionThe following example shows a sample of the output from dmpdictrelated to database conditions.INDCND #0

RootCndNd 0

NODE #0IsConj 0CENbr 0

CND #0

Name AAXSET2CndType 1 FILEFLDnOccurs 0RootCndNd 0

...

CND #2

Name ACACCTCATXCndType 2 OTOFLDSnOccurs 0RootCndNd 2

Field DescriptionThe following example shows a sample of the output from dmpdictrelated to database field definitions.FILEFLD #0Name CONTRACTFldType 1 FT_DBElmType 0 ALPHAOffset 0Size 10DecSize 0FldNbr 0

FILEFLD #1Name MOD-NBRFldType 1 FT_DBElmType 30 ALPHALCOffset 10Size 15DecSize 0FldNbr 1


editda Directives File DescriptionThe following example shows a sample of the output from dmpdictrelated to editda directives.B LOC00 Oracle Location=datts IndLocation=idxtsD APPS803 LOC00F ACACCTCAT 500 50F ACACCTCATX 15000 1000F ACACCTCLSS 10 10F ACACRESRT 10 10F ACACRESRTX 10 10F ACACTCOPY 10 10F ACACTGPREL 10 10F ACACTGRP 10 10

States and Events DescriptionThe following example shows a sample of the output from dmpdictrelated to database states and events.STATE #0

Name EDITnEvents 3FstEvent 0CndNbr -1nRules 0FstRule 0nStpRules 0FstStpRules 0

EVENT #0

Name ADDEvtType 0 ET_ADDnRules 0FstRule 0nStpRules 0FstStpRules 0

...

Build Headers (-h) OutputThe following example shows a sample of the output from dmpdictrelated to headers.Dictionary APPS803

Stamp 1055184647nFiles 2035nSystems 50mRunFd 22096mUserFd 22232mFd 44328DictSize 6033432

FILE ACACCTCAT

Gen file ACACCTCAT.c built


dmpdftxtdmpdftxt Dump Data File Text

dmpdftxt [-a] [-l language [-t]] dumpfile productlinesystemcode [filename...]

Create an ASCII text file containing all U.S. English data file help text for aproduct line and system code.



dmpfldtxtdmpfldtxt Dump Field Text

dmpfldtxt [-adi] [-m module] [-l language [-t ]] dumpfileproductline systemcode [formID...]

Create an ASCII text file containing all U.S. English field help text for a productline and system code, or for one or more form IDs in a system code. For moreinformation, see Lawson Administration: Translation.

Program Option Descriptiona Dump all form field address lines, regardless of form

field text.

d Dump text defaults if form field text does not exist.

i Dump only the input field help text.

l language Dump text in the specified language.

m module Process only the module in the system; for example,Report Writer (RW) in General Ledger (GL).

t Dump non-translated text in the specified language.

Field Descriptiondumpfile File to store the text in.

productline Product line to dump text for.

systemcode System code to dump text for.

formID Form ID to dump text for.



dmplangdmplang Dump Language

dmplang [-a|-u] [-p productline] dumpfile language[language...]

Create an ASCII text file containing all translated phrases, column phrases,titles, messages, and values for applications and the Lawson Environment.For more information, see Lawson Administration: Translation.

Program Option Descriptiona Dump application translations only.

u Dump Lawson Environment translations only.

pproductline

For application translations, the product line for theapplication translations you want to dump.

Field Descriptiondumpfile File to store the translations in.

language Language whose translation records you want todump. You can specify one or more languages.


dmplapmerrdmplapmerr Dump lapm Messages

dmplapmerr

Dump lapm messages to the standard output.

dmppgftxtdmppgftxt Dump Program Document File Text

dmppgftxt [-b] [-m module] [-l language [-t]] dumpfileproductline systemcode [ProgramCode]

Dump program document file text to a flat file.

Program Option Descriptionb Dump blank lines for documentation generation.

m module Process only the module in the system; for example,Report Writer (RW) in General Ledger (GL).





productline Product line for which to dump text.

systemcode System code for which to dump text.

programcode Program code for which to dump text.


dmpprodmenusdmpprodmenus Dump Product Line Menus

dmpprodmenus -x productline dumpfile [-a menu...] [-smenu...]

Dump menus from a product line to a dump file.

Program Option Descriptionx Dump transfer menus.

a menu Get a menu and all submenus used by the specifiedmenu.

s menu Get only the specified menu.

Field Descriptionproductline Product line for which to dump menus.

dumpfile File to store the menus in.


dmprpgpidmprpgpi Dump Program Information Structures

dmprpgpi productLine systemCode programCodedmprpgpi -PlibraryName productLine systemCode

The dmprpgpi utility dumps the information structures for a program.


Program Option DescriptionproductLine The product line from which you want to dump the

program information structures.

systemCode The system code containing the program or libraryyou want to dump the information structure for.

programCode The program code (such as HR01) for the programyou want to dump the information structure for.

P Indicates you want to specify a library from which todump program information structures.

libraryName The program description or working storage libraryyou want to dump the information structure for.

dmpscrtxtdmpscrtxt Dump Form Document Text

dmpscrtxt [-a] [-m module] [-l language [-t]] dumpfileproductline systemcode [formID...]

Create an ASCII text file containing all U.S. English form help text for aproduct line and system code or for one or more form IDs in a system code.For more information, see Lawson Administration: Translation.

Program Option Descriptiona Dump all form address lines, regardless of whether

they contain form document text.

m module Process just the module in the system; for example,the Report Writer (RW) module in the GeneralLedger (GL) application.

If you use this option, you must also type theassociated application system in the System Codefield.




productline Product line to dump text for.

systemcode System code to dump text for.

formID The form ID to dump text for.



dmpsecdictdmpsecdict Dump Security Dictionary

dmpsecdict [-aV] [-u user] dataarea|dataID [file]

Dump a security dictionary. You can then view file, field, and record securityconditions in a dump format.

Program Option Descriptiona Dump the application security dictionary only.


u Dump conditions on a product line for user.

Field Descriptiondataarea |dataID

The data area or data ID whose security dictionaryyou want to dump information from.

file Dump detailed conditions for this file only.


dmptitledmptitle Dump Titles

dmptitle [-l language [-t]] productline systemcodedumpfiledmptitle -m [-l language [-t]] productline dumpfile

Create an ASCII text file containing all titles.

Program Option Descriptionl language Dump titles in the specified language.

t Dump non-translated titles in the specified language.

m Dump titles for menus and menu options in aproduct line.

Field Descriptionproductline Product line to dump titles for.

systemcode System code to dump titles for.

dumpfile File to store the titles in.




dmpunivengdmpuniveng Dump English Language Records

dmpuniveng dumpfile

Dump Lawson Environment English language records to a dump file. Use thisutility to move English language records from one computer to another.


dmpunivlibdmpunivlib Dump Lawson Environment Libraries

dmpunivlib dumpfile

Dump Lawson Environment libraries to a dump file.


dmpunivmendmpunivmen Dump Lawson Environment Menus

dmpunivmen dumpfile [-a menuID...] [-s menuID...]

Dump Lawson Environment menus to a dump file.

Program Option Descriptiona Dump a menu ID and all menus used by the menu ID.

s Dump a single menu.



dmpunivtkndmpunivtkn Dump Environment Form IDs

dmpunivtkn -u dumpfile

Enables you to dump the Environment and user-defined form IDs to a file forloading with the Load Environment Tokens utility (ldunivtkns). Generally, youshould use the -u option. If you are copying form IDs to another Environment,that Environment should already contain all of the delivered Environmentform IDs.

Program Option Descriptionu Dump user-defined form IDs only.

dumpfile Name of the file that the user-defined form ID informationis dumped to.

dmpunvhlpdmpunvhlp Dump Lawson Environment Help Text

dmpunvhlp dumpfile [formID]

Dump Lawson Environment help text to a flat file.

dmpunvmsgdmpunvmsg Dump Lawson Environment Messages

dmpunvmsg [-l language] dumpfile

Create an ASCII text file containing all Lawson Environment messages. Formore information, see Lawson Administration: Translation.

Program Option Descriptionl language Dump messages in the specified language.

Field Descriptiondumpfile File to store the messages in.

dmpunvphrdmpunvphr Dump Lawson Environment Phrases

dmpunvphr [-l language] dumpfile

Create an ASCII text file containing all Lawson Environment phrases.


Program Option Descriptionl language Dump phrases in the specified language.

Field Descriptiondumpfile File to store the phrases in.



docnamedocname Define Document Names

Define descriptive names for file, element, field, and form field names, makingthem easy to understand.1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type docname and click

the OK button or press Enter.3. On the Document Names Definition form, type or select the product line

you want to define descriptive names for.4. Press Enter or Define (F6).

Choose To

File Name Define descriptive names for database files.

Element Name Define descriptive names for database elements.

Field Name Define descriptive names for database fields.

Form Field Define descriptive names for form fields.

5. Press Enter twice to save the changes.

STEPS To define file names1. From the Document Names Definition form, press Define (F6) and

choose File Name.

Field Description

Document FileName

Descriptive file name that you want to print in yourapplication documents.

Short Name Short version of the descriptive file name.

This version of the file name prints when youroutput columns are not long enough to print the fulldocument file name.


2. Press Enter twice to save the changes.

STEPS To define element names1. From the Document Names Definition form, press Define (F6) and

choose Element Name.

Field Description

DocumentElement Name

Descriptive element name that you want to print inyour application documents.

Short Name Short version of the descriptive element name.

This version of the element name prints whenoutput columns are not long enough to print the fulldocument element name.

2. Press Enter twice.

STEPS To define field names1. From the Document Names Definition form, press Define (F6) and

choose Field Name.

Field Description

File Name File you want to define descriptive field names for.

Document FieldName

Descriptive field name that you want to print in yourapplication documents.

Short Name Short version of the descriptive field name.

This version of the field name prints when youroutput columns are not long enough to print the fulldocument field name.


STEPS To define form field names1. From the Document Names Definition form, press Define (F6) and

choose Form Field.

Field Description

System Code System code you want to type descriptive form fieldnames for.

Form ID Form ID you want to type descriptive form fieldnames for.

DocumentName

Descriptive form field name that you want to print inyour application documents.



editdaeditda Edit Data Area

editda

The Edit Data Area utility (editda) is a command line tool for managing someaspects of data areas without using the dbdef utility. This includes creatingnew data areas and data IDs and performing routine metadata changes fordata areas in a product line.

Any customer who wants to enable varchars for a table must use editda.All other features can be performed using the dbdef utility, and not allfunctionality of dbdef can be duplicated with editda.

You can use the following commands.

To do this Use this command

Print version information. editda -V

Change (or create) data areas asspecified in the file.

editda -c[lav] productlinedir-file

List data areas as specified in thefile.

editda -l[av] productlinedir-file

List an existing data area. editda -l[av] dataarea

Delete an existing data area. editda -d[Y] dataarea

The program options for the above commands are described below.

Program Option DescriptionV Print version information.

c Change/create data area(s) in dir-file to the product line.

l List data area changes.

d Delete the data area.

a Show all files and system codes in output.

v Show actual value for defaults in output.

productline The product line target for the directives in file.

Y When deleting, the utility asks the user, “Do you wantto delete?” The user may respond manually Y (Yes,delete) or N (No, don’t delete).

The Y option automates the manual prompt step.

dir-file contains a number of directives, each line having one of the followingformats.

For more information, see the Data Access manual for your database.

expsysdbexpsysdb Export System Data


expsysdb [-d|o|p|s] -E dataarea exportfilename[systemcode...]

Create a dump file for system data. expsysdb also dumps any relatedattachment files. You can choose to import just one or a few files, but if youdo, you must know your database well so that you preserve relational integrity.

Program Option Descriptionp Use Program files (default). The program file records

are delivered via the running of the Environmentpost-installation program.

o Use Owned By Files. Owned By files are files defined inthe database under a given product line.

s Use System files. System files include all files used bythe programs in an application system, as well as allfiles that are directly related to those files.

d System delivery files include all files you select fordelivery with a system. Use the System Files Definitionform to define these files. This is the preferred wayto create an export file. For more information, see"sysdelfile" on page 111.

E Exclude IsView objects.


or1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type expsysdb and click

the OK button and press Enter.3. Type or select the following data.

Field Description

ProgramOptions

See program options above.

Product Line Product line whose system data you want to export.

Export FileName

Flat file to load the system data to.

System Code(s) System codes whose data you want to export. Leaveblank to export data from the entire product line.


4. Press Enter.




fldrptfldrpt Field Usage Report

fldrpt [-f|e] productline [filename|fieldname]

The fldrpt utility lists the usage of fields in the specified file or for thespecified field.

fldrpt has the following program options:

Program Option Descriptionf The file containing the fields whose usage you want to

list.

e The field whose usage you want to list


or1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type fldrpt and click the

OK button or press Enter.3. On the Field Report form, type or select the following data.

Field Description

ProgramOptions

See above.

Product Line Product line for the fields.

File/ElementName

File or element name the fields reside under.


4. Press Enter.

gendbloadgendbload Load Database from Flat File

gendbload [-anr7] dataarea|dataID filename flatfilenameoverridedaraarea/dataID

Load a flat file into a database file, overriding the data area/data ID, andloading it into a data area/data ID with a different name.

IMPORTANT If the data area or data ID you dumped from is the same as thedata area or data ID you are loading to, do not use gendbload; use dbloadinstead.

Program Option Descriptiona Overwrite all duplicate records. Replaces

existing database records with duplicate recordsin the flat file. If the flat file has multiple


Program Option Descriptionoccurrences of a record, the last occurrence isstored in the database.

n Do not overwrite all duplicate records. Does notreplace existing database records with duplicaterecords from the flat file. It ignores the duplicaterecords in the flat file.

r Report on duplicate records. Prints duplicaterecords between the flat file and the database. Itdoes not replace the existing database records.

7 Flat file is from a Lawson 7.x product line onIBM i.

dataarea|dataID Data area or data ID dictionary you are loadingthe flat file to.

filename File you want to load.

flatfilename Flat file to load database files from.

overrideproductline Product line you want to load to.


For more information about transferring or copying, see LawsonAdministration: Server Setup and Maintenance.

grpdefgrpdef Distribution Group Definition

Define a set of users under a group name. For more information, see LawsonAdministration: Jobs and Reports.

To access the Distribution Group Definition utility:1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type grpdef and click the


hlpgenhlpgen Load Help File

hlpgen [-yn] productline systemcode helpfile

Load a help file for a system.


ibmduibmdu IBM DB2 Disk Usage

ibmdu [csw] [nx]bx [-u DBloginname] [-p password]dataarea [tablespace ...](online mode)ibmdu o[sw] [nx]bx dataarea [tablespace ...](offline mode)

This utility provides an estimate (plus or minus ten percent) of the amount ofdisk space required for the table and index data in a given data area. Usedduring initial setup or when migrating from another database.

In online mode, the utility:• Checks the IBM DB2 database to determine how much space you have

available in your table space.• Reads the Lawson dictionary to find the initial and incremental record

counts for each table and index listed in the dictionary. From the recordcounts and row sizes, the utility estimates the actual physical sizerequired.

Program Option Descriptionc Show information about the existing table spaces.

(Online mode only.)

o Run in offline mode.

s Show table space summary.

w Show detailed warning messages for tables andindexes.

nx Use a record count of x.

bx Use a block size of x KB. This must be the last specifiedoption in the command line.

u DBloginname The database user as specified in the databaseconfiguration file.

p password The password for the database user.

ilenameilename 4GL and RPG ILE Database Name Browser

ilename

Look up the corresponding file and field names for 4GL versus RPG ILEsystems.1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type ilename and click the

OK button or press Enter.3. In the Product Line field, type the product line containing the files or fields

whose names you want to look up.4. Select a file.


a. In the Lookup field, type the name of the file (either the 4GL or theRPG ILE version) and press Enter.

The utility displays more information about the file, including the 4GLand RPG ILE names of the fields.

- or -a. Press Select (F4) to view a list of system codes.b. Select the system code containing the file whose information you

want to check.

The utility displays a list of the files belonging to the system code,with 4GL and RPG ILE names.

c. To see more information about a file, including the 4GL and RPG ILEnames of the fields, select the file and press Enter.

impexpimpexp Import an Export File

impexp [-a|n] [-frsV] dataarea|dataID [exportfilename]

Import an exported database file.

The exported file must include the following characteristics:• Each record must end with a carriage return character. You can use

cnvexp to insert these characters.• The first ten characters of each record in the export file are the name of

the file, in uppercase, that the record belongs to. (Because each recordhas the file name attached to it, a single export file can include recordsfrom different files.)

• Every data field must be represented in the same order as in the data file,and in full length, including leading zeros for numeric data and trailingspaces for alphanumeric data.

• Signed numeric data must also include the sign in the first characterposition following the last value digit.

ProgramOption

Description

a Overwrite duplicate records. Replaces existingdatabase records with duplicate records in the flatfile. If the flat file has multiple occurrences of arecord, the last occurrence is the record stored in thedatabase. Overrides the -r option.

n No overwrite of duplicate records. Does not replaceexisting database records with duplicate recordsfrom the flat file. It ignores the duplicate records inthe flat file. Overrides the -r option.

f Fast; do not check for matching records.

NOTE Option -r is required for SQL databases.


ProgramOption

Description

Does not replace existing database records withduplicate records in the flat file. Using this optionassumes the -n option and overrides the -r option.

r Record differences report. Prints duplicate recordsbetween the flat file and the database. It doesnot replace the existing database records with theduplicate flat file records. It does not load anyrecords.

s Set the return code if there are DB or Dup errors. Usethis option to stop a multistep job after the impexpstep if all new records were not added successfully.The job displays in the Waiting job queue with astatus of Needs Recovery. Codes returned are:

1. Database error

2. Duplicate record

3. Both database error and duplicate record error


Description of summary headers:• Processed: Records in export file.• Added: Records added.• Duplicate: Records that have the same keys as existing records.• Match: Duplicates that exactly match existing records.• Changed: Duplicates overwritten by export file.• Bad: Records not imported because of an error.


- or -1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type impexp and click the


Option Description

DataArea/DataID Data area or data ID to import an export file into.

exportfilename Export file name to load the data from.


IMPORTANT Date, time, user name, type, utility name, and key fieldactivities of this utility are logged in the $LAWDIR/system/secadmin.logfile.


importdbimportdb Import Comma-Delimited File

importdb [-a|n] [-brlftudcweV] dataarea|dataID filenamecomma-delimitedfile

Load a comma-delimited flat file into a database file.

The fields in the CSV file must be in the same order as in the databasedefinition unless you use the -f option. If the fields in the CSV file containany special characters, you should enclose the field’s value in quotes.

Program Option Descriptiona Overwrite all duplicate records. Replaces existing

database records with duplicate records in the flat file. Ifthe flat file has multiple occurrences of a record, the lastoccurrence is stored in the database.

n Do not overwrite duplicate records. Does not replaceexisting database records with the duplicate recordsfrom the flat file. It ignores the duplicate records in theflat file.

b Batch inserts based on INSERTBUFSIZE.

r Report on duplicate records. Prints duplicate recordsbetween the flat file and the database.

l Log duplicate records.

f File has field headers.

t Tabs treated as separator value; default is Space.

u Update records; valid with -f option only.

d Do not reformat dates. Files in database format.

c Correct records. Valid with the -u and -f options only.

Enforces strict data type casting. For example, the datatype alpha converts to uppercase, and a leading zero isadded to floating point fields (.12 ? 0.12). The defaultenforces strict data type casting.

w Generate data type casting warnings. Overwrites the-c option.

e Halt program on any data or database error.



- or -1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type importdb and click





NOTE If you access importdb through amenu or by transferring to it, use the -a or -noption. These options prevent requests for userresponses that cannot be handled in this mode.Run importdb from the command line if you donot want to use the -a or -n option.

Data Area/Data ID Data area or data ID to import acomma-separated-value file into.

File Name File you want to load. Leave blank to load theentire product line.

Comma-DelimitedFile

Comma-delimited file to load the database filesfrom.


4. Press Enter.

IMPORTANT Date, time, user name, type, utility name, and key field activitiesof this utility are logged in the $LAWDIR/system/secadmin.log file.

integVerify Integrity ofDatabase

integ [-r] dataarea|dataid [filename]

integ checks the integrity of a data area, data ID, or a specified file.

Program Option Descriptionr Allows you to resume checking from a specified

file. If you do not use this option, or specify anyfile names, integ verifies all files in the data areaor data ID.

V Displays the version.

jbsubmitjbsubmit Job Submission

jbsubmit

Submit multiple jobs. For more information, see the section on submittingmultiple jobs in Lawson Administration: Jobs and Reports.


- or -



2. In the Form ID field on the Form Transfer form, type jbsubmit and clickthe OK button or press Enter.

jobdefjobdef Job Definition

Define a multiple-step job. For more information, see Lawson Administration:Jobs and Reports.

To access the Job Definition utility


2. In the Form ID field on the Form Transfer form, type jobdef and click theOK button or press Enter.

jobdumpjobdump Job Dump

jobdump [-dls] [-f inFileName] [-o objName [-v fieldNamevalue]*]*[-m type srcVal dstVal]* [outFileName]

(asterisks indicate options that may appear more than once)

Dump job-related information from the GEN database of one LawsonEnvironment to enable it to be loaded into another using jobload.

IMPORTANT You must specify the order you want data in for the dumpfile.Specify first DstGrp, second Job, and finally RecurJob to ensure the properexecution of jobload.

Program Option Descriptiond Output dump file format. Without the -d option, the

default is a -s summary list.

l Replace $LAWDIR with “$LAWDIR” in output. It isequivalent to -m LawDir $LAWDIR “$LAWDIR”.

f Dump information from dump file inFileName. Thedefault without this option is to dump all job informationfrom the database.

o Output objects of type objName, where object is a job orrecurring job. The default, without the option, dumps all(that is, -o Job dumps only jobs).

To limit selection:

jobdump -o job -v jobname xyz


Program Option Descriptions Output summary format.

v Output only objects with fieldName=value, for example,-o Job -v JobName MY JOB

Valid object types are DistGrp, Job, and RecurJob.

Valid field names for Job and RecurJob are UserNameand JobName.

m Replaces information where it appears in record fields.type = LawDir, UserName, ProductLine, Printer

For example: -m LawDir /test/apps//main/apps/

? Print usage and syntax.


- or -1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type jobdump and click



jobinqjobinq Job Inquiry

Inquire on a job. For more information, see Lawson Administration: Jobsand Reports.

To access the Job Inquiry utility1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type jobinq and click the


jobintegjobinteg Job Integrity

jobinteg [-dptvU] [increment]

Check and repair job and job step records.

Program Option Descriptiond Delete bad records.

p Validate parameters.


Program Option Descriptiont Terse; print totals only.

v Verbose; print bad records.

U Print usage and syntax.

increment The counting increment, for example, count byhundreds.

jobloadjobload Job Load

jobload [-clw] [-o objName [-v fieldName value]*]* [-mtype srcVal dstVal]* inFileName

(asterisks indicate options that may appear more than once)

Load into a destination Lawson Environment a job file created with jobdumpfrom a source Lawson Environment.

Program Option Descriptionc Commit to database. The default is a list only.

l Expand “$LAWDIR” before committing. It is equivalentto -m LawDir $LAWDIR “$LAWDIR”.

w Skip object validation.

o Load objects of type objName, where object is a jobor recurring job. The default without the option loads all.

v Load only objects with fieldName=value Forexample: -0 Job -v JobName MYJOB

m Replaces information where it appears in recordfields. type = LawDir , UserName, ProductLine,Printer. For example: -m LawDir/test/apps//main/apps/



- or -1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type jobload and click the




jobprmrptjobprmrpt Job Parameter Report

Print a report of the job parameters by data area or data ID, user, form, orjob name.

To access the Job Parameter utility1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type jobprmrpt and click


jobrptjobrpt Job Listing

jobrpt

Run a job listing. For more information, see Lawson Administration: Jobsand Reports.

To access the Job Listing utility1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type jobrpt and click the


jobstatusjobstatus Job Status Utility

jobstatus [-U] jobnumber

Use this utility to monitor jobs if you know the job number.

If you submit a job with the jqsubmit utility and the -n option, the utility willprint the job number.

You can also find the job number by selecting a job in the Lawson InterfaceDesktop Job Scheduler Waiting, Completed, or Active Jobs form, andpressing Drill Around (F5).


jobnumber The number of the job whose status you want to check.


jqdefjqdef Job Queue Definition

jqdef

Define up to 100 job queues for running batch jobs. For more information, seeLawson Administration: Jobs and Reports.

To access the Job Queue Definition utility1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type jqdef and click the


jqdfltjqdflt Job Queue Defaults

jqdflt

Assign default job queues to Lawson applications and programs. For moreinformation, see Lawson Administration: Jobs and Reports.

To access the Job Queue Defaults utility1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type jqdflt and click the


jqrptjqrpt Job Queue Listing

jqrpt

Retrieve the list of job queues defined on the Job Queue Definition form, theJob Queue Defaults form, or both. For more information, see the LawsonAdministration: Jobs and Reports.

To access the Job Queue Listing utility1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type jqrpt and click the



jqstatusjqstatus Job Queue Status

jqstatus [-Uhawrc] [JobNumber]

Use jqstatus to check the status of jobs in the job queue.


h Print header information.

a Print all active jobs.

w Print waiting jobs.

r Print needs recovery jobs.

c Print completed jobs.

JobNumber The job number of the specific job you want to check.

jqsubmitjqsubmit Submit Batch Job

jqsubmit [-Un] [-jjobqueue] [-ddate] [-ttime] usernamejobname

Submit a batch job. For more information, see Lawson Administration: Jobsand Reports.


n Print and return the job number. You can then use thefollowing command to check the status of the job.

jobstatus jobnumber

j jobqueue The job queue you want the job to run for.

d date The date you want the job to run, in mmddyy format.

t time The time you want the job to run, in hhmm format.

jsjs Batch Job Control

Display the Batch Job Control menu, for managing batch jobs. For moreinformation, see Lawson Administration: Jobs and Reports.

To access the Batch Job Control menu1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type js and click the OK

button or press Enter.


kndefkndef Key Number Definition

Define key numbers for a product line. For more information, see Doc forDevelopers: Application Development Workbench Standards.

To access the Key Number Definition utility1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type kndef and click the


laenvlaenv Lawson Environment Utilities Menu

Access the Lawson Environment Utilities main menu. For more information,see Lawson Administration: Server Setup and Maintenance.

To access the Lawson Environment Utilities main menu1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type laenv and click the


langdeflangdef Language Definition

Define languages and dialects. For more information, see LawsonAdministration: Translation.

To access the Language Definition utility1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type langdef and click the


laservipclaservipc Lawson Server, Process ID, Run Status and IPC Key

laservipc [-p] [-U] servername [servername...]

The laservipc utility returns the process ID (PID), run status, andInter-Process Communication (IPC) key for the lajs, ladb, and latm servers.The laservipc utility is useful when running multiple Lawson Environments todetermine which one a server process belongs to.

Program Option Descriptionp Print process ID only for servers.



Field Descriptionservername The name of the server you want to view information

about. You can view information about ladb, latm,and lajs.

lashowlashow Display File

View the output from a utility. To use lashow, type 2>&1 | lashow in the I/OOptions field for a utility. You cannot use lashow directly from a command line.

laualaua Lawson User Security

Display the Lawson User Security utility. For more information, see LawsonAdministration: LAUA Security.

Before you start You must be a Lawson security officer to access theLawson User Security utility (laua).

To access the Lawson User Security utility:1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type laua and click the


lawcmplawcmp Compile Lawson

lawcmp [-lDm] productline systemcode programcode/module

Compile a Lawson RPG program or module.

Program Option Descriptionl Produce compile listing.

This is stored as an .lst file in the IFS at$LAWDIR/productline/rpg/SYSCODERPGSRC/PROGRAMCODE.lst for programs and at $LAWDIR/productline/rpg/SYSCODEMODSRC/LIBNAME.lst formodules.

D Compile program for use with debugger.

m Compile program and its modules.


ldappclmphrldappclmphr Load Application Column Phrases

ldappclmphr dumpfile language

Load application column phrases from an ASCII text file containing translatedcolumn phrases for a product line that were created using the dmpappclmphrutility.



ldappmsgldappmsg Load Application Messages

ldappmsg [-xd | -xe | -xb] productline language dumpfile

Load application messages from an ASCII text file, containing translatedmessages for a product line. For more information, see LawsonAdministration: Translation.

Program Option Descriptionxd Load only messages that are marked for translation in

the dump file. If a message is not marked for translation,do not store the message. Instead, write it to the log file(ldappmsg.err in the current directory).

xe Load only messages that are marked for translation andexist in the base English language. Ignore the dumpfile flag. If a message is not marked for translation, donot store the message. Instead, write it to the log file(ldappmsg.err in the current directory).

xb Load only messages that are marked for Translation inboth the dump file and the base English language. If amessage is not marked for translation, do not store themessage. Instead, write it to the log file (ldappmsg.errin the current directory).

Parameter Descriptionproductline Product line to load application messages for.

language Language the messages have been translated into.

dumpfile File containing the translated messages.


ldappphrldappphr Load Application Phrases

ldappphr dumpfile language

Load application phrases from an ASCII text file containing translated phrasesfor a product line. The ldappphr utility loads phrases created with thedmpapphr utility. ldapphr uses the comment line produced by the dmpapphrutility to check the size of the translated phrase against the maximum sizestored into the comment line. If the translated phrase is greater than themaximum size indicated or if there are any other errors, ldappphr puts theoffending item, including all the lines that are attendant upon it, into error fileldappphr.err. This file may then be edited, renamed, and reloaded using theldappphr utility. However, this functionality is not available if a dump file wascreated by a 7.2.x or earlier version of the ldappphr utility.



ldappvallstldappvallst Load Application Value Lists

ldappvallst dumpfile language productline

Load application value list translations from an ASCII text file containingtranslated value lists for a product line. The ldappvallst utility loads valuelist translations created with the dmpappvallst utility. ldappvallst uses thecomment line produced by the dmpappvallst utility to check the size of thetranslated value lists against the maximum size stored into the commentline. If the translated value list is greater than the maximum size indicated orif there are any other errors, ldappvallst puts the offending item, includingall the lines that are attendant upon it, into error file ldappvallst.err. This filemay then be edited, renamed, and reloaded using the ldappvallst utility.




lddoctxtlddoctxt Load Help Text

lddoctxt [-o] productline language dumpfile

Load translated help text from an ASCII text file created by dmpfldtxt,dmpscrtxt, or dmpdftxt. For more information, see Lawson Administration:Translation.

Program Option Descriptiono Overwrite the current text.


ldhlptxtldhlptxt Load Lawson Environment Help Text

ldhlptxt textfile

Load the Lawson Environment help text.

ldlangldlang Load Language

ldlang [-l language] [-aodr] dumpfile[overrideproductline]

Load language translation records from a dump file created by dmplang.If the language in the language parameter does not exist, ldlang createsit and loads records with that language name into the GEN database. Ifthe language in the language parameter does exist, then you may appendrecords for that language with the -a option or overwrite records for thatlanguage with the -o option.


Program Option Descriptionl Load records into this language.

a Add new records only.

o Overwrite existing records.

d Report duplicate records (no update).

r Report on the records to load.



ldprodmenusldprodmenus Load Menus

ldprodmenus dumpfile [overrideproductline]

Load menus from a dump file.


ldtitleldtitle Load Titles

ldtitle productline language dumpfile

Load Lawson Environment titles from an ASCII text file containing translatedtitles.



ldunivenglduniveng Load Lawson Environment Records

lduniveng dumpfile

Load Lawson Environment English language records from a dump file.


ldunivlibsldunivlibs Load Lawson Environment Libraries

ldunivlibs dumpfile

Load Lawson Environment libraries from a dump file.



ldunivmenusldunivmenus Load Lawson Environment Menus

ldunivmenus dumpfile

Load Lawson Environment menus from a dump file.


ldunivtknsldunivtkns Load Lawson Environment Form IDs

ldunivtkns dumpfile

Load Lawson Environment form IDs from a dump file.


ldunvhlpldunvhlp Load Lawson Environment Help Text

ldunvhlp dumpfile

Load Lawson Environment help text from a flat file.

ldunvmsgldunvmsg Load Lawson Environment Messages

ldunvmsg dumpfile language

Load Lawson Environment messages from an ASCII text file containingtranslated messages.




ldunvphrldunvphr Load Lawson Environment Phrases

ldunvphr dumpfile language

Load Lawson Environment phrases from an ASCII text file containingtranslated phrases.



libdeflibdef Library Definition

libdef

Define and maintain procedure libraries for Application Program Interfaces(API) routines. For more information, see Doc for Developers: ApplicationDevelopment Workbench Standards.

To access the Library Definition utility:1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type libdef and click the


licstalicsta License Status

licsta [-r] | [-f] [licensefile] [-U] [-V]

Display your license status. Your license file is stored in the IFS in the/EnvironmentDirectory/law/system/license directory.

Program Option Descriptionr Print Status From Running System.

Displays the license status from ladb.

f Print Status From License File.

Displays the status from the license file in active use.

U Displays the usage or syntax.

V Displays the version number of the utility.


- or -1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).


2. In the Form ID field on the Form Transfer form, type licsta and click theOK button or press Enter.

3. In the License Status window, type the following data.

Field Description

ProgramOptions

Where to retrieve the license status from. Use eitherof the program options above.

License File Optional. The name of the license file you want todisplay.

If you use the -r option in the Program Options field,you must leave this field blank.

If you use the -f option in the ProgramOptions field, leaving this field blank displaysthe license status from the license file:/EnvironmentDirectory/law/system/license


To display to the screen, type 2>&1 | lashow.

4. Press Enter to display the license status.


loadusersloadusers Load Users

loadusers -f xmlFilename -p defaultProductlineloadusers -g username

Use this utility to mass load users from a file, or to designate a defaultoperating system user. The Single Sign-On authentication system will use theEnvironment/OS identity for the default operating system user for users whodo not have an Environment/OS identity.

Program Options Descriptionf xmlFilename Loads users from the specified XML file.

For more information on mass loading usersfrom a file, see Lawson Administration:Resources and Security.

p defaultProductline The product line to use if none is specified inthe XML file.

g username The IBM i user profile designated asthe default user profile. The SingleSign-On authentication system will usethe Environment/OS identity for the defaultuser profile for users who do not have anEnvironment/OS identity.


loanloan Loan Amortization

Calculate payments based on principal amount and interest rate. You canthen run an amortization report to view the resulting payments over time.

To access the Load Amortization utility:1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type loan and click the


locdeflocdef Locale Definition

Define form data display attributes for a locale, and link a language or dialectto a locale. For more information, see Lawson Administration: Translation.

To access the Locale Definition utility:1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type locdef and click the


lsconfiglsconfig Lawson Security Configuration

lsconfig -uartdl [-c password ON|OFF] [instanceName]

Use this utility to review and modify parameters for the Lawson Securitysystem. You can also use the Lawson Security Administrator to review theparameters and to modify many of them.

Program Option Descriptiona Add or modify security parameters.

l List security parameters for viewing.

r Assign a user to a role.

t Activate tracing for a specific user. Only turn tracing onfor a use if instructed to do so by Lawson. Generally,you can gain enough information for troubleshootingthrough other means, such as the auditing and loggingset up through the Lawson Security Administrator. Ifyou use the -t option, you will be prompted for a userafter you run the command. To indicate a user, enter aResource Management ID.

If you turn on tracing, the information is stored in$LAWDIR/system/Sec_username_Nbr_Nbr.log.


c passwordON|OFF

Turn security off or off. You must specify the SingleSign-On Configuration utility (ssoconfig) password touse the -c option.

instanceName The data source that the specified security changes willbe applied to.

u View usage and syntax for the utility.

Property Description

AUDIT Set to ON or OFF to turn auditing on or off.If auditing is on, it will track the items listedfor the AUDIT_TYPES parameter.

AUDIT_DATASRC The location where audit data is stored.If you select DB, the data is stored in theLSAUDIT file in the LOGAN data area. If youselect LDAP, the data is stored in the LDAPrepository. The default is DB. Be aware thatif you select LDAP, large amounts of datamay be placed in the LDAP repository.

AUDIT_TYPES The type of activities that will be monitored ifyou turn on auditing: ADD = adding securitydata for profiles, security classes, and rules;CHG = changing security data for profiles,security classes, and rules; DEL = deletingsecurity data for profiles, security classes,and rules; DEN = denial of access, SSO =authentication attempt.

CACHING_INTERVAL The time in seconds that the system waits tocheck for updated security information.

CHECKING_OFF_RULE The access rule to use when LawsonSecurity is turned off. If you set this toNO_ACCESS for the entire system, noteven security administrators will haveaccess to Lawson application, LawsonEnvironment programs, and the LawsonSecurity Administrator.

DEDICATED_HANDLERS Set to TRUE or FALSE. If TRUE, thenfor each security request, a separateevent handler is created that exists untilthe system is finished with the request.If FALSE, then the event handler for arequest goes into a pool after finishingwith each request, and is available forother requests. If you set this to FALSE,use the MAX_HANDLER_IDLETIME,MAX_CONN_BLOCK_TIME,MAX_HANDLER_COUNT, andMIN_HANDLER_COUNT parametersto control the event handler pool. TRUE


Property Descriptiongenerally results in faster performance butmore intensive resource use.

DEFAULT_USER Not used.

INSTALLEDTYPES Set to RM, ERP.

LAWDIR The path for the directory on the applicationserver for the Lawson applications,configuration files, and spooled print output.

LOCAL_EXECUTION Not used.

LOGGING_LEVEL The level of detail for the information that isincluded in the security logging for LawsonSecurity. The levels correspond as followsto the settings on the Auditing + Logging tabin the Lawson Security Administrator.• SEVERE and WARNING equal Critical.• INFO equals General.• FINER equals All.• FINEST equals Debug.

LOGGING_USERS The users that you have selected to audit.

LOG_DIR The directory where the log files are located.

MAX_CONN_BLOCK_TIME If DEDICATED_HANDLERS is set to FALSE,this is the amount of time in millisecondsuntil the pool of handlers becomes available.

MAX_HANDLER_COUNT If DEDICATED_HANDLERS is set toFALSE, this is the maximum number ofhandlers in the pool.

MAX_HANDLER_IDLETIME If DEDICATED_HANDLERS is set toFALSE, this is the time in milliseconds ahandler should stay in the pool until thehandler is stopped.

MIN_HANDLER_COUNT If DEDICATED_HANDLERS is set toFALSE, this the minimum number ofhandlers in the pool.

MODIFIEDON The most recent date and time securityinformaiton was modified.

PRINTNETMSG Set to TRUE to cause more verbose loggingoutput. If set to TRUE, the maximumamount of information is sent to thels<instancename>.log. Administratorsmust monitor the size of the log file if thisparameter is set to TRUE.

RM_DS_NAME Not used.

RM_DS_TYPE Must be LARM. It refers to the ResourceManagement APIs used to access theResource Management data source.


Property Description

RM_MODIFIED_ON The date and time Resource Managementdata was modified. The date and time are inthe format: yyyymmddhhmmss.

ROOTDN The LDAP node that is the root node forLawson data o=lwsnrmmetaroot

SEC_DS_NAME Set to GEN.

SEC_DS_TYPE Set to LDAP to indicate that security data isstored in LDAP.

SECURITY_CHECKING Whether security checking through LawsonSecurity is turned on or off for the Lawsonsystem.

SERVER_ADDR The address of the server (machine) thathosts the Lawson Security server.

SERVER_INSTANCE Set by installation to “default.”

SERVER_PORT The port used by the Lawson Securityserver.

TRACE Indicates whether tracing has been turnedon or off.

TRACE_DIR The directory where trace files are located.

USERMODIFIED The date and time that the last change wasmade to the security sytem. The date andtime are in the format: yyyymmddhhmmss.

USE_SECURESOCKET If TRUE, SSL is used for transport of thepassword from the Portal to LDAP. If FALSE,the password is sent as plain text usingTCPIP.

lsdumplsdump Lawson Security Dump utility

lsdump [-f filename] PROFILE [profileid][-addRoleMapping]lsdump [-f filename] SECCLASS profileid [secclassname1,secclassname2,...] [-addRoleMapping]lsdump [-f filename] ROLE rolename [-p profileid] [-ssecclassname1,secclassname2,...]lsdump [-f filename] ELMGRP profileid [elmgrpname1,elmgrpname2, ...]

Use this utility to dump Lawson Security information to standard out or to a file.If you dump the information into a file, you can use the lsload utility to load thatfile into another security profile. That profile can exist within the same LawsonEnvironment or a different Lawson Environment if that Lawson Environmenthas the same version of the Lawson Environment and applications as theLawson Environment you dump the Lawson Security information from.



f filename Use the -f option along with the name of a fileto dump the Lawson Security information to afile rather than to standard out.

p profileid When you are using lsdump to dump LawsonSecurity information related to a specific role,use the -p option along with a profile ID inorder to dump the information for only thespecified profile. If you do not use the -p option,information is dumped for all profiles.

s secclassname When you are using lsdump to dump LawsonSecurity information related to a specific role,use the -s option along with the names ofone or more security classes in order to dumpthe information for only the specified securityclasses. If you do not use the -s option,information is dumped for all security classes.

PROFILE Use PROFILE if you want to dump the securityinformation for all profiles or for a specifiedprofile. This information includes profiledefinition, security class, and rule information.

SECCLASS Use SECCLASS if you want to dump the securityclass and role information that belongs to aspecified profile. You can also specify one ormore security classes to dump information for.No profile definition information is included ifyou use SECCLASS.

-addRoleMapping When you use this option with PROFILE orSECCLASS, lsdump will not only dump the entireprofile or security class, but will also dump rolemappings and the users assigned to the roles.

ROLE Use ROLE if you want to dump the securityclass and rule information for a specified role.You can also specify one or more securityclasses to dump information for through the-s option, and you can optionally limit thesecurity information to a single profile. No profiledefinition information is included if you useROLE.

ELMGRP Use ELMGRP if you want to dump the securityclass and rule information for element groups.You can dump the information for all elementgroups or you can specify individual elementgroups.

lsloadlsload Lawson Security Load utility


lsload PROFILE filename [-p newProfileId] [-ddefinitionProductLine] [-a activeDataSource][-addRoleMapping]lsload SECCLASS filename [-p profileId] [-s newClass][-addRoleMapping]lsload ROLE filename [-r roleId] [-p profileIdlsload ELMGRP filename [-p profileId] [-e newElmgrp]

Use this utility to load Lawson Security information from a file created bylsdump. Using lsload and lsdump together enables you to transfer securityinformation (profile definitions, security classes, rules, and so on) from oneprofile to another. When you move security information from one profile toanother, the two profiles must be defined against Lawson objects (such as aproduct line) of the same release and type.

Program Option DescriptionPROFILE Use PROFILE if you want to load the security

informaton for one or more profiles. Youmust load this information from a file createdthrough lsdump with the PROFILE option.If you do not specify a profile ID, this utilitywill create a profile with the same ID as theprofile in the dump file or, if a profile of thatID already exists, if will overwrite the existingprofile. If you specify a profile ID, this utilitywill create a new profile if it does not existor, if a profile of that ID already exists, it willoverwrite the existing profile.

SECCLASS Use SECCLASS if you want to load thesecurity information for one or more securityclasses. You must load this informationfrom a file created through lsdump with theSECCLASS option. If you specify a profile,the profile must already exist. If you do notspecify a profile, a profile with the same IDas the profile ID for the security classes inthe dump file must already exist.

ROLE Use ROLE if you want to load the securityclass and rule information for one or moreroles. You must load this information from afile created through lsdump with the ROLEoption. If you specify a profile, the profilemust already exist. If you do not specifya profile, a profile with the same ID as theprofile ID for the role’s security classes inthe dump file must already exist

filename The name of the file containing the securityinformation to load.


Program Option Descriptionp newProfileId |profileId

Use the -p option along with a profile IDin order to load the information for onlythe specified profile. If you are using thePROFILE option, you can use the profile IDyou specifiy with the -p option to create anew profile. If you do not use the -p option,the utility loads in the profile informationbased on the profile IDs in the dump file,creating or overwriting profile definitionsdepending on whether the profile IDs matchexisting ones or not.

If you are using lsload in the SECCLASS orROLE mode, the -p option allows you toload the security information into a specificprofile. If you specify a profile, the profilemust already exist. If you do not specifya profile, a profile with the same ID as theprofile ID for the security classes in thedump file must already exist.

ddefinitionProductLine

The -d option changes the definition productline for the Environment to which you areloading security information. (You can alsoset the definition product line through theSecurity Administrator).

a activeDataSource The -a option assigns the profile you areloading to the data source you specify. (Youcan also set the profile assignments for datasources through the Security Administrator)

-addRoleMapping This option allows you to load not only profileand security class information

This option can be used when a profile orsecurity class was dumped using the sameoption. This option will then create a newprofile, create new roles if they are notalready on the system, and create the roleassignments. Since the lsdump utility alsodumped the users assigned to the roles,using this option will also update the firstname, last name, and role attribute on anyuser that exists on the target system. Allusers that do no exist on the target systemare written to an xml file. This xml file isformatted so that you can add the usersthrough the loadusers utility.


Program Option Descriptions newClass The -s option along with a new security

class name allows you to create new securityclasses when you use lsload. If you areloading multiple security classes, the utilitywill prompt you for additional new names foreach security class past the first one.

o The -o option causes lsload to destroy allexisting data for a security class prior toloading when there is an existing securityclass of the same name as one you areloading.

r roleId Use the -r option along with a role ID inorder to load the security information for thesecurity classes associated only with thespecified role.

e [newElmgrp] Use the -e option to load element groupinformation. You can also specify a profile toload the element group information for andyou can supply a new name for the elementgroup.

lstinvklstinvk Print Compile Script For Programs Which Use 4GL INVOKE

lstinvk [-q] productline [ProgramCode] [>filename]

The lstinvk utility lists all programs affected by a change in a calledprogram. That is, it lists all invoked and invoking programs for a specifiedprogram. For more information, see Doc for Developers: ApplicationDevelopment Workbench Standards.

Program Option Descriptionq Submit the list of programs to the compile queue.

D Compile the listed programs for debug.

T Compile the listed programs for trace.

lstprodatchlstprodatch Attachment Report

lstprodatch [-U] [-C] dataarea|dataID

List all of the attachment-enabled files in a product line.

Program Option DescriptionU Print usage.

C Count attachment records.


Field Descriptiondataarea |dataID

The data area or data ID whose attachments you wantinformation about.

menurptmenurpt Menu Report

menurpt [-p productline] menuID...

Display a list of menus and their options. For more information, see LawsonAdministration: Server Setup and Maintenance.

msggenmsggen Load Program Messages

msggen productline messagefile

Load program messages from flat files.


- or -1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type msggen and click


msgmntmsgmnt Message Definition

Define messages used to process errors and information in online and batchprograms. You can define a message for a specific product line and program,or you can define a message that is global to the product line (independent ofthe program). For more information about programming and messages, seeDoc for Developers: Application Development Workbench Standards.

To access the Message Definition utility:1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type msgmnt and click


STEPS To define a message• On the Message Definition form, consider the following fields.


Field Description

Product Line The product line for which you want to definemessages.

Category The category (for example, program code or system)for which you want to define messages.

When you enter a category, the system displaysthe numbers (100 - 999) and their correspondingmessages for the selected product line or category.

If you leave this field blank, the system displays themessages that are global to the product line. Globalnumbers range from 1 to 99.

Number The message number.

Xlate Whether the message is flagged for translation. Thedefault is Yes. You use this flag in conjunction withthe Dump Application Messages (dmpappmsg) andLoad Application Messages (ldappmsg) utilitiesto control whether you dump or load tranlatablemessages.

Message Up to 60 characters of message text. To indicate avariable, use an integer inside curly brackets - forexample, {0}, {1}, and so on. You can use up to fivevariables, {0} to {4}.

IMPORTANT The 60-character limit applies to thelength of the message text plus the length of the textthe variables translate to.

Example:

The following example of message text (typed in the Message field) producesa message that inserts the employee number, employee name, companynumber, and company name.

Employee {0} {1} works at {2} [3} company.

msgrptmsgrpt Message Report

msgrpt [-n|t] [-p productline] language [translation]

Print language messages and translations. For more information, see LawsonAdministration: Translation.

Program Option Descriptionn Print messages without translations only.

t Print messages with translations only.



- or -1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type msgrpt and click the


pgftxtpgftxt Enter Technical Text

Update the text for the files (called program files) referenced by a specificprogram. This text is included in the printed documentation that is generatedwhen you select Print Technical Text from the User Desktop menu, ApplicationText submenu.1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type pgftxt and click the


Field Description

System Code System code you want to display program files for.

Form ID Form ID you want to display program files for.

The system displays the program files referenced bysystem code and form ID.

4. Select the program file you want to view or type text for, press Define(F6), and choose Text.

A text window appears. This window lets you type or view informationfor the files related to the system code and form ID you selected. Forcomplete information on text windows, see Getting Started with theLawson Inteface Desktop (LID).

5. Press Enter twice to save the text.

pgmdefpgmdef Program Definition

Create programs for a product line and system code. For more information,see Doc for Developers: Application Development Workbench Standards.

To access the Program Definition utility:1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type pgmdef and click the



pgmdef2pgmdef2 Query Definition

Create query programs defined for a product line and system code. For moreinformation, see Doc for Developers: Application Development WorkbenchStandards.

To access the Query Definition utility:1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type pgmdef2 and click


phraserptphraserpt Phrase Report

phraserpt [-n|t] baselanguage [translation]

Print language phrases and translations. For more information, see LawsonAdministration: Translation.

Program Option Descriptionn Print phrases without translations only.

t Print phrases with translations only.


- or -1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type phraserpt and click


phrcntphrcnt Phrase Count

phrcnt language

Count Lawson Environment and application phrases and uses.

prmdumpprmdump Job Parameter Dump utility

prmdump [-?] [-d AltDir] Outfile User Job

Use this utility to dump the parameters for jobs to an output file. You canmodify the values with a text editor and then load the new values with theprmload utility.


Program Option Description? Show usage and syntax.

d AltDir Does not apply to IBM i.

Outfile The output file you want to dump the existing parameterdefinitions to.

User The user who owns the job definition.

Job The job you are dumping the existing parameterdefinitions for.

prmloadprmload Job Parameter Update utility

prmload [-u?] InFileName

Use this utility to update the job step parameter values for jobs. Use this utilityin conjunction with the prmdump utility. The prmdump utility enables you todump the current set of parameter values for a job. You can then modify thosevalues and use the prmload utility to update the job’s parameter values.

Program Option Descriptionu Run the utility in update mode.

? Show usage and syntax.

InFileName The input file containing the updated parameters.

proddadiproddadi Product Line Data Area Data ID Report

proddadi dataarea|dataID

Report on a data area’s product line. For more information, see the Lawsondatabase access manual for your database.

prtdefprtdef Printer Definition

Define output destinations, including printers. For more information, seeLawson Administration: Jobs and Reports.

To access the Printer Definition utility:1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type prtdef and click the



qcompileqcompile Compile Program

qcompile [-lDm] productline systemcode programcode/module

Compile a Lawson RPG program using the compile queue. For moreinformation, see Doc for Developers: Application Development WorkbenchStandards.

Program Option Descriptionl Build the compile listing.


D Compile a program or a module for use with thedebugger.

m Compile a program and its modules.

qcontrolqcontrol Compile Queue Control

qcontrol [-d nbr] [-j machine,nbr] [-k nbr] [-s nbr,nbr]

Control the compile queue. The default machine name is local. Normally, twocompiles should be configured for each coprocessor, but this number can bereconfigured by the system administrator.

For more information, see Doc for Developers: Application DevelopmentWorkbench Standards.

Program Option Descriptiond nbr Delete the compile number.

j machine,nbr

The maximum number of compile jobs for the machine.

k nbr Kill the compile number.

s nbr,nbr Swap the first job number with the second job number.

S Restarts compile queue after a non-purging stop orfailure.


qstatusqstatus Compile Queue Status

qstatus

View the status of jobs on the compile queue. For more information, see Docfor Developers: Application Development Workbench.

queuequeue Start Lawson Compile Queue

queue

Start the Lawson Compile Queue Server. For more information, see LawsonAdministration: Server Setup and Maintenance.

recdefrecdef Recurring Job Definition

Define a recurring job. For more information, see Lawson Administration:Jobs and Reports.

To access the Recurring Job Definition utility:1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type recdef and click the


recrptrecrpt Recurring Job Listing

Run a recurring job listing. For more information, see Lawson Administration:Jobs and Reports.

To access the Recurring Job Listing utility:1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type recrpt and click the


rngdbdumprngdbdump Dump Database File Range

rngdbdump [-ctnd] [-i index] dataarea|dataID filename [-ffieldname...][-k rangekey...][-v fieldvalue...]

Dump a selection of records from one database file to standard output. Basedon the primary index of the file or an index you specify, you can extract all the


fields in a record, or any combination of fields. You can control the range ofrecords selected by specifying values for the various keys in the index or byspecifying a value or range of values for one field.

The default format of the extracted data is columns, separated by spaces.Data in this format can be routed to a printer or the screen and easily read.The extracted data can be formatted as a comma-separated-value (CSV) filefor use in another program, such as a spreadsheet. If the data is to be loadedinto another file, it can be formatted so that the Lawson dbload commandcan accept the extracted records. You can also choose whether to include thefield headers in the output.

IMPORTANT Unless you use the -d or -c option, the utility truncates fieldslarger than 80 columns.

Program Option Descriptionc Put the output in a comma-separated value format. You

can also use this option to dump files containing fieldslarger than 80 columns.

If you use this option, first set the text mode for the CSVfile by creating the file with the following command:

touch -C 819 directorypath/csvfilename

n Dump output without the field headers.

d Dump to flat file. Creates a file that the dbload utilitycan import. You can also use this option to dump filescontaining fields larger than 80 columns.

t Terse mode. Does not show record count. If you usethis option, specify one or more field names in thefieldname(s) field.

iindex Dumps the database using the index you specifyinstead of the primary index of the file (for example,-iGLMSET2).

ffieldname Dump the data only for the specified fields. If you usethis option, specify one or more field names in thefieldname(s) field.

krangekey Limit the output based on the values for the index keysof the file. This option dumps records only when thespecified keys are matched.

vfieldvalue Dumps data for a specified field.


- or -1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type rngdbdump and




Options See the above program, index, field, and rangeoptions.

Data Area/Data ID Data area or data ID containing the database fileyou want to dump.

File Name File you want to dump.

Field Name(s) Names of up to 250 fields (the limit on a filerecord) you want to dump data for.

Range Key(s) Values for each key in the index for the file youwant to dump data from.

Specify a value for up to 13 keys, each separatedby a space. If the value has spaces in it, enclosethat value in apostrophes or insert a hyphenwhere the space or spaces would be.

Field Value Option Dumps data for specified field.


4. Press Enter.

IMPORTANT Date, time, username, type, utility name and key fieldactivities of this utility are logged in the $LAWDIR/system/secadmin.logfile.

rpgcmprpgcmp Compile System

rpgcmp [-lobdn] productline [systemcode...]

Compile all RPG programs in a system code or product line. For moreinformation, see Doc for Developers: Application Development WorkbenchStandards.

Program Option Descriptionl Build compile listing.

o Compile online programs.

b Compile batch programs.

d Do not use the compile queue.

n Do not compile .sr and .or.


rpgshellrpgshell Build RPG Shell

rpgshell [-clmD] productline systemcode programcode

rpgshell -P[clmD] productline module

Use this utility to build the RPGLE program source from the componentsource files for a program or for a module, and optionally compile it.

Program Option Descriptionc Normal compile.

l Produce compile listing.


D Compile a program/module for use with debugger.

m Apply all the specified options to the modules aprogram or module calls as well as to the program ormodule itself. For example, specifying rpgshell -cmlawapp9 hr hr11 results in the compiling of HR11and any modules it calls.

P Specify a single module. (If you also provide the -moption, then the utility will build or compile the moduleand all modules it calls.)

rptgenrptgen Compile Report

rptgen [-t|c|r] [-snn] [-nVfvPGBNCR] [-l language]productline [systemcode [ProgramCode]]

Compile report definitions. For more information, see Doc for Developers:Application Development Workbench Standards.

Program Option Descriptiont Build .rd for COBOL.

c Build .rd for C. Used only at Lawson.

r Build .rd for RPG.

s nn Override default page size. Must be followed by atwo-digit specification for the page size (nn). Validvalues are 00 or 20 - 99.

n Set NOKEYBRK ON for all reports in .rpt.V Display the version number of this utility.

f Use the classic RptMap type (fixed size).


Program Option Descriptionv Use variable size RptMap type (US). This is the default.

P Build .prop file (no RptMap).

G Build .grp file (no RptMap).

B Build .prop and .grp files, and the RptMap.

N Build the RptMap only. Do not build .grp or .propfiles. This is the default. Any existing .grp or .propfiles are removed.

C Build the CSV specification files only. (Do not build theRptMap or the .grp or .prop files.)

R Do not build the CSV specification files with the RptMap.

l The language for the .prop files.


or1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type rptgen and click the


rulerptrulerpt Rule Report

rulerpt [-c] productline [filename]

List existing state/event rules for the specified database file.

Program Option Descriptionc Print condition.


or1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type rulerpt and click the

OK button or press Enter.3. On the Rule Report form, type or select the following data.

Field Description

ProgramOptions

See the above program options.

Product Line Product line for the rules.

File Name File name the rules reside under.


4. Press Enter.


IMPORTANT You can also run a rule report from the Rule Definition form.Press Detail (F5) and choose Rule Report. The system displays thereport on the form using the product line and file name for the file in theRule Definition form.

For more information, see Doc for Developers: Application DevelopmentWorkbench Standards.

scrgenscrgen Compile Form

scrgen [-s|c|r|F] [-xv] productline [systemcode[ProgramCode...]]

Compile the form definition file for the selected program or for all programsin a product line or system code. The compiler builds the files that the userinterfaces use to process the form, including the form’s SD file, TranMapfile, help file, and .xml file. For more information, see Doc for Developers:Application Development Workbench Standards.

Program Option Descriptions Build COBOL SD.

c Build C-type SD. Used only at Lawson.

r Do not build RPG type SD (default).

F Build RPG SD in the IFS.

x Create executable form IDs.

v Verbose.


or1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type scrgen and click the


secdumpsecdump Security Dump

secdump dataarea|dataID dumpfile [adminclass |securityclass]

WARNING You must rebuild the security dictionary after usingthis utility.

Used when copying security from one Lawson Environment or product line toanother. The default dumps both the administrator class and security classinformation.


IMPORTANT The secdump utility does not run an integrity check on theconditions or security classes it is dumping. It is advised to run utilities suchas secinteg to check the state of the conditions.

Field Description

DataArea/DataID

The data area or data ID whose security or administratorclasses you want to dump.

DumpFile File to store the security information in.

Program Options AdmClass - Dump administrator class and all itssecurity classes.

SecClass - Dump specified security class and all itssecurity classes.

Blank - Dump all administrator and security classes.


- or -1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type secdump and click



secintegsecinteg Security Database Integrity

secinteg [-fdeuvtVU]

Check the integrity of the Lawson Environment security database files.

Program Option Descriptionf Fix corrupt definitions. (Do not use with -d.) Definitions

created in pre-8.0.3 Environment releases weresometimes corrupt because the nTimesUsed field in theUSERCND table contained an incorrect value.

d Delete records. (Do not use with -f.) Use with -u todelete records with unused conditions. Use with -e todelete records with deprecated elements.

u Detect conditions usage only.

e Detect conditions with deprecated elements.Deprecated elements are those based on superelements and element groups. Super elements andelement groups were retired as of the 8.0.3 applicationrelease.


Program Option Descriptiont Terse; print totals only.

v Print a count of the corrupt definitions.

V Print additional information about each corrupt definition.


secloadsecload Security Load

secload [-ascldmov] dumpfile [overridedataarea|dataID]

WARNING You should run the Security Integrity utility (secinteg)after you run thhis utility. Also, you must rebuild the securitydictionary after using this utility.

Used when copying security from one data area/data ID to a file.

The default (no options) deletes the existing data area/data ID setup for anadministrator and/or security class and loads the new data area/ID securityfor the security class.

By default, secload loads to a data area/ID with the same name as thedumpfile data area/ID. If that data area/ID does not exist, an error messageis generated.

You can override the data area/ID named in the dumpfile file by naminganother existing data area/ID within the target file.

If there are conditions in the USERCND file, then a merge/add processoccurs. If no conditions are present, no changes occur to the USERCND,USERPROD, USERFILE, or USERFLD files.

secload loads the security data contained in a file with the following options.

Program Option Descriptiona Load administrator classes only.

s Load security classes only.

c Exclude conditions (USERCND file).

l List only, does not update files.

d Exclude data security (USERKEY file).

m Merge the security access settings from the secdumpfile into the security access settings for the dataarea/data ID where you are loading the file. It overridesany duplicate named records with the record from thedumpfile. It does not change any non-duplicate securitysettings. Any new security classes are added.

o Destroy all existing data for security classes prior toload.

v Verbose output.



- or -1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type secload and click the



setdbverssetdbvers Set Database Time Stamp in Data Dictionary

setdbvers productline versionfile

Update the time stamps in the data dictionary. See also blddbvers.

setnotusedsetnotused Set Not Used Flag for Relations

setnotused [-a] productline

Use this procedure to mark relations that are not being used so that blddbdictwill ignore them. The lawappinstall activate process runs setnotusedautomatically, but in other cases you may have table definitions loaded thathave relations to other Lawson tables that you do not have. If you do not runsetnotused, blddbdict will not run successfully. Instead, you will receive errormessages similar to the following: "Condition Field FIELD-NAME: ConditionCONDITION-NAME Not Found."

Program Option Descriptiona Run setnotused for all product lines.

setsflsetsfl Update SYSFILE

setsfl

Use this procedure to update the SYSFILE table in the GEN product line withtable and system code information.


skndefskndef System Key Number Definition

Define key numbers for a system. For more information about key numbers,see Doc for Developers: Application Development Workbench Standards.

To access the System Key Number Definition utility:1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type skndef and click the


sqldbcopysqldbcopy Copy database file between data areas using SQL code

sqldbcopy [-H] -P propertiesFile [-D directivesFile]

sqldbcopy executes SQL code that upgrades one Lawson database filefrom one data area to another.

Type the above at a Qshell command line.

Program Option Description-H Print detailed usage.

-P Input file name and path for setting properties.

-D Directives file defining which Lawson files ordata locations to include or exclude in the datacopy

Properties FileConsider the following options:

Attribute DescriptionSRCSCHEMA This attribute is the source schema.

It overrides the value set in the capfile when OVERRIDE is TRUE.

DSTSCHEMA This attribute is the destinationschema. It overrides the value setin the cap file when OVERRIDE isTRUE.

SRCDATAAREA This attribute is the source dataarea.

DSTDATAAREA This attribute is the destination dataarea.

DBTYPE This attribute is the database type:msf, msf2005, ora9, ora10, or ibm.

DATABASELINK This attribute is the database link.


Attribute DescriptionHOST host[:port] for the Oracle or

Microsoft SQL Server databaseserver.

LOGGINGDIRECTORY This attribute is the directory nameand path where message and logfiles are written to.

For each Lawson file that failed in thecopy, warnings and errors are loggedin a message file LawsonFile.msg.

For each run, results are logged insqldbcopy.log.timestamp.

DIRECTIVESFILE This attribute is the input file nameand path. This value is overriddenwhen the -D option is specified atthe command line.

FIELDDATFILE This attribute is the input file nameand path for initializing destinationfile fields.

DEGREEOFPARALLELISM This attribute refers to the degree ofparallelism.

RECREATETABLE This attribute is set to TRUE if youwant to drop and recreate the tablebefore the copy. The default valueis FALSE.

If the value is set to TRUE, indexesare created only at the end of thecopying process.

DONOTEXECUTE This attribute is for not executingin the database. This attribute canhave a value of either TRUE orFALSE.

OVERRIDE This attribute allows the valuesfor srcschema and dstschema tooverride the actual schema values inthe source and destination databaseconfiguration cap files. it can have avalue of either true or false.


Attribute Description7xiseries This attribute is used for indicating

whether the source is iseries 7x. Itcan have a value of either TRUE orFALSE.

TRACE This attribute prints SQL commandsto LOGGINGDIRECTORY/sqldbcopy.sql. This attributecan have a value of TRUE orFALSE. The default value is FALSE.

IMPORTANT Property values that include back slashes must be escapedwith a back slash. For example, $This/is/an/example should be$This//is//an//example.

Directives FileThis attribute is an input file name and path of directives defining whichLawson files or data locations should be copied. The directives or entries inthe input file are defined as follows:

A [AllFiles] <Y | N>

D <Include | Exclude> DatLocation

F <Include | Exclude> LawsonFileName

IMPORTANT The A directive is mandatory and specifies whether all Lawsonfiles in the data area are to be processed.

srgensrgen Compile Form and Object Rules

srgen productline [systemcode...]

Compile form and object rules. For more information, see Doc for Developers:Application Development Workbench Standards.


- or -1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type srgen and click the



startladbstartladb Start Lawson Database Server

startladb

Start the Lawson Database Server.

startlajsstartlajs Start Lawson Batch Server

startlajs

Start the Lawson Batch Server.

startlasestartlase Start Lawson Security Engine

startlase

Use this utility to start the Lawson Security Engine. (This is the server forLawson Security, not LAUA.)

startlatmstartlatm Start Lawson Application Server

startlatm

Start the Lawson Application Server. For more information, see LawsonAdministration: Server Setup and Maintenance.

startlawstartlaw Start All Lawson Servers

startlaw

Start all of the Lawson servers.

Start the subsystem (if it is not running) and all of the Lawson servers (ifthey are not running). The startlaw command is very similar to the IBM iStart Subsystem command (STRSBS). They both start the subsystem andthe Lawson servers. The startlaw command differs because it starts anyLawson servers that are not running even though the subsystem is alreadyrunning. The STRSBS command does not start the Lawson servers if thesubsystem is already running.

IMPORTANT Run this utility from the Qshell command line.


startqueuestartqueue Start Lawson Compile Queue

startqueue

Start the Lawson Compile Queue Server. For more information, see LawsonAdministration: Server Setup and Maintenance.

stopjobqstopjobq Stop Lawson Job Queue

stopjobq [-aA[#]ksSU]

Stop the Lawson Batch Server. For more information on the Lawson BatchServer, see Lawson Administration: Server Setup and Maintenance.

Option orParameter

Description

a Automatically shutdown the job server when all runningjobs have completed.

A# Same as -a but stopjobq does not return until the jobsever has shutdown. Optional # is a time in secondsbetween printing time stamp.

k Kill job server, sends KILL signal to job server.

m Not applicable.

s Stop job server, checks for running jobs (default).

S Stop job server, does not check for running jobs.


stopladbstopladb Stop Lawson Database Server

stopladb

Stop the Lawson Database Server.

stoplajsstoplajs Stop Lawson Batch Server

stoplajs

Stop the Lawson Batch Server. For more information, see LawsonAdministration: Server Setup and Maintenance.


stoplasestoplase Stop Lawson Security Engine

stoplase

Use this utility to stop the Lawson Security Engine.

stoplatmstoplatm Stop Lawson Application Server

stoplatm

Stop the Lawson Application Server. For more information, see LawsonAdministration: Server Setup and Maintenance.

stoplawstoplaw Stop All Lawson Servers

stoplaw

Stop all of the Lawson servers, including the subsystem.

IMPORTANT You must stop the application server (such as WebSphere)before you stop the Lawson servers.

stopqueuestopqueue Stop Lawson Compile Queue

stopqueue

Stop the Lawson Compile Queue Server. For more information, see LawsonAdministration: Server Setup and Maintenance.

sysdelfilesysdelfile System Files Definition

Identify the files that are a part of a particular system so you can deliver thosefiles. The Database Definition utility (dbdef) provides one way to identify thefiles that belong to a particular system; when you define database files, youassign them to a system. When you deliver a system to a target machine,however, you might need to include files in the delivery that belong to othersystems.

For example, the Glmaster file belongs to the Lawson General Ledger(GL) system. Because the Lawson Inventory Control (IC) system uses the


Glmaster file, when you deliver the IC system, you might need to include theGlmaster file in the delivery.1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type sysdelfile and click


Field Description

Product Line Product line you want to deliver.

System Code System code you want to deliver.

4. If you have not yet selected files, the Select Files for systemcode formappears.

Select the files you want to deliver with the product line and system code,and press Enter.

The system puts the selected files under the Deliverable Files heading.5. If you have selected files, the files appear under the Deliverable Files

heading.

To add a file to the list, press Select (F4) and choose the desired file.

To delete a file from the list, select the desired file and press Delete (F9).6. Press Enter twice.

sysdumpsysdump Export System Definition

sysdump [-iemrupv] productline dumpfile [systemcode...]

Copy existing system definitions to a flat file, making it possible to importthem to another product line.

The export function dumps information about the product line and creates aflat file that you can either load to a new product line or use to overwrite anexisting product line. This utility delivers system definitions for a product line.

Program Option Descriptioni Internal delivery.

e Includes all element definitions in the product line, evenif system code(s) are specified.

m IBM Midrange.

r Report Writer.

u Lawson Environment.

p Dump PGMCALL records. (The default is no PGMCALLrecords.)

v Display current dump version.



- or -1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type sysdump and click


Program Options Type the letter of the system you want to export.Only the definitions owned by the specifiedsystem code(s) are dumped.

See the program options listed above.

IMPORTANT Under normal conditions, Lawsonrecommends that you leave the Program Optionsfield blank.

Product Line The product line you want to export.

Dump File Name The name of the file you want to dump to.

System Code(s) System codes you want to export definitions for.Dumps all definitions owned by or referencedby the specified system code(s). When usedwith the -i option, only the definitions owned bysystem code(s) are dumped.

Leave blank to export system definitions for theentire product line.

4. Press Enter.


sysloadsysload Import System Definition

sysload [-irefpkcqVa] [-Tnnnn] dumpfilename[newproductline] [-l filepathname

Install new system definitions or update existing system definitions from aflat file. You can install or update data dictionaries from Lawson with thismenu option.

IMPORTANT When creating a new product line with sysload, the newproduct line is automatically added to the Lawson security class of the userwho is creating it. All users in this same security class then have access tothe new product line with access and restrictions to the system codes andform IDs the same as the creator.


Program Option Descriptioni Interactive updating of existing objects. If a program,

file, or element definition already exists in the database,a message asks you whether you want to update it.

r Report on existing objects; no updating. Writes to thestandard output the names of all objects in the importfile that are already in the database. It performs noupdating, even of new objects.

e Update all elements. Loads all elements from the flatfile, whether or not they already exist.

f Update all files. Loads all elements from the flat file,whether or not they already exist.

p Update all programs. Loads all programs from the flatfile, whether or not they already exist.

k Does not delete relations currently in the databasebefore updating a system definition. If you do not usethis option, the system deletes all relations owned bythe systems you are updating.

c Load PGMCALL records. By default, these are notloaded.

q Log all processing messages (sysldlog file).

V Show version number.

a Overwrite database file record allocations.

lfilepathname

Log all processing messages in the specified log file.


or1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type sysload and click the



Dump File Name The flat file that has the system definitions.

New Product Line The product line you want to move the systemdefinitions to.

4. Press Enter.



titlerpttitlerpt Titles Report

titlerpt [-n|t] language [translation]

Report on language titles and translations. For more information, see LawsonAdministration: Translation.

Program Option Descriptionn Print titles without translations only.

t Print titles with translations only.


- or -1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type titlerpt and click the


tknsecrpttknsecrpt Form ID Security Listing

List the form IDs, categories, product lines, and system codes defined inLawson user security. For more information, see Lawson Administration:LAUA Security.

To access the Form ID Security Listing utility:1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type tknsecrpt and click


tmcontroltmcontrol Transaction Monitor Control

tmcontrol [-ct [ProgramCode [ProgramCode...]]][-rpdataarea ProgramCode] [-sp dataarea ProgramCode[numberprocesses]] [-cto] [-cs][-p] [-da] [-dc] [-dm][-dn] [-dp] [-ds] [-du] [-lt] [-moff] [-mon] [-rc] [-v][-U]

Send transactions to the Lawson Application Server (latm). For moreinformation, see Lawson Administration: Server Setup and Maintenance.

ProgramOptions

Description

ct Capture a transaction; the default is all program codes.

rp Restart running programs; used to make latm use anew program object after a compile.


ProgramOptions

Description

sp Start the program(s).

cto Turn the transaction capture feature off.

cs Clear the statistic table.

p Send a “ping” message to latm to test response time.

da Dump the application objects.

dc Dump the form IDs that the transactions are beingcaptured for.

dm Dump the message buffers.

dn Dump the machine node table.

dp Dump the latm.cfg parameters.

ds Dump the processing statistics.

du Dump the lapm users.

lt Reload the “users per form ID” values.

moff Turn monitoring off.

mon Turn monitoring on.

rc Read the latm.cfg file and update the configurationparameters.

v Toggle debugging on and off.


IMPORTANT Use the -p, -ct, and -cto options with the LawsonTransaction Generator (transgen) when performance tuning.

tokendeftokendef Form ID Definition

Define form IDs to represent executable objects. For more information, seeLawson Administration: Server Setup and Maintenance.

To access the Form ID Definition utility:1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type tokendef and click


ujobdumpujobdump Dump Upgraded Job Definitions


ujobdump [-vclx?] [-d AltDir] DataArea Outfile [-u User[Jobs]] [-t Tokens]

ujobdump is a utility that dumps job definitions based on the selection criteriaspecified. The ujobdump utility, in conjunction with the ujobdump utility,enables you to update job definitions more easily when a batch update orreport parameter form has a new form definition file (xxxxD, such as HR211D)as a result of a CTP or MSP installation or an application upgrade. Todetermine if a new or updated form definition file has been added, examinethe install.log file (in the case of a CTP or MSP) or the readme file (in the caseof an application upgrade). Because ujobdump and ujobload update thejob definitions, you do not have to manually change the job definitions whennew or modified form definition files are installed.

The purpose of ujobdump and ujobload is to provide the capability to mapthe parameter fields when loading job definitions. These two scripts use thestandard Lawson jobdump and jobload utilities, but enhance the process byparsing the job parameters fields and mapping their values during the loadprocess. Default values to new fields will also be loaded.

Program Option Descriptionv Verbose. This option lists the jobs as they are being

processed and any jobs that are not dumped.

c Count. The count option displays the number of jobsthat will be processed. This option does not processany jobs.

l List. The list option lists, across the page, all jobs thatare counted with the -c option.

x Include upgrade job.


d AltDir Does not apply to IBM i.

DataArea You must specify a data area. Only jobs with all theirsteps run in the specified data area will be dumped,regardless of any other parameter entered. If you donot specify any other options, all jobs for that data areawill be dumped.

OutFile You must specify an output file. This is the file to whichthe job definitions will be dumped. If you specify a dash(-), job definitions will be dumped to standard out.

u User[Jobs]

User. The user option causes only jobs for thedesignated user to be dumped. If job names are listedafter the user name, only those jobs for the given userwill be dumped. Multiple jobs may be specified.

t Tokens Tokens. The tokens option causes only jobs containingthe specified form IDs to be dumped. If this option isspecified, specific jobs cannot be specified with the -uoption.


For more information about jobs and reports, see Lawson Administration:Jobs and Reports.


Considerations• It takes about 5 seconds to dump and load an average job. That’s about

720 jobs an hour, or 17,280 per day. Clients with a lot of jobs may want tobreak down the upgrade by user. Also, the average time depends on theparameter list. If the parameter list of the dump matches the parameterlist of the job being loaded, the job only takes a second or two. If they donot match, the job will take several seconds to run. CTPs and MSPsshould run faster than the 5 second average and will be limited to thenumber of jobs attempted to dump and load if the -d option is used.

• When upgrading from product line A to product line B within the sameenvironment, if you do not rename the jobs, they will overwrite productline A’s jobs.

• Parameter field values are mapped between fields with the same name. Ifa field was renamed, the value will not be mapped.

• Clients should check carefully the “deleted fields” summary for possibleproblems (see the previous consideration).

• Program names that are recycled will get unpredictable results. The jobwill be loaded and parameter fields will be mapped if any of the fieldnames match.

ujobloadujobload Load Upgraded Job Definitions

ujobload [-oudl?] [-x OldJobName:NewJobName...]DataArea InFile

The ujobload utility, in conjunction with the ujobdump utility, enables you toupdate job definitions more easily when a batch update or report parameterform has a new form definition file (xxxxxD file, such as HR211D) as a resultof a CTP or MSP installation or an application upgrade. To determine if a newor updated .form definition file has been added, examine the install.log file (inthe case of a CTP or MSP) or the readme file (in the case of an applicationupgrade). Because ujobdump and ujobload update the job definitions, youdo not have to manually change the job definitions when new or modified formdefinition files are installed.

The purpose of ujobdump and ujobload is to provide the capability to mapthe parameter fields when loading job definitions. These two scripts use thestandard Lawson jobdump and jobload utilities, but enhance the process byparsing the job parameters fields and mapping their values during the loadprocess. Default values to new fields will also be loaded.

ujobload is a utility that creates and optionally processes a standard Lawsonjobload file for each job found in the input file. For each job, the LAWDIR,PROJECT, PRODUCTLINE, JOBNAME, and PARAMS lines are altered tomatch the current Environment, data area specified and parameter fieldsof the form.


Program Option Descriptiono Overwrite. The overwrite option causes any existing job

definitions to be overwritten. If you do not specify thisoption, only jobs that do not exist will be created.

u Update. If you do not specify an update option, no jobswill be overwritten or created. List only is then assumed.

d List "deleted" fields. This option causes ujobload tolist, with the other mapped fields, parameter fieldswhich exist in the job definition and have values, butare not mapped to any field in the new job definition.Regardless of whether this option is specified or not, all"deleted" fields will be listed in the summary report atthe end of the output log

l Display the job log from the last ujobload run by thedesignated user. You must specify the DataArea whenusing the -l option. No other parameters are requiredwhen using this option.


xOldJobName:NewJobName

Translate. The translate option renames specified jobnames from OldJobName to NewJobName. You canspecify as many translate options as necessary.

For example:

ujobload -x JOB-1:JOB-1a -x JOB2:JOB-2a

DataArea You must specify a data area. All job steps will becreated to run in this data area.

InFile You must specify an input file. This is the file from whichthe job definitions will be read. If you specify a dash (-),job definitions will be read from standard in.


For more information about jobs and reports, see Lawson Administration:Jobs and Reports.

Considerations• It takes about 5 seconds to dump and load an average job. That’s about

720 jobs an hour, or 17,280 per day. Clients with a lot of jobs may want tobreak down the upgrade by user. Also, the average time depends on theparameter list. If the parameter list of the dump matches the parameterlist of the job being loaded, the job only takes a second or two. If they donot match, the job will take several seconds to run. CTPs and MSPsshould run faster than the 5 second average and will be limited to thenumber of jobs attempted to dump and load if the -d option is used.

• When upgrading from product line A to product line B within the sameenvironment, if you do not rename the jobs, they will overwrite productline A’s jobs.

• Parameter field values are mapped between fields with the same name. Ifa field was renamed, the value will not be mapped.


• Clients should check carefully the “deleted fields” summary for possibleproblems (see the previous consideration).

• Program names that are recycled will get unpredictable results. The jobwill be loaded and parameter fields will be mapped if any of the fieldnames match.

univverunivver Environment Version

univver [-v] program [program...]

Print the version of an Environment program.

Program Option DescriptionV Print the version of the univver program.

program The name of the Environment program whose versionyou want to print.

unvmnurptunvmnurpt Menu Report

unvmnurpt [-a productline] menuID language

Check for missing translations for form IDs on a menu and its submenus.

Program Option Descriptiona Check the application menu for a product line.

updatchfileupdatchfile Clear Attachment ID Field

updatchfile [-c] [-m maxtrans] productline [filename]

Clear attachment ID fields from parent records, in an entire product lineor in an individual file, that have no corresponding attachment records.(Attachment ID fields are hidden fields that the system adds to files when youenable them for attachments.) Use this utility to clear unnecessary attachmentID fields before reissuing attachment records, because parent records withoutcorresponding attachments no longer need these hidden fields.

Program Option Descriptionc Clear attachment ID fields from parent records that have

no corresponding attachment records. If you do not usethis option, updatchfile produces a report listing the


Program Option Descriptionnumber of parent records without attachments; it doesnot clear any ID fields.

m Specify, in maxtrans, the number of records to clearat one time (internal to the program; that is, within onedatabase transaction). The default of 50 helps to limitthe loss of data in a recovery situation.

productline Product line for which you want attachment ID fieldscleared.

filename File name you want attachment ID fields to clear.

updatchorphupdatchorph Delete Orphaned Attachments

updatchorph [-n] [-d] [-m maxtrans] productline[filename]

Delete all attachment records, in an entire product line or in an individual file,that do not have a corresponding parent record.

Program Option Descriptiond Delete attachment records that do not have a

corresponding parent record. If you do not use thisoption, updatchorph produces a report listing thenumber of orphaned attachments; it does not delete anyattachment.

m Specify, in maxtrans, the number of records to deleteat one time (internal to the program; that is, within onedatabase transaction). The default of 50 helps to limitthe loss of data in a recovery situation.

n Remove null space in attachment tables.

productline Product line you want to delete orphaned attachmentsfor.

filename File name you want to delete orphaned attachments for.

upgenvgrpsupgenvgrps Upgrade Lawson Environment Groups

upgenvgrps

For upgrading to the 9.0.x Lawson Environment when users have not beenassigned to printer groups, user groups, distribution list groups, and jobqueue groups, this utility assigns a default group for each type of group in theuser profile. You must still define the contents of the default groups. See theLawson Administration: Jobs and Reports.


useraccuseracc User Accessories

Display the User Accessories menu, which provides you with utilities toperform calculations, define a calendar, calculate loan amounts, and edittext files and report output.

To access the User Accessories menu:1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type useracc and click


userdocuserdoc Print User Text

Print user text, which is detailed reference information about all forms andfields in an application program. For more information, see Getting Startedwith the Lawson Interface Desktop (LID).

To access the Print User Text utility:1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type userdoc and click


Program Option Descriptione Print items without document text.

p Print cover, copyright, and form listing.

n Do not print value lists.

o Online programs only.

b Batch programs only.

m Process system module only.


vallstrptvallstrpt Value List Report

vallstrpt [-n|t] language [translation]

Report on language value lists and translations. For more information, seeLawson Administration: Translation.

Program Option Descriptionn Print value lists without translations only.

t Print value lists with translations only.


- or -1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type vallstrpt and click


verifyibmverifyibm Verify IBM DB2 Database

verifyibm[-qcsV] [-u DbLoginName] [-p Password]productline|dataarea [systemcode filename]

Compare the file, field, and index definitions in the Lawson dictionary with thetable, column, and index definitions in the IBM DB2 database and identifymissing objects or mismatched column definitions.

This parameter Indicates-q Quiet mode.

-c Check views.

-s Strict mode.

-u DbLoginName The database login name to use.

-p Password The password for the database login name.

-V Print the utility version number.

vwdblogvwdblog View Database Log File

vwdblog

View the database log file ($LAWDIR/system/ladb.log) from the Qshellcommand line. You can also view the log file with a text editor. As thedatabase is running, the system writes any error messages that occur tothis file, including error messages sent by any relational databases. If thedatabase fills, ladb writes a message in the log file describing the reason.


Information is appended to the log file. Should the file become too large,you can delete it or move it.


or1. From the Database Administration menu, choose Lawson Database

Server Tools.2. From the Lawson Database Server Tools menu, choose View Database

Log File.

The lashow utility displays the log file.

STEPS To empty the database log file1. Stop the Lawson system.2. Delete or move the log file using operating system commands.3. Start the Lawson system.

The system creates a new log file when there is information to store in it.

workdefworkdef Work File Definition

Define work files for secondary print files (that is, you have added $PRINTFILEsections to a report). For more information about report development, seeDoc for Developers: Application Development Workbench Standards.

To access the Work File Definition utility:1. In a Lawson Interface Desktop (LID) session, use Form Transfer (F8).2. In the Form ID field on the Form Transfer form, type workdef and click


workgenworkgen Application Workfile Generator

workgen productline (programcode| GLOBAL) workfilename

Examples:

workgen lawapp9 ac120 actgpwrk

workgen lawapp9 GLOBAL glrptswrk

After you have made a change to work file definitions in the Workfile Definitionutility, use this utility to update the work file information in the IBM i physicalfile members for a product line, for a program’s work files, or for global workfiles. You usually do not need to use this utility to accomplish an update ofthe work file information in the physical file members because compiling theprogram or module will call workgen. Only use this utility if the work fileinformation was not updated through the compile process.


Program Option Descriptionproductline The product line containing the work files whose

physical file members you want to update.

programcode The program that the work files belong to whosephysical file members you want to update.

GLOBAL Indicates that the work files whose physical file membersare to be updated are ones that do not belong to aspecific program.

workfilename The specific work file whose physical file members youwant to update.

wtsubmitwtsubmit Wait Submission

wtsubmit [-Un] [-r] [-v] [-jjobqueue -dDate -tTimeusername jobname

Executes a single-step job. When a job is submitted, wtsubmit waits until thejob has completed before it returns control back to the calling script or shell.


n Print and return job number.

r Return if the job goes into Waiting Recovery.

v Verbose output (job submitted acknowledgment).

jJobQueue Specify queue for this job.

dDate Specify date when job should run. Use MMDDYYformat.

tTime Specify time when job should run. Use HHMM format.

Parameter Descriptionusername System ID of user submitting the job.

jobname Name of job being submitted.



Appendix A

Documentation Conventions and Support

Utility Documentation ConventionsThis manual references certain Lawson Environment programs and utilities.Often you can access these programs and utilities in more than one way.However, this manual will not describe all ways that you can access eachprogram or utility.

If you can access the program or utility through a form transfer within theLawson Interface Desktop (LID), the manual will describe that access method.If you can access the program or utility through either the System i commandline or through a Qshell command line, the manual will describe the Qshellmethod. If only the System i command line is available, this manual willprovide the syntax for the System i command.

Lawson Interface Desktop Form TransferThe form transfer method of access to programs and utilities is availablethrough the Lawson Interface Desktop (LID). After you log in to LID, you pressForm Transfer (F8), enter the name of the program or utility on the FormTransfer form (such as laua), and then click the OK button (the button with agreen check mark). You can also navigate to a program or utility through theForm Transfer form by selecting the appropriate tab, a category or systemcode, and then the program or form you want to view.

Qshell Command LineYou start a Qshell session with the qsh command at the System i commandline. In a Qshell session, you type commands for Lawson programs andutilities in the following format:

ProgramName -Options Parameter1 Parameter2 ...

If options or parameters are optional, they will be enclosed in square brackets( [ ] ). If you are allowed to use only one option or parameters from a set ofoptions or parameters, your choices will be separated by vertical bars ( | ).

For example, the syntax for the Security Dump utility (secdump) and theLoad Language utility (ldlang) is:

secdump dataarea|dataID dumpfile [adminclass |securityclass]

ldlang [-l language] [-aodr] dumpfile[overrideproductline]

Samples:

System Utilities Reference Guide Appendix A Documentation Conventionsand Support

127

secdump lawapp9 secfile secclass1

ldlang -l Spanish -r SpanTrans.txt lawapp9

System i Command LineThis manual does not show the System i command line syntax for eachprogram or utility unless that is the only way to access a program or utility.To access a program or utility through the System i command line, use thefollowing syntax format:

CALL PROGRAMNAME PARM(’PARAMETER1’ ’PARAMETER2’ ...’PARAMETERn’)

Using the System i command line syntax, the secdump command is in thefollowing format:

CALL SECDUMP PARM(’DATAAREA’|’DATAID DUMPFILE’[’ADMINCLASS’|’SECURITYCLASS’])

Sample: CALL SECDUMP PARM(’LAWAPP9’ ’SECFILE’ ’SECCLASS1’)

Utilities or Programs for Editing Text FilesWhen this manual refers to editing or viewing a text file, such as aconfiguration file, it will generally say to open the file in the IFS with atext editor and it will give the file’s IFS location. For a text editor, Lawsonrecommends WordPad, but discourages the use of Notepad becauseNotepad does not handle carriage returns properly.

You can also use the EDTF command from the System i command line inorder to edit or view files in the IFS. However, this manual will usually notprovide the command line syntax. If you want to use EDTF, supply the fullpath to the text file you want to edit or view as a parameter to the EDTFcommand. For example:

EDTF ’law8/DB/lawapp9/reorg.hist’

Special Note for Submitting Batch Jobs from theSystem i Command LineIf you use the System i SBMJOB command to submit a Lawson Environmentutility program, you must set the CPYENVVAR parameter (“Copy environmentvariables”) to *YES.

For example:

SBMJOB CMD(CALL PGM(LDLANG) PARM(’-l’ ’SPANISH’ ’-r’’/home/SpanTrans.txt’ ’LAWAPP9’)) CPYENVVAR(*YES)

Documentation ConventionsThis document uses specific text conventions and visual elements.

128 Appendix A Documentation Conventionsand Support


Text ConventionsThis Represents

bold A key name or function key name. For example, Shift isa key name and Help (F1) is a function key name.

A value or command that must be typed exactly as itappears.

A program or file name.

italics A manual title or form name.

An emphasized word or phrase.

A placeholder for a user-defined value or variable.

(F1)-(F24) A function key number. Press Help (F1) instructs you topress the key mapped for the (F1) function.

Key1+Key2 A key combination. Press Shift+FndNxt (F3) instructsyou to press and hold down the Shift key and thenpress the FndNxt (F3) function key. Release both keysto complete the action.

[ ] Optional parameters. Type none, one, or more ofthe parameters within the brackets. For example, thecommand:

qsubmit [-Un] [-jJobQueue -dDate -tTime]username jobname

means that you can type a specific job queue, date, ortime, or you can omit these parameters.

[ | ] Optional parameters. You can type only one of theparameters separated by a vertical line. For example,the command:

phraserpt[-n|t] BaseLanguage[Translation]

means that you can type either the n or t parameter;you cannot type both.

... A parameter that can be repeated. For example, thecommand:

scrgen [-scxvV] productline [systemcode[programcode...]]

means that you can type any number of program codes.


129

Visual Elements

Before you start Information you need to know before you attempt theprocedure or process.

IMPORTANT Important information to consider when you perform theprocedure.

CAUTION Cautionary information about actions that involve a risk ofpossible damage to equipment, data, or software.

WARNING Warning information about actions that involve a risk ofpersonal injury or irreversible destruction to the data or operatingsystem.

Product DocumentationLawson offers the following product documentation:• Online help• User guides and manuals• Release notes and installation instructions

To find Lawson documentation, see the user interface or http://support.lawson.com. To obtain a login password and ID for the Support site,see your organizations Lawson contact or your Lawson client manager.

Support & DeliveryLawson Support & Delivery (S&D) is available to all Lawson customerswho are on maintenance support for Lawson products. See the SupportOperations Handbook for the following information:• What information to gather before you contact S&D• How to contact S&D• How S&D processes your request• Which services are standard maintenance and which are billable

To find the Support Operations Handbook, see http://support.lawson.com.To obtain a login password and ID for the support web site, see yourorganizations Lawson contact or your Lawson client manager.

Documentation ContactWe welcome your questions or suggestions about Lawson documentation.Please send comments to [email protected].



Related Lawson DocumentationThis guide is one in a series of Lawson administration guides. This seriesincludes:• Lawson Administration: Server Setup and Maintenance• Lawson Administration: Resources and Security• Lawson Administration: LAUA Security• Lawson Administration: Portal• Lawson Administration: Jobs and Reports• Lawson Administration: Translation• System Utilities Reference Guide• Lawson Administration: Data Access Using IBM DB2• For information on function keys and terminal configuration, formerly

included in the Lawson Administration Guide, see the Lawson KnowledgeBase.

In addition, Lawson offers the following product documentation:• Online help• Users guides and manuals• Installation guides• Release notes• Integration guides for third-party products• Enhancement and patch documentation

To find Lawson documentation, see the user interface or http://support.lawson.com. In addition to the Document Center atsupport.lawson.com, the Lawson support site includes the Lawson KnowledgeBase. You can search the Knowledge Base for most product documentationas well as for special topics not covered in any manual. To obtain a login IDand password for the Support site, see your organization’s Lawson contact oryour Lawson client manager.


131



Index

Numeric/Symbols4GL and RPG ILE Database Name Browser, 63

AAnalyze Element Node utility, 34analyze_stats utility, 7Application Workfile Generator utility, 124Attachment Report utility, 90

BBatch Job Control utility, 73blddbdict utility, 8blddbvers utility, 8bldexpfd utility, 9bldibmddl utility, 9bldibmsec utility, 11bldsecdict utility, 13bldxffiles utility, 13Build Data Definition Language utility, 9Build Database Version File utility, 8Build Dictionary utility, 8Build Export File Description utility, 9Build RPG Shell utility, 100Build Security Dictionary utility, 13

Ccalc utility, 16caldef utility, 16Calendar Definition utility, 16Check Records utility, 16chkrec utility, 16Clear Attachment ID Field utility, 120cndrpt utility, 23cnvexp utility, 24cnvimp utility, 24cnvtape utility, 25Compile Form and Object Rules utility, 108Compile Form utility, 102Compile Lawson utility, 75

Compile Program utility, 96Compile Queue Control utility, 96Compile Queue Status utility, 97Compile Report utility, 100Compile System utility, 99Condition Report utility, 23Condition Usage Report utility, 27Convert a Line Sequential Import File utility, 24Convert Sequential Export File utility, 24Convert Tape utility, 25Copy database file between data areas using SQL

code utility, 106Copying

data, 71job information, 68, 70

Count Records in Table utility, 25count utility, 25Create Database utility, 29Create Product Line utility, 26Create Security Objects in an IBM DB2 Database

utility, 11createprodline utility, 26

DData

copying, preparing for, 71Database

creating, 29mode, setting, 34

Database Copy utility, 28Database Definition utility, 29database driver configuration file

variablesDIR, 26PROGRAM_FILTER, 26TIMESTATS, 26TIMESTATSLOG, 26USER_FILTER, 26

dbadmin utility, 26dbcndusage utility, 27dbcopy utility, 28dbcreate utility, 29dbdef utility, 29dbdoc utility, 29dbdump utility, 30

System Utilities Reference Guide Index 133

dbfldusage utility, 32dbindusage utility, 32dbload utility, 33dbmode utility, 34dbnode utility, 34dbrelusage utility, 35dbreorg -g utility, 37dbreorg utility

description, 35dburf utility, 39dbusers utility, 40Define Document Names utility, 57delckpoint utility, 40delement utility, 40Delete Checkpoint Records utility, 40Delete Job History utility, 41Delete Orphaned Attachments utility, 121Delete Unused Elements utility, 40deljobhst utility, 41derfldrpt utility, 42Derived Field Report utility, 42DIR, 26Display File utility, 75Distribution Group Definition utility, 62dmpappclmphr utility, 43dmpappmsg utility, 43dmpappphr utility, 44dmpdftxt utility, 50dmpfldtxt utility, 50dmplang utility, 51dmplapmerr utility, 51dmppgftxt utility, 51dmpprodmenus utility, 52dmprpgpi utility, 52dmpscrtxt utility, 53dmpsecdict utility, 54dmptitle utility, 54dmpuniveng utility, 55dmpunivlib utility, 55dmpunivmen utility, 55dmpunivtkn utility, 56dmpunvhlp utility, 56dmpunvmsg utility, 56dmpunvphr utility, 56docname utility, 57Dump Application Column Phrases utility, 43Dump Application Messages utility, 43Dump Application Phrases utility, 44Dump Data File Text utility, 50Dump Database File Range utility, 97Dump Database File utility, 30Dump English Language Records utility, 55

Dump Environment Form IDs utility, 56Dump Field Text utility, 50Dump Form Document Text utility, 53Dump Language utility, 51Dump lapm Messages utility, 51Dump Lawson Environment Help Text utility, 56Dump Lawson Environment Libraries utility, 55Dump Lawson Environment Menus utility, 55Dump Lawson Environment Messages utility, 56Dump Lawson Environment Phrases utility, 56Dump Product Line Menus utility, 52Dump Program Document File Text utility, 51Dump Program Information Structures utility, 52Dump Security Dictionary utility, 54Dump Titles utility, 54Dump Upgraded Job Definitions utility, 116

EEdit Data Area utility, 59editda utility, 59Elements

names, defining for documents, 57Enter Technical Text utility, 93Environment utilities

setdbvers, 105Environment Version utility, 120Export System Data utility, 59Export System Definition utility, 112expsysdb utility, 59

FField Usage Report utility, 32, 61Fields

names, defining for documents, 58Files

names, defining for documents, 57fldrpt utility, 61Form field names, defining for documents, 57Form ID Definition utility, 116Form ID Security Listing utility, 115

GGarbage Collection utility, 37gendbload utility, 61grpdef utility, 62

134 Index System Utilities Reference Guide

Hhlpgen utility, 62

IIBM DB2 Disk Usage utility, 63ibmdu utility, 63ilename utility, 63impexp utility, 64Import an Export File utility, 64Import Comma-Delimited File utility, 66Import System Definition utility, 113importdb utility, 66Index Usage Report utility, 32integ utility, 67

Jjbsubmit utility, 67Job Definition utility, 68Job Dump utility, 68Job Inquiry utility, 69Job Integrity utility, 69Job Listing utility, 71Job Load utility, 70Job Parameter Dump utility, 94Job Parameter Report utility, 71Job Parameter Update utility, 95Job Queue Defaults utility, 72Job Queue Definition utility, 72Job Queue Listing utility, 72Job Queue Status utility, 73Job Status utility, 71Job Submission utility, 67jobdef utility, 68jobdump utility, 68jobinq utility, 69jobinteg utility, 69jobload utility, 70jobprmrpt utility, 71jobrpt utility, 71Jobs

copying, 68, 70jobstatus utility, 71jqdef utility, 72jqdflt utility, 72jqrpt utility, 72jqstatus utility, 73jqsubmit utility, 73js utility, 73

KKey Number Definition utility, 74kndef utility, 74

Lladb Administration utility, 26ladb.log, 123laenv utility, 74langdef utility, 74Language Definition utility, 74laservipc utility, 74lashow utility, 75lawcmp utility, 75Lawson Security Configuration utility, 83Lawson Security Dump utility, 86Lawson Security Load utility, 87Lawson Server Process ID Run Status and IPC

Key utility, 74Lawson User Security utility, 75ldappclmphr utility, 76ldappmsg utility, 76ldappphr utility, 77ldappvallst utility, 77lddoctxt utility, 78ldhlptxt utility, 78ldlang utility, 78ldprodmenus utility, 79ldtitle utility, 79lduniveng utility, 79ldunivlibs utility, 79ldunivmenus utility, 80ldunivtkns utility, 80ldunvhlp utility, 80ldunvmsg utility, 80ldunvphr utility, 81libdef utility, 81Library Definition utility, 81License Status utility, 81licsta utility, 81List Invoke utility, seePrint Compile Script For

Programs Which Use 4GL INVOKElistprodatch utility, 90Load Application Column Phrases utility, 76Load Application Messages utility, 76Load Application Phrases utility, 77Load Application Value Lists utility, 77Load Database from Flat File utility, 33, 61Load Environment Form IDs utility, 80Load Environment Menus utility, 80Load Help File utility, 62Load Help Text utility, 78


Load Language utility, 78Load Lawson Environment Help Text utility, 78, 80Load Lawson Environment Libraries utility, 79Load Lawson Environment Messages utility, 80Load Lawson Environment Phrases utility, 81Load Lawson Environment Records utility, 79Load Menus utility, 79Load Program Messages utility, 91Load Titles utility, 79Load Upgraded Job Definitions utility, 118Load Users utility, 82loadusers utility, 82Loan Amortization utility, 83loan utility, 83Locale Definition utility, 83locdef utility, 83Log files

ladb.log, 123lsconfig utility, 83lsdump utility, 86lsload utility, 87lstinvk utility, 90

MMenu Report utility, 91, 120menurpt utility, 91Message Definition utility, 91Message Report utility, 92msggen utility, 91msgmnt utility, 91msgrpt utility, 92

NNeeds Recovery jobs, 40

Ppgftxt utility, 93pgmdef utility, 93pgmdef2 utility, 94Phrase Count utility, 94Phrase Report utility, 94phraserpt utility, 94phrcnt utility, 94Print Compile Script For Programs Which Use 4GL

INVOKE utility, 90Print Data File Text utility, 29Print Technical Text utility, 39

Print User Text utility, 122Printer Definition utility, 95prmdump utility, 94prmload utility, 95proddadi utility, 95Product Line Data Area Data ID Report utility, 95Product lines

copying, preparing for, 71Program Definition utility, 93PROGRAM_FILTER, 26prtdef utility, 95

Qqcompile utility, 96qcontrol utility, 96qstatus utility, 97Query Definition utility, 94

Rrecdef utility, 97recrpt utility, 97Recurring Job Definition utility, 97Recurring Job Listing utility, 97Relation Usage Report utility, 35Reorganize Database utility, 35rngdbdump utility, 97rpgcmp utility, 99rpgshell utility, 100rptgen utility, 100Rule Report utility, 101rulerpt utility, 101

Sscrgen utility, 102secdump utility, 102secinteg utility, 103secload utility, 104Security Database Integrity utility, 103Security Dump utility, 102Security Load utility, 104Set Database Mode utility, 34Set Not Used Flag for Relations utility, 105setdbvers utility, 105setnotused utility, 105setsfl utility, 105skndef utility, 106sqldbcopy utility, 106

136 Index System Utilities Reference Guide

srgen utility, 108Start All Lawson Servers utility, 109Start Lawson Application Server utility, 109Start Lawson Batch Server utility, 109Start Lawson Compile Queue utility, 97, 110Start Lawson Database Server utility, 109Start Lawson Security Engine utility, 109startladb utility, 109startlajs utility, 109startlase utility, 109startlatm utility, 109startlaw, 109startqueue utility, 97, 110Stop All Lawson Servers utility, 111Stop Lawson Batch Server utility, 110Stop Lawson Compile Queue utility, 111Stop Lawson Database Server utility, 110Stop Lawson Security Engine utiltiy, 111Stop Lawson Transaction Manager utility, 111stopjobq utility, 110stopladb utility, 110stoplajs utility, 110stoplase utility, 111stoplatm utility, 111stoplaw, 111stopqueue utility, 111Submit Batch Job utility, 73sysdelfile utility, 111sysdump utility, 112sysload utility, 113System Files Definition utility, 111System Key Number Definition utility, 106

Ttimed statistics, 7TIMESTATS, 26TIMESTATSLOG, 26titlerpt utility, 115Titles Report utility, 115tknsecrpt utility, 115tmcontrol utility, 115tokendef utility, 116Transaction Monitor Control utility, 115

Uujobdump utility, 116ujobload utility, 118univver utility, 120unvmnurpt utility, 120updatchfile utility, 120updatchorph utility, 121Update SYSFILE utility, 105upgenvgrps utility, 121Upgrade Lawson Environment Groups utility, 121User Accessories Calculator utility, 16User Accessories utility, 122USER_FILTER, 26useracc utility, 122userdoc utility, 122

Vvallstrpt utility, 123Value List Report utility, 123Verify IBM DB2 Database utility, 123Verify Integrity of Database utility, 67verifyibm utility, 123View Database Log File utility, 123View Database Processes utility, 40vwdblog utility, 123

WWait Submission utility, 125Work File Definition utility, 124workdef utility, 124workgen utility, 124wtsubmit utility, 125

XXternal Format File Builder utility, 13


Documents

System Utilities Reference Guide