CL Reference
CL Reference
SC41-5722-01
AS/400e series IBM
CL Reference
CL Reference Part 2 (Full Version)
Common CL Information
Version 4
SC41-5722-01
ii OS/400 CL Reference - Part 2 (Full Version)
Contents
Chapter 2. OS/400 Command Descriptions . . . P3-11 DSPCMD (Display Command) Command . . . . . P3-61
DMPCLPGM (Dump Control Language Program) DSPCNNL (Display Connection List) Command . . P3-62
Command . . . . . . . . . . . . . . . . . . . . . P3-12 DSPCNNSTS (Display Connection Status) Command P3-63
DMPDLO (Dump Document Library Object) DSPCOSD (Display Class-of-Service Description)
Command . . . . . . . . . . . . . . . . . . . . . P3-13 Command . . . . . . . . . . . . . . . . . . . . . P3-64
| DMPJOB (Dump Job) Command . . . . . . . . . . P3-14 DSPCPCST (Display Check Pending Constraint)
DMPJOBINT (Dump Job Internal) Command . . . P3-16 Command . . . . . . . . . . . . . . . . . . . . . P3-65
DMPOBJ (Dump Object) Command . . . . . . . . P3-17 DSPCSI (Display Communications Side Information)
DMPSYSOBJ (Dump System Object) Command . P3-18 Command . . . . . . . . . . . . . . . . . . . . . P3-66
DMPTAP (Dump Tape) Command . . . . . . . . . P3-22 DSPCTLD (Display Controller Description) Command P3-67
DMPTRC (Dump Trace) Command . . . . . . . . P3-26 DSPCURDIR (Display Current Directory) Command P3-68
DO (Do) Command . . . . . . . . . . . . . . . . . P3-27 DSPDBG (Display Debug) Command . . . . . . . P3-69
DSCJOB (Disconnect Job) Command . . . . . . . P3-28 DSPDBGWCH (Display Debug Watches) Command P3-70
DSPACC (Display Access Code) Command . . . . P3-30 DSPDBR (Display Database Relations) Command P3-71
DSPACCAUT (Display Access Code Authority) DSPDDMF (Display Distributed Data Management
Command . . . . . . . . . . . . . . . . . . . . . P3-31 File) Command . . . . . . . . . . . . . . . . . . P3-75
DSPACTPJ (Display Active Prestart Jobs) Command P3-32 DSPDEVD (Display Device Description) Command P3-77
DSPACTPRFL (Display Active Profile List) Command P3-33 DSPDIRE (Display Directory Entries) Command . . P3-78
DSPACTSCD (Display Activation Schedule) DSPDKT (Display Diskette) Command . . . . . . . P3-82
Command . . . . . . . . . . . . . . . . . . . . . P3-34 DSPDLOAUD (Display Document Library Object
DSPAPPNINF (Display APPN Information) Command P3-35 Audit) Command . . . . . . . . . . . . . . . . . P3-83
DSPAUDJRNE (Display Audit Journal Entries) DSPDLOAUT (Display Document Library Object
Command . . . . . . . . . . . . . . . . . . . . . P3-37 Authority) Command . . . . . . . . . . . . . . . P3-85
DSPAUT (Display Authority) Command . . . . . . P3-40 DSPDLONAM (Display Document Library Object
DSPAUTHLR (Display Authority Holder) Command P3-41 Name) Command . . . . . . . . . . . . . . . . . P3-87
DSPAUTL (Display Authorization List) Command . P3-42 DSPDOC (Display Document) Command . . . . . P3-89
DSPAUTLDLO (Display Authorization List Document DSPDSTL (Display Distribution List) Command . . P3-90
Library Objects) Command . . . . . . . . . . . . P3-44 DSPDSTLOG (Display Distribution Log) Command P3-93
DSPAUTLOBJ (Display Authorization List Objects) DSPDSTSRV (Display Distribution Services)
Command . . . . . . . . . . . . . . . . . . . . . P3-45 Command . . . . . . . . . . . . . . . . . . . . . P3-97
DSPAUTUSR (Display Authorized Users) Command P3-47 DSPDTAARA (Display Data Area) Command . . . P3-98
DSPBCKSTS (Display Backup Status) Command . P3-48 DSPDTADCT (Display Data Dictionary) Command P3-100
DSPBCKUP (Display Backup Options) Command . P3-49 DSPEDTD (Display Edit Description) Command . . P3-102
DSPBCKUPL (Display Backup List) Command . . P3-50 DSPEWCBCDE (Display Extended Wireless
DSPBKP (Display Breakpoints) Command . . . . . P3-51 Controller Bar Code Entry) Command . . . . . . P3-103
DSPBNDDIR (Display Binding Directory) Command P3-52 DSPEWCM (Display Extended Wireless Controller
DSPCCTRTE (Display Circuit Route) Command . P3-54 Member) Command . . . . . . . . . . . . . . . . P3-104
DSPCCTSRV (Display Circuit Service) Command . P3-55 DSPEWCPTCE (Display Extended Wireless
DSPCDEFNT (Display Coded Font) Command . . P3-57 Controller PTC Entry) Command . . . . . . . . . P3-105
DSPCFGL (Display Configuration List) Command . P3-59 DSPEWLM (Display Extended Wireless Line
DSPCLS (Display Class) Command . . . . . . . . P3-60 Member) Command . . . . . . . . . . . . . . . . P3-106
Contents v
GENCAT (Merge Message Catalog) Command . . P3-379 OVRICFF (Override with Intersystem
GO (Go to Menu) Command . . . . . . . . . . . . P3-380 Communications Function File) Command . . . . P3-523
GOTO (Go To) Command . . . . . . . . . . . . . P3-382 OVRMSGF (Override with Message File) Command P3-526
GRTACCAUT (Grant Access Code Authority) | OVRPRTF (Override with Printer File) Command . P3-527
Command . . . . . . . . . . . . . . . . . . . . . P3-383 OVRSAVF (Override with Save File) Command . . P3-544
GRTOBJAUT (Grant Object Authority) Command . P3-385 OVRTAPF (Override with Tape File) Command . . P3-547
GRTUSRAUT (Grant User Authority) Command . . P3-389 PGM (Program) Command . . . . . . . . . . . . . P3-557
GRTUSRPMN (Grant User Permission) Command P3-390 PING Command . . . . . . . . . . . . . . . . . . P3-559
GRTWSOAUT (Grant Workstation Object Authority) POSDBF (Position Database File) Command . . . P3-560
Command . . . . . . . . . . . . . . . . . . . . . P3-391 PRTADPOBJ (Print Adopting Objects) Command . P3-561
HLDCMNDEV (Hold Communications Device) PRTAFPDTA (Print Advanced Function Printer Data)
Command . . . . . . . . . . . . . . . . . . . . . P3-394 Command . . . . . . . . . . . . . . . . . . . . . P3-562
HLDDSTQ (Hold Distribution Queue) Command . . P3-395 PRTCMDUSG (Print Command Usage) Command P3-564
HLDJOB (Hold Job) Command . . . . . . . . . . . P3-396 PRTCMNSEC (Print Communications Security)
HLDJOBQ (Hold Job Queue) Command . . . . . . P3-398 Command . . . . . . . . . . . . . . . . . . . . . P3-566
HLDJOBSCDE (Hold Job Schedule Entry) PRTCMNTRC (Print Communications Trace)
Command . . . . . . . . . . . . . . . . . . . . . P3-399 Command . . . . . . . . . . . . . . . . . . . . . P3-567
HLDOUTQ (Hold Output Queue) Command . . . . P3-400 PRTDEVADR (Print Device Addresses) Command P3-570
HLDRDR (Hold Reader) Command . . . . . . . . P3-401 PRTDOC (Print Document) Command . . . . . . . P3-571
HLDSPLF (Hold Spooled File) Command . . . . . P3-402 PRTDSKINF (Print Disk Information) Command . . P3-581
HLDWTR (Hold Writer) Command . . . . . . . . . P3-404 PRTERRLOG (Print Error Log) Command . . . . . P3-583
IF (If) Command . . . . . . . . . . . . . . . . . . P3-405 PRTINTDTA (Print Internal Data) Command . . . . P3-587
INSFLMSVR (Install FlowMark Server) Command . P3-407 PRTIPSCFG (Print IP over SNA Configuration)
INSNWSAPP (Install Network Server Application) Command . . . . . . . . . . . . . . . . . . . . . P3-589
Command . . . . . . . . . . . . . . . . . . . . . P3-410 PRTJOBDAUT (Print Job Description Authority)
INSPTF (Install Program Temporary Fix) Command P3-413 Command . . . . . . . . . . . . . . . . . . . . . P3-590
INZDKT (Initialize Diskette) Command . . . . . . . P3-416 PRTPUBAUT (Print Publicly Authorized Objects)
INZDSTQ (Initialize Distribution Queue) Command P3-419 Command . . . . . . . . . . . . . . . . . . . . . P3-591
INZOPT (Initialize Optical) Command . . . . . . . P3-421 PRTPVTAUT (Print Private Authorities) Command P3-593
INZPCS (Initialize Client Access) Command . . . . P3-423 PRTQAUT (Print Queue Authority) Command . . . P3-595
INZPFM (Initialize Physical File Member) Command P3-425 PRTSBSDAUT (Print Subsystem Description
INZSYS (Initialize System) Command . . . . . . . P3-427 Authority ) Command . . . . . . . . . . . . . . . P3-596
INZTAP (Initialize Tape) Command . . . . . . . . P3-428 PRTSQLINF (Print Structured Query Language
IPXPING Command . . . . . . . . . . . . . . . . P3-432 Information) Command . . . . . . . . . . . . . . P3-597
LNKDTADFN (Link Data Definition) Command . . P3-433 PRTSWL (Print Stop Word List) Command . . . . P3-598
LODPTF (Load Program Temporary Fix) Command P3-435 | PRTSYSINF (Print System Information) Command P3-599
LODQSTDB (Load Question-and-Answer Database) PRTSYSSECA (Print System Security Attributes)
Command . . . . . . . . . . . . . . . . . . . . . P3-438 Command . . . . . . . . . . . . . . . . . . . . . P3-600
LODRUN (Load and Run Media Program) PRTTRGPGM (Print Trigger Program) Command . P3-601
Command . . . . . . . . . . . . . . . . . . . . . P3-439 PRTUSROBJ (Print User Objects) Command . . . P3-602
MD (Create Directory) Command . . . . . . . . . P3-442 PRTUSRPRF (Print User Profile) Command . . . . P3-603
MKDIR (Create Directory) Command . . . . . . . P3-445 PWRDWNSYS (Power Down System) Command . P3-605
MONMSG (Monitor Message) Command . . . . . P3-448 QRYDOCLIB (Query Document Library) Command P3-608
MOUNT (Add Mounted File System) Command . . P3-451 QRYDST (Query Distribution) Command . . . . . P3-617
MOV (Move) Command . . . . . . . . . . . . . . P3-452 QRYPRBSTS (Query Problem Status) Command . P3-620
MOVDOC (Move Document) Command . . . . . . P3-454 QRYTIEF (Query Technical Information Exchange
MOVE (Move) Command . . . . . . . . . . . . . . P3-456 File) Command . . . . . . . . . . . . . . . . . . P3-622
MOVOBJ (Move Object) Command . . . . . . . . P3-458 | QSH (Start QSH) Command . . . . . . . . . . . . P3-623
MRGMSGCLG (Merge Message Catalog) Command P3-460 RCLACTGRP (Reclaim Activation Group) Command P3-624
MRGMSGF (Merge Message File) Command . . . P3-463 RCLDDMCNV (Reclaim Distributed Data
MRGTCPHT (Merge TCP/IP Host Table) . . . . . P3-465 Management Conversations) Command . . . . . P3-625
NETSTAT Command . . . . . . . . . . . . . . . . P3-467 | RCLDLO (Reclaim Document Library Object)
OPNDBF (Open Database File) . . . . . . . . . . P3-468 | Command . . . . . . . . . . . . . . . . . . . . . P3-626
OPNQRYF (Open Query File) Command . . . . . P3-471 RCLLIB (Reclaim Library) Command . . . . . . . . P3-629
OVRDBF (Override with Database File) Command P3-499 RCLOPT (Reclaim Optical) Command . . . . . . . P3-630
OVRDKTF (Override with Diskette File) Command P3-506 RCLRSC (Reclaim Resources) Command . . . . . P3-631
OVRDSPF (Override with Display File) Command . P3-511 RCLSPLSTG (Reclaim Spool Storage) Command . P3-634
OVRICFDEVE (Override with Intersystem RCLSTG (Reclaim Storage) Command . . . . . . P3-635
Communications Function Program Device Entry) RCLTMPSTG (Reclaim Temporary Storage)
Command . . . . . . . . . . . . . . . . . . . . . P3-515 Command . . . . . . . . . . . . . . . . . . . . . P3-638
Contents vii
RMVPEXDFN (Remove Performance Explorer ROLLBACK (Rollback) Command . . . . . . . . . P3-814
Definition) Command . . . . . . . . . . . . . . . P3-766 | RPCBIND (Start RPC Binder Daemon) Command P3-815
| RMVPFCST (Remove Physical File Constraint) | RPCGEN (Convert RPC Source) Command . . . . P3-816
| Command . . . . . . . . . . . . . . . . . . . . . P3-767 RPLDOC (Replace Document) Command . . . . . P3-817
RMVPFTRG (Remove Physical File Trigger) RQSORDAST (Request Order Assistance)
Command . . . . . . . . . . . . . . . . . . . . . P3-769 Command . . . . . . . . . . . . . . . . . . . . . P3-820
RMVPGM (Remove Program) Command . . . . . P3-771 RRTJOB (Reroute Job) Command . . . . . . . . . P3-821
RMVPJE (Remove Prestart Job Entry) Command . P3-772 RSMBKP (Resume Breakpoint) Command . . . . P3-822
| RMVPTF (Remove Program Temporary Fix) RSMCTLRCY (Resume Controller Recovery)
| Command . . . . . . . . . . . . . . . . . . . . . P3-773 Command . . . . . . . . . . . . . . . . . . . . . P3-823
RMVRDBDIRE (Remove Relational Database RSMDEVRCY (Resume Device Recovery)
Directory Entry) Command . . . . . . . . . . . . P3-775 Command . . . . . . . . . . . . . . . . . . . . . P3-824
RMVREXBUF (Remove REXX Buffer) Command . P3-776 RSMLINRCY (Resume Line Recovery) Command P3-825
RMVRMTDFN (Remove Remote Definition) RSMNWIRCY (Resume Network Interface
Command . . . . . . . . . . . . . . . . . . . . . P3-777 Recovery) Command . . . . . . . . . . . . . . . P3-826
RMVRPYLE (Remove Reply List Entry) Command P3-778 RST (Restore) Command . . . . . . . . . . . . . P3-827
RMVRTGE (Remove Routing Entry) Command . . P3-779 RSTAUT (Restore Authority) Command . . . . . . P3-832
RMVSCHIDXE (Remove Search Index Entry) RSTCFG (Restore Configuration) Command . . . P3-834
Command . . . . . . . . . . . . . . . . . . . . . P3-780 RSTDLO (Restore Document Library Object)
RMVSNILOC (Remove SNA over IPX Location) Command . . . . . . . . . . . . . . . . . . . . . P3-838
Command . . . . . . . . . . . . . . . . . . . . . P3-781 RSTLIB (Restore Library) Command . . . . . . . . P3-844
RMVSOCE (Remove Sphere of Control Entry) RSTLICPGM (Restore Licensed Program)
Command . . . . . . . . . . . . . . . . . . . . . P3-782 Command . . . . . . . . . . . . . . . . . . . . . P3-853
RMVSRVTBLE (Remove Service Table Entry) RSTOBJ (Restore Object) Command . . . . . . . P3-858
Command . . . . . . . . . . . . . . . . . . . . . P3-783 RSTSHF (Restore Bookshelf) Command . . . . . P3-867
| RMVSVRAUTE (Remove Server Authentication RSTS36F (Restore System/36 File) Command . . P3-869
| Entry) Command . . . . . . . . . . . . . . . . . P3-784 RSTS36FLR (Restore System/36 Folder) Command P3-874
RMVTAPCTG (Remove Tape Cartridge) Command P3-785 RSTS36LIBM (Restore System/36 Library Members)
RMVTCPHTE (Remove TCP/IP Host Table Entry) Command . . . . . . . . . . . . . . . . . . . . . P3-878
Command . . . . . . . . . . . . . . . . . . . . . P3-787 RSTUSFCNR (Restore Ultimedia System Facilities
RMVTCPIFC (Remove TCP/IP Interface) Command P3-788 Container) Command . . . . . . . . . . . . . . . P3-882
RMVTCPPORT (Remove TCP/IP Port Restriction) RSTUSRPRF (Restore User Profiles) Command . P3-885
Command . . . . . . . . . . . . . . . . . . . . . P3-789 RTVAUTLE (Retrieve Authorization List Entry)
RMVTCPRSI (Remove TCP/IP Remote System Command . . . . . . . . . . . . . . . . . . . . . P3-889
Information) Command . . . . . . . . . . . . . . P3-790 RTVBCKUP (Retrieve Backup) Command . . . . . P3-892
RMVTCPRTE (Remove TCP/IP Route) Command P3-791 RTVBNDSRC (Retrieve Binder Source) Command P3-894
| RMVTCPTBL (Remove TCP/IP Table) Command . P3-793 RTVCFGSRC (Retrieve Configuration Source)
RMVTRC (Remove Trace) Command . . . . . . . P3-794 Command . . . . . . . . . . . . . . . . . . . . . P3-896
RMVUSFCNNE (Remove Ultimedia System RTVCFGSTS (Retrieve Configuration Status)
Facilities Connection Entry) Command . . . . . . P3-796 Command . . . . . . . . . . . . . . . . . . . . . P3-898
RMVUSFDEVE (Remove Ultimedia System Facilities RTVCLNUP (Retrieve Cleanup) Command . . . . P3-900
Device Entry) Command . . . . . . . . . . . . . P3-797 RTVCLSRC (Retrieve CL Source) Command . . . P3-902
RMVUSFSVRE (Remove Ultimedia System Facilities RTVCURDIR (Retrieve Current Directory) Command P3-903
Server Entry) Command . . . . . . . . . . . . . P3-798 RTVDLOAUT (Retrieve Document Library Object
RMVWSE (Remove Work Station Entry) Command P3-799 Authority) Command . . . . . . . . . . . . . . . P3-904
RNM (Rename) Command . . . . . . . . . . . . . P3-801 RTVDLONAM (Retrieve Document Library Object
RNMCNNLE (Rename Connection List Entry) Name) Command . . . . . . . . . . . . . . . . . P3-908
Command . . . . . . . . . . . . . . . . . . . . . P3-802 RTVDOC (Retrieve Document) Command . . . . . P3-910
RNMDIRE (Rename Directory Entry) Command . . P3-803 RTVDSKINF (Retrieve Disk Information) Command P3-914
RNMDKT (Rename Diskette) Command . . . . . . P3-805 RTVDTAARA (Retrieve Data Area) Command . . . P3-915
RNMDLO (Rename Document Library Object) RTVGRPA (Retrieve Group Attributes) Command . P3-917
Command . . . . . . . . . . . . . . . . . . . . . P3-806 RTVJOBA (Retrieve Job Attributes) Command . . P3-920
RNMDSTL (Rename Distribution List) Command . P3-807 | RTVJRNE (Retrieve Journal Entry) Command . . . P3-925
RNMLANADPI (Rename Local Area Network RTVLIBD (Retrieve Library Description) Command P3-933
Adapter Information) Command . . . . . . . . . P3-808 RTVMBRD (Retrieve Member Description)
RNMM (Rename Member) Command . . . . . . . P3-809 Command . . . . . . . . . . . . . . . . . . . . . P3-934
RNMNCK (Rename Nickname) Command . . . . . P3-810 RTVMSG (Retrieve Message) Command . . . . . P3-938
RNMOBJ (Rename Object) Command . . . . . . . P3-811 RTVNETA (Retrieve Network Attributes) Command P3-941
RNMTCPHTE (Rename TCP/IP Host Table Entry) RTVOBJD (Retrieve Object Description) Command P3-947
Command . . . . . . . . . . . . . . . . . . . . . P3-813
Contents ix
| STRDSKRGZ (Start Disk Reorganization) STRTCP (Start TCP/IP) Command . . . . . . . . P3-1294
| Command . . . . . . . . . . . . . . . . . . . . P3-1209 STRTCPIFC (Start TCP/IP Interface) Command . P3-1296
STREDU (Start Education) Command . . . . . . P3-1210 STRTCPPTP (Start Point-to-Point TCP/IP)
STREML3270 (Start 3270 Display Emulation) Command . . . . . . . . . . . . . . . . . . . . P3-1297
Command . . . . . . . . . . . . . . . . . . . . P3-1211 STRTCPSVR (Start TCP/IP Server) Command . P3-1299
STRFMA (Start Font Management Aid) Command P3-1217 STRTIESSN (Start Technical Information Exchange
STRHOSTSVR (Start Host Server) Command . . P3-1218 Session) Command . . . . . . . . . . . . . . . P3-1302
STRIDD (Start Interactive Data Definition Utility) STRTRPMGR (Start Trap Manager) Command . P3-1303
Command . . . . . . . . . . . . . . . . . . . . P3-1220 STRUSF (Start Ultimedia System Facilities)
STRINFSKR (Start InfoSeeker) Command . . . . P3-1221 Command . . . . . . . . . . . . . . . . . . . . P3-1304
STRIPIIFC (Start IP over IPX Interface) Command P3-1223 TFRBCHJOB (Transfer Batch Job) Command . . P3-1305
STRIPSIFC (Start IP over SNA interface) TFRCTL (Transfer Control) Command . . . . . . P3-1307
Command . . . . . . . . . . . . . . . . . . . . P3-1224 TFRGRPJOB (Transfer to Group Job) Command P3-1309
STRIPX (Start IPX) Command . . . . . . . . . . P3-1225 TFRJOB (Transfer Job) Command . . . . . . . . P3-1311
STRIPXCCT (Start IPX Circuit) Command . . . . P3-1226 TFRM36 (Transfer to AS/400 Advanced 36
STRITF (Start Interactive Terminal Facility) Machine) Command . . . . . . . . . . . . . . . P3-1313
Command . . . . . . . . . . . . . . . . . . . . P3-1227 TFRPASTHR (Transfer Pass-Through) Command P3-1316
| STRJRNAP (Start Journal Access Path) Command P3-1228 TFRSECJOB (Transfer Secondary Job) Command P3-1317
| STRJRNPF (Start Journal Physical File) Command P3-1230 TRCCPIC (Trace CPI Communications) Command P3-1318
STRMOD (Start Mode) Command . . . . . . . . P3-1232 TRCICF (Trace ICF) Command . . . . . . . . . P3-1320
STRMSF (Start Mail Server Framework) Command P3-1233 TRCINT (Trace Internal) Command . . . . . . . P3-1322
STRM36 (Start AS/400 Advanced 36 Machine) TRCJOB (Trace Job) Command . . . . . . . . . P3-1326
Command . . . . . . . . . . . . . . . . . . . . P3-1234 TRCREX (Trace REXX) Command . . . . . . . P3-1329
STRM36PRC (Start AS/400 Advanced 36 Machine UNMOUNT (Remove Mounted File System)
Procedure) Command . . . . . . . . . . . . . . P3-1236 Command . . . . . . . . . . . . . . . . . . . . P3-1330
STRNFSSVR (Start Network File System Server) UPDPGM (Update Program) Command . . . . . P3-1331
Command . . . . . . . . . . . . . . . . . . . . P3-1238 UPDSRVPGM (Update Service Program)
| STRNWSAPP (Start Network Server Application) Command . . . . . . . . . . . . . . . . . . . . P3-1335
| Command . . . . . . . . . . . . . . . . . . . . P3-1240 UPDSYSINF (Update System Information)
STROBJCVN (Start Object Conversion) Command P3-1242 Command . . . . . . . . . . . . . . . . . . . . P3-1340
STRPASTHR (Start Pass-Through) Command . P3-1244 VFYAPPCCNN (Verify APPC Connection)
STRPEX (Start Performance Explorer) Command P3-1247 Command . . . . . . . . . . . . . . . . . . . . P3-1341
STRPFRCOL (Start Performance Collection) VFYCMN (Verify Communications) Command . . P3-1343
Command . . . . . . . . . . . . . . . . . . . . P3-1248 VFYIPXCNN (Verify IPX Connection) Command P3-1345
| STRPFRMON (Start Performance Monitor) VFYLNKLPDA (Verify Link Supporting LPDA-2)
| Command . . . . . . . . . . . . . . . . . . . . P3-1249 Command . . . . . . . . . . . . . . . . . . . . P3-1347
STRPGMMNU (Start Programmer Menu) VFYOPCCNN (Verify OptiConnect Connections)
Command . . . . . . . . . . . . . . . . . . . . P3-1254 Command . . . . . . . . . . . . . . . . . . . . P3-1349
| STRPGMPRF (Start Program Profiling) Command P3-1257 VFYOPT (Verify Optical) Command . . . . . . . P3-1350
STRPJ (Start Prestart Jobs) Command . . . . . P3-1258 VFYPRT (Verify Printer) Command . . . . . . . P3-1351
STRPRTEML (Start Printer Emulation) Command P3-1259 VFYTAP (Verify Tape) Command . . . . . . . . P3-1352
STRPRTWTR (Start Printer Writer) Command . . P3-1265 | VFYTCPCNN (Verify TCP/IP Connection)
STRQMPRC (Start Query Management Procedure) | Command . . . . . . . . . . . . . . . . . . . . P3-1353
Command . . . . . . . . . . . . . . . . . . . . P3-1269 VRYCFG (Vary Configuration) Command . . . . P3-1355
STRQMQRY (Start Query Management Query) WAIT (Wait) Command . . . . . . . . . . . . . . P3-1359
Command . . . . . . . . . . . . . . . . . . . . P3-1272 WRKACTJOB (Work with Active Jobs) Command P3-1360
STRQRY (Start Query) Command . . . . . . . . P3-1276 WRKALR (Work with Alerts) Command . . . . . P3-1363
| STRQSH (Start QSH) Command . . . . . . . . . P3-1277 WRKALRD (Work with Alert Descriptions)
STRQST (Start Question and Answer) Command P3-1279 Command . . . . . . . . . . . . . . . . . . . . P3-1366
STRREXPRC (Start REXX Procedure) Command P3-1280 WRKALRTBL (Work with Alert Tables) Command P3-1367
STRRMTSPT (Start Remote Support) Command P3-1282 | WRKAPPNSTS (Work with APPN Status)
STRRMTWTR (Start Remote Writer) Command . P3-1284 | Command . . . . . . . . . . . . . . . . . . . . P3-1369
STRSBS (Start Subsystem) Command . . . . . P3-1286 WRKAUT (Work with Authority) Command . . . P3-1371
STRSCHIDX (Start Search Index) Command . . P3-1288 WRKAUTL (Work with Authorization Lists)
STRSPTN (Start Support Network) Command . . P3-1289 Command . . . . . . . . . . . . . . . . . . . . P3-1372
STRSRVJOB (Start Service Job) Command . . . P3-1290 WRKBNDDIR (Work with Binding Directories)
STRSST (Start System Service Tools) Command P3-1291 Command . . . . . . . . . . . . . . . . . . . . P3-1373
STRS36 (Start System/36) Command . . . . . . P3-1292 WRKBNDDIRE (Work with Binding Directory
STRS36PRC (Start System/36 Procedure) Entries) Command . . . . . . . . . . . . . . . P3-1374
Command . . . . . . . . . . . . . . . . . . . . P3-1293 WRKBPTBL (Work with BOOTP Table) Command P3-1375
Contents xi
WRKNODLE (Work with Node List Entries) WRKPSFCFG (Work with Print Services Facility
Command . . . . . . . . . . . . . . . . . . . . P3-1474 Configurations) Command . . . . . . . . . . . P3-1520
WRKNTBD (Work with NetBIOS Descriptions) WRKQMFORM (Work with Query Management
Command . . . . . . . . . . . . . . . . . . . . P3-1475 Forms) Command . . . . . . . . . . . . . . . . P3-1521
WRKNWID (Work with Network Interface WRKQMQRY (Work with Query Management
Description) Command . . . . . . . . . . . . . P3-1476 Queries) Command . . . . . . . . . . . . . . . P3-1522
WRKNWSALS (Work with Network Server Aliases) WRKQST (Work with Questions) Command . . . P3-1523
Command . . . . . . . . . . . . . . . . . . . . P3-1477 WRKRDBDIRE (Work with Relational Database
WRKNWSD (Work with Network Server Directory Entries) Command . . . . . . . . . . P3-1524
Descriptions) Command . . . . . . . . . . . . P3-1478 WRKRDR (Work with Readers) Command . . . P3-1525
| WRKNWSENR (Work with Network Server User WRKREGINF (Work with Registration Information)
| Enrollment) Command . . . . . . . . . . . . . P3-1479 Command . . . . . . . . . . . . . . . . . . . . P3-1526
WRKNWSSSN (Work with Network Server WRKRMTDFN (Work with Remote Definitions)
Sessions) Command . . . . . . . . . . . . . . P3-1482 Command . . . . . . . . . . . . . . . . . . . . P3-1527
WRKNWSSTG (Work with Network Server WRKRPYLE (Work with System Reply List Entries)
Storage Spaces) Command . . . . . . . . . P3-1483 Command . . . . . . . . . . . . . . . . . . . . P3-1528
| WRKNWSSTS (Work with Network Server Status) WRKRTDCFG (Work with RouteD Configuration)
| Command . . . . . . . . . . . . . . . . . . . . P3-1484 Command . . . . . . . . . . . . . . . . . . . . P3-1529
WRKOBJ (Work with Objects) Command . . . . P3-1486 WRKSBMJOB (Work with Submitted Jobs)
WRKOBJLCK (Work with Object Locks) Command P3-1488 Command . . . . . . . . . . . . . . . . . . . . P3-1530
WRKOBJOWN (Work with Objects by Owner) WRKSBS (Work with Subsystems) Command . . P3-1531
Command . . . . . . . . . . . . . . . . . . . . P3-1490 WRKSBSD (Work with Subsystem Descriptions)
WRKOBJPGP (Work with Objects by Primary Command . . . . . . . . . . . . . . . . . . . . P3-1532
Group) Command . . . . . . . . . . . . . . . . P3-1491 WRKSBSJOB (Work with Subsystem Jobs)
WRKOPTDIR (Work with Optical Directories) Command . . . . . . . . . . . . . . . . . . . . P3-1534
Command . . . . . . . . . . . . . . . . . . . . P3-1492 WRKSCHIDX (Work with Search Indexes)
WRKOPTF (Work with Optical Files) Command . P3-1494 Command . . . . . . . . . . . . . . . . . . . . P3-1535
WRKOPTVOL (Work with Optical Volumes) WRKSCHIDXE (Work with Search Index Entries)
Command . . . . . . . . . . . . . . . . . . . . P3-1496 Command . . . . . . . . . . . . . . . . . . . . P3-1537
WRKOPCACT (Work with OptiConnect Activity) WRKSHRPOOL (Work with Shared Storage Pools)
Command . . . . . . . . . . . . . . . . . . . . P3-1497 Command . . . . . . . . . . . . . . . . . . . . P3-1538
WRKORDINF (Work with Order Information) WRKSOC (Work with Sphere of Control) Command P3-1539
Command . . . . . . . . . . . . . . . . . . . . P3-1498 WRKSPADCT (Work with Spelling Aid Dictionaries)
WRKORDRQS (Work with Order Requests) Command . . . . . . . . . . . . . . . . . . . . P3-1540
Command . . . . . . . . . . . . . . . . . . . . P3-1499 WRKSPLF (Work with Spooled Files) Command P3-1542
WRKOUTQ (Work with Output Queues) Command P3-1500 WRKSPLFA (Work with Spooled File Attributes)
WRKOUTQD (Work with Output Queue Command . . . . . . . . . . . . . . . . . . . . P3-1544
Description) Command . . . . . . . . . . . . . P3-1501 WRKSRVPGM (Work with Service Programs)
WRKOVL (Work with Overlays) Command . . . P3-1502 Command . . . . . . . . . . . . . . . . . . . . P3-1545
WRKPAGDFN (Work with Page Definitions) WRKSRVPVD (Work with Service Providers)
Command . . . . . . . . . . . . . . . . . . . . P3-1503 Command . . . . . . . . . . . . . . . . . . . . P3-1546
WRKPAGSEG (Work with Page Segments) WRKSRVTBLE (Work with Service Table Entry)
Command . . . . . . . . . . . . . . . . . . . . P3-1504 Command . . . . . . . . . . . . . . . . . . . . P3-1547
WRKPCLTBLE (Work with Protocol Table Entry) WRKSYSSTS (Work with System Status)
Command . . . . . . . . . . . . . . . . . . . . P3-1506 Command . . . . . . . . . . . . . . . . . . . . P3-1548
WRKPFCST (Work with Physical File Constraints) WRKSYSVAL (Work with System Values)
Command . . . . . . . . . . . . . . . . . . . . P3-1507 Command . . . . . . . . . . . . . . . . . . . . P3-1549
WRKPFRCOL (Work with Performance Collection) WRKS36 (Work with System/36) Command . . . P3-1551
Command . . . . . . . . . . . . . . . . . . . . P3-1508 WRKS36PGMA (Work with System/36 Program
WRKPGM (Work with Programs) Command . . . P3-1509 Attributes) Command . . . . . . . . . . . . . . P3-1552
WRKPGMTBL (Work with Program Tables) WRKS36PRCA (Work with System/36 Procedure
Command . . . . . . . . . . . . . . . . . . . . P3-1511 Attributes) Command . . . . . . . . . . . . . . P3-1553
WRKPNLGRP (Work with Panel Groups) WRKS36SRCA (Work with System/36 Source
Command . . . . . . . . . . . . . . . . . . . . P3-1512 Attributes) Command . . . . . . . . . . . . . . P3-1554
WRKPRB (Work with Problems) Command . . . P3-1513 WRKTAPCTG (Work with Tape Cartridges)
WRKPRDINF (Work with Product Information) Command . . . . . . . . . . . . . . . . . . . . P3-1555
Command . . . . . . . . . . . . . . . . . . . . P3-1518 WRKTBL (Work with Tables) Command . . . . . P3-1557
WRKPRTSTS (Work with Printing Status) WRKTCPPTP (Work with Point-to-Point TCP/IP)
Command . . . . . . . . . . . . . . . . . . . . P3-1519 Command . . . . . . . . . . . . . . . . . . . . P3-1558
Appendix A. Expanded Parameter Descriptions . P4-3 Appendix B. Font, Character Identifier, and Other
AUT Parameter . . . . . . . . . . . . . . . . . . P4-3 Values Supported for Different Printers . . . . P4-23
CLS Parameter . . . . . . . . . . . . . . . . . . P4-3 Font Attributes . . . . . . . . . . . . . . . . . . . P4-23
COUNTRY Parameter . . . . . . . . . . . . . . . P4-4 Types of Fonts . . . . . . . . . . . . . . . . . . P4-23
EXCHTYPE Parameter . . . . . . . . . . . . . . P4-7 Font Substitution . . . . . . . . . . . . . . . . . . P4-27
FILETYPE Parameter . . . . . . . . . . . . . . . P4-7 How To Use the Font Substitution Charts . . . P4-27
FRCRATIO Parameter . . . . . . . . . . . . . . P4-8 Font Substitution and the 4019 Printer . . . . . P4-27
IGCFEAT Parameter . . . . . . . . . . . . . . . P4-8 Font Substitution by Font ID Range . . . . . . . P4-34
JOB Parameter . . . . . . . . . . . . . . . . . . P4-9 Character Identifier (CHRID) Values Supported P4-35
LABEL Parameter . . . . . . . . . . . . . . . . P4-10 Lines Per Inch (LPI) Values Supported . . . . . . P4-40
MAXACT Parameter . . . . . . . . . . . . . . . P4-11 Characters Per Inch (CPI) Values Supported . . . P4-40
OBJ Parameter . . . . . . . . . . . . . . . . . P4-11
OBJTYPE Parameter . . . . . . . . . . . . . . P4-12 Appendix C. Parameter Values Used for Testing
OUTPUT Parameter . . . . . . . . . . . . . . . P4-15 and Debugging . . . . . . . . . . . . . . . . . . P4-43
PRTTXT Parameter . . . . . . . . . . . . . . . P4-16 Program-Variable Description . . . . . . . . . . P4-43
REPLACE Parameter . . . . . . . . . . . . . . P4-16 Basing-Pointer Description . . . . . . . . . . . P4-43
Scheduling Priority Parameters (JOBPTY, Subscript Description . . . . . . . . . . . . . . P4-43
OUTPTY, PTYLMT) . . . . . . . . . . . . . . P4-17 Qualified-Name Description . . . . . . . . . . . P4-43
SEV Parameter . . . . . . . . . . . . . . . . . P4-18 Rules for Qualified Name Description . . . . . . . P4-44
SPLNBR Parameter . . . . . . . . . . . . . . . P4-19
TEXT Parameter . . . . . . . . . . . . . . . . . P4-19 Bibliography . . . . . . . . . . . . . . . . . . . . . . H-1
VOL Parameter . . . . . . . . . . . . . . . . . P4-19
WAITFILE Parameter . . . . . . . . . . . . . . P4-20 Index . . . . . . . . . . . . . . . . . . . . . . . . . . X-1
Figures
1. Special Values for Workstation Objects . . . P3-292 5. ASCII Record Length Vlaues (RCDLEN
2. Special Values for Workstation Objects . . . P3-392 Parameter) . . . . . . . . . . . . . . . . . . P3-551
3. ANSI First-Character Forms-Control Codes . P3-534 6. Absolute Block Length (BLKLEN) Ranges . . P3-551
4. EBCDIC Record Length Vlaues (RCDLEN 7. Required RCDLEN/BLKLEN/BUFOFSET
Parameter) . . . . . . . . . . . . . . . . . . P3-551 Relation . . . . . . . . . . . . . . . . . . . P3-553
Tables
1. Lengths of Data Types That Can Be Coded . P1-9 7. OUTFILFMT(*TYPE3) Journal Entry Format P3-142
2. Lengths of Data Types That Cannot Be Coded P1-9 8. OUTFILFMT(*TYPE4) Journal Entry Format P3-143
3. DSPFD Type, File Attribute, Output File, and 9. Range of Values for ENTDTALEN Parameter P3-145
Record Format Combinations . . . . . . . . P3-112 10. Range of Values for NULLINDLEN Parameter P3-146
4. Physical File Field Values . . . . . . . . . . P3-122 11. DSPPRB Fields for Basic Problem Data
5. OUTFILFMT(*TYPE1) Journal Entry Format P3-142 (TYPE(*BASIC)) . . . . . . . . . . . . . . . P3-222
6. OUTFILFMT(*TYPE2) Journal Entry Format P3-142
Contents xiii
12. DSPPRB Fields for Possible Cause Data 30. NULLINDLEN(field-length) Journal Entry
(TYPE(*CAUSE)) . . . . . . . . . . . . . . . P3-224 Format for ENTFMT(*TYPE4) . . . . . . . . P3-655
13. DSPPRB Fields for Program Fix Data 31. NULLINDLEN(*VARLEN field-length) Journal
(TYPE(*FIX)) . . . . . . . . . . . . . . . . . P3-225 Entry Format for ENTFMT(*TYPE3) . . . . . P3-655
14. DSPPRB Fields for User Text Data 32. NULLINDLEN(*VARLEN field-length) Journal
(TYPE(*USRTXT)) . . . . . . . . . . . . . . P3-226 Entry Format for ENTFMT(*TYPE4) . . . . . P3-656
15. DSPPRB Fields for Supporting Data Identifier 33. Keyboard Mapping . . . . . . . . . . . . . . P3-876
Data (TYPE(*SPTDTA)) . . . . . . . . . . . P3-226 34. Keyboard Mapping . . . . . . . . . . . . . P3-1215
16. Valid Sector Size . . . . . . . . . . . . . . . P3-417 35. Actions Taken by the System When an Exit
17. Format for 5.25 Inch Diskette . . . . . . . . P3-418 Program Is Called . . . . . . . . . . . . . P3-1255
18. Keyboard Mapping . . . . . . . . . . . . . . P3-423 36. Keyboard Mapping . . . . . . . . . . . . . P3-1261
19. Language Feature Identifiers . . . . . . . . P3-424 | 37. Trace Code Table . . . . . . . . . . . . . P3-1323
20. Contents of the Files Before the Merge . . . P3-464 38. ISO X.400 Country Codes . . . . . . . . . . . P4-4
21. Contents of the Files After the Merge . . . . P3-464 39. DBCS Features Configurable on the IGCFEAT
22. Contents of the Files Before the Merge . . . P3-464 Parameter . . . . . . . . . . . . . . . . . . . P4-9
23. Contents of the Files After the Merge . . . . P3-464 40. Predefined Values and Default Library
24. Query Field Structure . . . . . . . . . . . . P3-482 Locations for OS/400 Object Types . . . . . P4-12
25. *TYPE1 Journal Entry Format . . . . . . . . P3-653 41. Object Types Used by Commands Containing
26. *TYPE2 Journal Entry Format . . . . . . . . P3-653 the OBJTYPE Parameter . . . . . . . . . . P4-14
27. NULLINDLEN(*ENTFMT) Journal Entry 42. Font Information . . . . . . . . . . . . . . . P4-24
Format for ENTFMT(*TYPE3) . . . . . . . . P3-654 43. Font Substitution . . . . . . . . . . . . . . . P4-28
28. NULLINDLEN(*ENTFMT) Journal Entry 44. Font Substitution by Font ID Range. . . . . . P4-35
Format for ENTFMT(*TYPE4) . . . . . . . . P3-654 45. CHRID Values and Applicable Printers (CHRID
29. NULLINDLEN(field-length) Journal Entry Parameter) . . . . . . . . . . . . . . . . . . P4-35
Format for ENTFMT(*TYPE3) . . . . . . . . P3-655 46. Lines per Page (LPI Parameter) . . . . . . . P4-40
47. Characters per Line (CPI Parameter) . . . . P4-41
┌─\NONE──────────────┐
55──CMD──PROMPT──(──┼─message-identifier─┼──)──────────────────────────────────────────────────────────────────────────────────5%
└─'prompt-text'──────┘
PROMPT Parameter acters, for the prompt text that is shown when the
Specifies the prompt text, if any, that is included in the command is being prompted. If a message having the
heading (title) of the prompt display for the command specified identifier cannot be found in the message file
being defined. The prompt text further describes the specified in the PMTFILE parameter of the Create
name of the command. For example, in the CRTLIB Command (CRTCMD) command, the message identifier
prompt heading, “Create Library (CRTLIB) Prompt,” the itself is used as the prompt text.
words Create Library would be specified as the prompt
'prompt-text': Specify the prompt text that is displayed
text in this PROMPT parameter.
during the command prompting. It must be a character
Note: Prompt text for each of the parameters in this string of no more than 30 characters, enclosed in apos-
command can be specified in the PROMPT trophes.
parameters of the PARM, ELEM, and QUAL
Note: Variables cannot be coded for this parameter.
command definition statements. They specify
the prompt text for the parameters, just as the
PROMPT parameter in the CMD statement spec-
ifies the prompt text for the command (in the
Example
heading). CMD PROMPT(UCDððð1)
*NONE: No prompt text is included in the displayed
heading of the prompt when the command is being This statement describes a command that is prompted with
prompted. additional text in the display heading; the prompt text comes
from the message identified by UCD0001.
message-identifier: Specify the message identifier that
specifies the message, containing no more than 30 char-
If a parameter has a default value and the parameter is not specified, the checking differs depending on whether the DEP
statement is performing a specification check or a relational check. If a specification check is made on an unspecified param-
eter (checking for the presence of a value for that parameter), the system assumes that no value was specified, and the default
value is not used. If a relational check is made on an unspecified parameter, the default value is used as the parameter value.
55──DEP──CTL──(──┬─\ALWAYS───────────────────────────────────────────────────┬──)───────────────────────────────────────────────5
(1) ───────────────────────────────────────────┤
├─keyword-name───
└─&keyword-name──relational-operator───(1) ─┬─value───────────┬─┘
(2) ┘
└─&keyword-name───
┌──
─────────────────────────────────────────────────────────────┐
5──PARM─── 6┬─keyword-name───
(1) ─(─── (1) ───────────────────────────────────────────┬┴───
(3) ──)─────────────────────────────────────────────5
└─&keyword-name──relational-operator─── (1) ─┬─value───────────┬─┘
(2) ┘
└─&keyword-name───
5──┬─────────────────────────────────────────────────────┬──┬─────────────────────────────────────┬────────────────────────────5%
│ ┌─\ALL─────────────────────────────┐ │ │ ┌─\NONE──────────────┐ │
└─NBRTRUE──(──┴─relational-operator──number-true─┴──)─┘ └─MSGID──(──┴─message-identifier─┴──)─┘
Notes:
1 Must not be defined as TYPE(*NULL).
3 A maximum of 25 repetitions
The names of one or more parameters that will be for NBRTRUE, then two, and only two, of the parameter
tested to determine if they are present. dependencies must be true for the PARM statement.
One or more test relationships of keyword values to Note: Variables cannot be coded for this parameter.
the values of other keywords or constants. A
MSGID Parameter
maximum of 25 parameters can be specified for the
Specifies the message identifier of an error message in
PARM parameter. Keywords specified in this
a message file that is sent to the user if all the specified
parameter must not be defined as TYPE(*NULL).
parameter dependencies have not been satisfied.
keyword-name: Specify the keyword name of each *NONE: No special message is sent. Instead, a
parameter that must have a value specified for it.
message generated by the command analyzer is sent to
&keyword-name relational-operator value: Specify the the user.
keyword name of each parameter followed by a rela-
message-identifier: Specify the message identifier of the
tional operator and a value to be tested. An ampersand
error message sent to the user if all the dependencies
must precede the keyword name to indicate that the
for this statement are not met. Messages whose identi-
value of the keyword is tested. The value specification
fiers begin with the 3-character prefixes CPF or CPD are
must be no longer than 32 characters.
retrieved from the IBM-supplied message file
If the value being used for testing comparison has been QCPFMSG. All other messages specified here are
specified as a special value or single value (SPCVAL or retrieved from the message file identified by the MSGF
SNGVAL parameters of the PARM statement), the to- parameter on the CRTCMD command which is used to
value must be used rather than the from-value. create the command being defined with these dependen-
cies.
If the controlling parameter is a qualified name, the first
qualifier will be used for the compare value. If the con- Note: Variables cannot be coded for this parameter.
trolling parameter is a list, then the first element of the
list will be used for the compare value. If the first
element is a list, then the first element of that list is Examples
used, and so on. DEP CTL(&TYPE \EQ LIST) PARM(ELEMLIST)
&keyword-name relational-operator &keyword-name:
If TYPE(LIST) is specified, the ELEMLIST parameter must be
Specify the keyword name of one parameter followed by
specified.
a relational operator and the keyword name of another
parameter whose value is compared with the value of DEP CTL(FILE) PARM(VOL LABEL) NBRTRUE(\EQ 2)
the first parameter. A keyword defined with
If the FILE parameter is specified, both the VOL and LABEL
PASSVAL(*NULL) cannot be specified.
parameters must be specified.
NBRTRUE Parameter DEP CTL(GLOOP) PARM(J1 D J2) NBRTRUE(\EQ 1)
Specifies the number of parameter dependencies
defined in the associated PARM statement that must be If the GLOOP parameter is specified, a value must be speci-
true to satisfy the control condition. fied for one (and only one) of the J1, D, and J2 parameters.
*ALL: All the parameter dependencies specified in the DEP CTL(&LIB \EQ MYLIB)
PARM statement must be true to satisfy the control con- PARM((&PASSWORD \eq XYZ5)
dition. (&USRPRF \EQ BðBJ))
NBRTRUE(\GE 1) MSGID(MSGðð1)
relational-operator number-true: Specify a relational
operator and a number that specifies the number of If the LIB parameter equals MYLIB, then the PASSWORD
parameter dependencies that must be true to satisfy the parameter must equal XYZ5, or the USRPRF parameter
specified relation. For example, if (*EQ 2) is specified must equal BOBJ. Otherwise, message MSG001 will be
sent to the user.
A list element is the value that represents one value among a group of values organized in a specific order in a list. If all of the
list elements are not of the same type, one ELEM statement must be used for each element that appears in the list being
defined. If all the elements are of the same type (a simple list), individual ELEM statements are not required. For a simple list,
specify the number of elements in the list on the MAX parameter of the PARM statement.
The order in which the ELEM statements are entered into the source file determines the position of the elements in the list.
The first ELEM statement (for the first list element) must have a statement label that matches TYPE (statement-label) on the
PARM or ELEM statements for the same list. The remaining ELEM statements in the list must be unlabeled. Lists of elements
having different values can be nested to the depth of three levels including the highest level. A maximum of 300 elements can
be included in one list.
Note: The ELEM statement contains certain parameters and predefined values that can be used only when an IBM-supplied
command processing program (CPP) is called by the command being defined. Because there are limitations in some
high-level languages, these values may not be useful in the definition statements of user-defined commands. If the
entire parameter is for IBM-supplied commands only, these parameters and values are identified by placing the phrase,
“(For IBM-supplied commands)” immediately following the parameter keyword or the predefined value to which it
applies.
55──ELEM──TYPE(──┬─\DEC────────────┬──)──┬────────────────────────────────────────┬──┬─────────────────────┬────────────────────5
├─\LGL────────────┤ └─LEN(──┬─length────────────────────┬──)─┘ └─CONSTANT(──value──)─┘
├─\CHAR───────────┤ └─length──decimal-positions─┘
├─\NAME───────────┤
├─\SNAME──────────┤
├─\CNAME──────────┤
├─\PNAME──────────┤
├─\GENERIC────────┤
├─\DATE───────────┤
├─\TIME───────────┤
├─\HEX────────────┤
├─\ZEROELEM───────┤
├─\INT2───────────┤
├─\INT4───────────┤
├─\VARNAME────────┤
└─statement-label─┘
5──┬────────────────────┬──┬────────────────────┬──┬───────────────────────────────────────────────────────────┬────────────────5
│ ┌─\NO──┐ │ └─DFT(────value────)─┘ │ ┌──
───────┐ │
└─RSTD(──┴─\YES─┴──)─┘ ├─VALUES(───6─value─┴───
(1) ──)──────────────────────────────────┤
├─REL(──relational-operator──┬─&keyword-name─┬──)───────────┤
│ └─value─────────┘ │
└─RANGE(──┬─&from-keyword-value─┬──┬─&to-keyword-value─┬──)─┘
└─lower-limit-value───┘ └─upper-limit-value─┘
5──┬───────────────────────────────────────────────────────┬──┬───────────────────────────────────────────────────────┬─────────5
│ ┌──
────────────────────────────────────┐ │ │ ┌──
────────────────────────────────────┐ │
└─SPCVAL(───6─(────from-value────┬──────────┬──)─┴─── 6─(────from-value────┬──────────┬──)─┴───
(1) ──)─┘ └─SNGVAL(─── (1) ──)─┘
└─to-value─┘ └─to-value─┘
5──┬─────────────────────────────┬──┬─────────────────────────────┬──┬────────────────────────┬──┬──────────────────────┬───────5
│ ┌─ð──────────────┐ │ │ ┌─1──────────────┐ │ │ ┌─\YES─┐ │ │ ┌─\YES─┐ │
└─MIN(──┴─minimum-number─┴──)─┘ └─MAX(──┴─maximum-number─┴──)─┘ └─ALWUNPRT(──┴─\NO──┴──)─┘ └─ALWVAR(──┴─\NO──┴──)─┘
5──┬───────────────────┬──┬──────────────────────┬──┬───────────────────────┬──┬────────────────────┬───────────────────────────5
│ ┌─\NO──┐ │ │ ┌─\NO──┐ │ │ ┌─\NO─────┐ │ │ ┌─\NO──┐ │
└─PGM(──┴─\YES─┴──)─┘ └─DTAARA(──┴─\YES─┴──)─┘ └─FILE(──┼─\IN─────┼──)─┘ └─FULL(──┴─\YES─┴──)─┘
├─\OUT────┤
├─\UPD────┤
├─\INOUT──┤
└─\UNSPFD─┘
5──┬────────────────────┬──┬─────────────────────────────────────┬──┬───────────────────────┬──┬────────────────────────┬───────5
│ ┌─\NO──┐ │ │ ┌─\NO───────────────────┐ │ │ ┌─\NO──┐ │ │ ┌─\MONO────┐ │
└─EXPR(──┴─\YES─┴──)─┘ │ │ ┌─\INT2─┐ │ │ └─PASSATR(──┴─\YES─┴──)─┘ └─CASE(──┴─\MIXED───(3) ┴──)─┘
(2)
└─VARY(──┴───\YES──────┼───────┼─┴──)─┘
└─\INT4─┘
5──┬───────────────────────────┬──┬────────────────────────────────────┬────────────────────────────────────────────────────────5
│ ┌─\YES────┐ │ │ ┌─\VALUES────────────┐ │
└─DSPINPUT(──┼─\PROMPT─┼──)─┘ └─CHOICE(──┼─\NONE──────────────┼──)─┘
└─\NO─────┘ ├─\PGM───────────────┤
├─message-identifier─┤
└─'choices-text'─────┘
5──┬────────────────────────────────────────────────────┬──┬────────────────────────────────────┬──────────────────────────────5%
│ ┌─\NONE───────────────────────────┐ │ │ ┌─\NONE──────────────┐ │
│ │ ┌─\LIBL/────────┐ │ │ └─PROMPT(──┼─message-identifier─┼──)─┘
└─CHOICEPGM(──┴─┼───────────────┼──program-name─┴──)─┘ └─'prompt-text'──────┘
├─\CURLIB/──────┤
└─library-name/─┘
Notes:
1 A maximum of 300 repetitions
2 *YES is valid only for the following parameter types: *CHAR, *NAME, *SNAME, *CNAME, *PNAME, *GENERIC, *LGL,
TYPE Parameter Path names are used in the integrated file system. For
Specifies the type of list element being defined. The more information on using the list element *PNAME, see
element can be an integer, a decimal or logical value, or the Integrated File System Introduction book.
a quoted or unquoted character string that can be a
*GENERIC: The list element is a character string that
name, label, date, or time. Enter one of the following
represents a generic name. A generic name contains a
values to specify the type of element.
maximum of 255 characters followed by an asterisk (*)
Note: For more information on names (below), see or 256 characters without an asterisk and must conform
"Rules for Specifying Names" in chapter 2. to the rules for generic names. The name identifies a
group of objects whose names all begin with the charac-
*NAME: The list element is a character string that
ters preceding the *. If an * is not included, the system
represents a basic name. The maximum length of the
assumes that the generic name is a complete object
name is 256 characters; the first character must be A-Z,
name.
$, @, or #. The remaining characters can be the same
as the first character but can also include the numbers 0 *DATE: The list element is a character string that repre-
through 9, underscores (_), and periods (.). The name sents a date. When entering the command, the year
can also be a string of characters starting and ending may be specified in either 2 digits or 4 digits. If a 2-digit
with double quotation marks ("). If a special value is year is specified, the date is assumed to be in the range
used (as in *LIBL or *NONE), it must be specified in the of January 1, 1940 through December 31, 2039. If a
SPCVAL parameter. 4-digit year is specified, the date may be in the range of
August 24, 1928 through May 9, 2071. When the date
*SNAME: The list element is a character string that
is passed to the CPP, it is always passed in the format
represents a simple name. The maximum length of the
name is 256 characters; the first character must be A-Z,
Cyymmdd, where C = century, yy = year, mm = month,
| and dd = day. The century digit is set to 0 for years
$, @, or #. The remaining characters can be the same
| 19xx, and it is set to 1 (one) for years 20xx. When a
as the first but may also include the numbers 0 through
date value is specified in this ELEM statement, it must
9 and underscores (_). Periods (.) are not allowed. If a
| be specified without quotation marks in one of the fol-
special value is used (such as *LIBL or *NONE), it must
| lowing formats: mmddyy, mmddyyyy, or Cyymmdd. If
be specified in the SPCVAL parameter.
the user enters a date when the command is run, it must
*CNAME: The list element is a character string that be entered in the job date format. The job date sepa-
represents a communications name. The maximum rator specifies the optional separator character that must
length of the name is 256 characters; the first character be used when the date is entered. If the separator char-
must be A-Z, $, @, or #. The remaining characters can acter is used, the date must be enclosed in apostrophes.
be the same as the first character but may also include
*TIME: The list element is a character string that repre-
the numbers 0 through 9. Periods (.) and underscores
sents a time. It is in the format hhmmss, where hh =
(_) are not allowed. If a special value is used (such as
hours, mm = minutes, and ss = seconds. It is passed to
*LIBL or *NONE), it must be specified in the SPCVAL
the CPP in a 6-byte character string as hhmmss.
parameter.
Values specified in this statement must be in the format
*PNAME: The list element is a character string that hhmmss. The job time separator specifies the optional
represents a path name. The path name can be separator character that can be used when the time is
enclosed in apostrophes. If the path name contains any entered. If the separator character is used, the time
special characters (not including an asterisk (*)), it must must be enclosed in apostrophes.
be enclosed in apostrophes. The maximum length of
the path name character string is 5000 characters.
acter constant is specified in this parameter, it can be no this list is optional. The DFT parameter is not valid if the
longer than 32 characters. CONSTANT is not valid with CONSTANT parameter is specified. A default cannot be
TYPE(*ZEROELEM), EXPR(*YES), or MAX(>1), or if specified if TYPE(*ZEROELEM) is specified; in that
DFT was coded for ELEM. case, an assumed default is passed.
If a constant is specified for the element being defined, If DFT is not specified, the default assumed is as
no prompt text can be specified for the PROMPT param- follows, depending on the specified element type:
eter of this ELEM statement. However, the other ele-
Assumed Element
ments of the list parameter (of which this list element is
Default Types
a part) are still prompted, and their values (along with
this constant value) are still passed to the CPP as a list. 0 *DEC *INT2 *INT4
Variables cannot be coded for this parameter. *ZEROELEM
For an element that does not allow multiple like values, accepted. A maximum greater than one (1) is not valid
only zero (0) for optional and one (1) for required can be if the CONSTANT parameter is also specified.
specified as the minimum number of values.
ALWUNPRT Parameter
For an element that allows multiple like values because Specifies whether this ELEM statement should accept
a value greater than one (1) is specified in the MAX the hexadecimal characters X'FF' or those in the range
parameter, zero (0) indicates that no values must be of X'00' to X'3F'. This parameter is valid only for
entered; therefore, it is an optional element. A value TYPE(*CHAR) or TYPE(*X).
equal to or greater than one (1) indicates the minimum
*YES: Allows any characters to be sent to the display or
number of values that must be entered for the element.
printer.
Therefore, it is a required element. The value specified
for MIN cannot exceed the value specified for the MAX *NO: Does not allow unprintable characters to be
parameter. passed to the command processing program.
The number specified tells how many list elements are ALWVAR Parameter
required in another list. If MIN is not specified, zero (0) Specifies whether to allow variable names for the
is assumed, meaning that the element is optional. element. If TYPE was specified as *VARNAME,
0: The list element is optional; it does not have to be *ZEROELEM, *NULL, or statement-label, ALWVAR(*NO)
entered. is not allowed.
minimum-number: Specify the minimum number of ele- *YES: Allows the use of variable names for the
ments that must be specified in the nested list. If 1 is element.
the assigned value, it specifies that at least one value is *NO: Does not allow the use of variable names for the
required for the element. If a number greater than one element.
(1) is specified, the element contains a list that must
have at least as many elements as the number speci- PGM Parameter
fied. Specifies whether the list element is a program name.
PGM(*YES) is valid only for a statement-label, *CHAR,
MAX Parameter *NAME, *SNAME, *CNAME, and *GENERIC types. The
Specifies, if this ELEM statement is defining a simple list specification of the PGM(*YES) parameter has no effect
element, the maximum number of elements that this list on the element being defined by the ELEM statement; it
element can have in its nested list. If a value greater only indicates to the compiler that the value for this
than 1 is specified, the element is capable of accepting element is a program name. This information is stored
multiple like values (that is, a simple nested list). All so it can be included in the output of the Display
values entered for this element (at the time the Program References (DSPPGMREF) command.
command is run) must satisfy the validity checking
*NO: The element defined in this ELEM statement is
requirements specified by the values specified in the
not a program name.
other parameters on this ELEM statement.
*YES: The element is a program name.
Note: The values for a nested list are passed consec-
utively, preceded by a 2-byte binary value that DTAARA Parameter
indicates the number of values entered in the list Specifies whether the list element is a data area name.
element by the user. CL programs do not DTAARA(*YES) is valid only for statement-label, *CHAR,
support the handling of binary values in vari- *NAME, *SNAME, *CNAME, and *GENERIC types. The
ables, but you can use the %BINARY built-in specification of the DTAARA(*YES) parameter has no
function to examine the length. effect on the element being defined by the ELEM state-
1: The list element accepts only one value; there is no ment; it only indicates to the CL compiler that the value
nested list. for this element is a data area. This information is
stored so it can be included in the output of the Display
maximum-number: Specify the maximum number of ele- Program References (DSPPGMREF) command.
ments that the list element can accept. The specified
maximum must be greater than or equal to the value *NO: The element defined in this ELEM statement is
specified in MIN, and less than or equal to 300. If the not a data area name.
maximum is greater than one (1) and TYPE is not a *YES: The element is a data area name.
statement label that identifies a QUAL statement or
another ELEM statement, the parameter–which is also FILE Parameter
an element –is a simple list of like values (that is, each Specifies whether the list element is a file name and the
element in the list has the same requirements, such as expected use of the file. The element can be specified
type and length). If TYPE(statement-label) is specified as the name of a file that has a specific use so that, at
and it points to the label of a QUAL statement or another CL compile time, the names can be used to get file ref-
ELEM statement, MAX should only be specified greater erence information about where the files are used. FILE
than 1 if a list of lists or a list of qualified names is to be is valid only if the value for TYPE is statement-label,
*CHAR, *NAME, *SNAME, *CNAME, or *GENERIC. *YES: The element value passed to the CPP is pre-
The specification in the FILE parameter has no effect on ceded by a field that indicates the number of characters
the list element being defined by the ELEM statement; it actually specified for the parameter. *YES is valid only
only indicates to the CL compiler that the value for this for the following parameter types: *CHAR, *NAME,
element is a file name and what type of file it is. This *SNAME, *CNAME, *PNAME, *GENERIC, *LGL,
information is stored so it can be included in the output *VARNAME, *CMD, *CMDSTR, and *X.
of the DSPPGMREF (Display Program References)
Note: The length value is the actual number of charac-
command. One of the following types of files can be
ters entered for the command parameter with
specified:
trailing blanks removed. The length value
*NO: The list element defined in this ELEM statement is passed may be different than the defined param-
not a file name. eter length or the declared variable length. The
length of the field containing the character string
*IN: The list element is an input file name.
data is determined by the defined length for the
*OUT: The list element is an output file name. parameter or the declared LEN for CL Program
*UPD: The list element is an update file name. variables. The length value defines how many
characters in the character string data field were
*INOUT: The list element value is the name of a file to
actually entered for the command parameter.
be used for both input and output.
Element 2: Value Length
*UNSPFD: The list element value is the name of a file,
but its use cannot be specified. *INT2: The element value is an integer passed as a
2-byte signed binary number.
FULL Parameter
*INT4: The element value is an integer passed as a
Specifies whether the number of characters in the list
4-byte signed binary number.
element must be exactly the same as the number speci-
fied in the LEN parameter (if specified) or its default PASSATR Parameter
length (if LEN is not specified). (For IBM-supplied commands) Specifies whether an attri-
*NO: The number of characters in the list element can bute byte is to be passed to the CPP with the list
be less than that specified by the LEN parameter. element data. PASSATR is not valid for
TYPE(statement-label) or for TYPE(*ZEROELEM).
*YES: The number of characters in the list element
must equal the number specified by the LEN parameter *NO: No attribute byte is passed with the list element.
or the default length for that type. The exact length is *YES: An attribute byte is passed with the list element;
valid only for element types *LGL, *CHAR, *NAME, the attribute byte indicates whether the data value came
*SNAME, *CNAME, *GENERIC, *VARNAME, and *HEX. from the default, the data type of the value, and (if
TYPE(*CHAR) was specified) whether the character
EXPR Parameter
string was enclosed in apostrophes.
Specifies whether the list element can accept an
expression containing a character concatenation. Valid CASE Parameter
character concatenation operators are as follows: Specifies whether the value that is passed to the CPP is
changed from lowercase to uppercase, or is preserved in
Concatenation *CAT or, ||
Blank insertion with concatenation *BCAT or, |>
the case specified on the command parameter.
Blank truncation with concatenation *TCAT or, |< *MONO: The element value is changed from lowercase
to uppercase. Single quoted parameters with apostro-
*NO: The element value cannot be a concatenation phes preserve the case whether or not this value is
expression. specified.
*YES: The element value can be a concatenation *MIXED: The element value is preserved in the case
expression. *YES is not valid if a value is specified for specified on the command parameter. This value can
the CONSTANT parameter. be specified only for *CHAR and *PNAME parameter
VARY Parameter types.
Specifies whether the list element value passed to the DSPINPUT Parameter
CPP is preceded by a length value that indicates the Specifies whether the keyword value is shown (dis-
number of characters entered for the element's value. played) in the job log or on a prompt display.
This parameter may be specified as a single value (*NO) DSPINPUT(*PROMPT) and DSPINPUT(*NO) are valid
or as a list of two values (elements). only for the following element types: *CHAR, *NAME,
*NO: The element value is not preceded by a length *SNAME, *CNAME, *GENERIC, *DEC, *LGL, *INT2,
value. *INT4, *DATE, *TIME, and *HEX.
Element 1: Return Length Value Note: The DSPINPUT parameter will have no effect on
the job log entries for a database reader job, for
imbedded commands (for example, a command text for the possible values field. The message file
submitted on the SBMJOB command), or for specified on the PMTFILE parameter of the Create
commands executed using the QCMDEXC or Command (CRTCMD) command is used to find the
QCAEXEC APIs. message.
*YES: The element value is shown both on the prompt 'choices-text': Specify no more than 30 characters,
screen and in the job log. enclosed in apostrophes.
*PROMPT: The element value is shown on the prompt CHOICEPGM Parameter
screen but not in the job log. Specifies the name of the program that is called during
*NO: The element value is not shown in either the job the prompting to fill in the possible choices text and the
log or a prompt screen. When a previously entered permissible values during prompting. This parameter
command is retrieved, the nondisplayed field entries must be specified only if CHOICE(*PGM) is specified.
must be retyped and their previous values are not *NONE: No program is identified to fill in the possible
retrievable. When a job log entry is created, the nondis- choices text and permissible values.
played field is replaced by empty parentheses ().
The possible library values are:
CHOICE Parameter
*LIBL: The library list is used to locate the program
Specifies the text that is displayed to the right of the
name.
prompt line of each parameter on the prompt screen.
Up to 30 characters of text can be displayed. *CURLIB: The current library for the job is used to
locate the program name. If no library is specified
*VALUES: Each possible value is displayed in the pos-
as the current library for the job, the QGPL library is
sible values field, separated by a comma and a space.
used.
If values are specified for the Default, Single value, or
Special value parameters, the first value displayed is the library-name: Specify the name of the library where
default value; the next value is a single value, and the the program name is located.
values following that are special values. If there are too
many values to fit in 30 characters, the last value is fol-
program-name: Specify the name of the program to be
called during prompting to fill in the possible choices text
lowed by three periods.
or to supply a permissible value.
Examples of possible values text follow:
If any exception occurs when the program is called, no
If *NO is specified on the RSTD parameter and possible-choices text will be left blank, and the list of
*DEC is specified on the TYPE parameter and the permissible values will be obtained from the command.
RANGE parameter is not specified, the word
PROMPT Parameter
"Number" is displayed in the possible values field.
Specifies the prompt text, if any, that is used for the list
The resulting line will appear in the form: Number,
element being defined in this ELEM statement. The
*XXX, *YYY, *ZZZ...
prompt text describes the element to the user, who may
If *NO is specified on the RSTD parameter and enter a response to the information displayed. Prompt
*DEC is specified on the TYPE parameter and the text cannot be specified if TYPE(*ZEROELEM) is speci-
RANGE parameter is specified, the range of pos- fied or if a constant value is specified in the CONSTANT
sible values is displayed in the possible values field. parameter.
The resulting line will appear in the form: a-b,
*NONE: No prompt text is displayed for the list element
*XXX, *YYY, *ZZZ (where a and b are numerals
defined by this ELEM statement. The input field still
defining the range).
asks for this list element, but no text is displayed with it.
If *YES is specified on the RSTD parameter, the
possible values displayed are determined by the
message-identifier: Specify the message identifier that
identifies the prompt text message of up to 30 charac-
VALUES parameter, the SNGVAL parameter, and
ters displayed when the program is asking for the list
the SPCVAL parameter. The resulting line will
element. If a message having the specified identifier
appear in the form: *XXX, *YYY, *ZZZ...
cannot be found in the message file contained in the
*NONE: No values are displayed. PMTFILE parameter of the Create Command (CRTCMD)
command, the message identifier itself is used as the
*PGM: A program that is called determines the values
prompt text.
that are displayed. The program that is called is identi-
fied in CHOICEPGM parameter. 'prompt-text': Specify the prompt text displayed when
the program is asking for the list element. The text must
message-identifier: Specify the message ID of the
be a character string of no more than 30 characters,
message used to retrieve the message containing the
enclosed in apostrophes.
5──┬──────────────────────────────────────┬──┬──────────────────────────────────────────────────────┬───────────────────────────5
│ ┌─\VALUES────────────┐ │ │ ┌─\NONE───────────────────────────┐ │
└─CHOICE──(──┼─\NONE──────────────┼──)─┘ │ │ ┌─\LIBL/────────┐ │ │
├─\PGM───────────────┤ └─CHOICEPGM──(──┴─┼───────────────┼──program-name─┴──)─┘
├─message-identifier─┤ ├─\CURLIB/──────┤
└─'choices-text'─────┘ └─library-name/─┘
5──┬───────────────────────────────────┬──┬──────────────────────────────────────────────────────┬──────────────────────────────5
│ ┌─\NONE───────────┐ │ │ ┌─\NONE───────────────────────────┐ │
└─PMTCTL──(──┼─\PMTRQS─────────┼──)─┘ │ │ ┌─\LIBL/────────┐ │ │
└─statement-label─┘ └─PMTCTLPGM──(──┴─┼───────────────┼──program-name─┴──)─┘
├─\CURLIB/──────┤
└─library-name/─┘
5──┬─────────────────────────┬──┬──────────────────────────────────────────────────────────────────┬───────────────────────────5%
│ ┌─\NO──┐ │ │ ┌─\NONE──────────────────────────────────────────┐ │
└─KEYPARM──(──┴─\YES─┴──)─┘ └─PROMPT──(──┴─┬─message-identifier─┬──relative-prompt-number─┴──)─┘
└─'prompt-text'──────┘
Notes:
1 A maximum of 300 repetitions
2 *YES is valid only for the following parameter types: *CHAR, *NAME, *SNAME, *CNAME, *PNAME, *GENERIC, *LGL,
*VARNAME, *CMD, *CMDSTR, and *X. *YES must be specified if PASSATR(*YES) and RTNVAL(*YES) are specified.
3 This value can be specified only on *CHAR and *PNAME parameter types.
*NAME: The parameter value is a character string that *GENERIC: The parameter value is a character string
represents a basic name. The maximum length of the that represents a generic name. A generic name con-
name is 256 characters; the first character must A-Z, $, tains a maximum of 255 characters followed by an
@, or #. The remaining characters can be the same as asterisk (*) or 256 characters without an asterisk and
the first character but can also include the numbers 0 must conform to the rules for generic names. The name
through 9, underscores (_), and periods (.). The name identifies a group of objects whose names all begin with
can also be a string of characters starting and ending the characters preceding the *. If an * is not included,
with double quotation marks ("). If a special value is the system assumes that the generic name is a com-
used (as in *LIBL or *NONE), it must be specified in the plete object name.
SPCVAL parameter. *CMDSTR: The parameter value is a command string
*SNAME: The parameter value element is a character that is checked for validity by the command analyzer. It
string that represents a simple name. The maximum is passed to the CPP as a character string.
length of the name is 256 characters; the first character Note: Selective prompting is not allowed with the
must be A-Z, $, @, or #. The remaining characters can *CMDSTR parameter.
be the same as the first but may also include the
*DATE: The parameter value is a character string that
numbers 0 through 9 and underscores (_). Periods (.)
represents a date. When entering the command, the
are not allowed. If a special value is used (such as
year may be specified with either 2 digits or 4 digits. If a
*LIBL or *NONE), it must be specified in the SPCVAL
2-digit year is specified, the date is assumed to be in the
parameter.
range of January 1, 1940 through December 31, 2039.
*CNAME: The parameter value is a character string that If a 4-digit year is specified, the date may be in the
represents a communications name. The maximum range of August 24, 1928 through May 9, 2071. When it
length of the name is 256 characters; the first character is passed to the CPP, it is always passed in the format
Cyymmdd, where C = century, yy = year, mm = month, *VARNAME: (For IBM-supplied commands) The
| and dd = day. The century digit is set to 0 for years parameter value is a CL variable name that is passed as
| 19xx, and it is set to 1 (one) for years 20xx. When a a character string. The name can contain a maximum of
date value is specified in this PARM statement, it must 11 characters, including the ampersand (&).
| be specified in one of the following formats: mmddyy,
*CMD: (For IBM-supplied commands) The parameter
| mmddyyyy, or Cyymmdd. When a user enters a date in value is a command. For example, the IF command has
the command at run time, it must be entered in the job
a parameter called THEN whose value must be another
date format. The job date separator specifies the
command. The command is checked for validity by the
optional separator character that can be used when the
command analyzer.
date is entered. If the separator character is used, the
date must be enclosed in apostrophes. *NULL: The parameter value is to be a null pointer,
which can be used as a constant place holder. A DEP
*TIME: The parameter value is a character string that
statement or the REL and RANGE keywords of other
represents a time. It is entered in the format hhmmss.
PARM statements may not reference the value of a
It is passed to the CPP in a 6-byte character string as
parameter defined with TYPE(*NULL).
hhmmss. The job time separator specifies the optional
separator character that can be used when the time is statement-label: Specify a qualified name or a mixed list
entered. If the separator character is used, the time of values. The statement label specified here by the
must be enclosed in apostrophes. TYPE parameter is the statement label that identifies the
first of a series of QUAL or ELEM statements that further
*CHAR: The parameter value is a character string that
describe the qualified name or the mixed list being
(optionally) can be enclosed in apostrophes. If the char-
defined by this PARM statement.
acter string contains any special characters (not
including an asterisk (*)), it must be enclosed in apostro- LEN Parameter
phes. The maximum length of the character string is Specifies the length of the parameter value that is
5000 characters. passed to the CPP. LEN is not allowed if TYPE was
specified as *INT2, *INT4, *DATE, *TIME, *CMD,
*DEC: The parameter value is a packed decimal
*ZEROELEM, *NULL, or statement-label. With other
number.
TYPE specifications, this parameter has the following
*LGL: The parameter value is a logical value, either a applications:
one ('1') or a zero ('0').
If TYPE(*DEC) was specified, the decimal length is
*HEX: The parameter value is in hexadecimal form. specified in the form (length1 length2), where
The specified characters must be 0 through F. They are length1 specifies the total number of digits in the
converted to hexadecimal (EBCDIC) characters (2 hex value (including the decimal portion), and length2
digits per byte), right-justified, and padded on the left specifies the number of allowable decimal digits to
with zeros. If the value is enclosed in apostrophes, an the right of the decimal point. (The value for
even number of digits is required. If the value is not length2 is optional. Zero is assumed if it is not
enclosed in apostrophes, an even number of digits is not entered.)
required.
If TYPE(*CHAR), TYPE(*NAME), TYPE(*SNAME),
*ZEROELEM: The parameter is always considered as a
TYPE(*CNAME), TYPE(*CMDSTR), or
list of zero elements, for which no value can be specified
TYPE(*VARNAME) was specified, only length1 is
in the command. It is used to prevent a value from
specified. It identifies the number of characters
being entered for a parameter that is a list even though
passed.
the CPP expects one. For example, if two commands
use the same CPP, one command could pass a list for a If TYPE(*HEX) was specified, only length1 is speci-
parameter and the other command may not have any fied. This length specifies the number of characters
values to pass. The second command would be coded passed after the hexadecimal digits have been con-
with TYPE(*ZEROELEM). verted to character digits. Because 2 hexadecimal
digits are converted to 1 decimal digit, the number
*X: (For IBM-supplied commands) The parameter value
of hexadecimal digits converted is twice the value of
is a character string, variable name, or numeric value.
this length.
The value is passed as a numeric value if it contains
only digits, a "+" or "–" sign, and/or a decimal point; oth- If TYPE(*X) was specified, the LEN parameter is
erwise, it is passed as a character string. used as follows:
*INT2: The parameter value is an integer that is passed – For character data, length1 specifies the
as a 2-byte signed binary number. CL programs do not minimum length to be passed. If a longer value
support binary values in variables. is entered, the entire value is passed.
*INT4: The parameter value is an integer that is passed – For decimal data, length2 and length3 specify
as a 4-byte signed binary number. CL programs do not the length and decimal positions for a constant
support binary values in variables.
CONSTANT Parameter
Maximum
Data Type Length Length Passed Specifies that a value is passed to the CPP as a con-
stant when the command being defined is processed.
*DATE1 8 7
The parameter does not appear externally on the
*TIME2 8 6 command. The value specified in this parameter (if any)
*ZEROELEM 0 0 must satisfy the requirements specified by the TYPE,
*INT23 6 2 LEN, VALUES, REL, RANGE, SPCVAL, and FULL
parameters. As noted in the LEN parameter chart, if a
*INT44 11 4
character constant is specified in this parameter, it can
*CMD Any Length needed be no longer than 32 characters.
If a constant is specified for the parameter being
defined, no prompt text can be specified for the
PROMPT parameter in the PARM statement, because
the parameter will not be prompted.
The CONSTANT parameter is not valid with specified. If TYPE(*VARNAME) is specified, a default
TYPE(*CMD), TYPE(*NULL), TYPE(*ZEROELEM), special value can be specified; a default variable name
MAX(>1), DFT, RTNVAL(*YES), or EXPR(*YES). cannot be specified.
Variables cannot be coded for this parameter. If DFT is not specified and MIN(0) and RTNVAL(*NO)
are specified, then the default assumed is as follows,
RSTD Parameter
depending on the specified type:
Specifies whether the value entered for the parameter
(specified in the PARM statement) is restricted to only Assumed Parameter
one of the values given in the VALUES, SPCVAL, or Default Types
SNGVAL parameters, or whether the value can be any
0 *DEC *INT2 *INT4
value that satisfies the requirements specified by the
TYPE, LEN, REL, RANGE, SPCVAL, SNGVAL, and *ZEROELEM
FULL parameters. '0' *LGL
*NO: The value entered for the parameter specified by zeros *DATE *TIME *HEX
KWD in this PARM statement can be anything that
matches the requirement specified by parameters TYPE, blanks *CHAR *NAME *SNAME
LEN, REL, RANGE, SPCVAL, SNGVAL and FULL in *CNAME *PNAME *GENERIC
this PARM statement.
*VARNAME *CMDSTR
*YES: The value entered for the parameter specified by
null *CMD *X *NULL
KWD in this PARM statement is restricted to one of the
values in the VALUES parameter, or to one of the from- An assumed default value is not displayed by the
values in the SPCVAL or SNGVAL parameters. *YES command prompt; a blank input field is shown instead.
cannot be specified if TYPE(statement-label), If a default is specified in the DFT parameter, it is dis-
TYPE(*CMD), TYPE(*NULL), TYPE(*ZEROELEM), played by the prompt exactly as specified.
TYPE(*X), or RTNVAL(*YES) is specified.
value: Specify the default value that meets the specified
DFT Parameter requirements or that is one of the values specified in the
Specifies the default value that is assigned to the param- VALUES, SPCVAL, or SNGVAL parameters.
eter if a value is not specified by the user. That is, the Variables cannot be coded for this value.
default value is used as the value of the parameter if the
user omits the parameter while entering the command or VALUES Parameter
if *N is entered as the parameter value. The default Specifies a list of up to 300 constants (fixed values) from
value must satisfy one of the following: which one constant can be entered as the value of the
parameter named in the KWD parameter. The VALUES
It must match the requirements specified by the parameter is valid only if all of the following are true:
TYPE, LEN, REL, RANGE, and FULL parameters. RSTD(*YES) is specified, both the RANGE and REL
It must be one of the from-values in the SPCVAL or parameters are not specified, and each constant
SNGVAL parameters. matches the attributes specified by the TYPE, LEN, and
FULL parameters. As noted in the LEN parameter chart,
If the default is a character constant, it can have no
character constants specified in this parameter can be
more than 32 characters (as noted in the LEN
no longer than 32 characters. Enter the constants (not
parameter chart).
more than 300) that can be specified as the value of the
If RSTD(*YES) is specified, it must be in the list of parameter. The VALUES parameter is not valid if
values in the VALUES parameter or in the list of TYPE(*CMD), TYPE(*CMDSTR), TYPE(*X),
from-values of the SPCVAL or SNGVAL parame- TYPE(*NULL), TYPE(statement-label),
ters. TYPE(*VARNAME), or TYPE(*ZEROELEM), or if
RTNVAL(*YES) is specified.
It must be a from-value in the SNGVAL parameter if
the parameter being defined is a list of unlike values REL Parameter
or it is a qualified name. This is true when a state- Specifies the relationship between the parameter value
ment label is specified for TYPE; the label is used to of this parameter and the value of a constant or another
identify a QUAL or ELEM statement. parameter. If a keyword is specified, it must be pre-
ceded by an ampersand (&) to indicate that it is the
The DFT parameter is not valid if CONSTANT is speci-
value of the keyword that is to be tested. The value
fied. The DFT parameter is valid only if MIN is 0, which
associated with the referenced keyword, not the user-
means the parameter named in the KWD parameter is
specified value, is the value passed to the CPP. If the
optional. A default cannot be specified if
relationship is with another parameter whose value is a
RTNVAL(*YES) is specified; instead, a null pointer is
list of values or a qualified name, only the first value is
passed for the default. A default cannot be specified if
used in the comparison.
TYPE(*CMD), TYPE(*ZEROELEM), or TYPE(*NULL) is
To specify the relationship, enter one of the following As noted in the LEN parameter chart, character con-
relational operators followed by either a constant or the stants specified in this parameter can be no longer than
keyword name (KWD) of the other parameter (which 32 characters.
must be preceded by an &).
Variables can be coded for this element.
*LT less than
SPCVAL Parameter
*LE less than or equal to Specifies a list of up to 300 entries that define special
*EQ equal to values that can be entered on the parameter named in
the KWD parameter. Each entry specifies a character
*GE greater than or equal to string (a from-value) that can be entered even though it
*GT greater than may not meet all validity checking requirements. If the
entered character string matches the from-value of one
*NL not less than
of the entries, and the to-value is specified, the string is
*NE not equal to replaced with the to-value and is then passed to the
CPP without further checking. If the to-value is omitted,
*NG not greater than
the from-value is passed to the CPP. SPCVAL is not
The REL parameter is not valid if RTNVAL(*YES) is valid if TYPE is specified as *CMD, *CMDSTR, *X,
specified, if either RANGE or VALUES is specified, or if *NULL, statement-label, or *ZEROELEM, or if
TYPE is specified as *LGL, *VARNAME, *CMD, RTNVAL(*YES) is specified.
*CMDSTR, *X, *ZEROELEM, *NULL, or a statement
The from-value is a character string, but the to-value can
label.
be anything that is passable. However, for
If a character type is specified by TYPE(*CHAR), the | TYPE(*DATE), the to-value must be specified unquoted
EBCDIC value of the character string is used as an | in mmddyy, mmddyyyy, or Cyymmdd format. If a CL
unsigned integer in the comparison. As noted in the variable is used for the from-value, its type must be
LEN parameter chart, if a character constant is specified *CHAR. The to-value must be no longer than LEN spec-
in this parameter, it can be no longer than 32 characters. ifies and, if TYPE is *DEC, *INT2, or *INT4, the type of
the to-value must be the same; if TYPE is a character
Variables can be coded for this element.
type (such as *CHAR, *LGL, or *DATE), the to-value
RANGE Parameter must be a character string. As noted in the LEN param-
Specifies the range (the limits) for the value of the eter chart, character constants specified in this param-
parameter. The parameter value must be greater than eter can be no longer than 32 characters. If a to-value
or equal to the lower limit value specified, and it must be is not specified, the from-value must be passable.
less than or equal to the upper limit value specified. For If a to-value of *CURLIB is specified, the name of the
example, 15 would be valid if RANGE was specified as current job library is passed to the CPP instead of the
(0 16). value *CURLIB. If the from-value is *CURLIB and no
For nonnumeric data types, such as *CHAR, the range to-value is specified, or if the to-value is *CURLIB and it
of values and the data specified are left-justified and is enclosed in apostrophes, the value *CURLIB is
padded on the right with blanks. A numeric range passed to the CPP.
should not be used to define an interval for nonnumeric Variables cannot be coded for this element.
data unless leading zeros are specified or the data is
only 1 character long. SNGVAL Parameter
Specifies a list of up to 300 single values that can be
Variables can be coded for this element.
specified for a parameter being defined as a mixed list
The upper and lower limits of the range can be specified or as a qualified name (when a statement label is speci-
either by a keyword representing the value or by the fied for TYPE), or specifies that it is to accept two or
value itself. If a keyword is specified, it must be pre- more values as defined by the MAX parameter. Any
ceded by an ampersand (&) to indicate that the value of one of the single values can be used instead of a list of
the keyword is to be tested. The value of its parameter values or a qualified name that the parameter is defined
at the time of the check is used to determine the range. to accept. Each entry specifies a character string (a
The value that is tested is the value passed to the CPP, from-value) that can be entered. If an entered character
not the user-specified value. If the keyword identifies a string matches the from-value of one of the entries and
list of values or a qualified name, only the first value is the to-value is specified, the data is replaced with the
used as the range limit. A keyword may not reference a to-value and is passed to the CPP without further
parameter that is defined with PASSVAL(*NULL), and checking. If the to-value is omitted, the from-value is
RANGE is not valid with PASSVAL(*NULL). passed to the CPP.
The RANGE parameter is not valid if RTNVAL(*YES) is The to-value (or the from-value, if the to-value is
specified, if either REL or VALUES is specified, or if omitted) must be passable, as specified in the SPCVAL
TYPE is specified as *LGL, *VARNAME, *CMD, parameter. As noted in the LEN parameter chart, char-
*CMDSTR, *X, *ZEROELEM, *NULL, or statement label.
acter constants specified in this parameter can be no values entered for this parameter (at the time the
longer than 32 characters. SNGVAL can be specified command is run) must satisfy the validity checking
only if the MAX parameter is greater than 1 or TYPE is requirements specified by the other parameter values on
specified as a statement label of a QUAL or ELEM state- this PARM statement.
ment. Each single value can only substitute for a list of
Note: The values for a list parameter are passed con-
values or a qualified name; it cannot be a list element or
secutively, preceded by a 2-byte binary value
qualifier. It is passed as the first and only element of the
that indicates the number of values entered in
list.
the parameter by the user. CL programs do not
SNGVAL is not valid if RTNVAL(*YES) is specified or if support the handling of binary values in vari-
TYPE is specified as *CMD, *CMDSTR, *NULL, ables.
*ZEROELEM, or *X.
1: The parameter accepts only one value; the param-
If a to-value of *CURLIB is specified, the name of the eter is not a list parameter.
current job library, instead of the value *CURLIB, is
maximum-number: Specify the maximum number of ele-
passed to the CPP. If the from-value is *CURLIB and
ments that the list parameter can accept. The specified
no to-value is specified, or if the to-value is *CURLIB
maximum must be greater than or equal to the value
and it is enclosed in apostrophes, the value *CURLIB is
specified in MIN, and less than or equal to 300. If the
passed to the CPP.
maximum is greater than 1 and TYPE is not a statement
Variables cannot be coded for this element. label that identifies a QUAL or ELEM statement, the
parameter is a simple list of like elements (that is, each
MIN Parameter
element in the list has the same requirements, such as
Specifies the minimum number of values that must be
type and length). If TYPE(statement-label) is specified
entered for the parameter being defined.
and it points to the label of an ELEM or QUAL state-
For a parameter that does not allow multiple like values, ment, MAX should only be specified greater than 1 if a
only zero (0) for optional and 1 for required can be spec- list of lists or a list of qualified names is accepted. A
ified as the minimum number of values. maximum greater than 1 is not valid if TYPE is specified
as *CMD, *CMDSTR, or *NULL, or if RTNVAL(*YES) or
Note: Required parameter statements must precede
CONSTANT is specified.
optional statements. If required parameter state-
ments are not specified first, the system ALWUNPRT Parameter
assumes that the specified parameter is optional, Specifies whether this PARM statement accepts the
and the minimum number of values for required hexadecimal characters X'FF' or those in the range of
parameters is ignored. X'00' to X'3F'. This parameter is valid only for
For a parameter that allows multiple like values TYPE(*CHAR) or TYPE(*X).
(because a value greater than 1 is specified for the MAX *YES: Any characters can be passed to the CPP and
parameter), zero (0) indicates that no values need be sent to the display or printer.
entered; therefore, it is an optional parameter. A value
*NO: Unprintable characters cannot be passed to the
equal to or greater than one (1) indicates the minimum
CPP.
number of values that must be entered for the param-
eter; therefore, it is a required parameter. The value ALWVAR Parameter
exceeds the value specified for the MAX parameter and Specifies whether to allow variable names for the param-
cannot exceed 1 for TYPE(*NULL). eter. If TYPE was specified as *VARNAME,
0: The parameter is optional; it does not have to be *ZEROELEM, *NULL, or statement-label, ALWVAR(*NO)
entered. is not allowed.
minimum-number: Specify the minimum number of ele- *YES: Variable names can be used for the parameter.
ments that must be specified for this parameter (named *NO: Variable names cannot be used for the parameter.
by the KWD parameter). If 1 is the assigned value, it
specifies that at least one value is required for the PGM Parameter
parameter. If a number greater than 1 is specified, the Specifies whether this parameter element is a program
parameter is a list that must have at least as many ele- name. PGM(*YES) is valid only for statement-label,
ments as the number specified. *CHAR, *NAME, *SNAME, *CNAME, and *GENERIC
types. The specification of the PGM(*YES) parameter
MAX Parameter does not have any effect on the parameter element
Specifies, if this PARM statement is defining a simple list being defined by the PARM statement; it only indicates
parameter, the maximum number of list elements that to the compiler that the value for this parameter is a
this list parameter can contain. If a value greater than 1 program name. This information is stored so it can be
is specified, the parameter is capable of accepting mul- included in the output of the Display Program Refer-
tiple like values (that is, a simple list). This support is ences (DSPPGMREF) command.
primarily intended for IBM-supplied commands. All
*NO: The parameter defined in this PARM statement is *NO: The number of characters in the parameter can be
not a program name. less than that specified by the LEN parameter.
*YES: The parameter defined in this PARM statement is *YES: The number of characters in the parameter must
a program name. equal the number specified by LEN or the default length
for that type. The exact length is valid only for the fol-
DTAARA Parameter
lowing parameter types: *LGL, *CHAR, *NAME,
Specifies whether the parameter is a data area name.
*SNAME, *CNAME, *GENERIC, *VARNAME, and *HEX.
DTAARA(*YES) is valid only for statement-label, *CHAR,
FULL(*YES) is valid with RTNVAL(*YES).
*NAME, *SNAME, *CNAME, and *GENERIC types. The
specification of the DTAARA(*YES) parameter does not EXPR Parameter
have any effect on the parameter being defined by the Specifies whether the parameter named in the KWD
PARM statement; it only indicates to the compiler that parameter can accept an expression containing a char-
the value for this parameter is a data area. This infor- acter concatenation or a built-in function (%SUBSTRING
mation is stored so it can be included in the output of or %BIN). Valid character concatenation operators are
the Display Program References (DSPPGMREF) as follows:
command.
Concatenation *CAT or, ||
*NO: The parameter defined in this PARM statement is Blank insertion with concatenation *BCAT or, |>
not a data area name. Blank truncation with concatenation *TCAT or, |<
*YES: The parameter defined in this PARM statement is
Restrictions: Expressions are not allowed on parame-
a data area name.
ters where the TYPE parameter specifies *CMDSTR,
FILE Parameter *CMD, *ZEROELEM, *NULL, or statement-label.
Specifies whether the parameter is a file name and the *NO: The parameter value cannot be a concatenation
expected use of the file. The parameter can be speci- expression or a built-in function.
fied as the name of a file that has a specific use so that,
at compile time, the names can be used to get file refer- *YES: The parameter value can be a concatenation
ence information about where the files are used. The expression or a built-in function.
specification in the FILE parameter does not have any VARY Parameter
effect on the operation of the parameter being defined; it Specifies whether the value that is passed to the CPP is
only indicates to the compiler that the value for this preceded by a length value that indicates the number of
parameter is a file name and what type of file it is. This characters entered for the command parameter.
information is stored so it can be included in the output
of the Display Program References (DSPPGMREF) The length value is the actual number of characters
command. The FILE parameter is valid only if *CHAR, entered for the command parameters with trailing blanks
*NAME, *SNAME, *CNAME, *GENERIC, or statement- removed. The length value passed may be different
label is specified for the TYPE parameter. The FILE than the defined parameter length or the declared vari-
parameter is not valid with RTNVAL(*YES). One of the able length. The length of the field containing the char-
following types of files can be specified: acter string data is determined by the defined length for
the parameter or the declared LEN for CL program vari-
*NO: The parameter (named by KWD) is not a file ables. The length value defines how many characters in
name. the character string data field were actually entered for
*IN: The parameter value is an input file name. the command parameter. This parameter may be speci-
fied as a single value (*NO) or as a list of two values
*OUT: The parameter value is an output file name.
(elements).
*UPD: The parameter value is an update file name.
*NO: The parameter value is not preceded by a length
*INOUT: The parameter value is the name of a file that value.
is used for both input and output.
Element 1: Return Length Value:
*UNSPFD: The parameter value is the name of a file,
*YES: The parameter value passed to the CPP is pre-
but its use cannot be specified.
ceded by a field that indicates the number of characters
The use of the file must match the type of file specified. actually specified for the parameter.
For example, if *IN is specified, the file can be used only
Note: *YES is valid only for the following parameter
for input; if *UPD is specified, it can be used only to
types: *CHAR, *NAME, *SNAME, *CNAME,
update existing records.
*PNAME, *GENERIC, *LGL, *VARNAME, *CMD,
FULL Parameter *CMDSTR, and *X. *YES must be specified if
Specifies whether the number of characters in the PASSATR(*YES) and RTNVAL(*YES) are speci-
parameter must be exactly the same as the number fied.
specified in the LEN parameter (if specified) or its default Element 2: Value Length:
length (if LEN is not specified).
*NONE: No values are displayed. The conditions specified on the referred to PMTCTL
statement have been met.
*PGM: A program that is called determines the values
that are displayed. The program that is called is identi- A value was entered for the parameter before the
fied in CHOICEPGM parameter. prompt was called.
message-identifier: Specify the message ID of the PMTCTLPGM Parameter
message used to retrieve the message containing the Specifies the qualified name of the program called to
text for the possible values field. The message file convert the value specified for the parameter into a
specified on the PMTFILE parameter of the Create value used on a PMTCTL statement. This parameter is
Command (CRTCMD) command is used to find the valid only on parameters that are referred to in the CTL
message. parameter of a PMTCTL statement.
'choices-text': Specify no more than 30 characters, *NONE: There is no program to convert the parameter
enclosed in apostrophes. value for prompt control statements. If the parameter is
specified in a PMTCTL statement, the actual value is
CHOICEPGM Parameter
compared in the PMTCTL statement.
Specifies the qualified name of the program that is called
during the prompting to fill in the possible choices text The possible library values are:
and the permissible values during prompting. This
*LIBL: The library list is used to locate the program
parameter must be specified if CHOICE(*PGM) is speci-
name.
fied, and it may not be specified otherwise.
*CURLIB: The current library for the job is used to
*NONE: No program is identified to fill in the possible
locate the program name. If no library is specified
choices text and permissible values.
as the current library for the job, the QGPL library is
The possible library values are: used.
*LIBL: The library list is used to locate the program library-name: Specify the name of the library where
name. the program name is located.
*CURLIB: The current library for the job is used to program-name: Specifies the qualified name of the
locate the program name. If no library is specified program called to convert the parameter value.
as the current library for the job, the QGPL library is
used. KEYPARM Parameter
Specifies whether the parameter is a key parameter.
library-name: Specify the name of the library where Key parameters can be used only if a prompt override
the program name is located.
program is specified on the PMTOVRPGM parameter of
program-name: Specify the name of the program called the CRTCMD or CHGCMD commands. The prompt
during prompting to fill in the possible choices text or a override program overrides the command processing
permissible value. program (CPP) by showing only the key parameters on
the initial prompt display. Values must be input for these
If an exception occurs when the program is called, no
parameters before the remaining parameters are shown.
possible choices text will be left blank, and the list of
The remaining parameters are shown on the prompt
permissible values will be taken from the command.
display with the actual values, instead of *SAME or
PMTCTL Parameter *PRV.
Specifies how prompting is controlled for this parameter. *NO: The parameter is not a key parameter.
Prompting may be conditioned by another parameter,
*YES: The parameter is a key parameter. The following
specified by a PMTCTL statement referred to by label in
rules are followed if *YES is specified:
this parameter, or called for by pressing the F10 key.
*NONE: Specifies that this parameter is always 1. Key parameters must be placed before non-key
prompted, unless it is omitted due to selective parameters in the command definition statement.
prompting. 2. Key parameters appear on the prompt display in the
*PMTRQS: Specifies that this parameter is not same order as they appear in the command defi-
prompted unless: nition statement.
3. Key parameters are valid only if a prompt override
The user requests additional parameters.
program is specified on the PMTOVRPGM param-
A value was entered for the parameter before the eter of the CRTCMD or CHGCMD commands; if a
prompt was called. prompt override program is not specified, the key
parameters are treated as non-key parameters, and
statement-label: Specifies the label of the PMTCTL
a warning message is issued.
statement that is used to determine whether this param-
eter is prompted. The parameter is not prompted
unless:
4. Key parameters must not be the only parameters in for before parameters having no prompt numbers and
the command definition statement; if they are, a that have PMTCTL(*PMTRQS) coded.
warning message is sent.
'prompt-text' relative-prompt-number: Specify the prompt
PROMPT Parameter text that is displayed when the parameter is prompted.
Specifies the prompt text, if any, that is used for the The text must be a character string of no more than 30
parameter named by the KWD parameter. The prompt characters, enclosed in apostrophes. An optional rela-
text further describes the keyword and input field to the tive prompt number can be specified with the prompt
user, who may enter a response to the information dis- text, the same as for the message identifier option.
played. For example, the prompt text for the TYPE
parameter on the Create Library (CRTLIB) command is: Examples
Library Type (*PROD *TEST):
PARM KWD(X) TYPE(\DEC) LEN(2) MIN(1) REL(\GT 5)
When the prompt for the command is displayed, the
prompt for the TYPE parameter is: The value for the parameter named X, a 2-digit decimal
Library Type (*PROD *TEST): TYPE *PROD number, must be entered. The value must be greater than 5.
The underscored field is the prompt input field where the PARM KWD(CLASS) TYPE(\CHAR) LEN(1)
user enters the value for the TYPE parameter. When DFT(A) VALUES(A B C) RSTD(\YES)
the prompt is displayed, the prompt input field contains
the default value (*PROD in this example). Prompt text The value of the parameter named CLASS must be A, B, or
cannot be specified if TYPE(*ZEROELEM) or C, if entered. If it is not present, A is assumed.
TYPE(*NULL) is specified or if a constant value is speci-
PARM KWD(MAXREC) TYPE(\DEC) LEN(3)
fied in the CONSTANT parameter.
MIN(1) RANGE(&MINREC 999)
*NONE: No prompt text is displayed for the parameter
defined by this PARM statement. This parameter is still The value of the MAXREC parameter must be entered as a
asked for by its keyword name, but no text is displayed decimal number of 3 digits or less, with no digits to the right
with it. of the decimal point. The value must be greater than or
equal to the value entered for parameter MINREC and also
message-identifier relative-prompt-number: Specify the
must be less than or equal to 999.
message identifier that specifies the message that con-
tains the prompt text of up to 30 characters that is dis- PARM KWD(FILES) TYPE(\NAME) MIN(2) MAX(5)
played when the parameter is prompted. If a message
having the specified identifier cannot be found in the The FILES parameter is a homogeneous list that contains 2
message file specified in the PMTFILE parameter of the to 5 names.
Create Command (CRTCMD) command, the message
identifier itself is used as the prompt text. PARM KWD(INVFNAME) TYPE(\NAME) DFT(\ALL)
SNGVAL((\ALL XXX)) VALUES(DEPT1 DEPT2 DEPT3)
Optionally, a relative prompt number can be specified FILE(\UPD) MIN(ð) MAX(3) RSTD(\YES)
with the message identifier. The relative prompt number PROMPT(USRððð2 1)
specifies the order in which parameter keywords are to
be asked for. This order affects only the order of The value of the parameter named INVFNAME can be a list
prompting, not the order in which the parameters are of up to three file names of which DEPT1, DEPT2, DEPT3,
passed to the CPP. Parameters having prompt numbers and *ALL are the valid choices. If *ALL is entered, no other
are asked for before parameters having no prompt values can be entered for the parameter. If this parameter is
numbers. Parameters having no prompt numbers and omitted, file name XXX is passed to the command pro-
that do not have PMTCTL(*PMTRQS) coded are asked cessing program. If this parameter is entered through the
prompt, the prompt text, as stored in the message file, is dis-
played and *ALL is listed as the default.
The PMTCTL statement (or the first PMTCTL statement if there is more than one) must have a statement label that matches
the label referred to in the PMTCTL parameter of one or more PARM statements in the command definition source.
55──PMTCTL──CTL──(──keyword-name──)──COND──(──┬─\SPCFD───────────────────────────┬──)───────────────────────────────────────────5
├─\UNSPCFD─────────────────────────┤
│ ┌──
───────────────────────────┐ │
└──6─relational-operator-value─┴───
(1) ─┘
5──┬───────────────────────────────────────────────┬──┬────────────────────────┬───────────────────────────────────────────────5%
│ ┌─\ALL───────────────────────┐ │ │ ┌─\AND─┐ │
└─NBRTRUE──(──┴─relational-operator-number─┴──)─┘ └─LGLREL──(──┴─\OR──┴──)─┘
Note:
1 A maximum of 50 repetitions
CTL Parameter parameter. Valid values are *GT, *EQ, *GE, *NL, *LT,
Specifies the name of the parameter that controls the *NE, *LE, and *NG.
prompting. The value of the parameter specified here is
LGLREL Parameter
compared to the value specified in the COND parameter.
Specifies, when multiple PMTCTL statements are in a
If the PMTCTLPGM parameter is coded for the param-
group, the logical relationship of the statement to the
eter specified here, the value returned by the program
previous statements in the group. This parameter is not
specified in the PMTCTLPGM parameter is compared to
allowed on the first PMTCTL statement in a group.
the values specified in the COND parameter. If the
parameter specified here is a list or qualified name, only *AND: This statement is in an AND relationship of the
the first list element or qualifier is compared. statement to the previous statements in the group.
The order in which the QUAL statements are entered into the source file determines the positional order in which the qualifiers
must be specified and passed to the validity checker and the command processing program (CPP).
The QUAL statement (or only the first QUAL statement if there is more than one) must have a statement label that matches the
statement label value that must be specified in a PARM or ELEM statement for which the qualifier is being defined. The
| qualifiers for the parameter or list element are then entered on the command in the form value3/value2/value1 where values 1
| through 3 are qualifiers described by a QUAL statement.
Note: In the System/38 environment, the values are passed in sequential order with periods as delimiters. An example of this
form is value1.value2.value3.
The values are passed with each value padded to its defined length and with the delimiters (slashes or periods) removed.
Note: The QUAL statement contains certain parameters and predefined values that can be used only when IBM-supplied
CPPs are called by the command being defined. Limitations in some high-level languages reduce the usefulness of
these values in the definition statements of user-defined commands. These parameters and values are identified by the
phrase “(For IBM-supplied commands)” that immediately follows the parameter keyword (if the entire parameter is for
IBM-supplied commands only) or the predefined value to which it applies.
(P) ──┬───────────────────────┬──┬──────────────────────┬───────────────5
55──QUAL──TYPE──(──┬─\NAME────┬──)──┬───────────────────┬───
├─\SNAME───┤ └─LEN──(──length──)─┘ └─CONSTANT──(──value──)─┘ │ ┌─\NO──┐ │
├─\CNAME───┤ └─RSTD──(──┴─\YES─┴──)─┘
├─\GENERIC─┤
├─\CHAR────┤
├─\INT2────┤
└─\INT4────┘
5──┬────────────────────────────────────────────────────────────┬──┬───────────────────────────────────────────────┬────────────5
│ ┌──
───────┐ │ └─SPCVAL──(──┬─from-value──────────────────┬──)─┘
└─DFT──(──┬─VALUES───6─value─┴───
(1) ────────────────────────┬──)─┘ │ ┌──
──────────────────────┐ │
├─REL──relational-operator-value──────────────┤ └──6─from-value──to-value─┴───
(1) ─┘
└─RANGE──lower-limit-value──upper-limit-value─┘
5──┬──────────────────────────┬──┬────────────────────────┬──┬──────────────────┬──┬──────────────────────┬─────────────────────5
│ ┌─\YES─┐ │ │ ┌─\YES─┐ │ │ ┌─ð─┐ │ │ ┌─\NO──┐ │
└─ALWUNPRT──(──┴─\NO──┴──)─┘ └─ALWVAR──(──┴─\NO──┴──)─┘ └─MIN──(──┴─1─┴──)─┘ └─FULL──(──┴─\YES─┴──)─┘
5──┬──────────────────────┬──┬──────────────────────┬──┬─────────────────────────┬──┬─────────────────────────────┬─────────────5
│ ┌─\NO──┐ │ │ ┌─\NO──┐ │ │ ┌─\NO──┐ │ │ ┌─\YES────┐ │
└─EXPR──(──┴─\YES─┴──)─┘ └─VARY──(──┴─\YES─┴──)─┘ └─PASSATR──(──┴─\YES─┴──)─┘ └─DSPINPUT──(──┼─\PROMPT─┼──)─┘
└─\NO─────┘
5──┬──────────────────────────────────────┬──┬──────────────────────────────────────────────────────┬───────────────────────────5
│ ┌─\VALUES────────────┐ │ │ ┌─\NONE───────────────────────────┐ │
└─CHOICE──(──┼─\NONE──────────────┼──)─┘ │ │ ┌─\LIBL/────────┐ │ │
├─\PGM───────────────┤ └─CHOICEPGM──(──┴─┼───────────────┼──program-name─┴──)─┘
├─message-identifier─┤ ├─\CURLIB/──────┤
└─'choices-text'─────┘ └─library-name/─┘
5──┬──────────────────────────────────────┬────────────────────────────────────────────────────────────────────────────────────5%
│ ┌─\NONE──────────────┐ │
└─PROMPT──(──┼─message-identifier─┼──)─┘
└─'prompt-text'──────┘
Notes:
1 A maximum of 300 repetitions
*YES: The value entered for the qualifier defined by this the relationship, enter one of the following relational
QUAL statement is restricted to one of the values in the operators followed by a constant or the value of another
VALUES parameter, or to one of the from-values in the parameter.
SPCVAL parameters.
*LT less than
DFT Parameter *LE less than or equal to
Specifies the default value assigned to the qualifier if a *EQ equal to
value is not specified by the user. The default value *GE greater than or equal to
must satisfy one of the following: *GT greater than
*NL not less than
It must match the qualifier requirements specified by
*NE not equal to
the TYPE, LEN, REL, and RANGE parameters.
*NG not greater than
It must be one of the from-values in the SPCVAL
The REL parameter is not valid if either RANGE or
parameter.
VALUES is specified. If a character type is specified by
If RSTD(*YES) is specified, it must be in the list of TYPE(*CHAR), the EBCDIC value of the character string
values in the VALUES parameter or in the list of is used as an unsigned integer in the comparison. As
from-values in the SPCVAL parameter. noted in the LEN parameter chart, if a character con-
If the default is a character constant, it can have no stant is specified in this parameter, it can be no longer
more than 32 characters as noted in the LEN than 32 characters.
parameter chart. RANGE Parameter
The DFT parameter is valid only if the MIN parameter is Specifies the range (limits) for the value of the qualifier.
0, which means the qualifier defined by this QUAL state- The qualifier value must be greater than or equal to the
ment for this list is optional. A default is not meaningful lower limit value specified, and it must be less than or
on this QUAL statement if it is the first one (defining the equal to the upper limit value specified. For example, 15
first part) for a qualified name and if a default is speci- would be valid if the RANGE parameter was specified as
fied on the PARM or ELEM statement that this QUAL (0 16). For nonnumeric data types, such as *CHAR, the
statement further defines. range of values and the data specified is left-justified
and padded on the right with blanks. A numerical range
If DFT is not specified, it has a default of its own: a should not be used to define an interval for nonnumeric
blank (␣) if TYPE was specified as *CHAR, *NAME, data unless leading zeros are specified or the data is
*SNAME, *CNAME, or *GENERIC; or a zero (0) if TYPE only 1 character in length. The RANGE parameter is
was specified as *INT2 or *INT4. An assumed default not valid if either the REL or VALUES parameter is
value is not displayed by the command prompt; a blank specified. As noted in the LEN parameter chart, char-
input field is shown instead. If a default is specified in acter constants specified in this parameter can be no
the DFT parameter, it is displayed by the prompt exactly longer than 32 characters.
as specified.
SPCVAL Parameter
The DFT parameter is not valid if the CONSTANT
Specifies a list of up to 300 entries that define special
parameter is specified.
values that can be entered on the parameter named in
value: Specify the default value that meets the specified the KWD parameter on the PARM statement. Each
requirements or that is one of the values specified in the entry specifies a character string (a from-value) that can
SPCVAL or VALUES parameters. be entered even though it may not meet all validity
Variables cannot be coded for this value. checking requirements. If the entered character string
matches the from-value of one of the entries, and the
VALUES Parameter to-value is specified, the string is replaced with the to-
Specifies a list of up to 300 constants (fixed values) from value and is then passed to the CPP without further
which one constant can be entered as the value of the checking. If the to-value is omitted, the from-value is
qualifier. The VALUES parameter is valid only if all of passed to the CPP. The from-value is a character
the following are true: RSTD(*YES) is specified, both string, but the to-value can be anything that is passable.
RANGE and REL are not specified, and the constant If a CL variable is used for the from-value, its type must
matches the attributes specified by the TYPE and LEN be *CHAR.
parameters in this QUAL statement. As noted in the
However, the first qualifier can only have special to-
LEN parameter chart, character constants specified in
values with the from-values that are a name, a generic
this parameter can be no longer than 32 characters.
name, or an asterisk, followed by a name, such as *ALL.
Enter the constants (not more than 300) that can be
specified as the value of the qualifier. Each to-value must be passable to the CPP. The to-
value must be no longer than the LEN parameter speci-
REL Parameter
fies and, if TYPE is *INT2 or *INT4, the type of the
Specifies the relationship between the qualifier value and
to-value must be the same; if TYPE is a character type
the value of another parameter or constant. To specify
When a job log entry is created, the nondisplay field is and the permissible values during prompting. This
replaced by empty parentheses (). parameter must be specified if CHOICE(*PGM) is speci-
fied, and may not be specified otherwise.
CHOICE Parameter
Specifies the text that is displayed to the right of the *NONE: No program is identified to fill in the possible
prompt line of each parameter on the prompt screen. choices text and permissible values.
Up to 30 characters of text can be displayed. The possible library values are:
*VALUES: Each possible value is displayed in the pos-
*LIBL: The library list is used to locate the program
sible values field, separated by a comma and a space.
name.
If values are specified for the Default, Single value, or
Special value parameters, the first value displayed is the *CURLIB: The current library for the job is used to
default value; the next value is a single value, and the locate the program name. If no library is specified
values following that are special values. If there are too as the current library for the job, the QGPL library is
many values to fit in 30 characters, the last value is fol- used.
lowed by three periods. library-name: Specify the name of the library where
Examples of possible values text follow: the program name is located.
If *NO is specified on the RSTD parameter and program-name: Specify the name of the program to be
*DEC is specified on the TYPE parameter and the called during prompting to fill in the possible choices text
RANGE parameter is not specified, the word or a permissible value.
"RANGE" is displayed in the possible values field. If an exception occurs when the program is called, no
The resulting line will appear in the form: RANGE, possible choices text is left blank, and the list of permis-
*XXX, *YYY, *ZZZ... sible values is taken from the command.
If *NO is specified on the RSTD parameter and
PROMPT Parameter
*DEC is specified on the TYPE parameter and the
Specifies the prompt text, if any, that is used for the
RANGE parameter is specified, the range of pos-
qualifier (defined in this QUAL statement). The
sible values is displayed in the possible values field.
PROMPT parameter is not allowed for the first qualifier
The resulting line will appear in the form: a-b,
or for a qualifier for which the CONSTANT parameter is
*XXX, *YYY, *ZZZ (where a and b are numerals
specified. The prompt text for the first qualifier comes
defining the range).
from the PARM or ELEM statement PROMPT parameter
If *YES is specified on the RSTD parameter, the that points to the qualifier. The prompt text describes
possible values displayed are determined by the the qualifier input field to the user, who may enter a
VALUES parameter, the SNGVAL parameter, and response to the information displayed.
the SPCVAL parameter. The resulting line will
*NONE: No prompt text is shown for the qualifier
appear in the form: *XXX, *YYY, *ZZZ...
defined by this QUAL statement. This qualifier is still
*NONE: No values are displayed. prompted by an input field, but no text is shown with it.
*PGM: A program that is called determines the values message-identifier: Specify the message identifier that
that are displayed. The program that is called is identi- specifies the message containing the prompt text of up
fied in CHOICEPGM parameter. to 30 characters that is shown. When the program is
prompting for the qualifier. If a message having the
message-identifier: Specify the message ID of the specified identifier cannot be found in the message file
message used to retrieve the message containing the
specified in the PMTFILE parameter of the Create
text for the possible values field. The message file
Command (CRTCMD) command, the message identifier
specified on the PMTFILE parameter of the Create
itself is used as the prompt text.
Command (CRTCMD) command is used to find the
message. 'prompt-text': Specify the prompt text that is shown
when the program is prompting the qualifier. The text
'choices-text': Specify no more than 30 characters, must be a character string of no more than 30 charac-
enclosed in apostrophes.
ters, enclosed in apostrophes.
CHOICEPGM Parameter
Specifies the qualified name of the program that is called
during the prompting to fill in the possible choices text
Job: B,I
┌─\─────────────────────────────────────────────┐
55──SPLFILE(──┼─file-name─────────────────────────────────────┼──)─────────────────────────────────────────────────────────────5%
├─file-name─────────────────────────────────────┤
└───┬─────────────────────────────┬──job-name───┘
└─┬─────────────┬──user-name/─┘
└─job-number/─┘
The SPLFILE parameter is optional and, if not specified, defaults to an asterisk (*). Otherwise, the value consists of a two-
element list. The first element is a file name and it is required. The second element is a qualified job name. The first qualifier
is required; the last two qualifiers are optional.
Job: B,I
┌─\ALL──────────────────────────────────────────────────────────┐
│ ┌──
────────────────────────────────────────────────────────┐ │
│ │ ┌─\CURLIB/──────┐ ┌─\NONE───────┐ │ │
6 (1)
55──DTAMBRS(──┴───┼───────────────┼──physical-file-name──┼─────────────┼─┴────┴──)─────────────────────────────────────────────5%
└─library-name/─┘ └─member-name─┘
Note:
1 A maximum of 32 repetitions
The parameter named DTAMBRS is optional and, if not specified, defaults to *ALL. Otherwise, the value consists of a list,
each element of which is itself a list. Each sublist consists of a qualified file name optionally followed by one or more member
names. If no member name is specified, *NONE is taken as the default. If no library qualifier is specified for the physical file,
*CURRENT is taken as the default. This means that the library is the one currently indicated by the qualified physical file
name saved in the description of the logical file to which this DTAMBRS parameter applies. Each sublist can contain one file
name and up to 32 member names. Up to 32 such sublists can appear as the value of DTAMBRS.
Chapter 2. OS/400 Command Descriptions . . . P3-11 DSPDDMF (Display Distributed Data Management
DMPCLPGM (Dump Control Language Program) File) Command . . . . . . . . . . . . . . . . . . P3-75
Command . . . . . . . . . . . . . . . . . . . . . P3-12 DSPDEVD (Display Device Description) Command P3-77
DMPDLO (Dump Document Library Object) DSPDIRE (Display Directory Entries) Command . . P3-78
Command . . . . . . . . . . . . . . . . . . . . . P3-13 DSPDKT (Display Diskette) Command . . . . . . . P3-82
| DMPJOB (Dump Job) Command . . . . . . . . . . P3-14 DSPDLOAUD (Display Document Library Object
DMPJOBINT (Dump Job Internal) Command . . . P3-16 Audit) Command . . . . . . . . . . . . . . . . . P3-83
DMPOBJ (Dump Object) Command . . . . . . . . P3-17 DSPDLOAUT (Display Document Library Object
DMPSYSOBJ (Dump System Object) Command . P3-18 Authority) Command . . . . . . . . . . . . . . . P3-85
DMPTAP (Dump Tape) Command . . . . . . . . . P3-22 DSPDLONAM (Display Document Library Object
DMPTRC (Dump Trace) Command . . . . . . . . P3-26 Name) Command . . . . . . . . . . . . . . . . . P3-87
DO (Do) Command . . . . . . . . . . . . . . . . . P3-27 DSPDOC (Display Document) Command . . . . . P3-89
DSCJOB (Disconnect Job) Command . . . . . . . P3-28 DSPDSTL (Display Distribution List) Command . . P3-90
DSPACC (Display Access Code) Command . . . . P3-30 DSPDSTLOG (Display Distribution Log) Command P3-93
DSPACCAUT (Display Access Code Authority) DSPDSTSRV (Display Distribution Services)
Command . . . . . . . . . . . . . . . . . . . . . P3-31 Command . . . . . . . . . . . . . . . . . . . . . P3-97
DSPACTPJ (Display Active Prestart Jobs) Command P3-32 DSPDTAARA (Display Data Area) Command . . . P3-98
DSPACTPRFL (Display Active Profile List) Command P3-33 DSPDTADCT (Display Data Dictionary) Command P3-100
DSPACTSCD (Display Activation Schedule) DSPEDTD (Display Edit Description) Command . . P3-102
Command . . . . . . . . . . . . . . . . . . . . . P3-34 DSPEWCBCDE (Display Extended Wireless
DSPAPPNINF (Display APPN Information) Command P3-35 Controller Bar Code Entry) Command . . . . . . P3-103
DSPAUDJRNE (Display Audit Journal Entries) DSPEWCM (Display Extended Wireless Controller
Command . . . . . . . . . . . . . . . . . . . . . P3-37 Member) Command . . . . . . . . . . . . . . . . P3-104
DSPAUT (Display Authority) Command . . . . . . P3-40 DSPEWCPTCE (Display Extended Wireless
DSPAUTHLR (Display Authority Holder) Command P3-41 Controller PTC Entry) Command . . . . . . . . . P3-105
DSPAUTL (Display Authorization List) Command . P3-42 DSPEWLM (Display Extended Wireless Line
DSPAUTLDLO (Display Authorization List Document Member) Command . . . . . . . . . . . . . . . . P3-106
Library Objects) Command . . . . . . . . . . . . P3-44 DSPEXPSCD (Display Expiration Schedule)
DSPAUTLOBJ (Display Authorization List Objects) Command . . . . . . . . . . . . . . . . . . . . . P3-107
Command . . . . . . . . . . . . . . . . . . . . . P3-45 DSPFD (Display File Description) Command . . . P3-108
DSPAUTUSR (Display Authorized Users) Command P3-47 DSPFFD (Display File Field Description) Command P3-114
DSPBCKSTS (Display Backup Status) Command . P3-48 | DSPFLR (Display Folder) Command . . . . . . . . P3-117
DSPBCKUP (Display Backup Options) Command . P3-49 DSPFNTTBL (Display Font Table) Command . . . P3-119
DSPBCKUPL (Display Backup List) Command . . P3-50 | DSPFNTRSCA (Display Font Resource Attributes)
DSPBKP (Display Breakpoints) Command . . . . . P3-51 | Command . . . . . . . . . . . . . . . . . . . . . P3-120
DSPBNDDIR (Display Binding Directory) Command P3-52 DSPHDWRSC (Display Hardware Resources)
DSPCCTRTE (Display Circuit Route) Command . P3-54 Command . . . . . . . . . . . . . . . . . . . . . P3-121
DSPCCTSRV (Display Circuit Service) Command . P3-55 DSPHFS (Display Hierarchical File Systems)
DSPCDEFNT (Display Coded Font) Command . . P3-57 Command . . . . . . . . . . . . . . . . . . . . . P3-124
DSPCFGL (Display Configuration List) Command . P3-59 DSPHLPDOC (Display Help Document) Command P3-125
DSPCLS (Display Class) Command . . . . . . . . P3-60 DSPIGCDCT (Display DBCS Conversion Dictionary)
DSPCMD (Display Command) Command . . . . . P3-61 Command . . . . . . . . . . . . . . . . . . . . . P3-126
DSPCNNL (Display Connection List) Command . . P3-62 DSPIPLA (Display IPL Attributes) Command . . . P3-128
DSPCNNSTS (Display Connection Status) Command P3-63 DSPIPXCCT (Display IPX Circuit) Command . . . P3-129
DSPCOSD (Display Class-of-Service Description) DSPIPXD (Display IPX Description) Command . . P3-130
Command . . . . . . . . . . . . . . . . . . . . . P3-64 DSPJOB (Display Job) Command . . . . . . . . . P3-131
DSPCPCST (Display Check Pending Constraint) DSPJOBD (Display Job Description) Command . . P3-133
Command . . . . . . . . . . . . . . . . . . . . . P3-65 DSPJOBLOG (Display Job Log) Command . . . . P3-134
DSPCSI (Display Communications Side Information) DSPJOBTBL (Display Job Tables) Command . . . P3-136
Command . . . . . . . . . . . . . . . . . . . . . P3-66 | DSPJRN (Display Journal) Command . . . . . . . P3-137
DSPCTLD (Display Controller Description) Command P3-67 | DSPJRNRCVA (Display Journal Receiver Attributes)
DSPCURDIR (Display Current Directory) Command P3-68 | Command . . . . . . . . . . . . . . . . . . . . . P3-148
DSPDBG (Display Debug) Command . . . . . . . P3-69 DSPKBDMAP (Display Keyboard Map) Command P3-149
DSPDBGWCH (Display Debug Watches) Command P3-70 DSPLANADPP (Display Local Area Network Adapter
DSPDBR (Display Database Relations) Command P3-71 Profile) Command . . . . . . . . . . . . . . . . . P3-150
55──DMPCLPGM───────────────────────────────────────────────────────────────────────────────────────────────────────────────────5%
Purpose PGM
DCL . . .
The Dump CL Program (DMPCLPGM) command dumps all DCL . . .
variables (declared in the CL program in which the command MONMSG MSGID(CPF9999) EXEC(GOTO DUMP)
is processed) and all messages on the program's message
queue to a spooled printer file (QPPGMDMP). This
command is valid only in a CL program; after the program is
RETURN
dumped, it continues processing.
DUMP: DMPCLPGM
ENDPGM
Restriction: The user of this command must have read
authority for the program. This CL program monitors for the function check message
CPF9999. If a function check occurs in the program, control
There are no parameters for this command.
is passed to the command at label DUMP. This causes a
dump of the program's message queue and causes the pro-
Example gram's variables to be printed. This dump can be used to
determine the cause of the function check.
55──DMPDLO──DLO(──┬─\SYSOBJNAM──────────────┬──)──┬─────────────────────────────────────────────────────────────────┬──────────5%
├─\INT────────────────────┤ │ ┌─\NONE───────┐ │
└─document-or-folder-name─┘ ├─FLR(──┴─folder-name─┴──)────────────────────────────────────────┤
│ ┌─\NONE───┐ │
(1) ─system-object-name──)──SYSOBJATR(──┼─\INTDOC─┼──)─┘
└─SYSOBJNAM(───
└─\DST────┘
Note:
1 The SYSOBJNAM parameter is valid only when DLO(*SYSOBJNAM) is specified.
Purpose FLR
Specifies the name of the folder that contains the docu-
The Dump Document Library Object (DMPDLO) command is ment.
used primarily for problem analysis. It copies the contents
Note: A folder name can be entered in this parameter
and/or attributes of folders, documents, or internal document
only if a folder or document name is entered in
library system objects to a spooled printer file named
the DLO parameter.
QPSRVDMP. If the printed output is not spooled, and the
printer is not available, the printer file (QPSRVDMP) is over- *NONE: The object is not in a folder.
ridden. folder-name: Specify the name of the folder that con-
tains the folder or document being dumped.
Restrictions:
1. This command is shipped with public *EXCLUDE SYSOBJNAM
authority and the QPGMR, QSYSOPR, QSRV, and Specifies the system object name. This parameter is
QSRVBAS user profiles have private authorities to use valid only when DLO(*SYSOBJNAM) or
the command. DOCL(*SYSOBJNAM) is specified. A full ten characters
must be specified.
2. The user must have read authority to a document or
folder to dump it. SYSOBJATR
Specifies attributes of the object being dumped. A value
3. The user must have *ALLOBJ authority to dump internal
other than *NONE applies only to documents, and can
system objects.
be entered in this parameter only if *SYSOBJNAM is
Note: To see the parameter and value descriptions for this specified on the DLO parameter.
command, refer to the online help text. For more
*NONE: No attributes are specified for the object.
information about printing the help text, refer to
“Printing CL Command Descriptions” in Chapter 1. *INTDOC: The object being dumped is an internal docu-
ment.
document-or-folder-name: Specify the name of the doc- Example 2: Specifying a System Object Name
ument or folder being dumped.
DMPDLO DLO(\SYSOBJNAM) SYSOBJNAM(BHZMð52634)
Optional Parameters This command dumps the document library object identified
by the system object name BHZM052634.
55──DMPJOB──┬─────────────────────────────────────────────────────────────────────────────┬──┬───────────────────────┬──────────5
│ ┌─\ALL───────────────────────────────────────────────────────────┐ │ │ ┌─\ALL──┐ │
└─PGM(──┼─\NONE──────────────────────────────────────────────────────────┼──)─┘ └─JOBARA(──┴─\NONE─┴──)─┘
│ ┌──
─────────────────────────────────────────────────────────┐ │
│ │ ┌─\ALL/─────────┐ ┌─\LAST──────┐ │ │
└──6─(──┼───────────────┼──program-name───
(1) ─┼────────────┼──)─┴───
(2) ─┘
└─library-name/─┘ ├─\FIRST─────┤
├─\ALL───────┤
└─call-level─┘
5──┬──────────────────────┬──┬──────────────────────┬──────────────────────────────────────────────────────────────────────────5%
| │ ┌─\YES─┐ │ │ ┌─\YES─┐ │
| └─ADROBJ(──┴─\NO──┴──)─┘ └─JOBTHD(──┴─\NO──┴──)─┘
Notes:
1 Both the library qualifier of *ALL and a recursion level cannot be specified.
2 A maximum of 10 repetitions
*NONE: The job structure areas are not dumped. | *YES: The thread list and information is dumped.
55──DMPJOBINT──────────────────────────────────────────────────────────────────────────────────────────────────────────────────5%
┌─\LIBL/────────┐
(1) ─)────
55──DMPOBJ──OBJ(──┼───────────────┼──object-name──)──OBJTYPE(──object-type─── (P) ────────────────────────────────────────────5%
├─\CURLIB/──────┤
└─library-name/─┘
Notes:
1 A list of the valid OS/400 object types for this command is in Appendix A.
Required Parameters This command dumps the first copy of the program
MYPROG that is found in the library list. The dump is
OBJ spooled to the printer output file QPSRVDMP.
Specifies the qualified name of the OS/400 system
object being dumped.
55──DMPSYSOBJ──┬──────────────────────────────────────────┬──┬───────────────────────────────┬──────────────────────────────────5
│ ┌─\PCS────────────────────────┐ │ │ ┌─\NONE────────┐ │
└─OBJ(──┼─\MCHCTX─────────────────────┼──)─┘ └─CONTEXT(──┼─\MCHCTX──────┼──)─┘
├─\ALL────────────────────────┤ └─context-name─┘
├─generic\-system-object-name─┤
└─system-object-name──────────┘
5──┬───────────────────────────────────────────────────────────────────────────┬──┬─────────────────────────────────────┬───────5
│ ┌─\ALL────────────────────┐ │ │ ┌─\NONE───────────────┐ │
(1) ─┴─MI-object-type-in-hex───
├─TYPE(─── (2) ┴──)──SUBTYPE(──┤ SUBTYPE Details ├──)─┤ │ │ ┌──
──────────────┐ │ │
(3) 6 (4)
└─OBJTYPE(────┬─\ALL────────┬──)────────────────────────────────────────────┘ └─OFFSET(──┴───offset-value─┴────┴──)─┘
└─object-type─┘
(P) ──────────────────────────────────────────────────────────────────────────────5%
5──┬─────────────────────────────────────────┬───
│ ┌─\────────────────────────┐ │
│ │ ┌─\──────┐ │ │
└─SPACE(──┴─offset-value──┼────────┼─┴──)─┘
└─length─┘
SUBTYPE Details:
┌─\ALL─────────────────────┐
├──┴─MI-object-subtype-in-hex─┴─────────────────────────────────────────────────────────────────────────────────────────────────┤
Notes:
1 To code the following parameters positionally, they must be coded in this order, using *N for those not being specified:
3 A list of the valid OS/400 object types for this command is in Appendix A.
4 A maximum of 50 repetitions
Purpose OBJ
Specifies which of the MI system objects are being
The Dump System Object (DMPSYSOBJ) command is used dumped. The name of a specific object, the generic
primarily for problem analysis. It dumps the contents and/or name of a group of objects, the process control space of
attributes of machine interface (MI) system objects to a the job, the machine context, or all of the MI objects in a
spooled printer file named QPSRVDMP. If the user had context can be specified. If a library name is specified,
specified SPOOL(*NO) on either the CHGPRTF command or the library is dumped, but not the objects in it.
the OVRPRTF command, then the output is not spooled but
If OBJ(QTEMP) is specified along with either
printed directly; and, if the printer is not available, then this
OBJTYPE(*LIB) or TYPE(04) SUBTYPE(01), the tempo-
command overrides the print job and spools the output.
rary job context associated with the job that this
When the user specifies SPOOL(*NO) on one of the two
command is entered from, or the job being serviced as a
commands above, the user must specify QPSRVDMP as the
result of the Start Service Job (STRSRVJOB) command,
printer file. Any MI object that is stored in any library
is dumped. In either case, the CONTEXT parameter is
(context) or that is addressable through an object can be
ignored.
dumped. A specific object, a generic group, or all of the MI
objects in a context can be specified. The dump operation *PCS: The process control space of the current job or
can also be limited to objects of a specified type and, that of the job being serviced as a result of the Start
optionally, of a specified subtype. Service Job (STRSRVJOB) command is dumped.
OBJ(*PCS) can be used with the OFFSET and SPACE
Restrictions: parameters to dump objects in the job structure. If
1. This command is shipped with public *EXCLUDE OBJ(*PCS) is specified, the CONTEXT, TYPE,
authority and the QPGMR, QSYSOPR, QSRV, and SUBTYPE, and OBJTYPE parameters are ignored.
QSRVBAS user profiles have private authorities to use *MCHCTX: The machine context (which contains a list
the command. of the objects in the context) is dumped. If
2. The user must have use authority to the object and read OBJ(*MCHCTX) is specified, all the other parameters in
authority to the program and the user profile. this command are ignored.
*ALL: All the MI system objects in the specified context
are dumped if they match the requirements specified in
Optional Parameters
this parameter is specified, the TYPE or SUBTYPE that points to a location in the associated space
parameters cannot be specified. More information on of the object addressed by the system pointer.
this parameter is in Appendix A, “Expanded Parameter
Descriptions.” The result of step 2b or 2c is a space pointer that is
used to perform step 2 again if there is another offset. If
*ALL: The specified MI objects of all OS/400 system the last offset has been used, the final result is a
object types are dumped. location contained in a space pointer that is used as
object-type: Specify the specific OS/400 system object follows:
type whose associated MI system objects are to be
If the resulting location contains a system pointer
dumped.
and the SPACE parameter is not specified, the
OFFSET system object pointed to by the system pointer is
Specifies a list of values to use as offsets to indirectly dumped. If the SPACE parameter is specified, the
address a single object that is being dumped. The SPACE specification determines the portion of the
values must be positive hexadecimal values or zeros system object that is dumped.
that, when added to a pointer, result in valid addresses. If the resulting location contains a space pointer and
If an offset of zero is added to a system pointer, the the SPACE parameter is not specified, the portion of
result is a space pointer to the start of the space associ- the space that starts at the location pointed to by
ated with the object that is addressed by the system the space pointer is dumped. If the SPACE param-
pointer. (In this discussion, the associated space of a eter is specified, the SPACE specification deter-
space object is the space itself.) mines the portion of the space to be dumped.
Note: The OFFSET and SPACE parameters cannot be
The following chart shows the offsets into the process
specified if *ALL or a generic object name is
control space (PCS) at which there are pointers to the
specified for the OBJ, TYPE, SUBTYPE, or
components of a job structure. If one of these offsets is
OBJTYPE parameters.
specified, OBJ(*PCS) must be specified or assumed.
*NONE: No offset is specified. The object located
Object Object Offset
through the context is dumped. (Descriptive Name and Abbreviation) Name
offset-value: Specify the list of offsets to pointers to use Data management communications queue QDMCQ 20
to address the object or space to be dumped. The (DMCQ)
Job temporary context (QTEMP) QTEMP 40
values specified in this parameter are used as follows:
MI response queue (MIRQ) QMIRQ 80
Process definition template (PDT) PDT 60
1. The first offset is added to a space pointer that Process access group (PAG) PAG 60 100
points to the associated space of the object located Spooling control block (SCB) QSPSCB 200
through the context. The result is a space pointer Work control block table (WCBT) QWCBT 10
that points to a location further into the space.
a. If only one offset value is specified in this SPACE
parameter, step 2 is not done and the dump Specifies the area of a space or associated space to be
operation, as indicated by the rest of the dumped. The space is pointed to by the final pointer
parameters in the command, is taken. determined by the OFFSET parameter. If the OFFSET
parameter is not specified, the final pointer is a system
b. If more than one offset is specified in this pointer to the specified object in the context. See Note
parameter, step 2 is repeated for each addi- in the OFFSET parameter description.
tional offset given.
Element 1: Offset Value
2. Regarding the location pointed to by the space
pointer produced in the previous step: *: If the final pointer is a system pointer, the object
pointed to by that pointer is dumped. If the final pointer
a. If the location does not contain another pointer, is a space pointer, the portion of the space that starts at
the command is ended, an error message is the location pointed to by that pointer is dumped.
sent to the user, and no dump operation is
done. offset-value: Specify the value to add to the final pointer
to point to the beginning of the area to dump. The value
b. If the location contains a space pointer, the specified must be a positive hexadecimal value, ranging
(next) offset is added to it. The result is from 00000000 through 00FFFFFF, and, when added to
another space pointer that points to either the the final pointer, results in a valid address.
same space or a different space or associated
space. Element 2: Length
c. If the location contains a system pointer, the *: The rest of the space pointed to as a result of the
associated space pointer is set from the system offset value is being dumped.
pointer, and the (next) offset is added to the length: Specify a positive hexadecimal value ranging
space pointer. The result is a space pointer from 00000001 through 00FFFFFF that specifies the
length of the area to be dumped. If the length specified This command dumps the device description for work station
is greater than the actual length of the space, only the WS1, which is stored in the machine context.
actual space available is dumped.
Example 3: Dumping Process Control Space
DMPSYSOBJ OBJ(\PCS) SPACE(ð 2Að)
Examples
This command dumps the work control block from the space
Example 1: Dumping Indexes
associated with the process control space for the job.
DMPSYSOBJ CONTEXT(QTEMP) TYPE(ðE)
Example 4: Specifying Offset Values
This command dumps the contents and attributes of all the
DMPSYSOBJ OBJ(\PCS) OFFSET(6ð Eð 1ð 1ð) SPACE(ð 2ð)
indexes in the temporary job context to a spooled file for
printing. MI indexes are identified by the type code 0E. This command dumps the second call entry of the process
automatic storage area (offset 60 E0) for a length of 32 bytes
Example 2: Dumping a Device Description
(SPACE(0 20)). If the third call level is dumped, OFFSET(60
DMPSYSOBJ OBJ(WS1) CONTEXT(\MCHCTX) OBJTYPE(\DEVD) E0 10 10 10) is specified.
55──DMPTAP──DEV(──device-name──)──┬────────────────────────────────┬────────────────────────────────────────────────────────────5
│ ┌─\MOUNTED──────────┐ │
└─VOL(──┴─volume-identifier─┴──)─┘
5──┬────────────────────────────────────────────────────────────────────────────────┬───────────────────────────────────────────5
│ ┌─\FIRST─────────────────────┐ ┌─\ONLY────────────────────┐ │
(1) ─┬─┴─start-file-sequence-number─┴──┼──────────────────────────┼─┬──)─┘
└─SEQNBR(───
│ ├─\LAST────────────────────┤ │
│ └─end-file-sequence-number─┘ │
├─\ALL─────────────────────────────────────────────────────────┤
└─\SEARCH──────────────────────────────────────────────────────┘
5──┬───────────────────────────────────────────┬───(P) ──┬────────────────────────────────────┬─────────────────────────────────────5
│ ┌─\NONE────────────────────┐ │ │ ┌─\BASIC─────────────┐ │
(1) ─┼─file-identifier──────────┼──)─┘
└─LABEL(─── (2) ─┼─\ALL───────────────┼──)─┘
└─TYPE(───
└─generic\-file-identifier─┘ ├─\NONE──────────────┤
│ ┌──
─────────────┐ │
└──6─┬─\HDRLBL─┬─┴───
(3) ─┘
├─\DTABLK─┤
└─\TLRLBL─┘
5──┬──────────────────────────────────────────────────────────┬──┬────────────────────────┬──┬───────────────────────┬──────────5
│ ┌─\FIRST───────────┐ ┌─\ONLY──────────┐ │ │ ┌─\YES─┐ │ │ ┌─\EBCDIC─┐ │
(2) ─┴─\NO──┴──)─┘ └─CODE(──┴─\ASCII──┴──)─┘
└─DTABLK(──┬─┴─start-data-block─┴──┼────────────────┼─┬──)─┘ └─VOLLBL(───
│ ├─\LAST──────────┤ │
│ └─end-data-block─┘ │
├─\ALL─────────────────────────────────────┤
└─\LAST────────────────────────────────────┘
5──┬─────────────────────────┬─────────────────────────────────────────────────────────────────────────────────────────────────5%
│ ┌─\REWIND─┐ │
└─ENDOPT(──┼─\LEAVE──┼──)─┘
└─\UNLOAD─┘
Notes:
1 SEQNBR(*SEARCH) and LABEL(*NONE) are mutually exclusive.
3 A maximum of 3 repetitions
Purpose Note: To see the parameter and value descriptions for this
command, refer to the online help text. For more
The DMPTAP (Dump Tape) command dumps label informa- information about printing the help text, refer to
tion, data blocks, or both from standard labeled tapes or “Printing CL Command Descriptions” in Chapter 1.
tapes with no labels to a spooled printer file named
QPTAPDMP. This command allows the user to dump one or
more data files from the tape volume, writing the information Required Parameters
to a printer file. DEV
Specifies the name of the device in which the volume
The tape volume being dumped must be on the specified
being dumped is placed. The volume may or may not
device. After the DMPTAP command is entered, as much of
be labeled. Specify the name of the tape or media
the tape as necessary is read before the requested informa-
library device.
tion is printed.
Data files on secured tapes can be dumped by the security Optional Parameters
officer only; any user can dump label information on secured
tapes. VOL
Specifies one or more volume identifiers used by the file.
When the default values for the parameters of the DMPTAP More information on this parameter is in Appendix A,
command are used, the tape label areas and a minimal “Expanded Parameter Descriptions.”
amount of data from the first file are printed. This command
Note: If the device specified is a media library device,
can help determine the record format of a data file on a tape
then the volume specified should be the cartridge
with no label, or it can determine the exact contents of all
identifier to be mounted and used.
label information for a labeled data file.
*MOUNTED: The volume on the specified device is the LABEL parameter value; when a match is found, the
dumped. The volume may or may not be labeled. Note data file is dumped. If VOLLBL(*NO) is specified and
that VOL(*MOUNTED) and LABEL(*NONE) must be the last operation on the device specified
specified to dump a volume that is not labeled. For a ENDOPT(*LEAVE) (the tape is positioned at the location
media library device, the volume to be used is the next where the last operation ended), the file search begins
cartridge in the category mounted by the Set Tape Cate- with the first data file beyond the current tape position.
gory (SETTAPCGY) command. If VOLLBL(*YES) is specified or ENDOPT(*LEAVE) was
not used for the last operation (or if the tape was manu-
volume-identifier: Specify the identifier of the labeled
ally rewound since an ENDOPT(*LEAVE) operation), the
volume being dumped. This value can be specified only
search begins with the first data file on the volume.
for dumping a labeled volume. If the tape on the speci-
SEQNBR(*SEARCH) is not valid when LABEL(*NONE)
fied device has a different volume identifier than the one
is specified, and cannot be used to dump a tape volume
specified in this parameter, or if it is not labeled, an error
that is not labeled.
message is sent to the user of the DMPTAP command
and the tape is not dumped. LABEL
Specifies the identifier of the specific data files that are
SEQNBR
dumped. The file identifier for a tape data file is stored
Specifies the range of sequence numbers for the data
on labels ahead of and following the data in the file.
files that are dumped. If SEQNBR(*ALL) is specified,
then all data files on the tape are dumped. If a range of *NONE: All data files on the volume in the specified
sequence numbers is specified, then only data files in SEQNBR range are dumped. Note that
that range of data file sequence numbers are dumped. VOL(*MOUNTED) and LABEL(*NONE) must be used to
The data files dumped may be further restricted by using dump a tape volume that is not labeled.
the LABEL parameter.
file-identifier: Specify the data file identifier (17 alphanu-
The sequence number for a labeled tape data file is meric characters maximum) of the data files being
stored on labels ahead of and following the data in the dumped. The system compares the LABEL identifier
file. For a volume that is not labeled, the data file with the data file identifier on the labels of each file in
sequence number is determined by the number of tape the range specified by the SEQNBR parameter. All data
markers from the beginning of the tape. This parameter files with an identifier that matches the LABEL identifier
can be specified as a list of two values (Elements 1 and are dumped; any data file with an identifier that does not
2) or as a single value (*ALL or *SEARCH). match the LABEL identifier is not dumped.
Element 1: First File to Dump generic*-file-identifier: Specify a character string for a
generic label identifier (17 alphanumeric characters
*FIRST: The range of data files being dumped begins
maximum), which contains at least one character fol-
with the first file on the tape volume, regardless of its
lowed by an asterisk (*). Any tape file that has a file
sequence number.
identifier with the same prefix as the generic data-file-
start-file-sequence-number: The range of data files identifier is dumped. A generic name is a character
being dumped begins with the data file with the specified string of one or more characters followed by an asterisk
sequence number. Specify a number that is less than or (*); for example, ABC*. The asterisk substitutes for any
| equal to the end-file-sequence-number value. Valid valid characters. A generic name specifies all objects
| values range from 1 through 16777215. with names that begin with the generic prefix for which
Element 2: Last File to Dump the user has authority. If an asterisk is not included with
the generic (prefix) name, the system assumes it to be
*ONLY: Only a single data file (specified by the start-
the complete object name. If the complete object name
file-sequence-number) is dumped.
is specified, and multiple libraries are searched, multiple
*LAST: The range of data files being dumped begins objects can be dumped only if *ALL or *ALLUSR library
with the start-file-sequence-number data file and ends values can be specified for the name. For more infor-
with the last data file on the end of the reel. mation on the use of generic names, refer to “Generic
Object Names” in Chapter 2.
end-file-sequence-number: The range of data files being
dumped ends with the specified sequence number data TYPE
file. Specify a number that is greater than or equal to Specifies the type of information that is being dumped.
| the start-file-sequence number. Valid values range from The dump may consist of the data file header labels or
| 1 thorugh 16777215. trailer labels (for a labeled tape volume only), data
Other Single Values blocks from the data portion of the file, or all three types
of information. If the tape volume on the device is not
*ALL: All data files on the volume on the specified
labeled, only *BASIC, *ALL, or *DTABLK can be speci-
device are dumped.
fied or an error message is sent to the user of the
*SEARCH: The volume that is on the device is DMPTAP command and the volume is not dumped.
searched for a data file with an identifier that matches
*BASIC: For a standard-labeled volume, the dump *LAST: The range of data blocks that are dumped
includes header labels and the data blocks specified by starts with the data block specified by the start-data-
the DTABLK parameter. For a volume that is not block value and goes to the last block in the file.
labeled, only the data blocks (DTABLK parameter) are
end-data-block: Specify the number of the last data
dumped.
block to dump within each file. If this number is less
*ALL: For a standard-labeled volume, the dump than the number specified for the start-data-block part of
includes header labels, trailer labels, and data blocks. the DTABLK parameter, an error message is sent to the
For a volume that is not labeled, TYPE(*ALL) dumps user who requested the dump, and the tape is not
only data blocks (since there are no labels). dumped. If the end-data-block value is larger than the
actual number of data blocks in the data file, then all
*NONE: No data file is dumped. If TYPE(*NONE) is
blocks from the start-block number to the end of the file
specified, the tape volume being dumped must be
are dumped (with no error messages).
labeled, and VOLLBL(*NO) cannot be specified, or an
error message is sent to the user of the DMPTAP Other Single Values
command.
*ALL: All data blocks in the specified data files on this
*HDRLBL: The data file header labels are dumped. volume are dumped. If a data file is continued from
Header labels are immediately ahead of the data in the another volume or continues onto another volume, only
file that they apply to. All header labels for the specified the part of the data file that is stored on this volume is
data files are dumped, including user-specified header dumped.
labels (if any exist). TYPE(*HDRLBL) is not valid for
*LAST: Only the last data block in the data file is
volumes that are not labeled.
dumped.
*DTABLK: One or more data blocks from the file data
VOLLBL
are dumped. The blocks within the data file that are
Specifies whether volume labels are dumped. This
dumped are specified by the DTABLK parameter.
parameter is ignored for volumes that are not labeled.
*TLRLBL: All data file trailer labels are dumped. Trailer
*YES: All volume labels (including user-specified labels)
labels immediately follow the data in the file to which
are dumped.
they apply. All the trailer labels for the specified data
files are dumped, including user-specified trailer labels (if *NO: No volume labels are dumped; the volume printout
any exist). TYPE(*TLRLBL) is not valid for volumes that does, however, include the volume identifier of a labeled
are not labeled. volume and other basic information for any dumped
tape.
DTABLK
Specifies which data blocks are dumped. This param- CODE
eter is used to limit the amount of tape file data dumped Specifies the character code used. The code can be
to the printer. If neither TYPE(*BASIC) nor TYPE(*ALL) either extended binary-coded decimal interchange code
is specified and the TYPE parameter value does not (*EBCDIC) or the American National Standard Code for
include *DTABLK, this parameter is ignored. Information Interchange (*ASCII).
This parameter can be specified as a list of two values *EBCDIC: The tape contains data in the EBCDIC char-
(Elements 1 and 2) or as a single value (*ALL or acter code. The dump output contains the hexadecimal
*LAST). value and the EBCDIC character equivalent of each data
byte.
Element 1: First Block to Dump
*ASCII: The tape contains data in the ASCII character
*FIRST: The data blocks being dumped begins with the
code. The dump output contains the hexadecimal value
first block in the data file.
and the ASCII character equivalent of each data byte.
start-data-block: Specify the number of the first data
block within each file that is dumped. If this number is ENDOPT
greater than the number specified for the end-data-block Specifies whether the tape is rewound only or rewound
portion of the DTABLK parameter, an error message is and unloaded after the operation ends.
sent to the user who requested the dump, and the tape *REWIND: The tape is automatically rewound, but not
is not dumped. If the start-data-block value is larger unloaded, after the operation has ended.
than the actual number of data blocks in the data file,
*LEAVE: The tape does not rewind or unload after the
then the last data block in the file is dumped (with no
operation ends. It remains at the current position on the
error messages).
tape drive.
Element 2: Last Block to Dump
*UNLOAD: The tape is automatically rewound and
*ONLY: Only the data block specified by the first part of unloaded after the operation ends.
the DTABLK parameter is dumped.
Example This command dumps information from the tape volume that
is on device QTAPE2. Data blocks 3 through 7 within the
DMPTAP DEV(QTAPE2) SEQNBR(5) TYPE(\DTABLK)
data file specified by sequence number 5 are dumped to a
DTABLK(3 7)
printer file.
(P) ─┬───────────────────────────┬──┬─────────────────────────────────────────────────────┬─────5
55──DMPTRC──MBR(──member-name──)────
│ ┌─QPFRDATA─────┐ │ │ ┌─QSYS/─────────┐ ┌─QCTL───────────┐ │
└─LIB(──┴─library-name─┴──)─┘ └─JOBQ(──┬─┼───────────────┼──┴─job-queue-name─┴─┬──)─┘
│ ├─\LIBL/────────┤ │
│ ├─\CURLIB/──────┤ │
│ └─library-name/─┘ │
└─\NONE─────────────────────────────────┘
5──┬─────────────────────────────┬─────────────────────────────────────────────────────────────────────────────────────────────5%
│ ┌─\BLANK────────┐ │
└─TEXT(──┴─'description'─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose JOBQ
Specifies the qualified name of the job queue on which
The Dump Trace (DMPTRC) command copies data from the this job is placed. The name of the job queue can be
vertical microcode (VMC) trace table to a database file. The qualified by one of the following library values:
user can optionally run the job interactively or submit it as a
batch job. QSYS: The IBM-supplied system library, QSYS, is
used to locate the job queue.
Note: To see the parameter and value descriptions for this
command, refer to the online help text. For more *LIBL: All libraries in the job's library list are
information about printing the help text, refer to searched until the first match is found.
“Printing CL Command Descriptions” in Chapter 1. *CURLIB: The current library for the job is
searched. If no library is specified as the current
library for the job, the QGPL library is used.
Required Parameters
library-name: Specify the name of the library to be
MBR searched.
Specifies the member name of the database file where
the trace table data is dumped. If STRPFRMON was QCTL: The IBM-supplied controlling subsystem QCTL
used to collect the trace data, the same name that was is used.
specified on the Start Performance Monitor job-queue-name: Specify the name of the job queue.
(STRPFRMON) command should be used. If Perfor-
mance Tools/400 is installed, this is a requirement for *NONE: No job is submitted. The DMPTRC request
the reporting function of the Print Transaction Report runs interactively.
(PRTTNSRPT) command. TEXT
Specifies the text that briefly describes the database
Optional Parameters member. More information on this parameter is in
Appendix A, “Expanded Parameter Descriptions.”
LIB
*BLANK: Text is not specified.
Specifies the library where the database file for trace
data is located. If the file is not found in the specified 'description': Specify no more than 50 characters of text,
library, the system automatically creates it in that library. enclosed in apostrophes.
The name of the database file can be qualified by one of
the following library values: Example
QPFRDATA: The data is located in the DMPTRC MBR(TUESAM)
IBM-supplied performance data library, QPFRDATA.
This command causes existing VMC trace data to be written
library-name: Specify the name of the library to be to the member TUESAM in library QPFRDATA. The file
searched. used is QAPMDMPT. The request is submitted to the job
queue QCTL in library QSYS. It runs as a batch job.
DO (Do) Command
Pgm: B,I
55──DO─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────5%
Purpose Examples
The Do (DO) command allows the user to group commands Example 1: Processing a Group of Commands
within a CL program. It is used with the ENDDO command DO
to identify a group of commands that are run together as a
group. Usually, the DO command specifies the starting of a (group of CL commands)
group of commands that are run as a result of a decision
made by the processing of an IF command. However, the ENDDO
DO command does not have to be associated with an IF
command. When used with an IF command, the DO The commands between the DO and ENDDO commands are
command can be either the true part of the decision (that is, processed once, as a group of commands.
the value of the THEN parameter of the IF command), or the
false part of a decision (on the ELSE command). Every Do Example 2: Processing a Group of Commands
group must be ended by the ENDDO command. Do groups If &SWITCH DO
can be nested within other Do groups, but each group must
have an ENDDO command to end its level of nesting. (group of CL commands)
Restriction: This command is valid only within a CL ENDDO
program. Up to 10 levels of Do groups can be nested within
each other. The commands between the DO and ENDDO commands are
processed if the value in the logical variable &SWITCH is '1'.
There are no parameters for this command. If &SWITCH is not '1', then control passes immediately to the
next command following the ENDDO command.
(P) ──┬────────────────────────────────────────────────────────┬────5
55──DSCJOB──┬──────────────────────┬──┬─────────────────────┬───
│ ┌─\NOLIST─┐ │ │ ┌─\DEVD─┐ │ └─JOB(──┬─\─────────────────────────────────────────┬──)─┘
└─LOG(──┴─\LIST───┴──)─┘ └─DROP(──┼─\YES──┼──)─┘ └─┬─────────────────────────────┬──job-name─┘
└─\NO───┘ └─┬─────────────┬──user-name/─┘
└─job-number/─┘
5──┬────────────────────────────┬──────────────────────────────────────────────────────────────────────────────────────────────5%
│ ┌─\SELECT─┐ │
└─DUPJOBOPT(──┴─\MSG────┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
*SELECT: The selection display is shown when dupli- Example 2: Disconnecting Job Without Releasing
cate jobs are found during an interactive session. Other- Switched Line
wise, a message is issued. DSCJOB LOG(\LIST) DROP(\NO)
*MSG: A message is issued when duplicate jobs are
found. This command disconnects the interactive job, but the
switched line is not released. If the job is ended due to the
QDSCJOBITV system value, the job log is included with the
Examples job's spooled output.
Example 1: Disconnecting All Interactive Jobs Example 3: Deleting Information in Job Log
DSCJOB DSCJOB LOG(\NOLIST) DROP(\DEVD) JOB(123497/DEPT1/DSPð4)
This command enables the user of the work station to dis- This command disconnects the interactive job
connect all the interactive jobs associated with the work 123497/DEPT1/DSP04 and any other jobs on that work
station. The switched line is dropped only if that is specified station, for example, secondary jobs or group jobs. If the job
in the work station device description of this work station and is disconnected when the disconnect interval in the
if no other work station on this line is active. If the job is QDSCJOBITV system value is reached, the job is ended and
disconnected when the disconnect interval in the the job log is not included with the job's spooled output. The
QDSCJOBITV system value is reached, the job is ended and work station device description is checked to determine
the job log is not included with the job's spooled output. whether the switched line is disconnected.
(P) ──────────────────────────────────────────────────────────────────────────────────────5%
55──DSPACC──┬────────────────────────┬───
│ ┌─\──────┐ │
└─OUTPUT(──┴─\PRINT─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
(P) ───────────────────────────────────────5%
55──DSPACCAUT──┬────────────────────────────────────────┬──┬────────────────────────┬───
│ ┌─\CURRENT─────────────────┐ │ │ ┌─\──────┐ │
└─USER(──┼─\ALL─────────────────────┼──)─┘ └─OUTPUT(──┴─\PRINT─┴──)─┘
│ ┌──
───────────────────┐ │
└──6─user-profile-name─┴───
(1) ─┘
Notes:
1 A maximum of 300 repetitions
┌─\LIBL/────────┐
(P) ─┬────────────────────────┬─────────────────5%
55──DSPACTPJ──SBS(──subsystem-name──)──PGM(──┼───────────────┼──program-name──)────
├─\CURLIB/──────┤ │ ┌─\──────┐ │
└─library-name/─┘ └─OUTPUT(──┴─\PRINT─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
(P) ──────────────────────────────────────────────────────────────────────────────────5%
55──DSPACTPRFL──┬────────────────────────┬───
│ ┌─\──────┐ │
└─OUTPUT(──┴─\PRINT─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
(P) ───────────────────────────────────────────────────────────────────────────────────5%
55──DSPACTSCD──┬────────────────────────┬───
│ ┌─\──────┐ │
└─OUTPUT(──┴─\PRINT─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose OUTPUT
Specifies whether the output from the command is
The Display Activation Schedule (DSPACTSCD) command shown at the requesting workstation or printed with the
displays user profiles and their enable and disable time, the job's spooled output. More information on this param-
days the profiles will be activated and the job schedule entry eter is in Appendix A, “Expanded Parameter
numbers for the corresponding job schedule entries. This Descriptions.”
information is in file QASECACT in library QUSRSYS and
*: The output is displayed (if requested by an interactive
was gathered from the Change Activation Schedule Entry
job) or printed with the job's spooled output (if requested
(CHGACTSCDE) command.
by a batch job).
Restrictions: *PRINT: The output is printed with the job's spooled
output.
You must have *ALLOBJ special authority to use this
command.
Example
Note: To see the parameter and value descriptions for this
command, refer to the online help text. For more DSPACTSCD OUTPUT(\PRINT)
information about printing the help text, refer to
The activation schedule is printed with the job's spooled
“Printing CL Command Descriptions” in Chapter 1.
output.
Optional Parameter
(P) ──┬──────────────────────────┬──┬──────────────────────────┬───────────────────5
55──DSPAPPNINF──┬────────────────────────────┬───
│ ┌─\TOPOLOGY─┐ │ │ ┌─\ALL──────┐ │ │ ┌─\ENDPNT─┐ │
└─INFTYPE(──┼─\LCLNODE──┼──)─┘ └─NODES(──┼─\ACTIVE───┼──)─┘ └─SSNTYPE(──┴─\INMSSN─┴──)─┘
└─\SSN──────┘ └─\INACTIVE─┘
5──┬────────────────────────────────────────────────────────┬──┬──────────────────────────────────────────┬─────────────────────5
└─JOB(────┬─────────────────────────────┬──job-name────)─┘ │ ┌─\ALL────────────────────────┐ │
└─┬─────────────┬──user-name/─┘ └─CTL(──┴─controller-description-name─┴──)─┘
└─job-number/─┘
5──┬──────────────────────────┬──┬───────────────────────────────────────────┬──────────────────────────────────────────────────5
│ ┌─\────────┐ │ │ ┌─\LIBL/────────┐ │
└─OUTPUT(──┼─\PRINT───┼──)─┘ └─OUTFILE(──┼───────────────┼──file-name──)─┘
└─\OUTFILE─┘ ├─\CURLIB/──────┤
└─library-name/─┘
5──┬───────────────────────────────────────────┬───────────────────────────────────────────────────────────────────────────────5%
│ ┌─\FIRST──────┐ ┌─\REPLACE─┐ │
└─OUTMBR(──┼─────────────┼──┴─\ADD─────┴──)─┘
└─member-name─┘
Note:
P All parameters preceding this point can be specified in positional form.
The name of the file can be qualified by one of the fol- DSPAPPNINF INFTYPE(\SSN) SSNTYPE(\ENDPNT)
lowing library values: JOB(APPNJOB/USERPROF/ððððð1) OUTPUT(\)
*LIBL: All libraries in the job's library list are This command shows a list of procedure correlation session
searched until the first match is found. identifiers (PCIDs) associated with the job name
APPNJOB/USERPROF/000001. From this list, the user can
*CURLIB: The current library for the job is
specify an option to show additional information about a
searched. If no library is specified as the current
session.
library for the job, the QGPL library is used.
library-name: Specify the name of the library to be Example 3: Storing Contents of a Directory
searched. DSPAPPNINF INFTYPE(\LCLNODE) OUTPUT(\OUTFILE)
OUTFILE(USERLIB/APPNFILE) OUTMBR(\FIRST, \REPLACE)
file-name: Specify the name of the file that is used to
store the requested APPN information. This command stores the contents of the local directory in
the first member of an output file named
USERLIB/APPNFILE. If information already exists in this
member, the new information replaces the existing informa-
tion.
55──DSPAUDJRNE──┬─────────────────────────┬──┬───────────────────────────────────┬──────────────────────────────────────────────5
│ ┌──
──────┐ │ │ ┌─\ALL──────────────┐ │
│ │┌─AF─┐│ │ └─USRPRF(──┴─user-profile-name─┴──)─┘
6 (1) ──)─┘
└─ENTTYP(───┼─CA─┼┴───
├─CD─┤
├─CO─┤
├─CP─┤
├─DO─┤
├─JS─┤
├─ND─┤
├─NE─┤
├─OR─┤
├─OW─┤
├─PG─┤
├─PO─┤
├─PW─┤
├─SF─┤
├─SV─┤
├─YC─┤
├─YR─┤
├─ZC─┤
└─ZR─┘
5──┬────────────────────────────────────────────────────────────────────────────────────────────────────────┬───────────────────5
│ ┌─\CURRENT───────────────────────────────────────────────────────────────────────────────┐ │
└─JRNRCV(──┼─\CURCHAIN──────────────────────────────────────────────────────────────────────────────┼──)─┘
│ ┌─\CURRENT────────────────────────────────┐ │
│ ┌─\LIBL/────────┐ │ ┌─\LIB/─────────┐ │ │
└─┼───────────────┼──start-journal-receiver──┴─┼───────────────┼──end-journal-receiver─┴─┘
├─\CURLIB/──────┤ ├─\CURLIB/──────┤
└─library-name/─┘ └─library-name/─┘
5──┬────────────────────────────────────────────────┬──┬──────────────────────────────────────────┬─────────────────────────────5
│ ┌─\FIRST───────────────────────┐ │ │ ┌─\LAST────────────────────┐ │
└─FROMTIME(──┴─starting-date──starting-time─┴──)─┘ └─TOTIME(──┴─ending-date──ending-time─┴──)─┘
5──┬────────────────────────┬──────────────────────────────────────────────────────────────────────────────────────────────────5%
│ ┌─\PRINT─┐ │
└─OUTPUT(──┴─\──────┴──)─┘
Note:
1 A maximum of 20 repetitions.
Purpose ENTTYP
Specifies the journal entry types to be included in the
The Display Audit Journal Entries (DSPAUDJRNE) command report.
allows you to generate security journal audit reports. The
AF: Authorization failure entries.
reports are based on the audit entry types and the user
profile specified on the command. Reports can be limited to CA: Change authority entries.
specific time frames and detached journal receivers can be CD: Command string entries.
searched. The reports are directed to the active display or a
spooled file. CO: Create object entries.
CP: Change user profile entries.
Restrictions:
DO: Delete object entries.
You must have *ALLOBJ and *AUDIT special authorities to JS: Actions against jobs entries.
use this command.
ND: Directory search filter violations.
Note: To see the parameter and value descriptions for this
command, refer to the online help text. For more NE: End point filter violations.
information about printing the help text, refer to OR: Object restored entries.
“Printing CL Command Descriptions” in Chapter 1.
OW: Object ownership changed entries.
PG: Change of an object's primary group.
Optional Parameters
PO: Printed output entries.
PW: Invalid password entries.
SF: Action on spooled files entries. ending-journal-receiver: Specify the name and library of
the last journal receiver from which entries are searched.
SV: System values changed entries.
YC: DLO object read entries. FROMTIME
Specifies the date and time of the first journal entry to be
YR: DLO object changed entries. searched.
ZC: Object read entries. *FIRST: The first journal entry in the journal receiver
ZR: Object changed entries. becomes the starting point for the range of entries to be
searched.
USRPRF
Journal entries created for a user profile's actions are Element 1: Starting entry date
included in the report. starting-date: Specify the starting date. The starting
*ALL: The report will include entries for all user profiles. date and time of the first journal entry occurring at or
after the specified starting date and time becomes the
user-profile-name: Specify the name of the user profile starting point for the range of entries to be searched.
whose journal entries are to be included in the report.
Element 2: Starting entry time
JRNRCV
Specifies the name of the starting (first) and ending (last)
starting-time: Specify the starting time. The starting
date and time of the first journal entry occurring at or
journal receivers whose journal entries are searched.
after the specified starting date and time becomes the
Note: If the maximum number of receivers (256) in the starting point for the range of entries to be searched.
range is surpassed, an error occurs and no
journal entries are converted. TOTIME
Specifies the creation date and time of the last journal
*CURRENT: Journal entries in the currently attached
entry to be searched.
journal receiver are searched.
*LAST: The last journal entry in the journal receiver
*CURCHAIN: Journal entries in the currently attached
becomes the ending point for the range of entries to be
journal receiver chain are searched. If there is a break
searched.
in the chain, the receiver range is from the most recent
break in the chain through the receiver that is attached Element 1: Ending entry date
when starting to convert journal entries. ending-date: Specify the ending date. The ending date
Element 1: Starting Journal Receiver and time of the first journal entry occurring at or before
the specified ending time on the specified ending date
The name of the staring journal receiver can be qualified
becomes the ending point for the range of entries to be
by one of the following library values:
searched.
*LIBL: The library list is used to locate the journal Element 2: Ending entry time
receiver.
ending-time: Specify the ending time. The ending date
*CURLIB: The current library for the job is used to and time of the first journal entry occurring at or before
locate the journal receiver. If no library is specified the specified ending time on the specified ending date
as the current library for the job, QGPL is used. becomes the ending point for the range of entries to be
library-name: Specify the library where the journal searched.
receiver is located.
OUTPUT
starting-journal-receiver: Specify the name and library of Specifies whether the output from the command is
the first journal receiver from which entries are searched. shown at the requesting workstation or printed with the
job's spooled output. More information on this param-
Element 2: Ending Journal Receiver *CURRENT:
eter is in Appendix A, “Expanded Parameter
The journal receiver that is currently attached is used.
Descriptions.”
The name of the ending journal receiver can be qualified
*PRINT: The output is printed with the job's spooled
by one of the following library values:
output.
*LIBL: The library list is used to locate the journal *: The output is shown (if requested by an interactive
receiver. job) or printed with the job's spooled output (if requested
*CURLIB: The current library for the job is used to by a batch job).
locate the journal receiver. If no library is specified
as the current library for the job, QGPL is used. Example
library-name: Specify the library where the journal DSPAUDJRNE ENTTYP(AF) OUTPUT(\)
receiver is located.
(P) ─────────────────────────────────────────────────────────5%
55──DSPAUT──OBJ(──'object-path-name'──)──┬────────────────────────┬───
│ ┌─\──────┐ │
└─OUTPUT(──┴─\PRINT─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
(P) ──────────────────────────5
55──DSPAUTHLR──┬──────────────────────────┬──┬────────────────────────────────────────────────────┬───
│ ┌─\────────┐ │ │ ┌─\LIBL/────────┐ │
└─OUTPUT(──┼─\PRINT───┼──)─┘ └─OUTFILE(──┼───────────────┼──database-file-name──)─┘
└─\OUTFILE─┘ ├─\CURLIB/──────┤
└─library-name/─┘
5──┬───────────────────────────────────────────┬───────────────────────────────────────────────────────────────────────────────5%
│ ┌─\FIRST──────┐ ┌─\REPLACE─┐ │
└─OUTMBR(──┴─member-name─┴──┼──────────┼──)─┘
└─\ADD─────┘
Note:
P All parameters preceding this point can be specified in positional form.
(P) ─────────────────────────────────────────────────5
55──DSPAUTL──AUTL(──authorization-list-name──)──┬──────────────────────────┬───
│ ┌─\────────┐ │
└─OUTPUT(──┼─\PRINT───┼──)─┘
└─\OUTFILE─┘
5──┬────────────────────────────────────────────────────┬──┬───────────────────────────────────────────┬───────────────────────5%
│ ┌─\LIBL/────────┐ │ │ ┌─\FIRST──────┐ ┌─\REPLACE─┐ │
└─OUTFILE(──┼───────────────┼──database-file-name──)─┘ └─OUTMBR(──┴─member-name─┴──┼──────────┼──)─┘
├─\CURLIB/──────┤ └─\ADD─────┘
└─library-name/─┘
Note:
P All parameters preceding this point can be specified in positional form.
Note: To see the parameter and value descriptions for this library-name: Specify the name of the library to be
command, refer to the online help text. For more searched.
information about printing the help text, refer to database-file-name: Specify the name of the database
“Printing CL Command Descriptions” in Chapter 1. file that receives the output of the display.
OUTMBR
Required Parameter Specifies the name of the database file member to which
AUTL the output is directed.
Specifies the name of the authorization list to be shown. Element 1: Member to Receive Output
*FIRST: The first member in the file receives the output.
Optional Parameters If OUTMBR(*FIRST) is specified and the member does
not exist, the system creates a member with the name of
OUTPUT the file specified on the OUTFILE parameter. If the
Specifies whether the output is sent to the display, to a member already exists, the option exists to add new
printer file, or to a database file. More information on records to the end of the existing outfile member or clear
this parameter is in Appendix A, “Expanded Parameter the member and add the new records.
Descriptions.”
member-name: Specify the file member that receives
*: Output requested by an interactive job is shown on the output. If OUTMBR(member-name) is specified and
the display. Output requested by a batch job is printed the member does not exist, the system creates it. If the
with the job's spooled output. member already exists, the option exists to add new
*PRINT: The output is printed with the job's spooled
output.
(P) ───────────────────────────────────────────────5%
55──DSPAUTLDLO──AUTL(──authorization-list-name──)──┬────────────────────────┬───
│ ┌─\──────┐ │
└─OUTPUT(──┴─\PRINT─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose AUTL
Specifies the name of the authorization list whose list of
The Display Authorization List Document Library Objects documents and folders is displayed.
(DSPAUTLDLO) command shows the list of documents and
folders whose access security is specified by the authori-
zation list specified in the AUTL parameter. Optional Parameters
OUTPUT
Restrictions:
Specifies whether the output from the command is
1. If a user on the list has authority other than *EXCLUDE, shown at the requesting workstation or printed with the
or is not on the list and public authority is something job's spooled output. More information on this param-
other than *EXCLUDE, that user is authorized to display eter is in Appendix A, “Expanded Parameter
the documents and folders. Descriptions.”
2. If the user is not authorized to the document or folder *: Output requested by an interactive job is shown on
because access authorities are private, the document the display. Output requested by a batch job is printed
library object is marked "not authorized" in the text field. with the spooled output of the job.
Note: To see the parameter and value descriptions for this *PRINT: The output is printed with the job's spooled
command, refer to the online help text. For more output.
information about printing the help text, refer to
“Printing CL Command Descriptions” in Chapter 1.
Example
DSPAUTLDLO AUTL(PAYROLL) OUTPUT(\PRINT)
Required Parameters
This command sends the display output for the authorization
list named PAYROLL to a printer.
(P) ──────────────────────────────────────────────5
55──DSPAUTLOBJ──AUTL(──authorization-list-name──)──┬──────────────────────────┬───
│ ┌─\────────┐ │
└─OUTPUT(──┼─\PRINT───┼──)─┘
└─\OUTFILE─┘
5──┬────────────────────────────────────────────────────┬──┬───────────────────────────────────────────┬───────────────────────5%
│ ┌─\LIBL/────────┐ │ │ ┌─\FIRST──────┐ ┌─\REPLACE─┐ │
└─OUTFILE(──┼───────────────┼──database-file-name──)─┘ └─OUTMBR(──┴─member-name─┴──┼──────────┼──)─┘
├─\CURLIB/──────┤ └─\ADD─────┘
└─library-name/─┘
Note:
P All parameters preceding this point can be specified in positional form.
Optional Parameters *FIRST: The first member in the file receives the output.
If OUTMBR(*FIRST) is specified and the member does
OUTPUT not exist, the system creates a member with the name of
Specifies whether the output from the command is the file specified on the OUTFILE parameter. If the
shown at the requesting work station, printed with the member already exists, the user has the option to add
job's spooled output, or directed to a database file. new records to the end of the existing member or to
More information on this parameter is in Appendix A, clear the existing member and then add the new
“Expanded Parameter Descriptions.” records.
*: Output requested by an interactive job is shown on member-name: Specify the file member that receives
the display. Output requested by a batch job is printed the output. If OUTMBR(member-name) is specified and
with the job's spooled output. the member does not exist, the system creates it.
*PRINT: The output is printed with the job's spooled Element 2: Operation to Perform on Member
output. *REPLACE: The system clears the existing member
*OUTFILE: The output is directed to the database file and adds the new records.
specified on the OUTFILE parameter. *ADD: The system adds the new records to the end of
the existing records.
OUTFILE
Specifies the qualified name of the database file to
which the output of the display is directed. If this file Example
DSPAUTLOBJ AUTL(PAYROLL) OUTFILE(\LIBL/PAYROLL) This command places the output in the database file
OUTMBR(DARL \REPLACE) PAYROLL, member name DARL. If member DARL already
exists, the system clears it and adds the new records.
(P) ─────────────────────────────────────────────────────────5%
55──DSPAUTUSR──┬──────────────────────┬──┬────────────────────────┬───
│ ┌─\USRPRF─┐ │ │ ┌─\──────┐ │
└─SEQ(──┴─\GRPPRF─┴──)─┘ └─OUTPUT(──┴─\PRINT─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose OUTPUT
Specifies whether the output from the command is
The Display Authorized Users (DSPAUTUSR) command dis- shown at the requesting work station or printed with the
plays or prints the names of the authorized system users, in job's spooled output. More information on this param-
alphabetic order. The following information is provided for eter is in Appendix A, “Expanded Parameter
each user: the group profile of which the user is a member, Descriptions.”
the most recent password change date, whether the user
*: Output requested by an interactive job is shown on
profile has a password, and the text of the user profile.
the display. Output requested by a batch job is printed
Note: While this command is searching for user profile with the job's spooled output.
information to display, another job cannot change
*PRINT: The output is printed with the job's spooled
user profiles (for example, with the Change User
output.
Profile (CHGUSRPRF) command).
(P) ───────────────────────────────────────────────────────────────────────────────────5%
55──DSPBCKSTS──┬────────────────────────┬───
│ ┌─\──────┐ │
└─OUTPUT(──┴─\PRINT─┴──)─┘
Note:
P All parameters preceding this point can be specified positionally.
Purpose OUTPUT
Specifies whether the backup status is displayed or
The Display Backup Status (DSPBCKSTS) command allows printed.
the user to display information about the tape sets used for
*: The output is displayed if requested by an interactive
backup and what was saved on each of them. Only informa-
job, or printed with the job's spooled output if requested
tion about backups performed using the backup options is
by a batch job.
displayed.
*PRINT: The output is printed with the job's spooled
Note: To see the parameter and value descriptions for this
output.
command, refer to the online help text. For more
information about printing the help text, refer to
“Printing CL Command Descriptions” in Chapter 1. Example
DSPBCKST OUTPUT(\PRINT)
Optional Parameters
This command prints the backup status.
(P) ────────────────────────────────────────────────────────5%
55──DSPBCKUP──BCKUPOPT(──┬─\DAILY───┬──)──┬────────────────────────┬───
├─\WEEKLY──┤ │ ┌─\──────┐ │
└─\MONTHLY─┘ └─OUTPUT(──┴─\PRINT─┴──)─┘
Note:
P All parameters preceding this point can be specified positionally.
Purpose OUTPUT
Specifies whether the backup options are displayed or
The Display Backup Options (DSPBCKUP) command allows printed.
the user to display the options in one of the predefined
*: The output is displayed if requested by an interactive
backups. More information on backup is in the Backup and
job, or printed with the job's spooled output if requested
Recovery book.
by a batch job.
Note: To see the parameter and value descriptions for this
*PRINT: The output is printed with the job's spooled
command, refer to the online help text. For more
output.
information about printing the help text, refer to
“Printing CL Command Descriptions” in Chapter 1.
Examples
Required Parameters Example 1: Displaying Backup Options
BCKUPOPT DSPBCKUP BCKUPOPT(\DAILY)
Specifies the backup options to be displayed.
This command displays the daily backup options.
*DAILY: The daily backup options are displayed.
*WEEKLY: The weekly backup options are displayed. Example 2: Printing Backup Options
*MONTHLY: The monthly backup options are displayed. DSPBCKUP BCKUPOPT(\MONTHLY) OUTPUT(\PRINT)
┌─\LIB─┐
(P) ─────────────────────────────────────────────────────────────5%
55──DSPBCKUPL──BCKUPL(──┴─\FLR─┴──)──┬────────────────────────┬───
│ ┌─\──────┐ │
└─OUTPUT(──┴─\PRINT─┴──)─┘
Note:
P All parameters preceding this point can be specified positionally.
Purpose OUTPUT
Specifies whether the backup list is displayed or printed.
The Display Backup List (DSPBCKUPL) command allows the
*: The output is displayed if requested by an interactive
user to view libraries and folders for backup. More informa-
job, or printed with the job's spooled output if requested
tion on backup is in the Backup and Recovery book.
by a batch job.
Note: To see the parameter and value descriptions for this
*PRINT: The output is printed with the job's spooled
command, refer to the online help text. For more
output.
information about printing the help text, refer to
“Printing CL Command Descriptions” in Chapter 1.
Examples
Required Parameters Example 1: Displaying a Library Backup List
BCKUPL DSPBCKUPL BCKUPL(\LIB)
Specifies the backup list to display.
This command displays the library backup list.
*LIB: The library backup list is displayed.
*FLR: The folder backup list is displayed. Example 2: Printing a Folder Backup List
DSPBCKUPL BCKUPL(\FLR) OUTPUT(\PRINT)
Optional Parameters This command prints the folder backup list.
(P) ──┬──────────────────────────────────┬────────────────────────────────────────────────5%
55──DSPBKP──┬────────────────────────┬───
│ ┌─\──────┐ │ │ ┌─\DFTPGM─────────────┐ │
└─OUTPUT(──┴─\PRINT─┴──)─┘ └─PGM(──┼─\ALL────────────────┼──)─┘
│ ┌──
──────────────┐ │
└──6─program-name─┴───
(1) ─┘
Notes:
P All parameters preceding this point can be specified in positional form.
1 A maximum of 20 repetitions
Example
Optional Parameters
DSPBKP
OUTPUT
Specifies whether the output from the command is Assuming that program MYPROG is the default program in
shown at the requesting display station or printed with an interactive debug session, this command shows all of the
the job's spooled output. More information on this breakpoint locations that are currently set in MYPROG. The
parameter is in Appendix A, “Expanded Parameter names of the program variables associated with each break-
Descriptions.” point are also shown.
┌─\LIBL/────────┐ ┌─\────────┐
(P)───────────────────────────────5
55──DSPBNDDIR──BNDDIR(──┼───────────────┼──binding-directory-name──)──OUTPUT(──┼──────────┼──)───
├─\CURLIB/──────┤ ├─\PRINT───┤
├─\USRLIBL/─────┤ └─\OUTFILE─┘
└─library-name/─┘
┌─\LIBL/────────┐ ┌─\FIRST──────┐ ┌─\REPLACE─┐
5──OUTFILE(──┼───────────────┼────database-file-name────)──OUTMBR(──┴─member-name─┴──┴─\ADD─────┴──)───────────────────────────5%
├─\CURLIB/──────┤
├─\USRLIBL/─────┤
└─library-name/─┘
Note:
P All parameters preceding this point can be specified in positional form.
1. You must have *USE authority to the library where the *OUTFILE: The output is directed to the database file
binding directory is located. specified on the OUTFILE parameter.
not exist and a member name is not specified, the Element 2: Operation to Perform on Member
system creates a member with the name of the file spec-
*REPLACE: The system clears the existing member
ified in the OUTFILE parameter. If a member name is
and adds the new records.
specified, but the member does not exist, the system
creates it. *ADD: The system adds the new records to the end of
the existing records.
Element 1: Member to Receive Output
*FIRST: The first member in the file receives the output.
If OUTMBR(*FIRST) is specified and the member does
Example
not exist, the system creates a member with the name of DSPBNDDIR BNDDIR(STORE)
the file specified on the OUTFILE parameter.
This command displays a binding directory named STORE.
member-name: Specify the file member that receives
the output. If OUTMBR(member-name) is specified and
the member does not exist, the system creates it.
(P) ─────────────────────────────────────5%
55──DSPCCTRTE──CCTNAME(──IPX-circuit-name──)──RMTNETNBR(──remote-IPX-network-number──)────
Note:
P All parameters preceding this point can be specified in positional form.
(P) ──────────────────────5%
55──DSPCCTSRV──CCTNAME(──IPX-circuit-name──)──SRVNAME(──service-name──)──SRVTYPE(──┬─\ADVPRTSVR──┬──)────
├─\ARCHIVEQ───┤
├─\ARCHIVESVR─┤
├─\FILESVR────┤
├─\JOBQ───────┤
├─\JOBSVR─────┤
├─\NTWENHINTG─┤
├─\PRTQ───────┤
├─\PRTSVR─────┤
├─\RMTBRGSVR──┤
└─\SVRMAP─────┘
Note:
P All parameters preceding this point can be specified in positional form.
┌─\LIBL/────────┐
(P) ────────────────────────────────5
55──DSPCDEFNT──CDEFNT(──┼───────────────┼──┬─\FNTCHRSET──────┬──)──┬────────────────────────┬───
├─\CURLIB/──────┤ └─coded-font-name─┘ │ ┌─\──────┐ │
├─\USRLIBL/─────┤ └─OUTPUT(──┴─\PRINT─┴──)─┘
├─\ALLUSR/──────┤
├─\ALL/─────────┤
├─\DBCSFNTLIB/──┤
└─library-name/─┘
(1) ───────────────────────────────────────────────────────────────────────────────5%
5──┬────────────────────────────────────────┬───
└─FNTCHRSET(──font-character-set-name──)─┘
Notes:
P All parameters preceding this point can be specified in positional form.
1 If CDEFNT(*FNTCHRSET) is specified, a font character set name must be specified for FNTCHRSET.
(P) ──────────────────────────────────────────────────5%
55──DSPCFGL──CFGL(──configuration-list-name──)──┬────────────────────────┬───
│ ┌─\──────┐ │
└─OUTPUT(──┴─\PRINT─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose OUTPUT
Specifies whether the output from the command is
The Display Configuration List (DSPCFGL) command dis- shown at the requesting workstation or printed with the
plays the entries of a configuration list. Output is directed to job's spooled output. More information on this param-
a display or a spooled printer file as indicated by the eter is in Appendix A, “Expanded Parameter
OUTPUT parameter and job type. Descriptions.”
Note: To see the parameter and value descriptions for this *: Output requested by an interactive job is shown on
command, refer to the online help text. For more the display. Output requested by a batch job is printed
information about printing the help text, refer to with the job's spooled output.
“Printing CL Command Descriptions” in Chapter 1.
*PRINT: The output is printed with the job's spooled
output.
Required Parameters
CFGL Example
Specifies the name of the configuration list being dis- DSPCFGL CFGL(CONFIGð1)
played.
This command displays the configuration list named
CONFIG01.
Optional Parameters
┌─\LIBL/────────┐
(P) ──────────────────────────────────────────────5%
55──DSPCLS──CLS(──┼───────────────┼──class-name──)──┬────────────────────────┬───
├─\CURLIB/──────┤ │ ┌─\──────┐ │
└─library-name/─┘ └─OUTPUT(──┴─\PRINT─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
┌─\LIBL/────────┐
(P) ────────────────────────────────────────────5%
55──DSPCMD──CMD(──┼───────────────┼──command-name──)──┬────────────────────────┬───
├─\CURLIB/──────┤ │ ┌─\──────┐ │
└─library-name/─┘ └─OUTPUT(──┴─\PRINT─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
(P) ──────────────────────────────────────────────────────5%
55──DSPCNNL──CNNL(────connection-list────)──┬────────────────────────┬───
│ ┌─\──────┐ │
└─OUTPUT(──┴─\PRINT─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
55──DSPCNNSTS──DEVD(──device-description-name──)──┬────────────────────────┬───────────────────────────────────────────────────5%
│ ┌─\──────┐ │
└─OUTPUT(──┴─\PRINT─┴──)─┘
Purpose DEVD
Specifies the name of the network device description
The Display Connection Status (DSPCNNSTS) command whose active connections are being displayed.
shows current information about connection-oriented proto-
cols used by, and all acceptable inbound routing data speci-
fied for, network devices. If one or more connections are Optional Parameters
active, the connection characteristics are shown for each. OUTPUT
Specifies whether the output from the command is
Restrictions:
shown at the requesting workstation or printed with the
1. The user must have operational authority to the device job's spooled output. More information on this param-
specified on the DEVD parameter. eter is in Appendix A, “Expanded Parameter
2. This command is valid for all network devices, but Descriptions.”
connection-oriented status is provided only for devices *: Output requested by an interactive job is shown on
with a link type of X.25. the display. Output requested by a batch job is printed
Note: To see the parameter and value descriptions for this with the job's spooled output.
command, refer to the online help text. For more *PRINT: The output is printed with the job's spooled
information about printing the help text, refer to output.
“Printing CL Command Descriptions” in Chapter 1.
Example
Required Parameters DSPCNNSTS DEVD(PRTR48X) OUTPUT(\PRINT)
(P) ────────────────────────────────────────5%
55──DSPCOSD──COSD(──class-of-service-description-name──)──┬────────────────────────┬───
│ ┌─\──────┐ │
└─OUTPUT(──┴─\PRINT─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
┌─\LIBL/────────┐
(P) ─┬────────────────────────┬──────────────5%
55──DSPCPCST──FILE(──┼───────────────┼──physical-file──)──CST(──constraint-name──)────
├─\CURLIB/──────┤ │ ┌─\──────┐ │
└─library-name/─┘ └─OUTPUT(──┴─\PRINT─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
┌─\LIBL/────────┐
(P) ─┬────────────────────────┬───────────────────────────────────5%
55──DSPCSI──CSI(──┼───────────────┼──side-information-name──)────
├─\CURLIB/──────┤ │ ┌─\──────┐ │
└─library-name/─┘ └─OUTPUT(──┴─\PRINT─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
*LIBL: All libraries in the job's library list are DSPCSI CSI(SIDEOBJ)
searched until the first match is found.
This command locates the first side information object named
*CURLIB: The current library for the job is SIDEOBJ in the library list and displays the side information.
searched. If no library is specified as the current
library for the job, the QGPL library is used. Example 2: Printing Side Information
library-name: Specify the name of the library to be DSPCSI CSI(QGPL/SIDEOBJ) OUTPUT(\PRINT)
searched.
This command prints the side information contained in the
side-information-name: Specify the name of the object object SIDEOBJ in library QGPL with the job's spooled
that contains the desired side information. This is the output.
Common Programming Interface (CPI)-Communications
symbolic destination name (sym_dest_name).
(P) ──────────────5%
55──DSPCTLD──CTLD(──controller-description-name──)──┬────────────────────────┬──┬────────────────────────────┬───
│ ┌─\──────┐ │ │ ┌─\ALL───────┐ │
└─OUTPUT(──┴─\PRINT─┴──)─┘ └─OPTION(──┼─\BASIC─────┼──)─┘
├─\SWTLINLST─┤
├─\DEV───────┤
├─\RMTID─────┤
├─\APPN──────┤
└─\TMRRTY────┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose OPTION
Specifies the displays to be shown.
The Display Controller Description (DSPCTLD) command
*ALL: All displays that apply to this controller are
displays a controller description. Output is directed to a
shown.
display or spooled printer file as indicated by the OUTPUT
and OPTION parameters as well as the job type. *BASIC: The basic displays that apply to this controller
are shown, but additional information displays are not
Note: To see the parameter and value descriptions for this
shown.
command, refer to the online help text. For more
information about printing the help text, refer to *SWTLINLST: The switched line list displays that apply
“Printing CL Command Descriptions” in Chapter 1. to this switched or switched network backup (SNBU)
controller are shown.
Required Parameters *DEV: The device attachment displays that apply to this
controller are shown.
CTLD
*RMTID: The remote identifiers for switched binary syn-
Specifies the name of the controller description being
chronous communications (BSC) controllers are dis-
displayed.
played.
*APPN: The advanced peer-to-peer networking (APPN)
Optional Parameters values for this controller are displayed.
OUTPUT *TMRRTY: The timer and retry options for this controller
Specifies whether the output from the command is are displayed.
shown at the requesting workstation or printed with the
job's spooled output. More information on this param-
eter is in Appendix A, “Expanded Parameter Example
Descriptions.” DSPCTLD CTLD(CONTROLð1)
*: Output requested by an interactive job is shown on The command displays information about the controller
the display. Output requested by a batch job is printed description named CONTROL01. The information is dis-
with the job's spooled output. played on the work station from which the command was
*PRINT: The output is printed with the job's spooled submitted. If the command is entered from a batch job, the
output. output from the display is printed with the job's spooled
output.
(P) ───────────────────────────────────────────────────────────────────────────────────5%
55──DSPCURDIR──┬────────────────────────┬───
│ ┌─\──────┐ │
└─OUTPUT(──┴─\PRINT─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose OUTPUT
Specifies whether the output from the command is
The Display Current Directory (DSPCURDIR) command is shown at the requesting workstation or printed with the
used to display the name of the current working directory. job's spooled output. More information on this param-
eter is in Appendix A, “Expanded Parameter
Restrictions: Descriptions.”
The user must have *X authority to the current directory. *: Output requested by an interactive job is shown on
The user must have *RX authority to each directory in the display. Output requested by a batch job is printed
the path. with the job's spooled output.
Note: To see the parameter and value descriptions for this *PRINT: The output is printed with the job's spooled
command, refer to the online help text. For more output.
information about printing the help text, refer to
“Printing CL Command Descriptions” in Chapter 1.
Example
DSPCURDIR
Optional Parameters
This command displays the name of the current working
directory.
(P) ──────────────────────────────────────────────────────────────────────────────────────5%
55──DSPDBG──┬────────────────────────┬───
│ ┌─\──────┐ │
└─OUTPUT(──┴─\PRINT─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
Programs that are in debug mode but have not been called *: Output requested by an interactive job is shown on
are also shown. the display. Output requested by a batch job is printed
with the job's spooled output.
Restrictions: *PRINT: The output is printed with the job's spooled
1. This command is valid only in debug mode. To start output.
debug mode, see the Start Debug (STRDBG) command.
2. This command cannot be used if the user is servicing Example
another job, and that job is on a job queue, or is being DSPDBG
held, suspended, or ended.
3. This command cannot be used to show the procedures If entered interactively, this command shows the current attri-
of a bound program on the stack. Use the Display Job butes of debug mode at the display station. Also shown are
(DSPJOB) command to show those procedures. the breakpoints at which any of the programs being
debugged are stopped, the recursion levels of the programs
4. This command cannot be used to show bound programs that are currently active, and the names of the programs that
that are being debugged. have not been called.
Note: To see the parameter and value descriptions for this
command, refer to the online help text. For more
55──DSPDBGWCH──────────────────────────────────────────────────────────────────────────────────────────────────────────────────5%
Purpose Example
DSPDBGWCH
The Display Debug Watches (DSPDBGWCH) command
shows the list of debug watches that have been set by This command shows the current debug watches that have
system debug support, for all processes on the system. This been set by the system debug support.
does not include watches that have been set in the Dedi-
cated Service Tool (DST) support of the system.
┌─\LIBL/────────┐
(P) ─────────────5
55──DSPDBR──FILE(──┼───────────────┼──┬─\ALL───────────────┬──)──┬─────────────────────────────────────────────┬───
├─\CURLIB/──────┤ ├─generic\-file-name─┤ │ ┌─\NONE───────┐ │
├─\USRLIBL/─────┤ └─file-name──────────┘ ├─MBR(──┴─member-name─┴──)────────────────────┤
├─\ALLUSR/──────┤ └─RCDFMT(──┬─\NONE───────────────────────┬──)─┘
├─\ALL/─────────┤ ├─\ALL────────────────────────┤
└─library-name/─┘ ├─record-format-name──────────┤
└─generic\-record-format-name─┘
5──┬──────────────────────────┬──┬──────────────────────────────────────────────────────┬───────────────────────────────────────5
│ ┌─\────────┐ │ │ ┌─\LIBL/────────┐ │
(1) ─)─┘
└─OUTPUT(──┼─\PRINT───┼──)─┘ └─OUTFILE(──┼───────────────┼──database-file-name───
└─\OUTFILE─┘ ├─\CURLIB/──────┤
└─library-name/─┘
5──┬─────────────────────────────────────────────┬─────────────────────────────────────────────────────────────────────────────5%
│ ┌─\FIRST──────┐ ┌─\REPLACE─┐ │
(2) ─┴─member-name─┴──┼──────────┼──)─┘
└─OUTMBR(───
└─\ADD─────┘
Notes:
P All parameters preceding this point can be specified in positional form.
shown. Only the libraries in the specified library qualifier file-name: Specify the full name of the database file that
that the user either owns or is authorized to use are has its relational information shown.
searched for the files.
The name of the file can be qualified by one of the fol- Optional Parameters
lowing library values:
MBR
*LIBL: All libraries in the job's library list are Specifies the name of the member in a database file
searched until the first match is found. whose dependent information is shown, printed, or
*CURLIB: The current library for the job is placed in a database file.
searched. If no library is specified as the current *NONE: No information about the file member's
library for the job, the QGPL library is used. relations is provided. File relations or record format
*USRLIBL: Only the libraries in the user portion of relations are provided.
the job's library list are searched. member-name: Specify the name of the database file
*ALL: All libraries in the system, including QSYS, member whose relations information is provided. If a
are searched. member name is specified, either one file name or a
generic file name must be specified. If MBR is specified,
*ALLUSR: All user libraries are searched. All RCDFMT cannot be specified.
libraries with names that do not begin with the letter
Q are searched except for the following: RCDFMT
#CGULIB #DFULIB #RPGLIB #SEULIB Specifies the name of the record format of the database
#COBLIB #DSULIB #SDALIB file member whose relations information is provided. If
RCDFMT is specified, MBR cannot be specified.
Although the following Qxxx libraries are provided
by IBM, they typically contain user data that *NONE: No record format relations information is pro-
changes frequently. Therefore, these libraries are vided.
considered user libraries and are also searched: *ALL: Relations information about all record formats in
| QDSNX QPFRDATA QUSRBRM QUSRSYS the specified files is provided.
| QGPL QRCL QUSRIJS QUSRVxRxMx record-format-name: Specify the full name of the record
| QGPL38 QS36F QUSRINFSKR format whose relations information is provided.
| QMQMDATA QUSER38 QUSRNOTES
| QMQMPROC QUSRADSM QUSRRDARS generic*-record-format-name: Specify the generic name
of the record format or several record formats in the
Note: A different library name, of the form
specified files whose relations information is provided. A
QUSRVxRxMx, can be created by the user
generic name is a character string of one or more char-
for each release that IBM supports. VxRxMx
acters followed by an asterisk (*); for example, ABC*.
is the version, release, and modification level
The asterisk substitutes for any valid characters. A
of the library.
generic name specifies all objects with names that begin
library-name: Specify the name of the library to be with the generic prefix for which the user has authority.
searched. If an asterisk is not included with the generic (prefix)
name, the system assumes it to be the complete object
*ALL: All files in the specified library (or in all libraries
name. If the complete object name is specified, and
identified in the library qualifier to which the user has
multiple libraries are searched, multiple objects can be
access) have their relational information shown.
displayed only if *ALL or *ALLUSR library values can be
generic*-file-name: Specify the name of the database specified for the name. For more information on the use
file or the generic name of several database files in the of generic names, refer to “Generic Object Names” in
specified library qualifier that have relational information Chapter 2.
shown. A generic name is a character string of one or
more characters followed by an asterisk (*); for example, OUTPUT
ABC*. The asterisk substitutes for any valid characters. Specifies whether the output from the command is
A generic name specifies all objects with names that shown at the requesting work station, printed with the
begin with the generic prefix for which the user has job's spooled output, or placed in a database file. More
authority. If an asterisk is not included with the generic information on this parameter is in Appendix A,
(prefix) name, the system assumes it to be the complete “Expanded Parameter Descriptions.”
object name. If the complete object name is specified, *: Output requested by an interactive job is shown on
and multiple libraries are searched, multiple objects can the display. Output requested by a batch job is printed
be displayed only if *ALL or *ALLUSR library values can with the job's spooled output.
be specified for the name. For more information on the
*PRINT: The output is printed with the job's spooled
use of generic names, refer to “Generic Object Names”
output on a printer.
in Chapter 2.
*OUTFILE: The output is sent to the database file spec- *ADD: If a member exists, the system adds the new
ified on the OUTFILE parameter. records to the end of the existing records.
OUTFILE
Specifies the qualified name of the database output file Examples
where the specified relational information is stored. If
the specified file does not exist, the system creates a In the following examples, assume that there is an interactive
database file and member in the specified library. environment and that the user of the command is authorized
When creating the database output file, the current date, to access all relevant libraries and objects.
time, and system name must be included. The system
Example 1: Displaying Database Relations Information
name is the name of the source system, not the target
system. DSPDBR FILE(LIBRARY1/FILE1) RCDFMT(FORMAT1)
If the file is created, the text is "Outfile for DSPDBR" and This command shows a list of the names and database
the public authority is *EXCLUDE. relations information for all files that use the FORMAT1
Note: The outfile format must be the same as format and are associated with FILE1 in LIBRARY1.
QWHDRDBR of system file QADSPDBR in the Because the environment is interactive, the output is shown
QSYS library. at the work station running this command.
The name of the database output file can be qualified by Example 2: Displaying Database Relations Information
one of the following library values:
DSPDBR FILE(LIB1/FILE1)
*LIBL: All libraries in the job's library list are
searched until the first match is found. This command shows database relations information for all
files that are dependent on FILE1 in LIB1 for data sharing. It
*CURLIB: The current library for the job is is shown at the work station running this command.
searched. If no library is specified as the current
library for the job, the QGPL library is used. Example 3: Displaying Database Relations Information
library-name: Specify the name of the library to be DSPDBR FILE(LIB1/FILE1) MBR(MEMBER1)
searched.
This command shows database relations information for all
database-file-name: Specify the name of the database members that are dependent on MEMBER1 in FILE1 in LIB1
file where the relational information is stored. If the for data sharing or access path sharing. They are shown at
specified file is not found, a file and a file member are the work station running this command.
created in the specified library, or in the current library if
its name is not qualified. This file can be used when
other DSPDBR commands are entered. The Additional Considerations
IBM-supplied database file, QADSPDBR, cannot be
specified. When the DSPDBR command is entered, the database is
searched for the specified relationships and a record is gen-
OUTMBR erated for each relationship (dependency) that is found. The
Specifies the name of the database file member to which records are placed in the printer device file named
the output is directed. QPDSPDBR. If OUTPUT(*PRINT) is specified on the
Element 1: Member to Receive Output command, the records are listed on the printer in the fol-
lowing order:
*FIRST: The first member in the file receives the output.
If OUTMBR(*FIRST) is specified and the member does Header information, which lists the DSPDBR command
not exist, the system creates a member with the name of input values and the files identified in the database that
the file specified in the OUTFILE parameter. match the command's request.
The names of the files that are dependent on the files
member-name: Specify the name of the file member identified by the FILE parameter. A file can be
that receives the output. If OUTMBR(member-name) is dependent on another file for its access path or its data.
specified and the member does not exist, the system This information is listed when neither MBR nor
creates it. If the member exists, the user has the option RCDFMT is specified.
to add records to the end of the existing member or to If a member name was specified in the MBR parameter,
clear the existing member before adding the new the names of the file members that are dependent on a
records. member in the file (a member can be dependent on
Element 2: Operation to Perform on Member another member for its access path or its data).
The names of the database files that are dependent on
*REPLACE: If a member exists, the system clears it
a record format of the specified files, if a record format
and adds the new records.
name was specified in the RCDFMT parameter.
┌─\LIBL/────────┐
(P) ────────────────────────────────5%
55──DSPDDMF──FILE(──┼───────────────┼──┬─\ALL───────────────┬──)──┬────────────────────────┬───
├─\CURLIB/──────┤ ├─file-name──────────┤ │ ┌─\──────┐ │
├─\USRLIBL/─────┤ └─generic\-file-name─┘ └─OUTPUT(──┴─\PRINT─┴──)─┘
├─\ALL/─────────┤
├─\ALLUSR/──────┤
└─library-name/─┘
Note:
P All parameters preceding this point can be specified in positional form.
(P) ──────────────────5%
55──DSPDEVD──DEVD(──device-description-name──)──┬────────────────────────┬──┬────────────────────────────┬───
│ ┌─\──────┐ │ │ ┌─\ALL───────┐ │
└─OUTPUT(──┴─\PRINT─┴──)─┘ └─OPTION(──┼─\BASIC─────┼──)─┘
├─\SWTLINLST─┤
├─\MODE──────┤
├─\AUXDEV────┤
├─\MLBRSC────┤
└─\USRDFNOPT─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose OPTION
Specifies the displays to be shown.
The Display Device Description (DSPDEVD) command dis-
*ALL: All displays that apply to this device type are
plays a device description. Output is directed to a display or
shown.
a spooled printer file as indicated by the output and option
parameters, and job type. *BASIC: The basic displays that apply to this device
type are shown, but additional information displays are
Note: To see the parameter and value descriptions for this
not shown.
command, refer to the online help text. For more
information about printing the help text, refer to *SWTLINLST: The display showing a list of switched
“Printing CL Command Descriptions” in Chapter 1. lines for this local area network (LAN) printer device is
shown.
(P) ──────────────────────────────────────────5
55──DSPDIRE──┬──────────────────────────────────────┬──┬──────────────────────────┬───
│ ┌─\ALL──────────────────┐ │ │ ┌─\────────┐ │
├─USRID(──┴─user-ID──user-address─┴──)─┤ └─OUTPUT(──┼─\PRINT───┼──)─┘
└─USER(──┬─\CURRENT──────────┬──)──────┘ └─\OUTFILE─┘
└─user-profile-name─┘
5──┬────────────────────────────────────────────────────┬──┬───────────────────────────────────────────┬────────────────────────5
│ ┌─\LIBL/────────┐ │ │ ┌─\FIRST──────┐ ┌─\REPLACE─┐ │
└─OUTFILE(──┼───────────────┼──database-file-name──)─┘ └─OUTMBR(──┴─member-name─┴──┼──────────┼──)─┘
├─\CURLIB/──────┤ └─\ADD─────┘
└─library-name/─┘
5──┬────────────────────────┬──┬───────────────────────────┬──┬────────────────────────┬────────────────────────────────────────5
│ ┌─\BASIC─┐ │ │ ┌─\TYPE1─┐ │ │ ┌─\LCL───┐ │
└─DETAIL(──┴─\FULL──┴──)─┘ └─OUTFILFMT(──┼─\TYPE2─┼──)─┘ └─OUTDTA(──┴─\ALL───(1) ┴──)─┘
└─\TYPE3─┘
5──┬────────────────────────────────────────────────────┬──────────────────────────────────────────────────────────────────────5%
│ ┌─\SYSVAL──────────────────────────┐ │
└─CMDCHRID(──┼─\DEVD────────────────────────────┼──)─┘
└─graphic-character-set──code-page─┘
Notes:
1 When OUTPUT(*) is specified, both local and shadowed data is displayed.
Purpose USRID
Specifies the user ID and address of the user for whom
The Display Directory Entries (DSPDIRE) command is used the directory entries are displayed, printed, or written to
to display, print, or create a database file for some or all a database file. If the USRID parameter is specified, the
system distribution directory entries. The database file USER parameter cannot be specified.
output is displayed, printed, or created based on the fol-
For displayed output, if the user ID and address specify
lowing:
an entry that has only one description, the directory
For displayed output, when the USRID or the USER details for that entry are displayed. If several
parameters apply to more than one directory entry, the descriptions are associated with the specified user ID
system provides a list of entries. When these parame- and address, a list of matching user IDs and addresses
ters uniquely identify a directory entry, the system pro- is displayed from which the user can select a user ID
vides the details for the entry. and address to view the details.
For printed or database file output, if the USRID param- For printed output or database file output, the full direc-
eter specifies the full directory, the DETAIL parameter tory details, including all descriptions for that user ID and
determines whether a list of the entries or the full details address, are printed or sent to a database file. More
for each entry is the output. If the USRID or the USER information on specifying the user ID and address is in
parameters specify a user ID or profile, the full details for the SNA Distribution Services book.
that user are sent to the output.
*ALL: All entries in the system distribution directory are
The DSPDIRE command does not update the directory. displayed, printed, or directed to a database file. The
That function is provided interactively with display support by entries are provided in alphabetical order by user ID and
the Work with Directory Entries (WRKDIRE) command, the address. If the output is directed to a printed list or
Add Directory Entry (ADDDIRE) command, the Remove output file, the DETAIL parameter specifies whether a
Directory Entry (RMVDIRE) command, the Change Directory list of user IDs, addresses, and descriptions is the output
Entry (CHGDIRE) command, and the Rename Directory or if the full directory detail is the output.
Entry (RNMDIRE) command. Element 1: User ID
Note: To see the parameter and value descriptions for this user-ID: Specify the user ID of the user for whom an
command, refer to the online help text. For more existing directory entry is displayed, printed, or directed
information about printing the help text, refer to to a database file.
“Printing CL Command Descriptions” in Chapter 1.
Element 2: User Address
user-address: Specify the user address of the user for
Optional Parameters whom an existing directory entry is displayed, printed, or
directed to a database file.
*OUTFILE: The output is directed to the database file Element 2: Operation to Perform on Member
specified on the OUTFILE parameter. *REPLACE: The system clears the existing member
and adds the new records.
OUTFILE
Specifies the qualified name of the database file to *ADD: The system adds the new records to the end of
which the output of the display is directed. If the data- the existing records.
base file does not exist, this command creates it in the
DETAIL
specified library. If no library is specified, the database
Specifies how much detail is printed or directed to the
file is created in the user default library specified in the
database file. This parameter is not used when the
user profile. If no default library is specified, the data-
output is directed to a display (OUTPUT(*)) or when a
base output file is created in the QGPL library.
specific user ID or profile is specified.
If the database file is qualified with *LIBL but the system
*BASIC: The output is a list of all user IDs, addresses,
cannot find the file, the database file is created in the
and descriptions contained in the directory.
user's default library, if it is specified in the user profile.
If the default library is not specified, the file is created in *FULL: The output is the full set of details for the user
the QGPL library. in the directory. When USRID(*ALL) is specified, the
printed list contains a page for each unique user ID and
See the OUTFILFMT parameter for the valid output file
address from the directory, with all of the details for that
types and their names. More information on defining the
entry. Multiple descriptions for a user ID and address
format of database files as output files is in the Office
are included with the details. For a database file, a
Services Concepts and Programmer’s Guide book.
record is created for each unique user ID, address, and
The name of the database file can be qualified by one of description, containing all of the details for each entry.
the following library values: When several descriptions exist for a user ID and
address, a full record is the output for each description,
*LIBL: All libraries in the job's library list are
and only the description field is different.
searched until the first match is found.
When a user ID and address or user profile name is
*CURLIB: The current library for the job is
specified on an input parameter, the printed list contains
searched. If no library is specified as the current
one page of output with all descriptions included with the
library for the job, the QGPL library is used.
details for the user ID and address. The output file has
a full detail record for each description. Only the code-page: Specify the code page. Valid values range
description field is different between the records. from 1 through 9999.
OUTFILFMT
Specifies the format of the output file. Examples
*TYPE1: The format is defined by model output file Example 1: Showing the Display for One Description
QAOSDIRO in library QSYS with record format name
OSDIRE. This format does not include the new directory DSPDIRE USRID(HURST NEWYORK)
fields added since Release 2.0.
This command shows the Display Directory Entry Details
*TYPE2: The output file format is defined by model display for user ID and address HURST NEWYORK if this
output files QAOSDIRB and QAOSDIRF in library QSYS. user ID has only one description associated with it. If more
If DETAIL(*BASIC) is specified, the output file contains than one description exists, the Display Directory Entries
only the basic fields, and the model output file display is shown with all entries for the user ID and address.
QAOSDIRB is used with the record format name
Example 2: Printing Directory Information
OSDIRB. If DETAIL(*FULL) is specified, the output file
contains all of the detail fields, and the model output file DSPDIRE USER(JONES) OUTPUT(\PRINT)
QAOSDIRF is used with the record format name
This command prints the full directory details for user profile
OSDIRF.
JONES. If there is more than one description in the directory
*TYPE3: The output file contains all the detail fields and for JONES, the printed output contains each description.
the X.400 originator/recipient (O/R) name. The model
output file QAOSDIRX in library QSYS is used with the Example 3: Sending Full Details to a Database File
record format name OSDIRX. DSPDIRE OUTPUT(\OUTFILE) OUTFILE(MYLIB/DIRLIST)
OUTMBR(\FIRST \REPLACE)
OUTDTA
DETAIL(\FULL)
Specifies the type of data to include as output to the
value specified on the OUTPUT parameter. This param- This command sends a record to the database file DIRLIST
eter is not used when the output is directed to a display in library MYLIB for each entry in the directory. This record
(OUTPUT(*)) or when a specific user ID or profile is contains the full details for each user. The format of the
specified. output file is the one used prior to Release 3.0 because of
*LCL: Locally-defined data is included. Shadowed data the default of OUTFILFMT(*TYPE1). If the file does not
is not included. exist, it is created. If the file does exist, it is replaced.
*ALL: All directory entry data is included. This includes Example 4: Sending Basic Information to a Database
locally-defined data and shadowed data. File
CMDCHRID DSPDIRE OUTPUT(\OUTFILE) OUTFILE(MYLIB/DIRLIST)
Specifies the character identifier (graphic character set DETAIL(\BASIC) OUTFILFMT(\TYPE2)
and code page) for data being specified as parameter
values on this command. This character identifier This command sends a record to the database file named
(CHRID) is related to the display device used to specify DIRLIST in the MYLIB library for each entry in the directory.
the command. More information about CHRID pro- The data contains only the basic fields, user ID, address, and
cessing is in the Application Display Programming book. description. If the file named DIRLIST in the MYLIB library
already exists for releases 1.0 or 2.0 data (see Example 2),
*SYSVAL: The system determines the graphic char- an error occurs; otherwise, the file is be created in the
acter set and code page values for the command param- Release 3.0 format.
eters from the QCHRID system values.
*DEVD: The system determines the graphic character
set and code page values for the command parameter
Additional Considerations
from the display device description where the command Error messages are returned when errors are encountered
is entered. This option is valid only when specified from while processing the DSPDIRE command. If the command
an interactive job. If this value is specified in an interac- is entered interactively, error messages are displayed at the
tive CL program or a batch job, an error message is work station. When a batch job enters the command, error
sent. messages are returned, and the job that runs the command
Element 1: Character Set is responsible for processing them.
graphic-character-set: Specify the graphic character set If the USRID parameter specifies the user ID and address of
values used to create the command parameters. Valid a user not currently in the directory, an error message is
values range from 1 through 9999. returned. Likewise, if a user profile not contained in the
Element 2: Code Page
(P) ─┬─────────────────────────────────────┬──┬───────────────────────┬─────────────────────────5
55──DSPDKT──DEV(──device-name──)────
│ ┌─\ALL─────────────────┐ │ │ ┌─\LABELS─┐ │
└─LABEL(──┴─data-file-identifier─┴──)─┘ └─DATA(──┴─\SAVRST─┴──)─┘
5──┬────────────────────────┬──────────────────────────────────────────────────────────────────────────────────────────────────5%
│ ┌─\──────┐ │
└─OUTPUT(──┴─\PRINT─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
Note: When showing diskettes with labels that are not IBM *SAVRST: Shows the save or restore summary infor-
standard labels, unpredictable results may occur. To mation about the command and each saved object.
initialize the diskette, run the Initialize Diskette OUTPUT
(INZDKT) command with CHECK(*NO) specified. Specifies whether the output from the command is
Note: To see the parameter and value descriptions for this shown at the requesting work station or printed with the
command, refer to the online help text. For more job's spooled output on a printer. More information on
information about printing the help text, refer to this parameter is in Appendix A, “Expanded Parameter
“Printing CL Command Descriptions” in Chapter 1. Descriptions.”
*: Output requested by an interactive job is shown on
Required Parameters the display. Output requested by a batch job is printed
with the job's spooled output.
DEV
*PRINT: The output is printed with the job's spooled
Specifies the name of the device on which the volume
output.
being displayed is located.
Note: Each file on the diskette that was created by the
Save (SAV) command is printed as a separate
Optional Parameters listing.
LABEL
Specifies the data file identifier, or all the identifiers, of
the data files on the diskette being shown. The data file Example
identifier is stored in a label in the volume label area of DSPDKT DEV(DKTð1)
the diskette, and it specifies the identifier of the file that
exists on the diskette. This command shows the volume label and all the data file
identifiers for the diskette in device DKT01.
55──DSPDLOAUD──DLO(──┬─\ALL─────────────────────────┬──)──┬──────────────────────────┬───(P) ──┬──────────────────────────────┬─────5
(1) ─────────────────────┤
├─\ROOT─── │ ┌─\NONE───────┐ │ (4) ─object-name──)─┘
└─SYSOBJNAM(───
├─\SYSOBJNAM───────────────────┤ (2) ─────┼──)─┘
└─FLR(──┼─\ANY───
└─document-library-object-name─┘ (3) ────┤
├─\ROOT───
└─folder-name─┘
5──┬──────────────────────────┬──┬────────────────────┬──┬─────────────────────────┬────────────────────────────────────────────5
│ ┌─\────────┐ │ │ ┌─\FLR─┐ │ │ ┌─\CURRENT─┐ │
└─OUTPUT(──┼─\PRINT───┼──)─┘ └─TYPE(──┼─\DOC─┼──)─┘ └─LEVEL(──┴─\ALL───(5) ──┴──)─┘
└─\OUTFILE─┘ └─\ALL─┘
5──┬────────────────────────────────────────────────────┬──┬───────────────────────────────────────────┬───────────────────────5%
│ ┌─\LIBL/────────┐ │ │ ┌─\FIRST──────┐ ┌─\REPLACE─┐ │
└─OUTFILE(──┼───────────────┼──database-file-name──)─┘ └─OUTMBR(──┴─member-name─┴──┼──────────┼──)─┘
├─\CURLIB/──────┤ └─\ADD─────┘
└─library-name/─┘
Notes:
1 DLO(*ROOT) is valid only when FLR(*NONE) is specified.
5 LEVEL(*ALL) is valid only when DLO(*ALL), FLR( folder-name), and OUTPUT(*PRINT) or OUTPUT(*OUTFILE) are speci-
fied.
P All parameters preceding this point can be specified in positional form.
*PRINT: The output is printed with the job's spooled library-name: Specify the name of the library to be
output. searched.
*OUTFILE: The output is directed to the database file database-file-name: Specify the name of the database
specified on the OUTFILE parameter. file to which the output from the command is directed.
TYPE OUTMBR
Specifies whether the documents or folders contained in Specifies the name of the database file member to which
the folder specified on the FLR parameter are displayed. the output from the command is directed. If the member
This parameter is valid when FLR(folder-name) is speci- already exists, the system uses the value specified on
fied and is defaulted in all other cases. When the second element of this parameter to determine
DLO(*ALL) FLR(*ANY) is specified, TYPE(*ALL) is used. whether the member is cleared before the new records
When DLO(*ALL) FLR(*ROOT) is specified, TYPE(*FLR) are added. If the member does not exist and a member
is used. When DLO(*ALL) FLR(*NONE) is specified, name is not specified, the system creates a member
TYPE(*DOC) is used. When a single object is specified using the name of the output file specified on the
on the command, the TYPE parameter is ignored. OUTFILE parameter. If an output file member name is
*FLR: The folders contained in the specified folder are specified but the member does not exist, the system
displayed. creates it.
*DOC: The documents contained in the specified folder Element 1: Member to Receive Output
are displayed. *FIRST: The first member in the database file is used.
*ALL: The documents and folders contained in the member-name: Specify the file member that receives
specified folder are displayed. the output. If OUTMBR(member-name) is specified and
the member does not exist, the system creates it.
LEVEL
Specifies whether documents and folders at nested Element 2: Operation to Perform on Member
levels in the specified folder are displayed.
*REPLACE: The system clears the existing member
*CURRENT: Only the documents and folders at the and adds the new records.
current level are included in the output.
*ADD: The system adds the new records to the end of
*ALL: The documents and folders at all levels are the existing records.
included in the output.
OUTFILE Examples
Specifies the name of the database file to which the
output of the command is directed. If the output file Example 1: Displaying an Auditing Level
does not exist, the command creates a database file in DSPDLOAUD DLO(MYDOC) FLR(MYFLR)
the specified library. If the command creates the file, the
text associated with the file is "Output file for This command displays the auditing level of document
DSPDLOAUD". The public authority is the same as the MYDOC in folder MYFLR.
create authority specified for the library in which the file
is created. Example 2: Printing Auditing Levels
DSPDLOAUD DLO(\ALL) FLR(\ROOT) OUTPUT(\PRINT)
The name of the database file can be qualified by one of
the following library values: This command prints the auditing levels of all first-level
*LIBL: All libraries in the job's library list are folders on the system.
searched until the first match is found.
Example 3: Listing all Auditing Levels
*CURLIB: The current library for the job is
DSPDLOAUD DLO(\ALL) FLR(\ANY)
searched. If no library is specified as the current
OUTPUT(\OUTFILE) OUTFILE(MYLIB/MYFILE)
library for the job, the QGPL library is used.
This command lists the auditing levels of all DLOs on the
system in the output file MYFILE in library MYLIB.
(P) ─┬──────────────────────────────┬──┬────────────────────────┬──────5%
55──DSPDLOAUT──DLO(──┬─\SYSOBJNAM───────────────────┬──)────
├─\ROOT────────────────────────┤ │ ┌─\NONE───────┐ │ │ ┌─\──────┐ │
└─document-library-object-name─┘ (1) ─┴─folder-name─┴──)───┤ └─OUTPUT(──┴─\PRINT─┴──)─┘
├─FLR(───
└─SYSOBJNAM(───(2) ─object-name──)─┘
Notes:
P All parameters preceding this point can be specified in positional form.
Personal status of the document or folder *NONE: A folder name is not specified. If DLO(name)
is specified and the object is located in a folder,
Specific user authority for the document or folder FLR(*NONE) cannot be specified.
The authority given to the users with no specific folder-name: Specify the name of the folder that con-
authority for the document or folder tains the object. The name can consist of a series of
If a function key is pressed, access codes attached to folder names if the folder that contains the object is
the document library object are displayed. located in another folder. Up to 63 characters can be
specified.
Restrictions:
SYSOBJNAM
1. A user must have *USE authority to the document or Specifies the system object name. A full 10 characters
folder to display that user's authority information about must be specified. This parameter is valid only when
the document or folder. DLO(*SYSOBJNAM) is specified.
2. If the user has *ALL or *ALLOBJ authority to the docu-
OUTPUT
ment or library object, the user sees all authority infor-
Specifies whether the output from the command is
mation.
shown at the requesting workstation or printed with the
3. The user must have *ALLOBJ special authority to job's spooled output. More information on this param-
display the *ROOT folder public authority. eter is in Appendix A, “Expanded Parameter
Note: To see the parameter and value descriptions for this Descriptions.”
command, refer to the online help text. For more *: Output requested by an interactive job is shown on
information about printing the help text, refer to the display. Output requested by a batch job is printed
“Printing CL Command Descriptions” in Chapter 1. with the job's spooled output.
*PRINT: The output is printed with the job's spooled
Required Parameters output.
DLO
Specifies the name of the document or folder to be dis- Example
played. DSPDLOAUT DLO(DOCA) FLR(MYFLR) OUTPUT(\PRINT)
This command prints for DOCA in folder MYFLR a list of all This command prints only the user's authorities if the user of
authorized users and their authorities if the user of this this command has *USE authority. Access codes are also
command has *ALL authority to DOCA in folder MYFLR. shown.
(P) ─┬─────────────────────────────────────────┬──┬────────────────────────┬───────────5
55──DSPDLONAM──DLO(──┬─\DOCID────────┬──)────
├─\LADNTSP──────┤ │ ┌─\NONE───────┐ │ │ ┌─\DOC───┐ │
├─\SYSOBJNAM────┤ (1) ─┴─folder-name─┴──)──────────────┤ └─OBJCLS(──┼─\FLR───┼──)─┘
├─FLR(───
├─document-name─┤ │ ┌─\NONE───────┐ │ (5) ┘
└─\DST───
└─folder-name───┘ ├─DOCID(───(2) ─┴─document-ID─┴──)────────────┤
│ ┌─\NONE──────────┐ │
├─LADNTSP(─── (3) ─┴─LADN-timestamp─┴──)───────┤
│ ┌─\NONE──────────────┐ │
└─SYSOBJNAM(─── (4) ─┴─system-object-name─┴──)─┘
5──┬────────────────────────┬──────────────────────────────────────────────────────────────────────────────────────────────────5%
│ ┌─\──────┐ │
└─OUTPUT(──┴─\PRINT─┴──)─┘
Notes:
P All parameters preceding this point can be specified in positional form.
1 FLR(*NONE) must be specified if *DOCID, *LADNTSP, or *SYSOBJNAM is specified on the DLO parameter.
SYSOBJNAM
Example
Specifies the system object name. DSPDLONAM DLO(MYDOC) FLR(MYFLR) OBJCLS(\DOC)
*NONE: The object is not identified using its system This command finds the document MYDOC in folder MYFLR
object name. and displays all forms of the document's name. If the job is
system-object-name: Specify the 10-character system running in batch mode, the information is printed and not dis-
object name of the document or folder. played.
(P) ──────────────────────────5%
55──DSPDOC──┬────────────────────────────┬──┬──────────────────────────┬──┬──────────────────────┬───
│ ┌─\PRV──────────┐ │ │ ┌─\PRV────────┐ │ │ ┌─\YES─┐ │
└─DOC(──┴─document-name─┴──)─┘ └─FLR(──┴─folder-name─┴──)─┘ └─ALWPRT(──┴─\NO──┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose FLR
Specifies the name of the folder that contains the docu-
The Display Document (DSPDOC) command allows the user ment.
to display a document using the word processing function of
*PRV: The name used in the previous session is used.
OfficeVision More information on displaying documents is in
the Using OfficeVision/400 Word Processing book. folder-name: Specify the name of the folder that con-
tains the document to be displayed.
Note: To see the parameter and value descriptions for this
command, refer to the online help text. For more ALWPRT
information about printing the help text, refer to Specifies whether the user is able to print a document
“Printing CL Command Descriptions” in Chapter 1. while viewing it.
*YES: The user can print a document while viewing it.
Optional Parameters *NO: The user cannot print a document while viewing it.
DOC
Specifies the name of the document to be displayed. Example
*PRV: The name used in the previous session is used. DSPDOC DOC(MYDOC) FLR(MYFLR)
document-name: Specify the name of the document that
This command displays the document MYDOC in folder
is displayed.
MYFLR.
55──DSPDSTL──┬───────────────────────────────────────────┬──┬──────────────────────────────────┬────────────────────────────────5
│ ┌─\ALL───────────────────────┐ │ │ ┌─\ALL──────────────┐ │
└─LSTID(──┴─list-ID──list-ID-qualifier─┴──)─┘ └─OWNER(──┼─\CURRENT──────────┼──)─┘
└─user-profile-name─┘
(P) ──┬────────────────────────────────────────────────────┬──────────────────────────────────────5
5──┬──────────────────────────┬───
│ ┌─\────────┐ │ │ ┌─\LIBL/────────┐ │
└─OUTPUT(──┼─\PRINT───┼──)─┘ └─OUTFILE(──┼───────────────┼──database-file-name──)─┘
└─\OUTFILE─┘ ├─\CURLIB/──────┤
└─library-name/─┘
5──┬───────────────────────────────────────────┬──┬────────────────────────┬────────────────────────────────────────────────────5
│ ┌─\FIRST──────┐ ┌─\REPLACE─┐ │ │ ┌─\BASIC─┐ │
└─OUTMBR(──┴─member-name─┴──┼──────────┼──)─┘ └─DETAIL(──┴─\FULL──┴──)─┘
└─\ADD─────┘
5──┬────────────────────────────────────────────────────┬──────────────────────────────────────────────────────────────────────5%
│ ┌─\SYSVAL──────────────────────────┐ │
└─CMDCHRID(──┼─\DEVD────────────────────────────┼──)─┘
└─graphic-character-set──code-page─┘
Note:
P All parameters preceding this point can be specified in positional form.
information on this parameter is in Appendix A, member-name: Specify the file member that receives
“Expanded Parameter Descriptions.” the output. If OUTMBR(member-name) is specified and
the member does not exist, the system creates it.
*: Output requested by an interactive job is shown on
the display. If the command is run as part of a batch Element 2: Operation to Perform on Member
job, the output is printed with the job's spooled output.
*REPLACE: The system clears the existing member
*PRINT: The output is printed with the job's spooled and adds the new records.
output.
*ADD: The system adds the new records to the end of
*OUTFILE: The output is directed to the database file the existing records.
specified on the OUTFILE parameter.
DETAIL
OUTFILE Specifies how much detail is printed or written to the
Specifies the name of the database file to which the database file. This parameter is not used when the
output of the display is directed. If the database file output is displayed (OUTPUT(*)) or when a specific list
does not exist, this command creates it in the specified ID is specified in the LSTID parameter.
library. If no library is specified, the database file is
Anytime LSTID(*ALL) is specified, the DETAIL param-
created in the user default library specified in the user
eter is used to determine whether a list of all distribution
profile. If no default library was specified, the database
lists or a list of all entries in every distribution list is the
file is created in the QGPL library. If the file is created,
output.
the text is "OUTFILE for DSPDSTL" and the public
authority is *EXCLUDE. Model output file QAOSDSTO in library QSYS is used.
More information on defining the format of database *BASIC: The output is a list of all distribution lists con-
output files is in the Office Services Concepts and tained in the directory.
Programmer’s Guide book. *FULL: The output contains all of the entries in every
The name of the database file can be qualified by one of distribution list contained in the directory.
the following library values:
CMDCHRID
*LIBL: All libraries in the job's library list are Specifies the character identifier (graphic character set
searched until the first match is found. and code page) for data being specified as parameter
values on this command. This character identifier
*CURLIB: The current library for the job is
(CHRID) is related to the display device used to specify
searched. If no library is specified as the current
the command. More information about CHRID pro-
library for the job, the QGPL library is used.
cessing is in the Application Display Programming book.
library-name: Specify the name of the library to be *SYSVAL: The system determines the graphic char-
searched.
acter set and code page values for the command param-
database-file-name: Specify the name of the database eters from the QCHRID system values.
file that receives the output of the display. If the data- *DEVD: The system determines the graphic character
base file is qualified with *LIBL but the system cannot set and code page values for the command parameters
find the file, one is created in the user's default library, if from the display device description where this command
it is specified. If the default library was not specified, the was entered. This option is supported only when the
file is created in the QGPL library. command is entered from an interactive job. If this
option is specified in a batch job, an error message is
OUTMBR
returned.
Specifies the name of the database file member to which
the output is directed. If a member already exists, the Element 1: Character Set
system uses the second element of this parameter to
graphic-character-set: Specify the graphic character set
determine whether the member is cleared before the
values used to create the command parameters. Valid
new records are added. If the member does not exist
values range from 1 through 9999.
and a member name is not specified, the system creates
a member with the name of the output file specified on Element 2: Code Page
the OUTFILE parameter. If an output file member name code-page: Specify the code page. Valid values range
is specified, but the member does not exist, the system from 1 through 9999.
creates it.
Element 1: Member to Receive Output Examples
*FIRST: The first member in the file receives the output.
If OUTMBR(*FIRST) is specified and the member does Example 1: Displaying a List
not exist, the system creates a member with the name of DSPDSTL LSTID(\ALL) OUTPUT(\)
the file specified on the OUTFILE parameter.
This command displays a list of all distribution lists in the This command writes one record for each distribution list
directory. Specifying DSPDSTL without parameters would contained in the directory to the database file ALLLISTS. If
result in the same action. this file is not found in the library list, it is created in the
QGPL library, since no library is specified.
Example 2: Printing a List
DSPDSTL LSTID(DEPT48K DISTLIST) OUTPUT(\PRINT) Example 4: Directing Output for a Distribution List
Owner to a Database File
This command prints a list of all entries in the distribution list DSPDSTL OWNER(ABSMITH) OUTFILE(DISTLIST/ABSMITH)
DEPT48K DISTLIST. The detail parameter is not used when OUTMBR(\FIRST \REPLACE) DETAIL(\BASIC)
printing for a specific list.
This command writes one record for each distribution list
Example 3: Directing Output to a Database File owned by user profile ABSMITH to the database file
DSPDSTL OUTPUT(\OUTFILE) OUTFILE(ALLLISTS) ABSMITH in the library DISTLIST. If this file is not found in
OUTMBR(\FIRST \REPLACE) DETAIL(\BASIC) the library DISTLIST, it is created.
(P)─┬──────────────────────────────────────────────────────────────────────────────────────┬───────────────────────5
55──DSPDSTLOG───
│ ┌─\AVAIL───────┐ ┌─\CURRENT───┐ │
(1) ┴──┼────────────┼──)──┬────────────────────────────────────┬─┘
└─PERIOD(──┴─start-time───
├─\BEGIN─────┤ │ ┌─\AVAIL─────┐ ┌─\CURRENT─┐ │
└─start-date─┘ (2) ┴──┼──────────┼──)─┘
└─(──┴─end-time───
├─\END─────┤
└─end-date─┘
5──┬─────────────────────────────────────┬──┬─────────────────────────────────────┬─────────────────────────────────────────────5
│ ┌─\ALL────────────┐ │ │ ┌─\ALLDST─────────┐ │
│ │ ┌──
──────────┐ │ (6, 7) ─┼─\ALL────────────┼──)─┘
│ └─ENTTYP(─────
(3, 4) 6 (5)
└─FNCTYP(──────┴───┬─\RCV─┬─┴────┴──)─┘ │ ┌──
──────────┐ │
├─\RTR─┤ └──6─┬─\NRM─┬─┴───
(8) ─┘
├─\SND─┤ ├─\ERR─┤
├─\CFG─┤ ├─\RTG─┤
├─\OPR─┤ ├─\DSQ─┤
├─\ORG─┤ └─\SYS─┘
├─\ARV─┤
└─\SYS─┘
5──┬────────────────────────────────────────┬──┬────────────────────────────────────────────────────────┬───────────────────────5
│ ┌─\ALL────┐ ┌─\ALL────┐ │ │ ┌─\ALL────────┐ ┌─\ALL──────────────┐ │
└─ORGUSRID(──┼─\BLANK──┼──┼─\BLANK──┼──)─┘ └─ORGSYSNAME(──┴─system-name─┴──┼─\BLANK────────────┼──)─┘
└─user-id─┘ └─address─┘ └─system-group-name─┘
┌─\ALL──────────────────────────────────────┐
5──JOB(──┴─┬─────────────────────────────┬──job-name─┴──)───────────────────────────────────────────────────────────────────────5
└─┬─────────────┬──user-name/─┘
└─job-number/─┘
5──┬──────────────────────────────────────────────────────────────────────────────────────────────────────────────┬─────────────5
│ ┌─\CURRENT─────────────────────────────────────────────────────────────────────────────────────┐ │
│ │ ┌─\CURRENT───────────────────────────────────┐ │ │
│ │ ┌─\LIBL/────────┐ │ ┌─\LIBL/────────┐ │ │ │
└─RCVRNG(──┴─┼───────────────┼──starting-journal-receiver──┴─┼───────────────┼──ending-journal-receiver─┴─┴──)─┘
├─\CURLIB/──────┤ ├─\CURLIB/──────┤
└─library-name/─┘ └─library-name/─┘
5──┬────────────────────────┬──────────────────────────────────────────────────────────────────────────────────────────────────5%
│ ┌─\──────┐ │
└─OUTPUT(──┴─\PRINT─┴──)─┘
Notes:
P All parameters preceding this point can be specified in positional form.
8 A maximum of 5 repetitions
display gives more specific information on that particular log minutes, and ss = seconds. Valid values for hh
entry. If the user requests printed output, a detail printout for range from 00 through 23. Valid values for mm and
each log entry in the selection is produced. ss range from 00 through 59.
By specifying the appropriate selection criteria, the user can Element 2: Starting Date
determine the following types of information: One of the following is used to specify the starting date
on which or after which the data must have been logged.
Configuration changes that were made, when and by
Entries logged before the specified date are not shown.
whom they were made for all tables or for specific tables
*CURRENT: The logged data for the current day and
Configuration changes correlated with error entries or
between the specified starting and ending times (if speci-
distributions routed and/or sent
fied) is shown.
List error entries for all functions or for specific functions
*BEGIN: The logged data from the beginning of the log
(such as routing errors)
is shown. If *BEGIN is specified, then any time value
All distributions received, routed, or sent during a other than *AVAIL for start-time is ignored.
selected time interval
start-date: Specify the date displayed. The date must
Activity for a specific sender or receiver job be entered in the format specified by the system values
QDATFMT and, if separators are used, QDATSEP.
Restrictions:
Element 3: Ending Time
1. This command is shipped with public *EXCLUDE
One of the following is used to specify the ending time
authority.
before which the data must have been logged.
2. This command cannot be used to show information on
*AVAIL: The logged data that is available for the speci-
the 12 by 80 size work station (*DS2) or on the console
fied ending date is shown.
(*DS1).
Note: To see the parameter and value descriptions for this
end-time: Specify the ending time for the specified
ending date that determines the logged data that is
command, refer to the online help text. For more
shown.
information about printing the help text, refer to
“Printing CL Command Descriptions” in Chapter 1. Element 4: Ending Date
One of the following is used to specify the ending date
Optional Parameters before which or on which the data must have been
logged.
PERIOD
Specifies the period of time for which the logged data is *CURRENT: The logged data for the current day and
shown. The following values can be coded in this between the specified starting and ending times (if speci-
parameter, which contains two lists of two elements fied) is shown.
each. *END: The last day on which data was logged is
Element 1: Starting Time shown. If PERIOD(*END) is specified, a time value
other than *AVAIL for end-time is ignored.
One of the following is used to specify the starting time
at which or after which the data must have been logged. end-date: Specify the ending date for which logged data
Entries logged before the specified time and date are not is shown. The date must be entered in the format speci-
shown. fied by the system values QDATFMT and, if separators
are used, QDATSEP.
*AVAIL: The logged data that is available for the speci-
fied starting date is shown. FNCTYP
Specifies the SNADS function that was being performed
start-time: Specify the starting time for the specified
when SNADS log entries were made. If the default
starting date that indicates the logged data that is
value *ALL is not specified, a maximum of eight func-
shown. The time is specified in 24-hour format with or
tions may be specified.
without a time separator as follows:
*ALL: All SNADS functions that made log entries are
With a time separator, specify a string of 5 or 8 used.
digits, where the time separator for the job sepa-
rates the hours, minutes, and seconds. If you issue *RCV: The SNADS receiver function is used.
this command from the command line, the string *RTR: The SNADS router function is used.
must be enclosed in apostrophes. If a time sepa-
*SND: The SNADS sender function is used.
rator other than the separator specified for your job
is used, this command fails. *CFG: The SNADS configuration function is used. If
FNCTYP(*CFG) is specified, the ORGUSRID and
Without a time separator, specify a string of 4 or 6
ORGSYSNAME parameters cannot be specified.
digits (hhmm or hhmmss) where hh = hours, mm =
*OPR: The SNADS operation function is used. originating system group name of distributions from
these systems. This may not be true of distributions
*ORG: The SNADS originator function is used.
originating from other SNADS implementations.
*ARV: The SNADS arrival function is used.
The name and group are translated to the character set
*SYS: The SNADS system function is used. and code page '697 500' using the job's coded character
set identifier (CCSID) before being used to select log
ENTTYP
entries.
Specifies the type of log entries shown. If *ALL or
*ALLDST are not specified, a maximum of five entry Element 1: Originating System Name
types can be specified.
*ALL: All log entries are shown regardless of the origi-
*ALLDST: All log entry types are shown except *SYS. nating system.
*ALL: All log entry types are shown. originating-system-name: Specify the name of the origi-
nating system.
*NRM: Normal (log entries without errors) log entries
are shown. Element 2: Originating System Group Name
*ERR: Error log entries are shown. *ALL: All log entries are shown regardless of the origi-
nating system group name.
*RTG: Routing table log entries or secondary node ID
log entries are shown. *BLANK: Only log entries with an originating address of
all blanks are shown.
*DSQ: Distribution queue log entries are shown.
*SYS: The QSNADS journal entries are shown.
originating-system-group-name: Specify the originating
system group name.
ORGUSRID
JOB
Specifies the originating user ID and address of logged
Specifies the name of the SNADS job that made the log
distributions. This parameter allows the user to display
entry. This parameter allows the user to display or print
or print only those logged entries made because of dis-
only those entries logged by the specified job. More
tributions originated by a user with the specified ID or
information on this parameter is in Appendix A,
address.
“Expanded Parameter Descriptions.”
The user ID and address are translated to the character
A job identifier is a special value or a qualified name
set and code page '697 500' using the job's coded char-
with up to three elements. For example:
acter set identifier (CCSID) before being used to select
log entries. \ALL
job-name
Element 1: Originating User ID user-name/job-name
*ALL: All log entries are shown regardless of the origi- job-number/user-name/job-name
nating user ID. *ALL: Entries are shown regardless of the job that
*BLANK: Only log entries with an originating user ID of logged them.
all blanks (as in the case of SNADS status distributions) job-name: Specify the name of the job being discon-
are shown. nected. If no job qualifier is given, all jobs currently in
originating-user-ID: Specify the originating user ID. the system are searched for the name of the job. If
duplicates of the specified name are found, a qualified
Element 2: Originating User Address
job name must be specified.
*ALL: All log entries are shown regardless of the origi-
user-name: Specify the name of the user who owns the
nating address.
job being disconnected. Specifying the user as a qual-
*BLANK: Only log entries with an originating address of ifier is necessary only if a duplicate job name exists for
all blanks (as in the case of SNADS status distributions) different users. If a duplicate job name exists for the
are shown. same user, the job must be qualified with the job
originating-user-address: Specify the originating number.
address. job-number: Specify the number of the job being discon-
nected. Specifying the job number as a qualifier is only
ORGSYSNAME
necessary if a duplicate job name exists for the same
Specifies the name of the originating system and group
user.
of logged distributions. This parameter allows the user
to display or print only those logged entries made RCVRNG
because of distributions that originated from the speci- Specifies the qualified names of the journal receivers
fied system or group. that contain the SNADS logs. This parameter displays
AS/400, System/38, and System/36 systems do not entries from SNADS logs that are kept in journal
specify a system group. Specify *BLANK to show the receivers that are no longer active.
Note: The maximum number of receivers that are used library-name: Specify the name of the library to be
in a range of receivers is 256. If more than 256 searched.
receivers are specified, an error message is sent
and no changes are applied.
ending-journal-receiver: Specify the qualified name of
the journal receiver used as the last (newest) receiver
*CURRENT: Only the currently attached receiver is with journal entries applied. If the end of the receiver
used in applying the journal entries. Application of chain is reached before finding a receiver with this
journal entries continues for all journal receivers in the name, the operation is not done and an escape
chain, beginning with the receiver specified by the first message is sent.
parameter value through the currently attached journal
receiver. OUTPUT
Specifies whether the output from the command is
Element 1: Starting Journal Receiver
shown at the requesting workstation or printed with the
The name of the journal receiver can be qualified by one job's spooled output. More information on this param-
of the following library values: eter is in Appendix A, “Expanded Parameter
Descriptions.”
*LIBL: All libraries in the job's library list are
searched until the first match is found. *: Output requested by an interactive job is shown on
the display. Output requested by a batch job is printed
*CURLIB: The current library for the job is
with the job's spooled output.
searched. If no library is specified as the current
library for the job, the QGPL library is used. *PRINT: The output is printed with the job's spooled
output.
library-name: Specify the name of the library to be
searched.
Example
starting-journal-receiver: Specify the name of the journal
receiver used as the first (oldest) receiver. Example 1: Printing a Distribution Log
Element 2: Ending Journal Receiver DSPDSTLOG OUTPUT(\PRINT)
*CURRENT: The currently attached receiver is the last
This command directs the distribution log information to the
(newest) receiver used in applying the journal entries.
job's output spooling queue to be printed. If OUTPUT(*) is
The name of the journal receiver can be qualified by one specified, and the command was entered from a work
of the following library values: station, the information about the distribution log is shown at
the work station.
*LIBL: All libraries in the job's library list are
searched until the first match is found. Example 2: Getting a SNADS Distribution Log
*CURLIB: The current library for the job is DSPDSTLOG ENTTYPE(\SYS)
searched. If no library is specified as the current
library for the job, the QGPL library is used. This command directs the SNADS distribution log entries to
be shown on the work station display for an interactive job,
or printed with the job's spooled output for a batch job.
(P) ──┬────────────────────────┬──────────────────────────────────────────────────────5%
55──DSPDSTSRV──┬─────────────────────────┬───
│ ┌─\SELECT─┐ │ │ ┌─\──────┐ │
└─OPTION(──┼─1───────┼──)─┘ └─OUTPUT(──┴─\PRINT─┴──)─┘
├─2───────┤
└─3───────┘
Note:
P All parameters preceding this point can be specified in positional form.
Optional Parameters
Example
OPTION DSPDSTSRV OUTPUT(\PRINT)
Specifies an option from the distribution services menu
display that bypasses the initial menu and goes directly This command prints the current SNADS configuration
to the indicated table. The distribution queues table, status.
┌─\LIBL/────────┐
(P) ──┬───────────────────────┬──────5
55──DSPDTAARA──DTAARA(──┬─┼───────────────┼──data-area-name─┬──)──┬────────────────────────┬───
│ ├─\CURLIB/──────┤ │ │ ┌─\──────┐ │ │ ┌─\CHAR─┐ │
│ └─library-name/─┘ │ └─OUTPUT(──┴─\PRINT─┴──)─┘ └─OUTFMT(──┴─\HEX──┴──)─┘
(1) ───────────────────────────┤
├─\GDA───
├─\LDA──────────────────────────────┤
(2) ───────────────────────────┘
└─\PDA───
5──┬────────────────────────┬──────────────────────────────────────────────────────────────────────────────────────────────────5%
│ ┌─\LCL─┐ │
(3) ─┴─\RMT─┴──)─┘
└─SYSTEM(───
Notes:
1 This value is valid only if this is a group job.
Purpose DTAARA
Specifies the name and library of the data area whose
The Display Data Area (DSPDTAARA) command displays attributes and value are to be displayed.
the attributes and value of the specified data area. The fol-
The name of the data area can be qualified by one of
lowing attributes are displayed: the type and length of the
the following library values:
data area, the library where the data area is located (there is
no library associated with a local data area, the group data *LIBL: All libraries in the job's library list are
area, or the program initialization parameter data area), and searched until the first match is found.
the text describing the data area.
*CURLIB: The current library for the job is
If the job is a group job, the data area specified may be the searched. If no library is specified as the current
group data area (*GDA). This data area is automatically library for the job, the QGPL library is used.
associated with the group and it cannot be read from jobs library-name: Specify the name of the library to be
outside the group. The length of this character data area is searched.
512 bytes. More information about group jobs is in the Work
Management book. data-area-name: Specify the name of the data area to
be displayed.
The local data area (*LDA) is a character data area 1024 *GDA: The group data area is displayed if this is a
bytes long. It is automatically associated with the job and group job.
cannot be accessed from another job.
*LDA: The local data area is displayed.
If the job is a prestart job, the data area specified may *PDA: The program initialization parameter data area is
contain program initialization parameter data (*PDA). This displayed if this is a prestart job.
data area is automatically associated with the prestart job
and is inaccessible from other jobs. The length of this char-
acter data area is 2000 bytes. More information about pre- Optional Parameters
start jobs is in the Work Management book.
OUTPUT
Restriction: To use this command, the user must have Specifies whether the output from the command is dis-
object operational authority for the data area and *EXECUTE played at the requesting work station or printed with the
authority for the library. No specific authority is required for job's spooled output. More information on this param-
the local data area or the group data area. eter is in Appendix A, “Expanded Parameter
Descriptions.”
Note: To see the parameter and value descriptions for this
command, refer to the online help text. For more *: Output requested by an interactive job is shown on
information about printing the help text, refer to the display. Output requested by a batch job is printed
“Printing CL Command Descriptions” in Chapter 1. with the job's spooled output.
*PRINT: The output is printed with the job's spooled
output.
Required Parameters
SYSTEM The value and attributes of data area HEXDATA are dis-
Specifies whether the information provided is the data played if the user has proper authority. Both character and
area on the local system (*LCL) or on the remote system hexadecimal representations are shown.
(*RMT).
Example 2: Displaying Output in Character Format
*LCL: The data displayed is for the local data area.
DSPDTAARA DTAARA(TIME) OUTPUT(\)
*RMT: The data displayed is from the remote data area
named on the RMTDTAARA paramter of a successfully The value and attributes of the data area TIME are displayed
issued CRTDTAARA command. To view this data, if the user has the proper authority. The library list is used to
specify the name of the data area created on the find the data area.
(P) ─┬───────────────────────────────────────┬──┬─────────────────────────┬──────5
55──DSPDTADCT──DTADCT(──data-dictionary-name──)────
│ ┌─\ALL─────────────────────┐ │ │ ┌─\FIRST─┐ │
└─DFN(──┼─definition-name──────────┼──)─┘ └─CRTDATE(──┴─date───┴──)─┘
└─generic\-definition-name─┘
5──┬────────────────────────────┬──┬────────────────────────┬──┬────────────────────────────┬───────────────────────────────────5
│ (1) ──┐
┌─\FILE─── │ │ ┌─\──────┐ │ │ ┌─\BASIC────┐ │
└─DFNTYPE(──┼─\RCDFMT─── (2) ┼──)─┘ └─OUTPUT(──┴─\PRINT─┴──)─┘ └─FILEINF(──┼─\DETAIL───┼──)─┘
(3)
└─\FLD──────┘ ├─\EXTENDED─┤
├─\ALL──────┤
└─\NONE─────┘
5──┬──────────────────────────────┬──┬─────────────────────────────┬───────────────────────────────────────────────────────────5%
│ ┌─\BASIC────┐ │ │ ┌─\BASIC────┐ │
(4) ─┼─\DETAIL───┼──)─┘
└─RCDFMTINF(──┼─\EXTENDED─┼──)─┘ └─FLDINF(───
├─\ALL──────┤ ├─\EXTENDED─┤
└─\NONE─────┘ ├─\ALL──────┤
└─\NONE─────┘
Notes:
P All parameters preceding this point can be specified in positional form.
eter is in Appendix A, “Expanded Parameter *ALL: The extended file definition information, any
Descriptions.” record ID codes, and a list of file definitions and files that
use this format definition are displayed or printed.
*: Output requested by an interactive job is shown on
the display. Output requested by a batch job is printed *NONE: No record format information is printed or dis-
with the job's spooled output. played.
*PRINT: The output is printed with the job's spooled FLDINF
output. Specifies the level of detail used in printing or displaying
the field definition information.
FILEINF
Specifies the level of detail used in displaying or printing *BASIC: The following basic field definition information
the file definition information. is displayed or printed: the definition name, the defi-
nition type, the dictionary where the definition is located,
*BASIC: The following basic information is displayed or
the definition's text, the data type, field length, buffer
printed: the definition name, the definition type, the dic-
length, and column headings. If record format informa-
tionary in which the definition is located, the date the
tion is also requested, the basic information also
definition was created, the user ID of the person who
includes the buffer position and field usage.
created it, the date it was last changed, the user ID of
the person who made the last change, the definition's *DETAIL: The basic field definition information plus the
text, the number of format definitions used by this file date the definition was created, the user ID of the
definition, and the type of file. person who created it, the date it was last changed, the
user ID of the person who made the last change, the
*DETAIL: The basic file definition information, plus any
keyboard shift, the alias name, and editing information is
key field information, is displayed or printed.
displayed or printed.
*EXTENDED: The detailed file definition information,
*EXTENDED: The detailed field definition information,
plus any long comment about the file definition, is dis-
plus any long comment about the field definition, is dis-
played or printed.
played or printed.
*ALL: The extended file definition information, plus a list
*ALL: All extended information, plus a list of definitions
of files that use this definition, is displayed or printed.
and files that use this definition, is displayed or printed.
*NONE: No file definition information is printed or dis-
*NONE: No field information is displayed or printed.
played.
RCDFMTINF
Specifies the level of detail used in printing or displaying
Example
the contents of the record format information. DSPDTADCT DTADCT(MINE) DFN(\ALL) DFNTYPE(\FILE)
OUTPUT(\PRINT) FILEINF(\BASIC) RCDFMTINF(\BASIC)
*BASIC: The following basic information is displayed or FLDINF(\EXTENDED)
printed: the definition name, the definition type, the dic-
tionary where the definition is located, the date the defi- This command prints all file definitions in the data dictionary
nition was created, the user ID of the person who MINE. Basic information for the file definitions is printed.
created it, the date it was last changed, the user ID of Basic information for the format definitions in each file defi-
the person who made the last change, the definition's nition, and the extended information for the field definitions in
text, the number of field definitions used by this format each RECORD format definition in the file definitions are
definition, and the record length. printed.
*EXTENDED: The basic file definition information, plus
any long comment about the format definition, is dis-
played or printed.
(P) ────────────────────────────────────────────────────────────────────5%
55──DSPEDTD──EDTD(──┬─5─┬──)──┬────────────────────────┬───
├─6─┤ │ ┌─\──────┐ │
├─7─┤ └─OUTPUT(──┴─\PRINT─┴──)─┘
├─8─┤
└─9─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose OUTPUT
Specifies whether the output from the command is
The Display Edit Description (DSPEDTD) command shows shown at the requesting workstation or printed with the
information about the specified user-defined edit description. job's spooled output. More information on this param-
Note: To see the parameter and value descriptions for this eter is in Appendix A, “Expanded Parameter
command, refer to the online help text. For more Descriptions.”
information about printing the help text, refer to *: Output requested by an interactive job is shown on
“Printing CL Command Descriptions” in Chapter 1. the display. Output requested by a batch job is printed
with the job's spooled output.
Required Parameters *PRINT: The output is printed with the job's spooled
output.
EDTD
Specifies the single-digit code (5, 6, 7, 8, or 9) that iden-
tifies the user-defined edit description to be displayed. Example
DSPEDTD EDTD(6)
Optional Parameters This command shows the user-defined edit description 6 on
either a printer or a display.
55──DSPEWCBCDE──BCDGRP(────bar-code-group-name────)──INZMBR(────source-member-name────)─────────────────────────────────────────5
(P) ─────────────────────────────────────────────────────────────────5%
5──┬──────────────────────────────────────────────────────┬───
│ ┌─\LIBL/────────┐ ┌─QEWCSRC──────────┐ │
└─INZFILE(──┼───────────────┼──┴─source-file-name─┴──)─┘
├─\CURLIB/──────┤
└─library-name/─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose INZFILE
Specifies the name of the source physical file that con-
The Display Extended Wireless Controller Bar Code Entry tains the source file member.
(DSPEWCBCDE) command displays the bar code parame-
The name of the source file can be qualified by one of
ters for the specified bar code group.
the following library values:
Note: To see the parameter and value descriptions for this
command, refer to the online help text. For more *LIBL: All libraries in the job's library list are
information about printing the help text, refer to searched until the first match is found.
“Printing CL Command Descriptions” in Chapter 1. *CURLIB: The current library for the job is
searched. If no library is specified as the current
library for the job, the QGPL library is used.
Required Parameters
library-name: Specify the name of the library to be
BCDGRP searched.
Specifies the name of the bar code group to be dis-
played. QEWCSRC: The source file name QEWCSRC is used.
(P) ───────────────────5%
55──DSPEWCM──INZMBR(────source-member-name────)──┬──────────────────────────────────────────────────────┬───
│ ┌─\LIBL/────────┐ ┌─QEWCSRC──────────┐ │
└─INZFILE(──┼───────────────┼──┴─source-file-name─┴──)─┘
├─\CURLIB/──────┤
└─library-name/─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose INZFILE
Specifies the name of the source physical file of the
The Display Extended Wireless Controller Member source file member. If the source physical file does not
(DSPEWCM) command displays the extended wireless con- exist, this command will fail.
troller parameters of the specified source file member. Spe-
The name of the source file can be qualified by one of
cific Portable Transaction Computer (PTC) and bar code
the following library values:
configuration parameters are displayed using the Display
Extended Wireless Controller PTC Entry (DSPEWCPTCE) *LIBL: All libraries in the job's library list are
and Display Extended Wireless Controller Bar Code Entry searched until the first match is found.
(DSPEWCBCDE) commands.
*CURLIB: The current library for the job is
Note: To see the parameter and value descriptions for this searched. If no library is specified as the current
command, refer to the online help text. For more library for the job, the QGPL library is used.
information about printing the help text, refer to
library-name: Specify the name of the library to be
“Printing CL Command Descriptions” in Chapter 1.
searched.
55──DSPEWCPTCE──PTCGRP(────ptc-group────)──INZMBR(────source-member-name────)───────────────────────────────────────────────────5
(P) ─────────────────────────────────────────────────────────────────5%
5──┬──────────────────────────────────────────────────────┬───
│ ┌─\LIBL/────────┐ ┌─QEWCSRC──────────┐ │
└─INZFILE(──┼───────────────┼──┴─source-file-name─┴──)─┘
├─\CURLIB/──────┤
└─library-name/─┘
Note:
P All parameters preceding this point can be specified in positional form.
INZMBR Example
Specifies the name of the source file member to which DSPEWCPTCE PTCGRP(PTCð1) INZMBR(EWCð1)
the PTC entry was added. The source file member con- INZFILE(\LIBL/QEWCSRC)
tains extended wireless controller configuration data.
This command displays PTC parameters for PTC group
PTC01 in source file member EWC01 in source file
Optional Parameter QEWCSRC in the library list.
INZFILE
Specifies the name of the source physical file that con-
tains the source file member.
(P) ───────────────────5%
55──DSPEWLM──INZMBR(────source-member-name────)──┬──────────────────────────────────────────────────────┬───
│ ┌─\LIBL/────────┐ ┌─QEWLSRC──────────┐ │
└─INZFILE(──┼───────────────┼──┴─source-file-name─┴──)─┘
├─\CURLIB/──────┤
└─library-name/─┘
Note:
P All parameters preceding this point can be specified in positional form.
Note: To see the parameter and value descriptions for this *CURLIB: The current library for the job is
command, refer to the online help text. For more searched. If no library is specified as the current
information about printing the help text, refer to library for the job, the QGPL library is used.
“Printing CL Command Descriptions” in Chapter 1. library-name: Specify the name of the library to be
searched.
Required Parameter QEWLSRC: The source file name QEWLSRC is used.
INZMBR source-file-name: Specify the name of an existing
Specifies the name of the source file member to be source physical file that contains the source member to
changed. This member contains the extended wireless display.
controller configuration data.
Example
Optional Parameter DSPEWLM INZMBR(EWLð1)
INZFILE This command displays extended wireless line parameters in
Specifies the name of the source physical file that con- source file member EWL01 in source file QEWLSRC in the
tains the source file member to display. If the source library list.
physical file does not exist, this command will fail.
(P) ───────────────────────────────────────────────────────────────────────────────────5%
55──DSPEXPSCD──┬────────────────────────┬───
│ ┌─\──────┐ │
└─OUTPUT(──┴─\PRINT─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
Note: To see the parameter and value descriptions for this The expiration schedule is displayed on the active work-
command, refer to the online help text. For more station.
information about printing the help text, refer to
“Printing CL Command Descriptions” in Chapter 1.
┌─\LIBL/────────┐
55──DSPFD──FILE(──┼───────────────┼──┬─\ALL───────────────┬──)──┬─────────────────────────────────┬─────────────────────────────5
├─\USRLIBL/─────┤ ├─generic\-file-name─┤ │ ┌─\ALL──────────────┐ │
├─\CURLIB/──────┤ └─file-name──────────┘ └─TYPE(──┼─\BASATR───────────┼──)─┘
├─\ALL/─────────┤ │ ┌──
────────────┐ │
├─\ALLUSR/──────┤ └──6┬─\ATR─────┬┴───
(1) ─┘
└─library-name/─┘ ├─\ACCPTH──┤
├─\MBRLIST─┤
├─\SELECT──┤
├─\SEQ─────┤
├─\RCDFMT──┤
├─\MBR─────┤
├─\SPOOL───┤
├─\JOIN────┤
├─\TRG─────┤
├─\CST─────┤
└─\NODGRP──┘
5──┬──────────────────────────────┬─── (P) ──┬───────────────────────────────────┬───────────────────────────────────────────────────5
│ ┌─\────────┐ │ │ ┌─\ALL─────────────┐ │
(2, 3) ─┼─\PRINT───┼──)─┘
└─OUTPUT(───── │ │ ┌──
───────────┐ │ │
└─\OUTFILE─┘ 6 (4) ─┴──)─┘
└─FILEATR(──┴───┬─\DSPF─┬─┴───
├─\PRTF─┤
├─\DKTF─┤
├─\TAPF─┤
├─\CMNF─┤
├─\BSCF─┤
├─\MXDF─┤
├─\PF───┤
├─\LF───┤
├─\SAVF─┤
├─\DDMF─┤
└─\ICFF─┘
5──┬────────────────────────────────────────────────────┬──┬───────────────────────────────────────────┬────────────────────────5
│ ┌─\LIBL/────────┐ │ │ ┌─\FIRST──────┐ ┌─\REPLACE─┐ │
└─OUTFILE(──┼───────────────┼──database-file-name──)─┘ └─OUTMBR(──┴─member-name─┴──┼──────────┼──)─┘
├─\CURLIB/──────┤ └─\ADD─────┘
└─library-name/─┘
5──┬────────────────────────┬──────────────────────────────────────────────────────────────────────────────────────────────────5%
│ ┌─\LCL─┐ │
(5) ─┼─\RMT─┼──)─┘
└─SYSTEM(───
└─\ALL─┘
Notes:
1 A maximum of 12 repetitions.
2 If OUTPUT(*OUTFILE) is specified, a file name must be specified for the OUTFILE parameter. If TYPE(*BASATR) is speci-
4 A maximum of 12 repetitions.
5 If SYSTEM(*RMT) is specified for displayed or listed output, the only valid file attributes (FILEATR) are *PF, *LF, or *ALL. If
SYSTEM(*RMT) or SYSTEM(*ALL) is specified for outfile processing, the FILEATR parameter must be either *PF or *LF.
library-name: Specify the name of the library to be Note: Only one type can be specified if a file name is
searched. specified for the OUTFILE parameter.
Single Values *TRG: For physical files only, the number of trigger pro-
*ALL: All the types of information that apply to the grams, each trigger program name and library, and the
specified file are provided. trigger events, trigger times, and trigger update condi-
tions for each file with a trigger are provided. The
Note: *ALL cannot be specified if a file name is speci- correct output file format is QWHFDTRG from system
fied on the OUTFILE parameter. file QAFDTRG.
*BASATR: The basic attribute information common to *CST: For physical files only, information about the con-
all files is provided. The correct output file format is straint relationships associated with the file is provided.
QWHFDBAS from system file QAFDBASI. The correct output file format is QWHFDCST from the
Note: TYPE(*BASATR) is valid only if system file QAFDCST.
OUTPUT(*OUTFILE) is specified and a file name *NODGRP: For distributed physical files only, data parti-
is specified for the OUTFILE parameter. tioning and relational data base information copied from
Multiple Values a node group (*NODGRP) at file creation time is pro-
vided. The correct output file format is QWHFDNGP
*ATR: The attribute information for the specified file is
from the system file QAFDNGP.
provided. For database files, the attributes include the
access path type and the maximum number of OUTPUT
members. The correct output file format is the format Specifies whether the output from the command is pro-
unique to the requested file attribute. vided at the requesting work station, printed, or placed in
*ACCPTH: For physical and logical files only, the a database output file. More information on this param-
access paths of the specified file are provided. For eter is in Appendix A, “Expanded Parameter
keyed access paths, the composite key description is Descriptions.”
also provided. The correct output file format is *: Output requested by an interactive job is shown on
QWHFDACP from system file QAFDACCP. the display. Output requested by a batch job is printed
with the job's spooled output.
*MBRLIST: For physical and logical files only, an alpha-
betical list that contains the names of all members in the *PRINT: The output is printed with the job's spooled
specified file and a brief description of each member is output.
provided. The correct output file format is QWHFDML Note: If OUTPUT(*OUTFILE) is specified, a type other
from system file QAFDMBRL. than *ALL must be specified for the TYPE
*SELECT: For logical files only, the select/omit attribute parameter (only one type may be specified). If
is provided. The correct output file format is TYPE(*ATR) is specified while
QWHFDDSO from system file QAFDSELO. OUTPUT(*OUTFILE) is specified,
FILEATR(*ALL) or FILEATR(*MXDF) cannot be
*SEQ: For physical and logical files only, the collating
specified.
sequence is provided. The correct output file format is
QWHFDSEQ from system file QAFDCSEQ. *OUTFILE: The output is directed to the database file
specified on the OUTFILE parameter.
*RCDFMT: The record format names and record format
level information for the file, including the record format FILEATR
name(s) and data association information for referenced Specifies the type of file whose attributes are shown.
files are provided. The correct output file format is See Table 3 at the end of this command description for
QWHFDFMT from system file QAFDRFMT. the values that can be specified on the FILEATR param-
*MBR: For physical and logical files only, information eter in combination with the TYPE, OUTFILE, and
about the file members (names, creation dates, sizes, FORMAT parameters.
types, and other attributes) in the specified file is pro- Note: If SYSTEM(*RMT) or SYSTEM(*ALL) is speci-
vided. Members are in the order in which they were fied, the only valid file attributes are *PF, *LF,
created. The correct output file format is QWHFDMBR and *ALL for displayed output, printed output, or
from system file QAFDMBR. output file processing.
*SPOOL: For device files only, the spooling attributes of *ALL: The attributes of all files are shown.
the specified diskette or printer file are provided. The
Note: *ALL cannot be specified if a value is specified
spooling attributes include the number of output copies
for the OUTFILE parameter, and TYPE(*ATR) is
produced, the output priority, and the maximum number
specified.
of records in the file. The correct output file format is
QWHFDSPL from system file QAFDSPOL. *DSPF: The attributes of display files are provided.
This includes both *DSPF and *DSPF38. If a value is
*JOIN: For join logical files only, the join from-file, the
specified for the OUTFILE parameter and TYPE(*ATR)
join to-file, and the fields that are involved in the join are
is specified, display files or mixed files with display
provided. The correct output file format is QWHFDJN
from system file QAFDJOIN.
device entries are shown. The correct output file format If the file entered as the OUTFILE does not exist, the
is QWHFDDSP from system file QAFDDSP. system creates it in the specified library, or in the
*PRTF: The attributes of printer files are provided. This *CURLIB library when *LIBL is specified as the library
includes both *PRTF and *PRTF38. The correct output name. The text for the created file is 'Outfile for DSPFD'
file format is QWHFDPRT from system file QAFDPRT. and the public authority is *EXCLUDE. The file is cor-
rectly formatted.
*DKTF: The attributes of diskette files are provided.
This includes both *DKTF and *DKTF38. The correct If the file specified on the OUTFILE parameter exists
output file format is QWHFDDKT from system file and has the correct format, the system uses the file.
QAFDDKT. Note: The outfile format must correspond to that of the
*TAPF: The attributes of tape files are provided. This TYPE and FILEATR parameter descriptions.
includes both *TAPF and *TAPF38. The correct output See Table 3 at the end of this command
file format is QWHFDTAP from system file QAFDTAP. description for the values that can be specified
on the OUTFILE parameter in combination with
*CMNF: The attributes of communications files are pro- the TYPE, FILEATR, and FORMAT parameters.
vided. This includes both *CMNF and *CMNF38. If a
value is specified for the OUTFILE parameter and The name of the database file can be qualified by one of
TYPE(*ATR) is specified, only communication files or the following library values:
mixed files with communications device entries are *LIBL: All libraries in the job's library list are
shown. The correct output file format is QWHFDCMN searched until the first match is found.
from system file QAFDCMN.
*CURLIB: The current library for the job is
*BSCF: The attributes of BSC communications files are searched. If no library is specified as the current
provided. This includes both *BSCF and *BSCF38. If a library for the job, the QGPL library is used.
value is specified for the OUTFILE parameter and
TYPE(*ATR) is specified, only BSC communication files
library-name: Specify the name of the library to be
searched.
or mixed files with BSC communications device entries
are shown. The correct output file format is database-file-name: Specify the name of the database
QWHFDBSC from system file QAFDBSC. file that receives the output of the command. If no file
*MXDF: The attributes of mixed files are provided. by that name is found, a file by that name is created and
stored either in the specified library, or, if not qualified, in
Note: *MXDF cannot be specified if a value is specified the current library. The file can be used again by other
for the OUTFILE parameter and TYPE(*ATR) is DSPFD commands that request the same types of infor-
specified. mation. The IBM-supplied model database files cannot
*PF: The attributes of physical files are provided. This be specified.
includes both *PF and *PF38. The correct output file
OUTMBR
format is QWHFDPHY from system file QAFDPHY.
Specifies the name of the database file member to which
*LF: The attributes of logical files are provided. This the output is directed.
includes both *LF and *LF38. The correct output file
Element 1: Member to Receive Output
format is QWHFDLGL from system file QAFDLGL.
*FIRST: The first member in the file receives the output.
*SAVF: The attributes of save files are provided. This
If OUTMBR(*FIRST) is specified and the member does
includes both *SAVF and *SAVF38. The correct output
not exist, the system creates a member with the name of
file format is QWHFDSAV from system file QAFDSAV.
the file specified on the OUTFILE parameter. If the
*DDMF: The attributes of the Distributed Data Manage- member exists, the user has the option to add records to
ment (DDM) files are provided. This includes both the end of the existing member or to clear the existing
*DDMF and *DDMF38. The correct output file format is member before adding the new records.
QWHFDDDM from system file QAFDDDM.
member-name: Specify the file member that receives
*ICFF: The attributes of ICF files are provided. The the output. If OUTMBR(member-name) is specified and
correct output file format is QWHFDICF from system file the member does not exist, the system creates it.
QAFDICF.
Element 2: Operation to Perform on Member
OUTFILE *REPLACE: The system clears the existing member
Specifies the qualified name of the database output file and adds the new records.
to which the output of the display is directed.
*ADD: The system adds the new records to the end of
When creating the database output file, the current date, the existing records.
time, and system name must be included. The system
name is the name of the source system, not the target SYSTEM
system. Specifies whether the information provided is about files
on the local system (*LCL), on the remote system or
Additional Considerations If the attributes of more than one file are shown or printed,
the attributes of the next file are shown only after all of the
When the DSPFD command is entered, the specified requested attributes for the first file are shown. For printed
libraries are searched for the file or files specified by the output, a separate page is used for each type of information
FILE parameter; then a group of records that give file-level that is printed, as indicated by the TYPE parameter.
information about each file is created. The records are
placed in the printer device file named QPDSPFD. If For displayed or printed output, if no detailed information
OUTPUT(*PRINT) is specified on the command, the records exists for the specified file type, an appropriate indication is
are listed on the printer in the following order: given under the section heading for that type of display. For
example, if a logical file is shown and TYPE(*MBR
1. On the first line, the leftmost fields show system identi- *MBRLIST) was specified, but no members have yet been
fier numbers. The right side shows the date and time defined for the file, the message (no members in file) is
the job was run and the page number. shown or printed under the section headings for the member
2. The file, library, type of information, file attributes, and attributes display and for the member list display.
processor are shown (page 1 only).
For output to a display, the first four lines of each display
3. The specific file, library, and type of file (to which the fol- contain information about the spooled file and fields used for
lowing information applies) are shown. display spooled file functions.
4. Header information that identifies the type of information
being presented is shown, followed by the requested Numeric values in select/omit field descriptions are shown
attribute information. without decimal points. See the description of the fields (by
using the Display File Field Description (DSPFFD) command)
to determine the decimal positions.
┌─\LIBL/────────┐
55──DSPFFD──FILE(──┼───────────────┼──┬─\ALL───────────────┬──)──┬────────────────────────────┬───(P) ──────────────────────────────5
├─\USRLIBL/─────┤ ├─generic\-file-name─┤ │ ┌─\────────┐ │
├─\CURLIB/──────┤ └─file-name──────────┘ (1) ─┼─\PRINT───┼──)─┘
└─OUTPUT(───
├─\ALL/─────────┤ └─\OUTFILE─┘
├─\ALLUSR/──────┤
└─library-name/─┘
5──┬──────────────────────────────────────────────────────┬──┬───────────────────────────────────────────┬──────────────────────5
│ ┌─\LIBL/────────┐ │ │ ┌─\FIRST──────┐ ┌─\REPLACE─┐ │
(2) ─┼───────────────┼──database-file-name──)─┘ └─OUTMBR(──┴─member-name─┴──┼──────────┼──)─┘
└─OUTFILE(───
├─\CURLIB/──────┤ └─\ADD─────┘
└─library-name/─┘
5──┬──────────────────────┬────────────────────────────────────────────────────────────────────────────────────────────────────5%
│ ┌─\LCL─┐ │
└─SYSTEM(──┼─\RMT─┼──)─┘
└─\ALL─┘
Notes:
1 If OUTPUT(*OUTFILE) is specified, a file name must be specified for OUTFILE.
example), or that all files in all libraries (*ALL/*ALL), file-name: Specify the name of the file whose field-level
have their field-level descriptions shown. information is shown.
Note: The user must have authority to both the files
and the libraries before this information is shown. Optional Parameters
The name of the file field description can be qualified by OUTPUT
one of the following library values: Specifies whether the output from the command is
*LIBL: All libraries in the job's library list are shown at the requesting work station, printed with the
searched until the first match is found. job's spooled output, or placed in a database outfile.
More information on this parameter is in Appendix A,
*CURLIB: The current library for the job is “Expanded Parameter Descriptions.”
searched. If no library is specified as the current
library for the job, the QGPL library is used. *: Output requested by an interactive job is shown on
the display. Output requested by a batch job is printed
*USRLIBL: Only the libraries in the user portion of with the job's spooled output.
the job's library list are searched.
*PRINT: The output is printed with the job's spooled
*ALL: All libraries in the system, including QSYS, output.
are searched.
*OUTFILE: The output is directed to the database file
*ALLUSR: All user libraries are searched. All specified on the OUTFILE parameter.
libraries with names that do not begin with the letter
Q are searched except for the following: OUTFILE
#CGULIB #DFULIB #RPGLIB #SEULIB Specifies the qualified name of the database file where
#COBLIB #DSULIB #SDALIB the displayed information is stored.
Although the following Qxxx libraries are provided When creating the database output file, the current date,
by IBM, they typically contain user data that time, and system name must be included. The system
changes frequently. Therefore, these libraries are name is the name of the source system, not the target
considered user libraries and are also searched: system. If the specified output file does not exist, then
the system creates a database file and member. If the
| QDSNX QPFRDATA QUSRBRM QUSRSYS
file is created, the text is OUTFILE for DSPFFD and the
| QGPL QRCL QUSRIJS QUSRVxRxMx
public authority is *EXCLUDE.
| QGPL38 QS36F QUSRINFSKR
| QMQMDATA QUSER38 QUSRNOTES Note: The outfile format must be the same as
| QMQMPROC QUSRADSM QUSRRDARS QWHDRFFD of system file QADSPFFD. For
Note: A different library name, of the form more information on the outfile format, refer to
QUSRVxRxMx, can be created by the user DB2 for AS/400 Database Programming book.
for each release that IBM supports. VxRxMx The name of the database file can be qualified by one of
is the version, release, and modification level the following library values:
of the library.
*LIBL: All libraries in the job's library list are
library-name: Specify the name of the library to be searched until the first match is found.
searched.
*CURLIB: The current library for the job is
*ALL: All files in the library or libraries specified have searched. If no library is specified as the current
their field-level information shown. library for the job, the QGPL library is used.
generic*-file-name: Specify the generic name of the file library-name: Specify the name of the library to be
or files that have field-level information shown. A searched.
generic name is a character string of one or more char-
acters followed by an asterisk (*); for example, ABC*. database-file-name: Specify the name of the database
The asterisk substitutes for any valid characters. A file where the field level information is written. If no file
generic name specifies all objects with names that begin is found by that name, a file by that name is created and
with the generic prefix for which the user has authority. stored in the specified library, or in *CURLIB if the file
If an asterisk is not included with the generic (prefix) name is not qualified. This file can be used again when
name, the system assumes it to be the complete object other DSPFFD commands are entered. The
name. If the complete object name is specified, and IBM-supplied database file QADSPFFD cannot be speci-
multiple libraries are searched, multiple objects can be fied.
displayed only if *ALL or *ALLUSR library values can be OUTMBR
specified for the name. For more information on the use Specifies the name of the database file member to which
of generic names, refer to “Generic Object Names” in the output is directed.
Chapter 2.
Element 1: Member to Receive Output
*FIRST: The first member in the file receives the output. displays show only information about the remote file that
If OUTMBR(*FIRST) is specified and the member does was named on the RMTFILE parameter of the
not exist, the system creates a member with the name of CRTDDMF command.
the file specified on the OUTFILE parameter. If the
member exists, the user has the option to add records to
the end of the existing member or to clear the existing
Examples
member and then add the new records. Example 1: Displaying Information About a File on the
member-name: Specify the file member that receives Local System
the output. If OUTMBR(member-name) is specified and DSPFFD FILE(LIB1/FILE2)
the member does not exist, the system creates it.
Element 2: Operation to Perform on Member This command shows the field-level information about file
FILE2 in LIB1 on the local system. The information is shown
*REPLACE: The system clears the existing member at the work station where the command was entered.
and adds the new records.
*ADD: The system adds the new records to the end of Example 2: Displaying Information About Files on the
the existing records. Local and Remote Systems
DSPFFD FILE(\ALL/\ALL) SYSTEM(\ALL)
SYSTEM
Specifies whether the information returned by the This command shows the field-level information of all files in
DSPFFD command is about files on the local system all libraries authorized to the user on the local system and on
(*LCL), about files on the remote system or systems all remote systems. For distributed data management files,
(*RMT), or about files on both local and remote systems the display shows only information about the remote file that
(*ALL). For performance considerations, unless explicitly is named on the RMTFILE parameter of the CRTDDMF
looking for information about files on systems other than command. The information is shown at the work station
the local system, the default value of *LCL should not be where the command was entered.
changed.
Example 3: Directing Output to a Database File
*LCL: The information provided is about local files only.
DSPFFD FILE(QGPL/FLDREF) OUTPUT(\OUTFILE)
*RMT: The information provided is about remote files OUTFILE(QGPL/FLDREFX)
that have been named on the RMTFILE parameter of
successfully run CRTDDMF commands. To look at this This command puts the field-level information for the file
information, specify the name of the distributed data FLDREF in the QGPL library on the local system into a data-
management file, not the name of the remote file. Only base file named FLDREFX in the general purpose library,
the information returned by the remote system is shown. QGPL. The FLDREFX file in the QGPL library can then be
*ALL: The information provided is about files on both processed by a program.
the local and the remote systems. For DDM files, the
55──DSPFLR──┬──────────────────────────┬──┬────────────────────┬──┬────────────────────────────┬───(P) ─────────────────────────────5
│ ┌─\ALL────────┐ │ │ ┌─\FLR─┐ │ │ ┌─\────────┐ │
└─FLR(──┴─folder-name─┴──)─┘ └─TYPE(──┴─\DOC─┴──)─┘ └─OUTPUT(───(1) ─┼─\PRINT───┼──)─┘
└─\OUTFILE─┘
5──┬─────────────────────────┬──┬────────────────────────────────────────────────────┬──────────────────────────────────────────5
│ ┌─\CURRENT─┐ │ │ ┌─\LIBL/────────┐ │
└─LEVEL(──┴─\ALL─────┴──)─┘ └─OUTFILE(──┼───────────────┼──database-file-name──)─┘
├─\CURLIB/──────┤
└─library-name/─┘
5──┬───────────────────────────────────────────┬──┬───────────────────────┬──┬─────────────────────────────┬───────────────────5%
│ ┌─\FIRST──────┐ ┌─\REPLACE─┐ │ └─OUTFILFMT──┬─\TYPE1─┬─┘ │ ┌─\ALL───────────┐ │
└─OUTMBR(──┴─member-name─┴──┼──────────┼──)─┘ └─\TYPE2─┘ └─ASP(──┴─ASP-identifier─┴──)─┘
└─\ADD─────┘
Notes:
1 Batch cannot be used if OUTPUT(*) is specified.
(P) ─┬────────────────────────┬────────────────────────────────────────────────────────5%
55──DSPFNTTBL──FNTTBL(──┬─\PHFCS────┬──)────
├─\PHCP─────┤ │ ┌─\──────┐ │
├─\HPFCS────┤ └─OUTPUT(──┴─\PRINT─┴──)─┘
├─\HPCP─────┤
├─\SYSPHFCS─┤
├─\SYSPHCP──┤
├─\SYSHPFCS─┤
└─\SYSHPCP──┘
Note:
P All parameters preceding this point can be specified in positional form.
1. The PSF/400 feature is required to use this command. *SYSHPFCS: The system host resident to printer resi-
dent font character set table is to be displayed. This
Note: To see the parameter and value descriptions for this table is documented in Appendix D of the Printer Device
command, refer to the online help text. For more Programming manual.
information about printing the help text, refer to
“Printing CL Command Descriptions” in Chapter 1. *SYSHPCP: The system host resident to printer resi-
dent code page mapping table is to be displayed. This
table is documented in Appendix D of the Printer Device
Required Parameter Programming manual.
FNTTBL
Specifies the name of the font table to be displayed. Optional Parameters
*PHFCS: The printer resident to host resident font char- OUTPUT
acter set table is to be displayed. Specifies whether the output from the command is dis-
*PHCP: The printer resident to host resident code page played at the requesting work station or printed with the
mapping table is to be displayed. job's spooled output.
*HPFCS: The host resident to printer resident font char- The possible values are:
acter set table is to be displayed. *: The output is displayed (if requested by an interactive
*HPCP: The host resident to printer resident code page job) or printed with job's spooled output (if requested by
mapping table is to be displayed. a batch job).
*SYSPHFCS: The system printer resident to host resi- *PRINT: The output is printed with the job's spooled
dent font character set table is to be displayed. This output.
┌─\LIBL/────────┐
(P) ─┬────────────────────────┬───────────────────────────────5%
55──DSPFNTRSCA──FNTRSC(──┼───────────────┼──font-resource-name──)────
├─\CURLIB/──────┤ │ ┌─\──────┐ │
└─library-name/─┘ └─OUTPUT(──┴─\PRINT─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
55──DSPHDWRSC──TYPE(──┬─\AHW───┬──)──┬──────────────────────────┬──┬───────────────────────────────────────────┬────────────────5
├─\CMN───┤ │ ┌─\────────┐ │ │ ┌─\LIBL/────────┐ │
├─\CSA───┤ └─OUTPUT(──┼─\PRINT───┼──)─┘ └─OUTFILE(──┼───────────────┼──file-name──)─┘
(1) ┤
├─\LAN─── └─\OUTFILE─┘ ├─\CURLIB/──────┤
├─\LWS───┤ └─library-name/─┘
├─\PRC───┤
└─\STG───┘
(P, K) ─────────────5%
5──┬───────────────────────────────────────────┬──┬───────────────────────────┬──┬──────────────────────────┬─────
│ ┌─\FIRST──────┐ ┌─\REPLACE─┐ │ │ ┌─\TYPE1─┐ │ │ ┌─\ALL─┐ │
└─OUTMBR(──┴─member-name─┴──┼──────────┼──)─┘ └─OUTFILFMT(──┴─\TYPE2─┴──)─┘ └─LINETYPE(──┼─\DDI─┼──)───(2) ┘
└─\ADD─────┘ └─\TRN─┘
Notes:
1 When this value is specified, a value must also be specified for the LINETYPE parameter.
*CMN: Displays, prints, or directs to an output file the *: Output requested by an interactive job is shown on
contents of each SRM communications resource record. the display. Output requested by a batch job is printed
This information consists of resource name, resource with the job's spooled output.
type, serial number, location, status, address, configura- *PRINT: The requested data is printed with the job's
tion description, and resource description. spooled output.
*CSA: Displays, prints, or directs to an output file the *OUTFILE: The requested data is directed to an output
coupled adapter resource information. This information database file.
consists of resource name, model, status, location,
resource description, and the system the adapter is con- OUTFILE
nected to. Specifies the qualified name of the database file to
which the output of the command is directed. If the file
*LAN: Displays, prints, or directs token-ring or distrib- does not exist, this command creates a database file in
uted data interface adapter resource information to an the specified library.
Resource Type Physical File Model Format name Resource 00 = Communications processor
Description 01 = Communications adapter
02 = Communications port
\AHW QARZALLF QRZALL
03 = Work station controller
\CMN QARZDCMN QRZDCMN
04 = Printer device
\CSA QARZDCSA QRZDCSA
05 = Work station device
\LAN QARZDTRA QRZDTRA 06 = ASCII work station controller
\LWS QARZDLWS QRZDLWS 07 = Work station printer
\PRC QARZDPRC QRZDPRC 08 = Main card enclosure
\STG QARZDSTG QRZDSTG 09 = Bus extender
Field level information for any of the above files can be 10 = System processor
obtained using the Display File Field Description 11 = Service processor
12 = Main storage card
(DSPFFD) command and specifying the physical file in
13 = Storage controller
library QSYS. 14 = Tape controller
The information for the following fields are not shown 15 = Disk storage controller
with the DSPFFD command: 16 = Diskette controller
17 = Tape unit
18 = Disk unit
Table 4. Physical File Field Values 19 = Diskette unit
Field Field values and description 20 = Tape input/output processor
21 = Work station processor
Record 0 = *CMN communications 22 = System control panel
Format resource 23 = Next level main storage card
1 = *LWS local work station 24 = Combined function IO processor
2 = *PRC processor type 25 = MFIO processor
3 = *STG storage resource 26 = Virtual controller
4 = *LAN adapter information
5 = *CSA coupled adapter resource Resource 0 = Not detected
Status 1 = Inoperative
Resource For *CMN type records: 2 = Not ready
Level 1 = Input/output processor 3 = Operational
2 = Input/output adapter
3 = Communications port Resource If resource description is
For *LWS or *STG type records: Extended 00 - Communications processor:
1 = Input/output processor Description 01 = Comm processor
2 = Controller (only applies 02 = MFIO processor
3 = Device to the 03 = Combined function IO processor
For *PRC type records: QARZDCMN and 04 = File server IO processor
0 = Processor unit QARZALLF If resource description is
1 = Processor/main storage physical file 01 - Communications adapter:
2 = Next level main storage models for 01 = Comm adapter
*CMN) 02 = LAN adapter
03 = ISDN adapter
04 = Fax adapter
If resource description is
02 - Communications port:
01 = Comm port
02 = ISDN port
03 = Token-ring port
04 = Autocall port
05 = Ethernet port
06 = V.24 port
07 = X.21 port
08 = V.35 port
09 = V.24 enhanced port
10 = V.36 port
11 = FDDI port
12 = SDDI port
13 = Fax port
14 = Wireless connection
15 = LAN port
This parameter is valid only if OUTPUT(*OUTFILE) is *TYPE1: The format of the output file is the same as
specified. Only one type of resource information: that of the physical file models, QARZDCMN,
*CMN, *LWS, *PRC, *STG, or *LAN can be directed to QARZDLWS, QARZDPRC, and QARZDSTG.
one output file.
*TYPE2: The format of the output file is the same as
The possible library values are: that of the physical file model, QARZALLF, and its asso-
ciated record format model, QRZALL. This value is the
*LIBL: The library list is used to locate the output
functional equivalent of the physical file, QARZHWOF,
file.
which was used by the Display Local Hardware
*CURLIB: The current library for the job is used to (DSPLCLHDW) command in releases prior to V3R6M0.
locate the output file. If no library is specified as the
LINETYPE
current library for the job, the QGPL library is used.
Specifies the local area network (LAN) type for which
library-name: Specify the name of the library where information is displayed, printed, or directed to an output
the output file is located. file.
file-name: Specify the name of the file where the This parameter is required if TYPE(*LAN) is specified.
requested information is to be located.
*ALL: Both distributed data interface and token-ring
OUTMBR network adapter resource information is displayed,
Specifies the member name to receive the requested printed, or directed to an output file.
SRM data. This parameter is valid only if OUTPUT *DDI: All distributed data interface adapter resource
(*OUTFILE) is specified. information is displayed, printed, or directed to an output
Element 1: Member to Receive Output file.
*FIRST: The first member name receives the requested *TRN: All token-ring network adapter resource informa-
SRM data. tion is displayed, printed, or directed to an output file.
55──DSPHFS──┬────────────────────────┬─────────────────────────────────────────────────────────────────────────────────────────5%
│ ┌─\──────┐ │
└─OUTPUT(──┴─\PRINT─┴──)─┘
(P) ────────────────────────────5%
55──DSPHLPDOC──DOC(──document-name──)──FLR(──folder-name──)──┬─────────────────────────────────┬───
│ ┌─\FIRST──────────┐ │
└─HLPLBL(──┴─help-label-name─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
FLR
Specifies the name of the folder that contains the docu-
ment.
┌─\LIBL/────────┐
(1) ─IGCDCT(──┼───────────────┼──dictionary-name──)────
55──DSPIGCDCT─── (P) ─┬────────────────────────────────┬──────────────────────────5
├─\CURLIB/──────┤ │ ┌─\ALL────────────┐ │
└─library-name/─┘ └─ENTRY(──┼─generic\-string─┼──)─┘
└─specific-string─┘
5──┬────────────────────────┬──────────────────────────────────────────────────────────────────────────────────────────────────5%
│ ┌─\──────┐ │
└─OUTPUT(──┴─\PRINT─┴──)─┘
Notes:
1 DBCS systems only
Examples
Optional Parameters
Example 1: Displaying Entries
ENTRY
Specifies the alphanumeric entries to be shown or DSPIGCDCT IGCDCT(DBCSLIB/QUSRIGCDCT) OUTPUT(\)
printed with their related words.
This command displays at a work station all entries in the DSPIGCDCT IGCDCT(DBCSLIB/QUSRIGCDCT) ENTRY('?')
DBCS conversion dictionary named QUSRIGCDCT, that is OUTPUT(\PRINT)
stored in the library DBCSLIB.
This command prints the entry ? and its related words from
Example 2: Printing Entries the DBCS conversion dictionary named QUSRIGCDCT,
which is stored in the library DBCSLIB.
(P)─┬────────────────────────┬──────────────────────────────────────────────────────────────────────────────────────5%
55──DSPIPLA───
│ ┌─\──────┐ │
└─OUTPUT(──┴─\PRINT─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
Example
Optional Parameters
DSPIPLA OUTPUT(\)
OUTPUT
Specifies whether the output from the command is dis- This command displays the IPL attribute information.
played at the requesting work station or printed with the
(P) ───────────────────────────────────────────────────────────────────────────5%
55──DSPIPXCCT──CCTNAME(────IPX-circuit-name────)────
Note:
P All parameters preceding this point can be specified in positional form.
Purpose CCTNAME
Specifies the name of the IPX circuit that you want to
The Display IPX Circuit (DSPIPXCCT) command displays an display. This circuit must have been previously config-
existing circuit from the Internetwork Packet Exchange (IPX) ured using the Add IPX Circuit (ADDIPXCCT) command
configuration. or by selecting Option 1 from the Work with IPX Circuits
Note: To see the parameter and value descriptions for this display. The IPX circuit name cannot exceed 18 charac-
command, refer to the online help text. For more ters in length.
information about printing the help text, refer to
“Printing CL Command Descriptions” in Chapter 1.
Example
DSPIPXCCT CCTNAME(CIRCUIT2)
Required Parameters
This command causes the IPX support to display information
about the circuit named CIRCUIT2.
(P) ─────────────────────────────────────────────────5%
55──DSPIPXD──IPXD(────IPX-description-name────)──┬────────────────────────┬───
│ ┌─\──────┐ │
└─OUTPUT(──┴─\PRINT─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose OUTPUT
Specifies whether the output from the command is
The Display IPX Description (DSPIPXD) command displays shown at the requesting workstation or printed with the
an IPX description. job's spooled output.
Note: To see the parameter and value descriptions for this *: Output requested by an interactive job is shown on
command, refer to the online help text. For more the display. Output requested by a batch job is printed
information about printing the help text, refer to with the job's spooled output.
“Printing CL Command Descriptions” in Chapter 1.
*PRINT: The output is printed with the job's spooled
output.
Required Parameter
IPXD Example
Specifies the name of the IPX description to be dis- DSPIPXD IPXD(IPXDESC)
played.
This command displays information about the IPX description
named IPXDESC. The information is shown at the work-
Optional Parameter station from which the command was entered. If the
command was submitted from a batch job, the output from
the command is printed with the job's spooled output.
┌─\─────────────────────────────────────────┐
(P) ───────────────────────────────5
55──DSPJOB──JOB(──┴─┬─────────────────────────────┬──job-name─┴──)──┬────────────────────────┬───
└─┬─────────────┬──user-name/─┘ │ ┌─\──────┐ │
└─job-number/─┘ └─OUTPUT(──┴─\PRINT─┴──)─┘
5──┬─────────────────────────┬──┬────────────────────────────┬─────────────────────────────────────────────────────────────────5%
│ ┌─\SELECT─┐ │ │ ┌─\SELECT─┐ │
└─OPTION(──┼─\STSA───┼──)─┘ └─DUPJOBOPT(──┴─\MSG────┴──)─┘
├─\DFNA───┤
├─\RUNA───┤
├─\SPLF───┤
├─\JOBLOG─┤
├─\PGMSTK─┤
├─\JOBLCK─┤
├─\LIBL───┤
├─\OPNF───┤
├─\FILOVR─┤
├─\CMTCTL─┤
├─\CMNSTS─┤
├─\ACTGRP─┤
├─\MUTEX──┤
| ├─\THREAD─┤
└─\ALL────┘
Note:
P All parameters preceding this point can be specified in positional form.
More information on this parameter is in Appendix A, *LIBL: The library list associated with the job is dis-
“Expanded Parameter Descriptions.” played.
*: The job whose information is displayed is the job *OPNF: The open files associated with the job are dis-
from which this display command is entered. played.
job-name: Specify the name of the job whose informa- *FILOVR: The file overrides associated with the job are
tion is to be displayed. displayed.
user-name: Specify the name of the user of the job *CMTCTL: The commit control status of the job is dis-
whose information is to be displayed. played.
job-number: Specify the number of the job whose infor- *CMNSTS: The communications status of the job is dis-
mation is to be displayed. played.
*PGMSTK: The call stack associated with the job is dis- DSPJOB OPTION(\ALL)
played.
This command displays all of the information for the current
*JOBLCK: The job locks associated with the job are job.
displayed.
┌─\LIBL/────────┐
(P) ──────────────────────────────────5%
55──DSPJOBD──JOBD(──┼───────────────┼──job-description-name──)──┬────────────────────────┬───
├─\CURLIB/──────┤ │ ┌─\──────┐ │
└─library-name/─┘ └─OUTPUT(──┴─\PRINT─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
(P) ──────────────────────5
55──DSPJOBLOG──┬────────────────────────────────────────────────────────┬──┬──────────────────────────┬───
│ ┌─\─────────────────────────────────────────┐ │ │ ┌─\────────┐ │
└─JOB(──┴─┬─────────────────────────────┬──job-name─┴──)─┘ └─OUTPUT(──┼─\PRINT───┼──)─┘
└─┬─────────────┬──user-name/─┘ ├─\OUTFILE─┤
└─job-number/─┘ └─\APIDFIN─┘
5──┬────────────────────────────────────────────────────┬──┬───────────────────────────────────────────┬───────────────────────5%
│ ┌─\LIBL/────────┐ │ │ ┌─\FIRST──────┐ ┌─\REPLACE─┐ │
└─OUTFILE(──┼───────────────┼──database-file-name──)─┘ └─OUTMBR(──┴─member-name─┴──┼──────────┼──)─┘
├─\CURLIB/──────┤ └─\ADD─────┘
└─library-name/─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose job-name: Specify the name of the job whose job log is
shown.
The Display Job Log (DSPJOBLOG) command shows com-
user-name: Specify the name of the user of the job
mands and related messages for a job whose job log is not
whose job log is shown.
written. You can also show commands for a job on a job
queue that has not started processing. job-number: Specify the number of the job whose job
log is shown.
This command is used to monitor the progress of a job.
OUTPUT
Note: This function can also be accessed through the Specifies whether the output from the command is
Display Job (DSPJOB) and Work with a Job shown at the requesting work station, printed with the
(WRKJOB) commands. job's spooled output or directed to a database file. More
information on this parameter is in Appendix A,
Restrictions:
“Expanded Parameter Descriptions.”
1. To display a job log, the user must have special job
*: Output requested by an interactive job is shown on
control authority (*JOBCTL), or the job must have the
the display. Output requested by a batch job is printed
same user name as the person running this command.
with the job's spooled output.
2. To display a job that is running for the security officer or
*PRINT: The output is printed with the job's spooled
a member of the security officer group, the user also
output.
must have *ALLOBJ special authority.
*OUTFILE: The output is directed to the database file
Note: To see the parameter and value descriptions for this
specified in the OUTFILE parameter. This option can
command, refer to the online help text. For more
only be used if the JOB parameter specifies the special
information about printing the help text, refer to
value asterisk (*). Using this option only allows a
“Printing CL Command Descriptions” in Chapter 1.
primary output file to be produced.
*APIDFN: The output is directed to the database files
Optional Parameters which were previously prepared by running the
JOB QMHCTLJL API. This option can only be used if the
Specifies the name of the job whose job log is shown. If JOB parameter specified the special value asterisk (*).
no job qualifier is given, all jobs currently in the system The OUTFILE and OUTMBR parameters are not used.
are searched for the simple job name. If duplicates of When this option is used both a primary and secondary
the specified name are found, a list of messages con- output file can be produced. Any message filtering
taining the qualified job names of all duplicate names is specified onthe API is applied to the messages before
shown. they are written to the data base. THe database format
A job identifier is a special value or a qualified name (QMHPFT) of the outpt file is the same as that used in
with up to three elements. For example: hte IBM-supplied database file QAMHJLPR.
\ OUTFILE
job-name Specifies the name of the database file to which the
user-name/job-name output of the display is directed. If this file does not
job-number/user-name/job-name exist, this command creates a database file in the speci-
*: The job in which this command is issued is the job fied library. The public authority is the same as the
whose job log is shown.
create authority specified for the library in which the file not exist, the system creates a member with the name of
is created. the file specified on the OUTFILE parameter. If the
member already exists, the user has the option to add
The file specified here cannot be a DDM file.
new records to the end of the existing member or clear
The possible library values are: the member and then add the new records.
*LIBL: The library list is used to locate the outfile. member-name: Specify the file member that receives
If the outfile is not found, one is created in the the output. If OUTMBR(member-name) is specified and
current library. If no current library exists, the outfile the member does not exist, the system creates it. If the
is created in the QGPL library. member already exists, you have the option to add new
records to the end of the existing member or clear the
*CURLIB: The current library for the job is used to
member and then add the new records.
locate the specified outfile. If no library is specified
as the current library for the job, the library QGPL is Element 2: Operation to Perform on Member
used.
*REPLACE: The system clears the existing member
library-name: Specify the name of the library where and adds the new records.
the outfile is located.
*ADD: The system adds the new records to the end of
Database-file-name: Specify the name of the outfile that the existing records.
receives the output of the display.
OUTMBR Example
Specifies the name of the database file member to which DSPJOBLOG JOB(ANDERSON/PAYROLL) OUTPUT(\PRINT)
the output is directed.
This command produces a job log for job PAYROLL for user
Element 1: Member to Receive Output
ANDERSON.
*FIRST: The first member in the file receives the output.
If OUTMBR(*FIRST) is specified and the member does
(P)─┬────────────────────────┬────────────────────────────────────────────────────────────────────────────────────5%
55──DSPJOBTBL───
│ ┌─\──────┐ │
└─OUTPUT(──┴─\PRINT─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose OUTPUT
Specifies whether the output from the command is dis-
The Display Job Tables (DSPJOBTBL) command displays played at the requesting work station or printed with the
information about the job tables which are internal system job's spooled output. More information on this param-
objects used by the operating system to track all jobs on the eter is in Appendix A, “Expanded Parameter
system. The information includes the size of the tables and Descriptions.”
the number of different types of entries in the tables. The
*: Output requested by an interactive job is shown on
number of entries in these tables can affect the performance
the display. Output requested by a batch job is printed
of various IPL steps and OS/400 commands and application
with the job's spooled output.
program interfaces (APIs) that work with jobs.
*PRINT: The output is printed with the job's spooled
Note: To see the parameter and value descriptions for this
output.
command, refer to the online help text. For more
information about printing the help text, refer to
“Printing CL Command Descriptions” in Chapter 1. Example
DSPJOBTBL OUTPUT(\)
Optional Parameters
This command displays information about the job tables.
(1) ───────────────────┬──)────────────────────────────────────────────────────────────────────────5
55──DSPJRN──JRN(──┬─\INTSYSJRN───
│ ┌─\LIBL/────────┐ │
└─┼───────────────┼──journal-name─┘
├─\CURLIB/──────┤
└─library-name/─┘
5──┬──────────────────────────────────────────────────────────────────────────────┬─────────────────────────────────────────────5
│ ┌─\ALLFILE───────────────────────────────────────────────────────┐ │
│ │ ┌──
─────────────────────────────────────────────────────────┐ │ │
│ │ │ ┌─\LIBL/────────┐ ┌─\FIRST──────┐ │ │ │
6 (2) (3)
└─FILE(──┴───(──┼───────────────┼──┬─\ALL──────┬──┼─────────────┼──)─┴────┴──)─┘
├─\CURLIB/──────┤ └─file-name─┘ ├─\ALL────────┤
└─library-name/─┘ └─member-name─┘
(P) ────────────────5
5──┬────────────────────────────────────────────────────────────────────────────────────────────────────────┬───
│ ┌─\CURRENT───────────────────────────────────────────────────────────────────────────────┐ │
└─RCVRNG(──┼─\CURCHAIN──────────────────────────────────────────────────────────────────────────────┼──)─┘
│ ┌─\CURRENT────────────────────────────────┐ │
│ ┌─\LIBL/────────┐ │ ┌─\LIB/─────────┐ │ │
└─┼───────────────┼──start-journal-receiver──┴─┼───────────────┼──end-journal-receiver─┴─┘
├─\CURLIB/──────┤ ├─\CURLIB/──────┤
└─library-name/─┘ └─library-name/─┘
5──┬────────────────────────────────────────────┬──┬───────────────────────────────────────┬────────────────────────────────────5
│ ┌─\FIRST───────────────────┐ │ │ ┌─\LAST──────────────────┐ │
├─FROMENT(──┴─starting-sequence-number─┴──)──┤ ├─TOENT(──┴─ending-sequence-number─┴──)─┤
└─FROMTIME(──starting-date──starting-time──)─┘ └─TOTIME(──ending-date──ending-time──)──┘
5──┬─────────────────────────────────┬──┬───────────────────────────────────────────────────────┬───────────────────────────────5
│ ┌─\ALL────────────┐ │ │ ┌─\ALL──────────────────────────────────┐ │
└─NBRENT(──┴─maximum-entries─┴──)─┘ └─JRNCDE(──┼─\CTL──────────────────────────────────┼──)─┘
│ ┌──
────────────────────────────────┐ │
│ │ ┌─\ALLSLT──────┐ │ │
6 (4) (5)
└───journal-code──┴─\IGNFILSLT───┴─┴────┘
5──┬───────────────────────────────────┬──┬────────────────────────────────────────────────────────┬────────────────────────────5
│ ┌─\ALL──────────────┐ │ │ ┌─\ALL──────────────────────────────────────┐ │
└─ENTTYP(──┼─\RCD──────────────┼──)─┘ └─JOB(──┴─┬─────────────────────────────┬──job-name─┴──)─┘
│ ┌──
────────────┐ │ └─┬─────────────┬──user-name/─┘
└──6─entry-type─┴───
(6) ─┘ └─job-number/─┘
5──┬───────────────────────────┬──┬───────────────────────────┬──┬───────────────────────────────────────────┬──────────────────5
│ ┌─\ALL─────────┐ │ │ ┌─\ALL──────┐ │ │ ┌─\ALL────────────────────┐ │
└─PGM(──┴─program-name─┴──)─┘ └─USRPRF(──┴─user-name─┴──)─┘ └─CMTCYCID(──┴─commit-cycle-identifier─┴──)─┘
5──┬───────────────────────┬──┬───────────────────────┬──┬─────────────────────────┬──┬──────────────────────────┬──────────────5
│ ┌─\ALL──┐ │ │ ┌─\CHAR─┐ (7) ─journal-ID──)─┘ │
│ └─JRNID(─── ┌─\────────┐ │
└─DEPENT(──┴─\NONE─┴──)─┘ └─OUTFMT(──┴─\HEX──┴──)─┘ └─OUTPUT(──┼─\PRINT───┼──)─┘
└─\OUTFILE─┘
5──┬─────────────────────────────┬──┬───────────────────────────────────────────┬───────────────────────────────────────────────5
│ ┌─\TYPE1─┐ │ │ ┌─\LIBL/────────┐ │
(8) ─┼─\TYPE2─┼──)─┘ └─OUTFILE(──┼───────────────┼──file-name──)─┘
└─OUTFILFMT(───
├─\TYPE3─┤ ├─\CURLIB/──────┤
└─\TYPE4─┘ └─library-name/─┘
5──┬─────────────────────────────────────────────┬──┬──────────────────────────────────────────────────────────────────────┬────5
│ ┌─\FIRST──────┐ ┌─\REPLACE─┐ │ │ ┌─\OUTFILFMT──────────────────────────────────────┐ │
(8) ─┴─member-name─┴──┼──────────┼──)─┘ └─ENTDTALEN(───
└─OUTMBR(─── (8) ─┼─\CALC───────────────────────────────────────────┼──)─┘
└─\ADD─────┘ ├─field-length────────────────────────────────────┤
│ ┌─\CALC────────┐ ┌─\FLDLEN──────────┐ │
└─\VARLEN──┴─field-length─┴──┼──────────────────┼─┘
└─allocated-length─┘
5──┬───────────────────────────────────────────────────────────────────────┬──┬───────────────────────────────┬────────────────5%
| │ ┌─\OUTFILFMT──────────────────────────────────────┐ │ │ ┌─\CONFIRMED─┐ │
| (9) ─┼─\CALC───────────────────────────────────────────┼──)─┘ └─INCENT(────
└─NULLINDLEN(─── (10) ─┴─\ALL───────┴──)─┘
├─field-length────────────────────────────────────┤
│ ┌─\CALC────────┐ ┌─\FLDLEN──────────┐ │
└─\VARLEN──┴─field-length─┴──┼──────────────────┼─┘
└─allocated-length─┘
Notes:
1 If the *INTSYSJRN value is specified, the JRNID parameter must be specified.
| 5 A maximum of 12 repetitions.
6 A maximum of 50 repetitions.
7 The JRNID parameter can be specified only if JRN(*INTSYSJRN) is specified.
8 This parameter is valid only if OUTPUT(*OUTFILE) is specified.
9 The NULLINDLEN parameter is valid only if OUTFILFMT(*TYPE3) or OUTFILFMT(*TYPE4) is specified.
| 10 This parameter is only valid for a remote journal.
P All parameters preceding this point can be specified in positional form.
| If the specified file member does not currently exist does not have the required authority to all of the files, an
| on the system, the specified receiver range is error occurs, and the command ends.
| searched to determine all possible journal identifiers
file-name: Specify the name of the physical database
| that are associated with the specified file member.
file whose journaled changes are being converted for
| All journal entries in the specified receiver range for
output.
| those journal identifiers are converted for output.
Element 2: Member Name
| There can be more than one journal identifier asso-
| ciated with the specified file member if, for example, *FIRST: Entries for the first member in the file are con-
| a file member was created by that name, it was verted for output.
| journaled, and then deleted. Then another file *ALL: Entries for currently existing members of the file
| member was created with the same name, and it are converted for output.
| was also journaled and then deleted. All of these
| actions would have to occur within the specified
member-name: Specify the name of the file member
whose entries are converted for output. If the specified
| receiver range.
physical file does not exist on the system, specify either
| Notes: *ALL or a specific file member name.
| 1. The journal identifier is the unique identifier associ- If *ALL is specified for the file-name value, this member
| ated with the object when journaling is started for name is used for all applicable files in the library. For
| that object. The journal identifier stays constant, example, if library-name/*ALL *FIRST is specified on the
| even if the object is renamed or moved. See the FILE parameter, the journal entries of the first members
| Backup and Recovery book for more information. of all applicable files in the specified library are con-
verted for output.
2. When specifying a database file on this parameter,
journal entries with the following journal code values | Note: If more than the maximum number of members
are converted for output only if they satisfy the | is identified (32767 members if a list of files is
values specified on the other parameters: specified), an error occurs and no entries are
converted for output. This restriction is ignored if
| Journal code D (database file-level information
*ALLFILE is specified.
| entries).
| Journal code F (file member-level information RCVRNG
| entries). Specifies the starting (first) and ending (last) journal
Journal code R (record-level information receivers (the receiver range) that contain the journal
entries). entries being converted for output. The system starts
Journal code U (user-generated entries). with the starting journal receiver (as specified by the first
Other journal codes, if *IGNFILSLT is the value) and proceeds through the receiver chain until the
second element of the journal code. If ending receiver (as specified by the last value) is pro-
*ALLSLT is the second element of the journal cessed.
code, no journal entries with that code are con-
If dual receivers are used at any time, the first of the
verted for output.
receivers is used when chaining through the receivers.
Single Value The Work with Journal Attributes (WRKJRNA) command
can be used to show the order of the receivers in the
*ALLFILE: For all files, all journal entries on the speci-
receiver chain. If a problem (such as damaged or not
fied journal receivers are converted.
found receivers) is found in the receiver chain prior to
Element 1: File Name starting the conversion, the system tries to use the
second of the dual receivers. If the second of the dual
The name of the file can be qualified by one of the fol-
receivers is damaged or not found, the command ends.
lowing library values:
Note: If the maximum number of receivers (256) in the
*LIBL: All libraries in the job's library list are
range is surpassed, an error occurs and no
searched until the first match is found.
journal entries are converted.
*CURLIB: The current library for the job is
*CURRENT: The journal receiver that is currently
searched. If no library is specified as the current
attached when starting to convert journal entries is used.
library for the job, the QGPL library is used.
*CURCHAIN: The journal receiver chain that includes
library-name: Specify the name of the library to be the journal receiver that is currently attached when
searched.
starting to convert journal entries is used. This receiver
*ALL: Journal entries in all physical files in the specified chain does not cross a break in the chain. If there is a
| library (the library name must be specified) whose jour- break in the chain, the receiver range is from the most
| naled changes are currently in the journal receiver are recent break in the chain through the receiver that is
converted for output. If *ALL is specified and the user attached when starting to convert journal entries.
Element 1: Starting Journal Receiver this command from the command line, the string
must be enclosed in apostrophes. If a time sepa-
The name of the starting journal receiver can be quali-
rator other than the separator specified for your job
fied by one of the following library values:
is used, this command fails.
*LIBL: All libraries in the job's library list are
Without a time separator, specify a string of 4 or 6
searched until the first match is found.
digits (hhmm or hhmmss) where hh = hours, mm =
*CURLIB: The current library for the job is minutes, and ss = seconds. Valid values for hh
searched. If no library is specified as the current range from 00 through 23. Valid values for mm and
library for the job, the QGPL library is used. ss range from 00 through 59.
library-name: Specify the name of the library to be TOENT
searched. Specifies the last journal entry to be converted for
output.
starting-journal-receiver: Specify the name of the first
journal receiver whose entries are converted for output. *LAST: The last journal entry in the specified journal
receiver chain is the final entry to be converted.
Element 2: Ending Journal Receiver
*CURRENT: The journal receiver that is currently
ending-sequence-number: Specify the sequence
number of the final journal entry being converted for
attached when starting to convert journal entries is used.
output.
The name of the ending journal receiver can be qualified
by one of the following library values: TOTIME
Specifies the date and time of the last entry to be con-
*LIBL: All libraries in the job's library list are verted for output. The journal entry with the specified
searched until the first match is found. date and time or the latest earlier journal entry is the
*CURLIB: The current library for the job is ending point for conversion of journal entries.
searched. If no library is specified as the current Element 1: Ending Date
library for the job, the QGPL library is used.
ending-date: Specify the date of the last entry.
library-name: Specify the name of the library to be
Element 2: Ending Time
searched.
ending-time: Specify the time on the date of the last
ending-journal-receiver: Specify the name of the last entry. The time is specified in 24-hour format with or
journal receiver whose entries are to be converted for
without a time separator as follows:
output.
With a time separator, specify a string of 5 or 8
FROMENT
digits, where the time separator for the job sepa-
Specifies the first journal entry to be considered for con-
rates the hours, minutes, and seconds. If you issue
version for output.
this command from the command line, the string
*FIRST: The first journal entry in the specified journal must be enclosed in apostrophes. If a time sepa-
receiver range is the first entry to be converted. rator other than the separator specified for your job
is used, this command fails.
starting-sequence-number: Specify the sequence
number of the first entry to be converted. Without a time separator, specify a string of 4 or 6
digits (hhmm or hhmmss) where hh = hours, mm =
FROMTIME
minutes, and ss = seconds. Valid values for hh
Specifies the date and time of the first journal entry to be
range from 00 through 23. Valid values for mm and
converted for output.
ss range from 00 through 59.
The first journal entry with the specified date and time or
NBRENT
the next later journal entry is the starting point for con-
Specifies the total number of journal entries to be con-
version of journal entries.
verted for output.
Element 1: Starting Date
*ALL: All journal entries that satisfy the selection values
starting-date: Specify the date of the first entry. in the specified journal receivers are converted.
Element 2: Starting Time maximum-entries: Specify the maximum number of
starting-time: Specify the time on the date of the first journal entries to be converted. If the journal entry spec-
entry. The time is specified in 24-hour format with or ified on the TOENT or TOTIME parameter is reached
without a time separator as follows: before the value specified on the NBRENT parameter is
met, the command ends normally.
With a time separator, specify a string of 5 or 8
digits, where the time separator for the job sepa- JRNCDE
rates the hours, minutes, and seconds. If you issue Specifies the journal codes for which journal entries are
converted for output.
Journal Types
Table 5. OUTFILFMT(*TYPE1) Journal Entry Format
10 System-managed access-path protection Field Name Length From To
(SMAPP)
Reserved 8 118 125
20 Directory Entry-Specific Data 1001 126 225
Note:
OUTPUT
1 This is the field length in the system-supplied data-
Specifies whether the output from the command is
base file, QADSPJRN. However, a length of up to
shown at the requesting work station, printed with the
32641 bytes can be specified for this field using the
job's spooled printer output, or sent to the database file ENTDTALEN parameter.
specified on the OUTFILE parameter. More information
on this parameter is in Appendix A, “Expanded Param-
eter Descriptions.” *TYPE2: The converted entries include the information
When the output of the command is directed to the returned when OUTFILFMT(*TYPE1) is specified, the
requesting work station, basic information on the journal name of the user profile for the job that generated the
entries is shown. From the basic display, an option can displayed journal entries, and the name of the system on
be selected to show information in detail for any journal which the output records were generated. The format of
entry being shown. the information in each journal entry is shown in the fol-
lowing table.
If the output is printed with the job's spooled printer
output, all of the information that would be shown is Table 6. OUTFILFMT(*TYPE2) Journal Entry Format
printed.
Field Name Length From To
*: Output requested by an interactive job is shown on
Entry Length 5 1 5
the display. Output requested by a batch job is printed
Sequence Number 10 6 15
with the job's spooled output. Journal Code 1 16 16
*PRINT: The output is printed with the job's spooled Journal Entry Type 2 17 18
output. Date 6 19 24
Time 6 25 30
*OUTFILE: The output is directed to the database file Job Name 10 31 40
specified on the OUTFILE parameter. User Name 10 41 50
Job Number 6 51 56
OUTFILFMT Program Name 10 57 66
Specifies the format of the journal entries written to the Object Name 10 67 76
output file specified on the OUTFILE parameter. This Object Library 10 77 86
parameter can be specified only if the value *OUTFILE Member Name 10 87 96
is specified on the OUTPUT parameter. For a Count/RRN 10 97 106
Flag 1 107 107
description of what is represented by each of the fields
Commit Cycle ID 10 108 117
in the journal entry, see the Backup and Recovery book
User Profile 10 118 127
*TYPE1: The converted entries are formatted to include System Name 8 128 135
the minimum information that can be specified. The Reserved 20 136 155
information fields and the format of the information in Entry-Specific Data 1001 156 255
Note:
each journal entry is shown in the following table.
1 This is the field length in the system-supplied data-
base file, QADSPJR2. However, a length of up to
Table 5. OUTFILFMT(*TYPE1) Journal Entry Format
32611 bytes can be specified for this field using the
Field Name Length From To ENTDTALEN parameter.
Entry Length 5 1 5
Sequence Number 10 6 15
Journal Code 1 16 16 *TYPE3: The converted entries include the information
Journal Entry Type 2 17 18 returned when OUTFILFMT(*TYPE2) is specified, and
Date 6 19 24 the null value indicators. The format of the information
Time 6 25 30 in each converted journal entry is shown in the following
Job Name 10 31 40 table.
User Name 10 41 50
Job Number 6 51 56
Table 7 (Page 1 of 2). OUTFILFMT(*TYPE3) Journal
Program Name 10 57 66
Entry Format
Object Name 10 67 76
Object Library 10 77 86 Field Name Length From To
Member Name 10 87 96
Entry Length 5 1 5
Count/RRN 10 97 106
Sequence Number 10 6 15
Flag 1 107 107
Journal Code 1 16 16
Commit Cycle ID 10 108 117
Journal Entry Type 2 17 18
Table 7 (Page 2 of 2). OUTFILFMT(*TYPE3) Journal Table 8. OUTFILFMT(*TYPE4) Journal Entry Format
Entry Format
Field Name Length From To
Field Name Length From To
System Name 8 142 149
Timestamp1 26 19 44 Journal Identifier 10 150 159
Job Name 10 45 54 Referential 1 160 160
User Name 10 55 64 Constraint
Job Number 6 65 70 Trigger 1 161 161
Program Name 10 71 80 Reserved 8 162 169
Object Name 10 81 90 Null Value Indicators 522,3 170 221
Object Library 10 91 100 Entry-Specific Data 1023,4 222 323
Member Name 10 101 110 Notes:
Count/RRN 10 111 120 1 The date and time of the journal entry is in 26-byte
Flag 1 121 121
SAA timestamp format instead of separate date and
Commit Cycle ID 10 122 131
time fields as in *TYPE1 and *TYPE2.
User Profile 10 132 141 2 This is a 50-character variable-length field in the
System Name 8 142 149
system-supplied database file QADSPJR4. However,
Reserved 20 150 169
a length of up to 8000 characters can be specified for
Null Value Indicators 522,3 170 221
this field using the NULLINDLEN parameter.
Entry-Specific Data 1023,4 222 323 3 The first two bytes are the length of the variable-length
Notes:
field followed by the actual data if the fields are
1 The date and time of the journal entry is in 26-byte variable-length fields.
SAA timestamp format instead of separate date and 4 This is a 100-character variable-length field in the
time fields as in *TYPE1 and *TYPE2. system-supplied database file QADSPJR4. However,
2 This is a 50-character variable-length field in the a length of up to 32596 characters can be specified for
system-supplied database file QADSPJR3. However, this field using the ENTDTALEN parameter if it is a
a length of up to 8000 characters can be specified for fixed-length field and the null value indicators field is
this field using the NULLINDLEN parameter. also a fixed-length field.
3 The first two bytes are the length of the variable-
length field followed by the actual data if the fields
are variable-length fields. OUTFILE
4 This is a 100-character variable-length field in the Specifies the qualified name of the physical database file
system-supplied database file QADSPJR3. However, to which the output is directed. If the output file already
a length of up to 32596 characters can be specified
exists, the system attempts to use it. Records may
for this field using the ENTDTALEN parameter if it is
a fixed-length field and the null value indicators field
replace or be added to the current data in the file
is also a fixed-length field. member. If no records are written to the database file
(because of the specified selection values), and
*REPLACE is specified on the OUTMBR parameter,
*TYPE4: The converted entries include the information records are cleared from the existing database file. If
returned when OUTFILFMT(*TYPE3) is specified, the the output file does not exist, the system creates a data-
journal identifier, the physical file trigger indicator, and base physical file with the name specified in the
the referential constraint indicator. The format of the OUTFILE parameter in the identified library, even if no
information in each converted journal entry is shown in records are written (because of the specified selection
the following table. values).
*LIBL: All libraries in the job's library list are database file will be a fixed length field 100 characters in
searched until the first match is found. length.
*CURLIB: The current library for the job is If *TYPE3 or *TYPE4 is specified on the OUTFILFMT
searched. If no library is specified as the current parameter, the entry-specific data field in the output file
library for the job, the QGPL library is used. is a variable-length field with a maximum field length of
100 characters and an allocated length of 100 charac-
library-name: Specify the name of the library to be
ters. The buffer is 2 bytes longer than the maximum
searched.
field length to include the length portion of the variable-
file-name: Specify the name of the output file that length field.
receives the journal entries.
*CALC: The system calculates the length of the entry-
OUTMBR specific data field to accommodate the longest entry-
Specifies the name of the database file member to which specific data of all journal entries in the specified
the output is directed. If a member already exists, the receiver range. In this case, the entry-specific data field
system uses the second element of this parameter to is a fixed-length character field. The minimum length of
determine whether the member is cleared before the the field is 114 characters. If the length calculated by
new records are added. If the member does not exist the system causes the record format length to exceed
and a member name is not specified, the system creates the maximum record length, a message is sent and the
a member with the name of the output file specified on entry-specific data field is truncated. See the table at
the OUTFILE parameter. If an output file member name the end of this parameter description for the possible
is specified, but the member does not exist, the system maximum record lengths of the various data types that
creates it. can be specified.
Element 1: Member to Receive Output field-length: Specify the number of characters for the
field length. In this case, the field is a fixed-length char-
*FIRST: The first member of the file specified by the
acter field. The maximum value prevents the total
OUTFILE parameter receives the journal entries. If the
record length of the output file from being greater than
OUTFILE is created and *FIRST is specified, the created
the length allowed for physical database files. A
member has the same name as the created file. If
nonzero value is required by the system to ensure that
OUTMBR is not specified, *FIRST is assumed.
the field exists when the output file is created.
member-name: Specify the file member that receives See the table at the end of this parameter description for
the output. If OUTMBR(member-name) is specified and
the allowable field lengths of the various data types that
the member does not exist, the system creates it.
can be specified
Element 2: Operation to Perform on Member
Element 1: Variable-Length Field
*REPLACE: The system clears the existing member
To specify a variable-length field, specify *VARLEN for
and adds the new records.
the first element and length values for the last two ele-
*ADD: The system adds the new records to the end of ments (or let the system use the default values).
the existing records.
*VARLEN: The entry-specific data field is a variable-
ENTDTALEN length field. This value can be specified only when
Specifies the maximum field length of the entry-specific OUTFILFMT(*TYPE3) or OUTFILFMT(*TYPE4) is speci-
data portion of the journal entry when the output file is fied.
created by the system. This field contains part of the Element 2: Maximum Field Length
variable portion of the journal entries (such as the after
image of records for update journal entries). If the The maximum length of the variable-length, entry-
output file exists, this parameter is ignored. specific data field.
The range of allowable values for this parameter is *CALC: The system calculates the maximum length of
the entry-specific data field to accommodate the longest
shown in the table at the end of this parameter
entry-specific data of all journal entries in the specified
description. A single value or a single list of three ele-
receiver range. The minimum length of this field is 114
ments can be specified.
bytes. The corresponding buffer length is 116 bytes:
Single Values 114 bytes of data and 2 bytes for the length portion of
*OUTFILFMT: The length of the entry-specific data field the variable-length field.
in the output file depends on the value specified on the field-length: Specify the number of characters for the
OUTFILFMT parameter. The attributes of this field are maximum field length. See the table at the end of this
the same as those of the entry-specific data field in the parameter description for the allowable field lengths of
corresponding system-supplied model output file. the various data types that can be specified.
If *TYPE1 or *TYPE2 is specified on the OUTFILFMT Element 3: Allocated Length
parameter, the entry-specific data field in the output
The allocated length of the variable-length entry-specific supplied model output file QADSPJR3 or QADSPJR4. It
data field. is a variable-length character field with a maximum
length of 50 characters and an allocated length of 50
*FLDLEN: The allocated length is the same as the
characters. The buffer is 2 bytes longer than the
maximum length of the field.
maximum field length to include the length portion of the
allocated-length: Specify the number of characters for variable-length field.
the allocated length.
*CALC: The system calculates the length of this field to
If *CALC is specified for the second element and the accommodate the journal entry with the maximum
system-calculated maximum field length is smaller than number of null value indicators in the specified receiver
the specified allocated length, the allocated length is set range. In this case, the null value indicators field is a
to the maximum field length. If the maximum field length fixed-length character field. The minimum length of this
is specified, the allocated length cannot exceed the field is 1 character to ensure that the field exists when
maximum field length. the output file is created. If the length calculated by the
system causes the record format length to exceed the
Table 9. Range of Values for ENTDTALEN Parameter maximum record length, a message is sent and the null
Entry- Null value indicators field is truncated. See the table at the
Output Specific Value Entry Maximum end of this parameter description for the possible
File Data Indicators Data Record maximum record lengths of the various data types that
Format Format Format Length Length can be specified for the NULLINDLEN parameter.
*TYPE1 Fixed Not appli- 1–32641 32766 field-length: Specify the number of characters for the
cable field length. Valid values range from 1 through 8000. A
*TYPE2 Fixed Not appli- 1–32611 32766 nonzero value is required by the system to ensure that
cable the field exists when the output file is created. In this
*TYPE3 Fixed Fixed 1–32596 32766 case, the null value indicators field is a fixed-length char-
*TYPE3 Fixed Variable 1–32570 32740 acter field.
*TYPE3 Variable Fixed 1–32570 32740 Element 1: Variable-Length Field
*TYPE3 Variable Variable 1–32568 32738 To specify a variable-length field, specify *VARLEN for
*TYPE4 Fixed Fixed 1–32596 32766 the first element and length values for the last two ele-
ments (or let the system use the default values).
*TYPE4 Fixed Variable 1–32570 32740
*TYPE4 Variable Fixed 1–32570 32740 *VARLEN: The null value indicators field is a variable-
length field.
*TYPE4 Variable Variable 1–32568 32738
Element 2: Maximum Field Length
Note: When the file contains variable-length fields, the
maximum record length does not include the 2 bytes per Specifies the maximum length of the variable-length null
variable-length field. value indicators field.
*CALC: The system calculates the length of this field to
NULLINDLEN accommodate the journal entry with the maximum
Specifies the length of the null value indicators field number of null value indicators in the specified receiver
when the output file is created by the system. This range. To ensure that this field exists in the output file
parameter can be specified only if OUTFILFMT(*TYPE3) that is created, the minimum length of this field is 1 byte.
or OUTFILFMT(*TYPE4) is specified. The corresponding buffer length is 3 bytes: 1 byte of
data and 2 bytes for the length portion of the variable-
Null value indicators are present only in journal entries
length field.
that contain a record image where the corresponding
physical file has null capable fields. There is one null field-length: Specify the maximum length of the null
value indicator per field in the physical file. Each indi- value indicators field. Valid values range from 1 through
cator is one character in length and can be one of two 8000 characters.
values: Element 3: Allocated Length
'Fð'X = Corresponding field is not null. Specifies the allocated length of the variable-length null
'F1'X = Corresponding field is null.
value indicators field.
The range of allowable values for this parameter is
*FLDLEN: The allocated length is the same as the
shown in the table at the end of this parameter
maximum length of the field.
description. A single value or a single list of three ele-
ments can be specified. If *CALC is specified for Element 2 and the system-
calculated maximum length is smaller than the specified
Single Values
allocated length, the allocated length is set to the
*OUTFILFMT: The null value indicators field has the maximum field length. If the maximum field length is
same attributes as the corresponding field in the system-
specified, the allocated length cannot exceed the shown by pressing the Page Down key. When entered from
maximum field length. a batch job, the above command prints all converted journal
entries with the job's spooled printer output. The entry-
allocated-length: Specify the number of characters for
specific data portion of the journal entries are shown in char-
the allocated length.
acter format.
Table 10. Range of Values for NULLINDLEN Parameter Example 2: Converting Journal Entries to an Output File
Entry- Null DSPJRN JRN(MYLIB/JRNLA) FILE((LIB1/A MBR3) (LIB1/C)
Output Specific Value Null Line Maximum (LIB2/\ALL \ALL)) RCVRNG((RCVLIB/RCV27
File Data Indicators Indicator Record
RCVLIB/RCV3ð)) FROMENT(4736) ENTTYP(UP DL)
Format Format Format Length Length
JOB(ððð666/QPGMR/WORKSTð1) PGM(TSTPGMA)
*TYPE3 Fixed Fixed 1–8000 32766 ENTDTALEN(28ð) OUTPUT(\OUTFILE)
*TYPE3 Fixed Variable 1–8000 32740 OUTFILE(MYLIB/JRNENTFIL1)
*TYPE3 Variable Fixed 1–8000 32740 This command converts selected journal entries in the journal
*TYPE3 Variable Variable 1–8000 32738 receiver chain (from receiver RCV27 in library RCVLIB to
*TYPE4 Fixed Fixed 1–8000 32766 receiver RCV30 in library RCVLIB) that are attached to
JRNLA in library MYLIB and places them in the first member
*TYPE4 Fixed Variable 1–8000 32740
of the database file JRNENTFIL1 in library MYLIB. If the
*TYPE4 Variable Fixed 1–8000 32740 database file does not exist, it is created with a format of
*TYPE4 Variable Variable 1–8000 32738 QJORDJE. The last field in the format is 280 bytes in length.
Note: When the file contains variable-length fields, the The journal entry that has a sequence number of 4736 is the
maximum record length does not include the 2 bytes per first entry written to the output file. Only entries for record
variable-length field. updates and deletes made by program TSTPGMA in the job
000666/QPGMR/WORKST01 to member MBR3 of file A in
library LIB1, the first member of file C in library LIB1, and all
| INCENT members of all files in library LIB2 are written to the output
| Specifies whether only the confirmed or both the con- file.
| firmed and unconfirmed, journal entries are converted for
| output. This parameter only applies when converting Example 3: Converting Journal Entries for a Specific
| journal entries for output from a remote journal. User Profile
| Confirmed entries are those journal entries which have DSPJRN JRN(SS/J) FILE(SS1/PF)
| been sent to this remote journal and the state of the RCVRNG((SS/R1 \CURRENT)) JRNCDE(F) USRPRF(MAC7)
| Input/Output (I/O) to auxiliary storage for the same OUTFILE(FMTLIB/ENTFILE) OUTFILFMT(\TYPE2)
| journal entries on the local journal is known.
This command converts selected journal entries in the journal
| Unconfirmed entries are those journal entries which have receiver range. The range begins with journal receiver R1 in
| been sent to this remote journal, but the state of the library SS and ends with the journal receiver currently
| Input/Output (I/O) to auxiliary storage for the same attached (when the converting of journal entries is started) to
| journal entries on the local journal is not known, or the journal J in library SS. The entries are placed in the first
| object name information for those journal entries is not member of the database file ENTFILE in library FMTLIB. If
| yet known to the remote journal. Unconfirmed journal the file does not exist, it is created with the QJORDJE2
| entries can only exist within the attached receiver of a format. The last field of the format is 100 bytes in length.
| remote journal. This only applies if synchronous delivery Only entries with file-level information made by the user
| mode is being used for a particular remote journal. MAC7 to the first member of file PF in library SS1 are written
| *CONFIRMED: Only those journal entries which have to the output file.
| been confirmed are converted for output.
Example 4: Converting Journal Entries with Null Value
| *ALL: All confirmed and unconfirmed journal entries are Field Length Specified
| converted for output.
DSPJRN JRN(LIBPROD/PRODJRN) FILE(APPLIB/PFILE)
OUTFILFMT(\TYPE3) OUTFILE(JRNLIB/ENTFILE)
Examples ENTDTALEN(\VARLEN 5ðð 1ðð) NULLINDLEN(25)
Example 1: Converting Journal Entries for Display This command converts selected journal entries that are in
the range from the journal receiver currently attached (when
DSPJRN JRN(MYLIB/JRNLA)
the converting of entries is started) to the journal PRODJRN
When issued at a work station, this command converts and in library LIBPROD. The entries are placed in the first
shows the first journal entries in the journal receiver currently member of the database file ENTFILE in library JRNLIB. If
attached (when the converting of journal entries is started) to the file does not exist, it is created with the QJORDJE3
the journal JRNLA in library MYLIB. Subsequent entries are format. The entry-specific data field is a variable-length field
with a maximum field length of 500 characters and an allo- length null value indicators field. The allocated length of this
cated length of 100 characters. The null value indicators field is the same as the maximum field length.
field is a fixed-length field of 25 characters. Only entries with
file-level information for the first member of file PFILE in Example 6: Converting Journal Entries Using
library APPLIB are written to the output file. *IGNFILSLT and *CURCHAIN
DSPJRN JRN(JRNLIB/JRNA) FILE(FILLIB/FILEA)
Example 5: Converting Journal Entries with Null Value RCVRNG(\CURCHAIN) JRNCDE((F \ALLSLT) (R \ALLSLT)
Field Length Calculated (U \IGNFILSLT)) OUTPUT(\PRINT)
DSPJRN JRN(JRNLIB/JRNA) FILE(FILLIB/FILEA)
FROMENT(4736) ENTTYP(UP DL) This command converts journal entries with:
JOB(ððð666/QPGMR/WORKSTð1) PGM(TSTPGMA) File-level information for the first member of file FILEA in
ENTDTALEN(28ð) OUTPUT(\OUTFILE) library FILLIB
OUTFILFMT(\TYPE3) OUTFILE(ENTLIB/ENTFILE)
ENTDTALEN(\CALC) NULLINDLEN(\VARLEN \CALC \FLDLEN) Record-level information for the first member of file
FILEA in library FILLIB
This command converts journal entries with file-level informa-
User-generated journal entries regardless of whether the
tion for the first member of file FILEA in library FILLIB in the
entry is associated with any journaled file member
range from the journal receiver currently attached (when the
converting of entries is started) to the journal JRNA in library Journal entries are converted from the chain of journal
JRNLIB. The entries are written to the first member of data- receivers, which are the journal receivers in the range from
base file ENTFILE in library ENTLIB. If the file does not the latest chain break through the journal receiver currently
exist, it is created with the QJORDJE3 format. The system attached when the converting of entries is started, associated
calculates the length of the fixed-length, entry-specific data with the journal JRNA in library JRNLIB. The converted
field. The system also calculates the length of the variable- entries are written to a print file.
┌─\LIBL/────────┐
(P) ────────────────────────────────────5%
55──DSPJRNRCVA──JRNRCV(──┼───────────────┼──receiver-name──)──┬────────────────────────┬───
├─\CURLIB/──────┤ │ ┌─\──────┐ │
└─library-name/─┘ └─OUTPUT(──┴─\PRINT─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
55──DSPKBDMAP──────────────────────────────────────────────────────────────────────────────────────────────────────────────────5%
(P) ─┬────────────────────────────────┬──────────────────────5
55──DSPLANADPP──LINE(──line-name──)──ADPTNAME(──┬─\ADPTADR─────┬──)────
└─adapter-name─┘ (1) ─adapter-address──)─┘
└─ADPTADR(───
5──┬────────────────────────┬──────────────────────────────────────────────────────────────────────────────────────────────────5%
│ ┌─\──────┐ │
└─OUTPUT(──┴─\PRINT─┴──)─┘
Notes:
P All parameters preceding this point can be specified in positional form.
ADPTNAME Example
Specifies the name of the adapter whose profile is to be
DSPLANADPP LINE(DETBRANCH) ADPTNAME(PAYROLL)
displayed.
*ADPTADR: The adapter address is used to identify the This command displays the profile of the adapter PAYROLL
adapter. which is attached to the line DETBRANCH.
adapter-name: Specify the name of the adapter whose
profile is to be displayed.
(P)─┬────────────────────────┬───────────────────────────────────────────────────5%
55──DSPLANMLB──LIND(──line-description-name──)───
│ ┌─\──────┐ │
└─OUTPUT(──┴─\PRINT─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose OUTPUT
Specifies whether the output from the command is dis-
The Display LAN information for a Media Library played at the requesting work station or printed with the
(DSPLANMLB) command displays local area network attri- job's spooled output.
butes of a line description that is associated with a media
*: The output is displayed (if requested by an interactive
library device. The information is obtained from the Display
job) or printed with the job's spooled output (if requested
Network Attributes (DSPNETA) and the Display Line
by a batch job).
Description (DSPLIND) commands.
*PRINT: The output is printed with the job's spooled
Note: To see the parameter and value descriptions for this
output.
command, refer to the online help text. For more
information about printing the help text, refer to
“Printing CL Command Descriptions” in Chapter 1. Examples
Example 1: Displaying the LAN information for a line
Required Parameter description
LIND DSPLANMLB LIND(TRNLINE) OUTPUT(\)
Specifies the line description that is used to attach the
media library device. This command displays the LAN information for the line
description TRNLINE that is attached to a media library
device.
Optional Parameters
(P) ──────────────────────────────────────────────────5%
55──DSPLANSTS──LINE(──line-description-name──)──┬────────────────────────┬───
│ ┌─\──────┐ │
└─OUTPUT(──┴─\PRINT─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose OUTPUT
Specifies whether the output from the command is
The Display Local Area Network Status (DSPLANSTS) shown at the requesting workstation or printed with the
command shows the status of an active token-ring or a dis- job's spooled output. More information on this param-
tributed data interface (DDI) line. eter is in Appendix A, “Expanded Parameter
Note: The DDI line status is the status of the local network Descriptions.”
from the perspective of the local adapter. *: Output requested by an interactive job is shown on
Note: To see the parameter and value descriptions for this the display. Output requested by a batch job is printed
command, refer to the online help text. For more with the job's spooled output.
information about printing the help text, refer to *PRINT: The output is printed with the job's spooled
“Printing CL Command Descriptions” in Chapter 1. output.
Optional Parameter
(P) ────────────────────────────────────────────────5%
55──DSPLIB──┬──────────────────────────────────┬──┬────────────────────────┬───
│ ┌─\LIBL───────────────┐ │ │ ┌─\──────┐ │
└─LIB(──┼─\CURLIB─────────────┼──)─┘ └─OUTPUT(──┴─\PRINT─┴──)─┘
├─\USRLIBL────────────┤
├─\ALL────────────────┤
├─\ALLUSR─────────────┤
│ ┌──
──────────────┐ │
└──6─library-name─┴───
(1) ─┘
Notes:
1 A maximum of 15 repetitions
55──DSPLIBD──LIB(──┬─\CURLIB──────┬──)──┬────────────────────────┬─────────────────────────────────────────────────────────────5%
└─library-name─┘ │ ┌─\──────┐ │
└─OUTPUT(──┴─\PRINT─┴──)─┘
(P) ─────────────────────────────────────────────────────────────────────────────────────5%
55──DSPLIBL──┬────────────────────────┬───
│ ┌─\──────┐ │
└─OUTPUT(──┴─\PRINT─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
55──DSPLICKEY──┬────────────────────────────────────────────┬──┬──────────────────────────────┬─────────────────────────────────5
│ ┌─\ALL────────────────────────┐ │ │ ┌─\ALL─────────┐ │
└─PRDID(──┼─generic\-product-identifier─┼──)─┘ └─LICTRM(──┴─license-term─┴──)─┘
└─product-identifier──────────┘
(P) ──┬──────────────────────────────────────┬──┬─────────────────────────────┬───────────────────5
5──┬──────────────────────────┬───
│ ┌─\ALL────┐ │ │ ┌─\LOCAL───────────────┐ │ │ ┌─\───────────┐ │
└─FEATURE(──┴─feature─┴──)─┘ └─SERIAL(──┼─\REMOTE──────────────┼──)─┘ └─OUTPUT(──┼─\PRINT──────┼──)─┘
├─\ALL─────────────────┤ └─\LICKEYFILE─┘
└─system-serial-number─┘
5──┬───────────────────────────────────────────────────────┬────────────────────────────────────────────────────────────────────5
│ ┌─\LIBL/────────┐ │
(1) ─┼───────────────┼──license-key-file──)─┘
└─LICKEYFILE(───
├─\CURLIB/──────┤
└─library-name/─┘
5──┬─────────────────────────────────────────────────────────────┬─────────────────────────────────────────────────────────────5%
│ ┌─\FIRST───────────────────┐ ┌─\REPLACE─┐ │
(1) ─┴─member-to-receive-output─┴──┼──────────┼──)─┘
└─LICKEYMBR(───
└─\ADD─────┘
Notes:
1 This parameter is valid only when OUTPUT(*LICKEYFILE) is specified.
Purpose PRDID
Specifies the seven-character identifier of the product for
The Display License Key Information (DSPLICKEY) which software license key information is shown.
command can be used to show the software license key
*ALL: The software license key information for all
information from the license repository for products with
product identifiers is shown.
keyed compliance. Products with keyed compliance require
that you have a software license key from the software pro- generic*-product-identifier: Specify the generic identifier
vider in order to change the usage limit or the expiration date for the products to be shown. A generic product identi-
of the license information. fier is specified in the same manner as a generic name.
A generic name is a character string of one or more
The license repository is used to store product license infor-
characters followed by an asterisk (*); for example,
mation for each unique product, license term, feature, and
ABC*. The asterisk substitutes for any valid characters.
system. The repository can contain licenses for any system,
A generic name specifies all objects with names that
and the product need not be installed.
begin with the generic prefix for which the user has
The information shown includes the processor group, the authority. If an asterisk is not included with the generic
serial number, the software license key, the usage limit, the (prefix) name, the system assumes it to be the complete
expiration date, and the vendor data. object name. For more information on the use of
generic names, refer to “Generic Object Names” in
The Display License Key Information (DSPLICKEY) Chapter 2.
command also can be used to create an output file, which product-identifier: Specify the seven-character identifier
can be used as input to the Add License Key Information of the product.
(ADDLICKEY) command or the Remove License Key Infor-
mation (RMVLICKEY) command. LICTRM
Specifies the license term for which software license key
Restrictions: This command is shipped with public information is shown.
*EXCLUDE authority.
*ALL: The software license key information for all
Note: To see the parameter and value descriptions for this license terms found on the system is shown.
command, refer to the online help text. For more
license-term: Specify the license term in Vx, VxRy, or
information about printing the help text, refer to
VxRyMz format, where x and y can be a number from 0
“Printing CL Command Descriptions” in Chapter 1.
through 9, and z can be a number from 0 through 9 or a
letter from A through Z.
Optional Parameters
LICKEYFILE Example
Specifies the qualified name of the file where the soft-
DSPLICKEY PRDID(\ALL) LICTRM(\ALL)
ware license key information is written. If this file does
FEATURE(\ALL) SERIAL(\REMOTE)
not exist, it is created using the file QSYS/QALZAKEY OUTPUT(\LICKEYFILE) LICKEYFILE(KEYS)
as a template. If this file exists it must be in the format LICKEYMBR(REMOTE \REPLACE)
of QSYS/QALZAKEY.
The name of the license key file can be qualified by one This command shows the software license key information
of the following library values: for all of the products, features, and license terms for all of
the systems except this system. The output is put in the
*LIBL: All libraries in the job's library list are member REMOTE of the file KEYS. Any existing records are
searched until the first match is found. replaced.
(P) ────────────────────5%
55──DSPLIND──LIND(──line-description-name──)──┬────────────────────────┬──┬────────────────────────────┬───
│ ┌─\──────┐ │ │ ┌─\ALL───────┐ │
└─OUTPUT(──┴─\PRINT─┴──)─┘ └─OPTION(──┼─\BASIC─────┼──)─┘
├─\SWTNWILST─┤
├─\CTL───────┤
├─\SWTCTLLST─┤
├─\ACTSWTCTL─┤
├─\SSAP──────┤
├─\GRPADR────┤
├─\FCNADR────┤
├─\EORTBL────┤
├─\LGLCHLE───┤
├─\APPN──────┤
├─\PHYCHAR───┤
├─\THRESHOLD─┤
└─\TMRRTY────┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose *BASIC: The basic displays that apply to this line type
are shown, but additional information displays are not
The Display Line Description (DSPLIND) command displays shown.
a line description. Output is directed to a display or a
*SWTNWILST: The switched network interface list
spooled printer file as indicated by the OUTPUT parameter
panels that apply to this line are displayed.
and job type.
*CTL: The attached nonswitched controller list panels
Note: To see the parameter and value descriptions for this
for this line are displayed.
command, refer to the online help text. For more
information about printing the help text, refer to *SWTCTLLST: The switched controller list panels that
“Printing CL Command Descriptions” in Chapter 1. apply to this line are displayed.
*ACTSWTCTL: The active switched controller list
Required Parameters panels that apply to this line are displayed.
*SSAP: The source service access point panels for this
LIND
token-ring or Ethernet line are displayed.
Specifies the name of the line description to be dis-
played. *GRPADR: The group address panels for this Ethernet
line are displayed.
Optional Parameters *FCNADR: The functional address panels for this token-
ring are displayed.
OUTPUT
*EORTBL: The end-of-record table panels for this asyn-
Specifies whether the output from the command is
chronous line are displayed.
shown at the requesting workstation or printed with the
job's spooled output. More information on this param- *LGLCHLE: The logical channel entries for this X.25
eter is in Appendix A, “Expanded Parameter line are displayed.
Descriptions.” *APPN: The advanced peer-to-peer networking (APPN)
*: Output requested by an interactive job is shown on values for this line are displayed.
the display. Output requested by a batch job is printed *PHYCHAR: The information concerning the physical
with the job's spooled output. characteristics of an asynchronous line is displayed.
*PRINT: The output is printed with the job's spooled *THRESHOLD: The information concerning the
output. threshold values of an IDLC line is displayed.
OPTION *TMRRTY: The timer and retry values for this line are
Specifies the panels to be displayed. displayed.
*ALL: All panels that apply to this specific line type are
displayed. Example
DSPLIND LIND(LINE21)
This command displays information about the line description the command is entered from a batch job, the output from
named LINE21. The information is shown on the work the display is printed with the job's spooled output.
station display from which the command was submitted. If
(P) ──┬────────────────────────────────┬──────────────5
55──DSPLNK──┬─────────────────────────────────┬──┬────────────────────────┬───
│ (1) ───────────────┐
┌─\─── │ │ ┌─\──────┐ │ │ ┌─\ALL────────┐ │
└─OBJ(──┴─'object-path-name'─┴──)─┘ └─OUTPUT(──┴─\PRINT─┴──)─┘ (2) ─┼─\ALLDIR─────┼──)─┘
└─OBJTYPE(───
└─object-type─┘
5──┬───────────────────────────┬──┬───────────────────────┬────────────────────────────────────────────────────────────────────5%
│ ┌─\PRV──────┐ │ │ ┌─\PRV──┐ │
└─DETAIL(──┼─\NAME─────┼──)─┘ └─DSPOPT(──┼─\USER─┼──)─┘
├─\BASIC────┤ └─\ALL──┘
└─\EXTENDED─┘
Notes:
1 You can specify a pattern for this path name.
2 A list of the valid OS/400 object types for this command is in Appendix A.
*USER: The PC system and hidden objects are not including the directory (.) and the parent directory (..)
shown. Objects beginning with a period (.) are not dis- entries.
played unless the specified pattern begins with a period
(.).
*ALL: All objects are shown, including the PC system Example
and hidden objects. Objects beginning with a period (.)
DSPLNK OBJ('X/PAY')
are displayed (with asterisk (*) specified for the pattern)
This command displays the object PAY located in directory X
in the current directory.
55──DSPLOG──┬───────────────────┬──┬────────────────────────────────────────────────────────────────────────────────────┬───────5
│ ┌─QHST─┐ │ │ ┌─\AVAIL─────┐ ┌─\CURRENT───┐ │
(1) ─┴─start-time─┴──┼────────────┼──)──┬──────────────────────────────────┬─┘
└─LOG(──┴──────┴──)─┘ └─PERIOD(───
├─\BEGIN─────┤ │ ┌─\AVAIL───┐ ┌─\CURRENT─┐ │
└─start-date─┘ └─(──┴─end-time─┴──┼──────────┼──)─┘
├─\END─────┤
└─end-date─┘
(P) ──┬──────────────────────────────────────────┬───────5
5──┬───────────────────────────────────────────────────────────────────┬───
│ ┌─\NONE────────────────────────────────────────────────┐ │ │ ┌─\ALL──────────────────────┐ │
│ │ ┌──
───────────────────────────────────────────────┐ │ │ │ │ ┌──
────────────────────┐ │ │
6 (2)
└─JOB(──┴─────┬─────────────────────────────┬──job-name───┴────┴──)─┘ 6 (3)
└─MSGID(──┴───message-identifier─┴────┴──)─┘
└─┬─────────────┬──user-name/─┘
└─job-number/─┘
5──┬──────────────────────────┬────────────────────────────────────────────────────────────────────────────────────────────────5%
│ ┌─\────────┐ │
└─OUTPUT(──┼─\PRINT───┼──)─┘
└─\PRTWRAP─┘
Notes:
1 *PERIOD contains 2 lists of 2 elements each. *N must be specified for any element that precedes the value to be specified,
*CURRENT: The logged data for the current day and \NONE
between the specified starting and ending times (if speci- job-name
fied) is shown. user-name/job-name
job-number/user-name/job-name
*BEGIN: The logged data from the beginning of the log
is shown. More information on this parameter is in Appendix A,
“Expanded Parameter Descriptions.”
start-date: Specify the date convert. The date must be
entered in the format specified by the system values *NONE: No job name is used to indicate which mes-
QDATFMT and, if separators are used, QDATSEP. sages are shown.
Element 3: Ending Time job-name: Specify the names of up to five jobs that are
to have their logged messages shown.
One of the following is used to specify the ending time
before which, or at which, the data must have been user-name: Specify the names of the users of the jobs
logged. that are to have their messages displayed.
*AVAIL: The logged data that is available for the speci- job-number: Specify the numbers of the jobs that are to
fied ending date is shown. The time can be entered as have their logged messages displayed.
either 4 or 6 digits (hhmm or hhmmss) where hh = MSGID
hours, mm = minutes, and ss = seconds. If time separa- Specifies up to 100 message identifiers (if any) of the
tors are used to separate the time values, the character logged messages that are shown. These messages are
string must be enclosed in apostrophes ('hh:mm:ss'). If shown only if they were logged in the period of time
a time separator other than the one specified for the job specified in this command and in the jobs specified, if
is used, the command fails. job names were given in this command.
Note: The values specified for the ending date and *ALL: All logged messages, regardless of their identi-
time are ignored if the output is shown. That is, fiers, are shown if they meet the previous parameters'
all data in the log that was logged on or after the specifications.
specified starting date and time can be shown,
regardless of the ending date and time specified. message-identifier: Specify the identifiers of up to fifty
messages that are shown. (Refer to the description of
end-time: Specify the ending time for the specified the MSGID parameter in the Add Message Description
ending date that determines the logged data that is (ADDMSGD) command description for more information
printed. on message identifiers.)
Element 4: Ending Date To display specific generic types of messages, specify
One of the following is used to specify the ending date the 3-character code that identifies the message file fol-
before which or on which the data must have been lowed by all zeros. For example, CPF0000 specifies
logged. that all CPF messages that meet the specifications of
the previous parameters are shown. If an identifier is
*CURRENT: The current day is the last day for which
specified as pppnnðð, any message beginning with the
logged data is shown.
specified five characters (pppnn) can be shown.
*END: The last day on which data was logged is
shown. If PERIOD(*END) is specified, a time value OUTPUT
other than *AVAIL for end-time is ignored. Specifies whether the output from the command is
shown at the requesting display station or printed with
end-date: Specify the ending date for which logged data the job's spooled output. More information on this
is to be printed. The date must be entered in the format parameter is in Appendix A, “Expanded Parameter
specified by the system values QDATFMT and, if sepa- Descriptions.”
rators are used, QDATSEP.
*: Output requested by an interactive job is shown on
Note: If no output is received after you run the the display. Output requested by a batch job is printed
DSPLOG command with *PRINT specified, the with the job's spooled output.
dates of some message data may be out of
sequence. To print the data in this case, specify: *PRINT: The output is printed with the job's spooled
output. Only one line will be printed for each message
PERIOD((\AVAIL \BEGIN)(\AVAIL \END)).
and only the first 105 characters of the first level
JOB message text will be printed.
Specifies the names of the jobs (if any) whose mes- *PRTWRAP: The output is printed with the job's
sages in the system log are shown. If a job name is not spooled output. If the message does not fit on one line,
qualified, all jobs by that name in the log will have their additional lines are printed to accomodate up to 2000
messages displayed. characters of the first level message text.
A job identifier is a special value or a qualified name
with up to three elements. For example:
(P) ─┬────────────────────────┬─────────────────────────────────────────────────────5%
55──DSPMFSINF──OBJ(──'object-path-name-'──)────
│ ┌─\──────┐ │
└─OUTPUT(──┴─\PRINT─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
Required Parameter *PRINT: The output is printed with the job's spooled
output.
OBJ
Specifies the path name of an object that is within the
mounted file system whose statistics are to be displayed.
Examples
Any object in the mounted file system can be specified.
Example 1: Displaying Statistics of a Mounted File
For example, it can be a directory (*DIR) or a stream file
System
(*STMF).
DSPMFSINF OBJ('/jsmith/file1')
This command can also be issued using the following
alternative command name: This command displays the statistics for the mounted file
system that contains /jsmith/file1.
STATFS
For more information about Network File System com- Example 2: Displaying '/QSYS.LIB' File System Statistics
mands, see OS/400 Network File System Support DSPMFSINF OBJ('/QSYS.LIB/MYLIB.LIB/MYFILE.FILE')
SC41-5714.
This command displays the statistics for the /QSYS.LIB file
system that contains *FILE object MYFILE in library MYLIB.
┌─\LIBL/────────┐
(P) ─┬────────────────────────┬─────────────────────────────────────────────5%
55──DSPMNUA──MENU(──┼───────────────┼──menu-name──)────
├─\CURLIB/──────┤ │ ┌─\──────┐ │
└─library-name/─┘ └─OUTPUT(──┴─\PRINT─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
┌─\LIBL/────────┐
55──DSPMOD──MODULE(──┼───────────────┼──module-name──)──┬────────────────────────────────┬──────────────────────────────────────5
├─\CURLIB/──────┤ │ ┌─\ALL───────────┐ │
└─library-name/─┘ └─DETAIL(──┴─┬─\BASIC─────┬─┴──)─┘
├─\SIZE──────┤
├─\EXPORT────┤
├─\IMPORT────┤
├─\PROCLIST──┤
├─\REFSYSOBJ─┤
└─\COPYRIGHT─┘
5──┬──────────────────────────────┬─── (P) ──┬────────────────────────────────────────────────────────┬──────────────────────────────5
│ ┌─\────────┐ │ │ ┌─\LIBL/────────┐ │
(1, 2) ─┼──────────┼──)─┘
└─OUTPUT(───── └─OUTFILE(──┼───────────────┼────database-file-name────)─┘
├─\PRINT───┤ ├─\CURLIB/──────┤
└─\OUTFILE─┘ └─library-name/─┘
5──┬───────────────────────────────────────────┬───────────────────────────────────────────────────────────────────────────────5%
│ ┌─\FIRST──────┐ ┌─\REPLACE─┐ │
└─OUTMBR(──┴─member-name─┴──┴─\ADD─────┴──)─┘
Notes:
1 If OUTPUT(*OUTFILE) is specified, a file name must be specified for the OUTFILE parameter.
2 If OUTPUT(*OUTFILE) is specified, a detail other than *ALL must be specified on the DETAIL parameter and only one
Required Parameters *SIZE: The size and size limits for this module are
shown.
MODULE
*EXPORT: The symbols and type defined in this
Specifies the qualified name of the module for which
module that are exported to other modules are shown.
information is displayed.
*IMPORT: The symbols and type defined externally to
The name of the module can be qualified by one of the
this module are shown.
following library values:
*PROCLIST: A list of the procedure names with their
*LIBL: All libraries in the job's library list are type is shown.
searched until the first match is found.
*REFSYSOBJ: A list of the system objects referred to
*CURLIB: The current library for the job is by this module when the module is bound into a bound
searched. If no library is specified as the current program or service program is shown.
library for the job, the QGPL library is used.
*COPYRIGHT: Copyright information for this module is
library-name: Specify the name of the library to be shown.
searched.
(P) ────────────────────────────────────────────────────5%
55──DSPMODD──MODD(──mode-description-name──)──┬────────────────────────┬───
│ ┌─\──────┐ │
└─OUTPUT(──┴─\PRINT─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose OUTPUT
Specifies whether the output from the command is
The Display Mode Description (DSPMODD) command dis- shown at the requesting workstation or printed with the
plays a mode description for advanced-program-to-program job's spooled output. More information on this param-
communications (APPC) devices. Output is directed to a eter is in Appendix A, “Expanded Parameter
display or a spooled printer file as indicated on the OUTPUT Descriptions.”
parameter and job type.
*: Output requested by an interactive job is shown on
Note: To see the parameter and value descriptions for this the display. Output requested by a batch job is printed
command, refer to the online help text. For more with the job's spooled output.
information about printing the help text, refer to
*PRINT: The output is printed with the job's spooled
“Printing CL Command Descriptions” in Chapter 1.
output.
55──DSPMODSRC──────────────────────────────────────────────────────────────────────────────────────────────────────────────────5%
Purpose Example
The Display Module Source (DSPMODSRC) command DSPMODSRC
allows the user to show the source debug displays for
debugging bound programs. This command shows the source debug displays for pro-
grams that are to be debugged.
There are no parameters for this command.
(P) ────────────────────────────────5%
55──DSPMODSTS──DEV(──device-name──)──┬─────────────────────────┬──┬────────────────────────┬───
│ ┌─\ALL──────┐ │ │ ┌─\──────┐ │
└─MODE(──┼─BLANK─────┼──)─┘ └─OUTPUT(──┴─\PRINT─┴──)─┘
└─mode-name─┘
Note:
P All parameters preceding this point can be specified in positional form.
MODE This command shows the status of the mode CICS2 used by
Specifies the name of the mode whose status is being the device MINN2. If the command is entered from a batch
shown. job, the output from the display is printed with the job's
spooled output.
*ALL: All the modes used by the specified device are
shown.
(P) ──┬────────────────────────┬──┬───────────────────────┬───5
55──DSPMSG──┬─────────────────────────────────────────────────────┬───
│ ┌─\WRKUSR───────────────────────────────┐ │ │ ┌─\ALL──┐ │ │ ┌─\LAST──┐ │
└─MSGQ(──┼─\SYSOPR───────────────────────────────┼──)─┘ └─MSGTYPE(──┼─\INFO─┼──)─┘ └─START(──┴─\FIRST─┴──)─┘
├─\USRPRF───────────────────────────────┤ ├─\INQ──┤
├─\WRKSTN───────────────────────────────┤ └─\COPY─┘
│ ┌─\LIBL/────────┐ │
└─┼───────────────┼──message-queue-name─┘
├─\CURLIB/──────┤
└─library-name/─┘
5──┬────────────────────────────┬──┬──────────────────────────┬──┬───────────────────────────┬─────────────────────────────────5%
│ ┌─ðð────────────┐ │ │ ┌─\────────┐ │ │ ┌─\PRV──────┐ │
└─SEV(──┼─\MSGQ─────────┼──)─┘ └─OUTPUT(──┼─\PRINT───┼──)─┘ └─ASTLVL(──┼─\USRPRF───┼──)─┘
└─severity-code─┘ └─\PRTWRAP─┘ ├─\BASIC────┤
└─\INTERMED─┘
Note:
P All parameters preceding this point can be specified in positional form.
(P) ─────5
55──DSPMSGD──┬─────────────────────────────────────────────────┬──┬────────────────────────────────────────────────────┬───
│ ┌─\FIRST──────┐ ┌─\ONLY───────┐ │ │ ┌─\LIBL/────────┐ ┌─QCPFMSG───────────┐ │
└─RANGE(──┬─┴─lower-value─┴──┼─────────────┼─┬──)─┘ └─MSGF(──┼───────────────┼──┴─message-file-name─┴──)─┘
│ ├─\LAST───────┤ │ ├─\CURLIB/──────┤
│ └─upper-value─┘ │ ├─\USRLIBL/─────┤
└─\ALL─────────────────────────────┘ └─library-name/─┘
5──┬────────────────────────┬──┬──────────────────────┬──┬────────────────────────┬────────────────────────────────────────────5%
│ ┌─\FULL──┐ │ │ ┌─\YES─┐ │ │ ┌─\──────┐ │
└─DETAIL(──┴─\BASIC─┴──)─┘ └─FMTTXT(──┴─\NO──┴──)─┘ └─OUTPUT(──┴─\PRINT─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
The first of the two values in the RANGE parameter library-name: Specify the name of the library to be
specifies the message identifier of the first message searched.
description to show or print. QCPFMSG: Message descriptions are taken from the
*FIRST: The first message in the file specified by the system message file, QCPFMSG.
MSGF parameter is the first one whose description is message-file-name: Specify the name of the message
shown or printed. file to use.
lower-value: Specify the 7-character identifier of the first
message description to show or print.
┌─\LIBL/────────┐
(P) ────────────────────────────────────────────5%
55──DSPM36──M36(──┼───────────────┼──machine-name──)──┬────────────────────────┬───
├─\CURLIB/──────┤ │ ┌─\──────┐ │
└─library-name/─┘ └─OUTPUT(──┴─\PRINT─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
┌─\LIBL/────────┐
(P) ────────────────────────────────5%
55──DSPM36CFG──M36CFG(──┼───────────────┼──configuration-name──)──┬────────────────────────┬───
├─\CURLIB/──────┤ │ ┌─\──────┐ │
└─library-name/─┘ └─OUTPUT(──┴─\PRINT─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
55──DSPNCK──┬─────────────────────────────────────┬──┬─────────────────────┬──┬──────────────────────────────────┬──────────────5
│ ┌─\ALL─────┐ ┌─\PRV─────┐ │ │ ┌─\ALL──┐ │ │ ┌─\ALL──────────────┐ │
└─NCK(──┴─nickname─┴──┼─\ALL─────┼──)─┘ └─TYPE(──┼─\USER─┼──)─┘ └─OWNER(──┼─\CURRENT──────────┼──)─┘
├─\PRIVATE─┤ └─\LIST─┘ └─user-profile-name─┘
└─\PUBLIC──┘
(P) ──┬──────────────────────────────────────────────────────┬────────────────────────────────────5
5──┬──────────────────────────┬───
│ ┌─\────────┐ │ │ ┌─\LIBL/────────┐ │
└─OUTPUT(──┼─\PRINT───┼──)─┘ (1) ─┼───────────────┼──database-file-name──)─┘
└─OUTFILE(───
└─\OUTFILE─┘ ├─\CURLIB/──────┤
└─library-name/─┘
5──┬───────────────────────────────────────────┬───────────────────────────────────────────────────────────────────────────────5%
│ ┌─\FIRST──────┐ ┌─\REPLACE─┐ │
└─OUTMBR(──┴─member-name─┴──┼──────────┼──)─┘
└─\ADD─────┘
Notes:
1 This parameter is required when OUTPUT(*OUTFILE) is specified.
(P) ─────────────────────────────────────────────────────────────────────────────────────5%
55──DSPNETA──┬────────────────────────┬───
│ ┌─\──────┐ │
└─OUTPUT(──┴─\PRINT─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
Example
Optional Parameters
DSPNETA OUTPUT(\)
OUTPUT
Specifies whether the output of the command is dis- If the job is interactive, this command displays the network
played at the requesting work station or printed with the attributes of the system at the work station. If the job is
job's spooled output. More information on this param- batch, the network attributes are printed with the job's
spooled output.
┌─\LIBL/────────┐
(P) ─┬────────────────────────┬────────────────────────────────────────5%
55──DSPNODGRP──NODGRP(──┼───────────────┼──node-group──)────
├─\CURLIB/──────┤ │ ┌─\──────┐ │
├─\USRLIBL/─────┤ └─OUTPUT(──┴─\PRINT─┴──)─┘
└─library-name/─┘
Note:
P All parameters preceding this point can be specified in positional form.
*LIBL: All libraries in the job's library list are DSPNODGRP NODGRP(LIB1/GROUP1)
searched until the first match is found.
This command displays the systems in the node group called
*CURLIB: The current library for the job is GROUP1 and the partitioning scheme associated with the
searched. If no library is specified as the current node group. The information is shown at the workstation.
library for the job, the QGPL library is used.
Example 2: Printing a Node Group
*USRLIBL: Only the libraries in the user portion of
the job's library list are searched. DSPNODGRP NODGRP(LIB1/GROUP2) OUTPUT(\PRINT)
library-name: Specify the name of the library to be This command creates a spooled file that contains a list of
searched. the systems in the node group called GROUP1 and the
node-group: Specify the name of the node group to be associated partitioning scheme.
displayed.
(P) ─────────────────────────────────────────────5%
55──DSPNTBD──NTBD(────NetBIOS-description-name────)──┬────────────────────────┬───
│ ┌─\──────┐ │
└─OUTPUT(──┴─\PRINT─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
(P) ──┬────────────────────────────┬───────────────5%
55──DSPNWID──NWID(────network-interface-name────)──┬────────────────────────┬───
└─OUTPUT(──┬─\──────┬──)─┘ │ ┌─\ALL───────┐ │
└─\PRINT─┘ └─OPTION(──┼─\BASIC─────┼──)─┘
├─\CHLENTRY──┤
├─\DLCI──────┤
├─\NETDIF────┤
├─\PCLENTRY──┤
├─\TMRRTY────┤
└─\THRESHOLD─┘
Note:
P All parameters preceding this point can be specified in positional form.
Note: To see the parameter and value descriptions for this *CHLENTRY: The channel entry list panels associated
command, refer to the online help text. For more with the network interface description are displayed.
information about printing the help text, refer to This value is valid only when an integrated services
“Printing CL Command Descriptions” in Chapter 1. digital network (ISDN) is used.
*DLCI: The data link connection identifier information,
including the DLCI numbers, status, and active or
Required Parameters attached lines is displayed. This value is valid only
NWID when a frame relay network (FR) is used.
Specifies the name of the network interface description *NETDIF: The values of the network difference parame-
to be displayed. ters in the network interface description are displayed.
This value is valid only when ISDN is used.
Optional Parameters *PCLENTRY: The protocol-specific information,
including the protocol entries for the network interface
OUTPUT
description, is displayed. This value is valid only when
Specifies whether the output from the command is
ISDN is used.
shown at the requesting workstation or printed with the
job's spooled output. More information on this param- *TMRRTY: The timer and retry values for this network
eter is in Appendix A, “Expanded Parameter interface are displayed.
Descriptions.” *THRESHOLD: The values specified on the threshold
*: Output requested by an interactive job is shown on parameters in the network interface description are dis-
the display. Output requested by a batch job is printed played. This value is valid only when ISDN is used.
with the job's spooled output.
*PRINT: The output is printed with the job's spooled Example
output. DSPNWID NWID(ISDNNET)
OPTION
This command displays information about the network inter-
Specifies the panels to be displayed.
face description named ISDNNET. The information is shown
*ALL: All panels that apply to this specific network inter- an the work station display from which the command was
face are displayed. submitted. If the command is entered from a batch job, the
output from the display is printed with the job's spooled
output.
(P) ─┬─────────────────────────┬──┬─────────────────────────┬──┬────────────────────────┬──5%
55──DSPNWSALS──ALIAS(──alias-name──)────
│ ┌─\PERM─┐ │ └─SERVER(──server-name──)─┘ │ ┌─\──────┐ │
└─DURATION(──┴─\TEMP─┴──)─┘ └─OUTPUT(──┴─\PRINT─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
(P) ──┬────────────────────────┬─────────────────────────────────────────────────────5%
55──DSPNWSA──┬────────────────────────────┬───
│ ┌─\ALL───────┐ │ │ ┌─\──────┐ │
└─OPTION(──┼─\AIX───────┼──)─┘ └─OUTPUT(──┴─\PRINT─┴──)─┘
├─\BASE──────┤
├─\LANSERVER─┤
├─\NETWARE───┤
| └─\WINDOWSNT─┘
Note:
P All parameters preceding this point can be specified in positional form.
(P) ──┬─────────────────────────┬─────────5%
55──DSPNWSD──NWSD(────network-server-description-name────)──┬────────────────────────┬───
│ ┌─\──────┐ │ │ ┌─\ALL────┐ │
└─OUTPUT(──┴─\PRINT─┴──)─┘ └─OPTION(──┼─\BASIC──┼──)─┘
├─\PORTS──┤
├─\STGLNK─┤
└─\TCPIP──┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose OPTION
Specifies what information you want displayed. You can
The Display Network Server Description (DSPNWSD) choose to display all information (*ALL) or specific infor-
command displays a network server description object. mation.
Note: To see the parameter and value descriptions for this *ALL: All information concerning the network server is
command, refer to the online help text. For more shown.
information about printing the help text, refer to
*BASIC: Only basic characteristics of the network
“Printing CL Command Descriptions” in Chapter 1.
server are shown.
*PORTS: Only the information concerning attached
Required Parameters communication descriptions is shown.
NWSD *STGLNK: Only the information concerning linked client
Specifies the name of the network server description to storage spaces is shown.
be displayed.
*TCPIP: Only the information concerning TCP/IP config-
uration is shown.
Optional Parameters
OUTPUT Example
Specifies whether the output from the command is DSPNWSD NWSD(SERVER1)
shown at the requesting workstation or printed with the
job's spooled output. More information on this param- This command displays information about the network server
eter is in Appendix A, “Expanded Parameter description named SERVER1. Since no option was speci-
Descriptions.” fied, all information is displayed. The information is shown at
the work station display from which the command was
*: Output requested by an interactive job is shown on
entered. If the command was submitted from a batch job,
the display. Output requested by a batch job is printed
the output from the command is printed with the job's
with the job's spooled output.
spooled output.
*PRINT: The output is printed with the job's spooled
output.
(P) ─┬────────────────────────┬───────────────────────────────5%
55──DSPNWSSSN──SESSION(──session-name──)──SERVER(──server-name──)────
│ ┌─\──────┐ │
└─OUTPUT(──┴─\PRINT─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose SERVER
Specifies the name of a specific, active server.
The Display Network Server Session (DSPNWSSSN)
command displays status data for a specific active network
server session. The session name, user ID, guest sign-on, Optional Parameter
session time, and idle time are displayed when this OUTPUT
command is issued. Specifies whether the output from the command is
shown at the requesting workstation or printed with the
This command is only valid for a server type of
job's spooled output. More information on this param-
*LANSERVER.
eter is in Appendix A, “Expanded Parameter
Output is directed to a display or a spooled printer file as Descriptions.”
indicated on the OUTPUT parameter and by the job type. *: Output requested by an interactive job is shown on
Note: To see the parameter and value descriptions for this the display. Output requested by a batch job is printed
command, refer to the online help text. For more with the job's spooled output.
information about printing the help text, refer to *PRINT: The output is printed with the job's spooled
“Printing CL Command Descriptions” in Chapter 1. output.
(P) ─┬────────────────────────┬──────────────────────────────────────────────────────────5%
55──DSPNWSSTC──SERVER(──server-name──)────
│ ┌─\──────┐ │
└─OUTPUT(──┴─\PRINT─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
Files and communications devices that have been *: Output requested by an interactive job is shown on
accessed the display. Output requested by a batch job is printed
with the job's spooled output.
Spooled print jobs
*PRINT: The output is printed with the job's spooled
Times buffers exhausted output.
(P) ─┬────────────────────────┬─────────────────────────────────────────5%
55──DSPNWSSTG──NWSSTG(──network-server-storage-space──)────
│ ┌─\──────┐ │
└─OUTPUT(──┴─\PRINT─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose NWSSTG
Specifies the name of the network server storage space
The Display Network Server Storage Space (DSPNWSSTG) to be displayed.
command can be used to display a network server storage
space. Output is directed to a display or to a spooled printer
file as indicated on the OUTPUT parameter and by the job Optional Parameter
type. Information displayed includes the format of the OUTPUT
storage space: (*HPFS, *FAT, *NETWARE, *AIX, and Specifies whether the output is shown on the display of
*NTFS), its size, the percentage used, the drive at which it is the requesting workstation or is printed with the job's
linked to an NWSD (network server description), whether the spooled output.
format operation is complete and the text entered at create
time. *: Output requested by an interactive job is shown on
the display. Output requested by a batch job is printed
Note: To see the parameter and value descriptions for this with the job's spooled output.
command, refer to the online help text. For more
information about printing the help text, refer to *PRINT: The output is printed with the job's spooled
“Printing CL Command Descriptions” in Chapter 1. output.
(P) ──┬────────────────────────┬─────────────────5%
55──DSPNWSUSR──┬─────────────────────────────┬──┬─────────────────────────────┬───
│ (1) ─────┐
┌─\ALL─── │ │ ┌─\NWSUSRA───┐ │ │ ┌─\──────┐ │
└─SERVER(──┴─server-name─┴──)─┘ └─SVRTYPE(──┼─\NWSA──────┼──)─┘ └─OUTPUT(──┴─\PRINT─┴──)─┘
├─\LANSERVER─┤
└─\NETWARE───┘
Notes:
1 This value is not valid when SVRTYPE(*NETWARE) is specified.
(P) ─────────────────5
55──DSPNWSUSRA──┬─────────────────────────────┬──┬─────────────────────────┬──┬────────────────────────────┬───
│ ┌─\CURRENT────┐ │ │ ┌─\USER──┐ │ │ ┌─\ALL───────┐ │
└─USRPRF(──┴─'user-name'─┴──)─┘ └─PRFTYPE(──┴─\GROUP─┴──)─┘ └─OPTION(──┼─\AIX───────┼──)─┘
├─\BASE──────┤
├─\LANSERVER─┤
├─\NETWARE───┤
└─\WINDOWSNT─┘
5──┬────────────────────────┬──────────────────────────────────────────────────────────────────────────────────────────────────5%
│ ┌─\──────┐ │
└─OUTPUT(──┴─\PRINT─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose *AIX: The displays that apply to the *AIX server type
are shown, but additional information displays are not
The Display Network Server User Attributes shown.
(DSPNWSUSRA) command displays the network server user
*BASE: The displays that apply to the *BASE server
attributes for a user or group profile.
type are shown, but additional information displays are
Output is directed to a display or a spooled printer file as not shown.
indicated by the OUTPUT parameter and job type. *LANSERVER: The displays that apply to the
Note: To see the parameter and value descriptions for this *LANSERVER server type are shown, but additional
command, refer to the online help text. For more information displays are not shown.
information about printing the help text, refer to *NETWARE: The displays that apply to the *NETWARE
“Printing CL Command Descriptions” in Chapter 1. server type are shown, but additional information dis-
plays are not shown.
Optional Parameters | *WINDOWSNT: The displays that apply to the
| *WINDOWSNT server type are shown, but additional
USRPRF | information displays are not shown.
Specifies the name of a user or group profile.
OUTPUT
*CURRENT: The user profile attributes for the current
Specifies whether the output from the command is
user profile are displayed.
shown at the requesting workstation or printed with the
user-name: Specify the name of a user or group profile job's spooled output. More information on this param-
to be displayed. eter is in Appendix A, “Expanded Parameter
Descriptions.”
PRFTYPE
Specifies whether the information to be displayed is for a *: Output requested by an interactive job is shown on
user profile or for a group profile. the display. Output requested by a batch job is printed
with the job's spooled output.
*USER: The information to be displayed is for a user
profile. *PRINT: The output is printed with the job's spooled
output.
*GROUP: The information to be displayed is for a group
profile.
Example
OPTION
Specifies the displays to be shown. DSPNWSUSRA USRPRF(NWSUSR1)
*ALL: All displays that apply to all server types are If the job is interactive, this command displays the network
shown. server user attributes defined for user NWSUSR1 at the
workstation. If the job is batch, the network server user attri-
butes for user NWSUSR1 is printed with the job's spooled
output.
┌─\LIBL/────────┐
(1) ─object-type──)──┬──────────────────────────┬───
55──DSPOBJAUT──OBJ(──┼───────────────┼──object-name──)──OBJTYPE(─── (P) ─────────────5
├─\CURLIB/──────┤ │ ┌─\────────┐ │
└─library-name/─┘ └─OUTPUT(──┼─\PRINT───┼──)─┘
└─\OUTFILE─┘
5──┬────────────────────────────────────────────────────┬──┬───────────────────────────────────────────┬────────────────────────5
│ ┌─\LIBL/────────┐ │ │ ┌─\FIRST──────┐ ┌─\REPLACE─┐ │
└─OUTFILE(──┼───────────────┼──database-file-name──)─┘ └─OUTMBR(──┴─member-name─┴──┼──────────┼──)─┘
├─\CURLIB/──────┤ └─\ADD─────┘
└─library-name/─┘
5──┬──────────────────────────┬────────────────────────────────────────────────────────────────────────────────────────────────5%
│ ┌─\OBJECT─┐ │
└─AUTTYPE(──┼─\FIELD──┼──)─┘
└─\ALL────┘
Notes:
1 A list of the valid OS/400 object types for this command is in Appendix A.
Element 1: Member to Receive Output This command shows the authorized users and their authori-
*FIRST: The first member in the file receives the output. ties for the object named PROG1 to the user who entered
If OUTMBR(*FIRST) is specified and the member does the command, if that user has object management authority
not exist, the system creates a member with the name of for the object. If the user does not have object management
the file specified on the OUTFILE parameter. authority, only personal authorities are shown. PROG1 is a
program (*PGM) located in the library named ARLIB. The
member-name: Specify the file member that receives system assumes * for the device that shows the output list.
the output. If OUTMBR(member-name) is specified and If the command was entered in the batch subsystem, the
the member does not exist, the system creates it. output is placed in the default output queue for the job. If the
Element 2: Operation to Perform on Member command was entered in the interactive subsystem, the
output is shown on the device where the user entered the
*REPLACE: The system clears the existing member
command.
and adds the new records.
*ADD: The system adds the new records to the end of Example 2: Printing List of Users
the existing records. DSPOBJAUT OBJ(ARLIB/PROG2) OBJTYPE(\PGM)
OUTPUT(\PRINT)
AUTTYPE This command causes the list of authorized users of the
Specifies whether object level authority, field level program named PROG2 in the ARLIB library to be printed. If
authority, or both object level and field level authority are the user who enters the command does not have object
displayed. Field level authority information only applies management authority for the program, only that user's name
to *FILE objects. and authorities are printed.
┌─\LIBL/────────┐
55──DSPOBJD──OBJ(──┬─┼───────────────┼──┬─\ALL─────────────────┬─┬──)──OBJTYPE(──┬─\ALL─────────────────┬──)────────────────────5
│ ├─\CURLIB/──────┤ ├─generic\-object-name─┤ │ │ ┌──
─────────────┐ │
│ ├─\USRLIBL/─────┤ └─object-name──────────┘ │ └──6─object-type─┴─────
(3, 4) ─┘
│ ├─\ALLUSR/──────┤ │
│ ├─\ALL/─────────┤ │
│ └─library-name/─┘ │
├─\ALLUSR───(1) ──────────────────────────────────┤
(2) ─────────────────────────────────────┘
└─\IBM───
(P) ──┬──────────────────────────┬──┬────────────────────────────────────────────────────┬────────5
5──┬──────────────────────────┬───
│ ┌─\BASIC───┐ │ │ ┌─\────────┐ │ │ ┌─\LIBL/────────┐ │
└─DETAIL(──┼─\FULL────┼──)─┘ └─OUTPUT(──┼─\PRINT───┼──)─┘ └─OUTFILE(──┼───────────────┼──database-file-name──)─┘
└─\SERVICE─┘ └─\OUTFILE─┘ ├─\CURLIB/──────┤
└─library-name/─┘
5──┬───────────────────────────────────────────┬───────────────────────────────────────────────────────────────────────────────5%
│ ┌─\FIRST──────┐ ┌─\REPLACE─┐ │
└─OUTMBR(──┴─member-name─┴──┴─\ADD─────┴──)─┘
Notes:
1 OBJTYPE must be *LIB if OBJ(*ALLUSR) specified.
3 A maximum of 60 repetitions
4 A list of the valid OS/400 object types for this command is in Appendix A.
Purpose 2. The size of a library object does not include the sizes of
the objects in the library. The size of a library, including
The Display Object Description (DSPOBJD) command shows the sizes of the objects in the library, can be obtained
the names and attributes of specified objects in the specified using the DSPLIB command with OUTPUT(*PRINT) or
library or in the libraries of the job's library list. The the QLIRLIBD API.
command can also be used to show the names and attri-
butes of libraries themselves. Restriction: The user who submits this command must
have execute authority for the specified libraries, and some
Only the object attributes of each object are shown; the data authority (that is, any one of the authorities) for each of the
attributes of data in the object, and the actual data in the objects. If the user does not have execute authority for a
object, are not shown. Also indicated is whether an object library, none of its objects are shown.
being shown has been damaged (possibly by a system
Note: To see the parameter and value descriptions for this
failure).
command, refer to the online help text. For more
Any OS/400 system object for which the user has some information about printing the help text, refer to
authority can be shown by this command. Libraries for which “Printing CL Command Descriptions” in Chapter 1.
the user does not have execute authority cannot be shown,
even if specified in the command. If only one object is to be Required Parameters
shown, the user can specify it by entering the object name,
object type, and the name of the library where it is located. OBJ
Depending on the specified library qualifier, either the first Specifies which objects in the libraries are to have their
| object found in the specified libraries is shown, or all objects object attributes shown. If no library qualifier is speci-
| in the specified libraries for which the user has some fied, *LIBL is assumed, and all libraries in the job's
| authority are shown. library list are searched for the objects. Objects in the
library for which the user does not have some authority
Notes: are not shown.
1. For objects that are damaged or locked, the information The name of the object can be qualified by one of the
shown, printed, or written to the output file is incomplete. following library values:
An indication that the object is locked or damaged is
written to the output file. If the description of the object *LIBL: All libraries in the job's library list are
is shown or printed, the text for the damaged or locked searched until the first match is found.
object indicates either the damaged or locked status.
*CURLIB: The current library for the job is object-name: Specify the name of the object that is
searched. If no library is specified as the current shown.
library for the job, the QGPL library is used.
*USRLIBL: Only the libraries in the user portion of Single Value
the job's library list are searched.
*ALLUSR: All user libraries are shown. When the
*ALL: All libraries in the system, including QSYS, object name has a value of *ALLUSR, the object type
are searched. must be *LIB.
*ALLUSR: All user libraries are searched. All
libraries with names that do not begin with the letter *IBM: All system (IBM) libraries are shown. This is the
Q are searched except for the following: list of libraries saved/restored on the SAVLIB/RSTLIB CL
#CGULIB #DFULIB #RPGLIB #SEULIB commands with LIB(*IBM). When the object name has a
#COBLIB #DSULIB #SDALIB value of *IBM, the object type must be *LIB.
Note: All data is written to the file specified on the not exist, the system creates a member with the name of
OUTFILE parameter regardless of the value the file specified on the OUTFILE parameter.
specified on the DETAIL parameter.
member-name: Specify the file member that receives
OUTFILE the output. If OUTMBR(member-name) is specified and
Specifies the qualified name of the database file to the member does not exist, the system creates it.
which the output of the display is directed. If the Element 2: Operation to Perform on Member
OUTFILE does not exist, this command creates a data-
*REPLACE: The system clears the existing member
base file in the specified library. If the file is created, the
and adds the new records.
text is "output file for DSPOBJD". The public authority is
the same as the create authority specified for the library *ADD: The system adds the new records to the end of
in which the file is created. The database format the existing records.
(QLIDOBJD) of the output file is the same as that used
in the IBM-supplied file database QADSPOBJ.
Examples
The name of the database file can be qualified by one of
the following library values: Example 1: Displaying a Basic Description of Objects
*LIBL: All libraries in the job's library list are DSPOBJD OBJ(X/PAY) OBJTYPE(\ALL)
searched until the first match is found.
A basic description of all the objects (for which the user has
*CURLIB: The current library for the job is some authority) that are named PAY in library X are shown.
searched. If no library is specified as the current Objects in the library for which the user has no authority are
library for the job, the QGPL library is used. not shown.
library-name: Specify the name of the library to be
Example 2: Displaying a Full Description of a Program
searched.
DSPOBJD OBJ(X/PAY) OBJTYPE(\PGM) DETAIL(\FULL)
database-file-name: Specify the name of the database
file that receives the output of the display. A full description of the program named PAY in library X is
shown. The display includes all the attributes of the
OUTMBR program.
Specifies the name of the database file member to which
the output is directed. If a member already exists, the Example 3: Displaying Program Information
system uses the second element of this parameter to
DSPOBJD OBJ(\USRLIBL/PAY) OBJTYPE(\PGM)
determine whether the member is cleared before the
new records are added. If the member does not exist This command shows information about the first program
and a member name is not specified, the system creates named PAY that is found in the user portion of the job's
a member with the name of the output file specified on library list.
the OUTFILE parameter. If an output file member name
is specified, but the member does not exist, the system Example 4: Displaying a Basic Description of Files
creates it. DSPOBJD OBJ(Z/ABC\) OBJTYPE(\FILE)
Element 1: Member to Receive Output
A basic description of all of the files whose names begin with
*FIRST: The first member in the file receives the output. ABC (generic name) located in library Z, for which the user
If OUTMBR(*FIRST) is specified and the member does has some authority, are shown.
55──DSPOPCLNK──────────────────────────────────────────────────────────────────────────────────────────────────────────────────5%
Purpose Examples
DSPOPCLNK
The Display OptiConnect Link Status (DSPOPCLNK)
command allows you to view the connection status of the This command displays a panel showing the connection
links between systems in the fiber optic network. status of the links between systems in the fiber optic
network.
There are no parameters for this command.
(P) ────────────5
55──DSPOPT──VOL(──┬─\ALL───────────────────────┬──)──┬───────────────────────────────┬──┬───────────────────────┬───
(1) ────────────────┤
├─\MOUNTED─── │ (3) ────────┐
┌─\ALL─── │ │ ┌─\VOLATR─┐ │
├─volume-identifier──────────┤ (2) ─┴─optical-device─┴──)─┘ └─DATA(──┼─\DIRATR─┼──)─┘
└─DEV(───
└─generic\-volume-identifier─┘ ├─\FILATR─┤
└─\SAVRST─┘
5──┬───────────────────────────────┬──┬──────────────────────────┬──┬─────────────────────────────────────────────────┬─────────5
(5, 9) ─┬─\ALL────
└─PATH(───── (10) ────┬──)─┘ │ ┌─\────────┐ │ │ ┌─\LIBL/───┐ │
└─'path-name'─┘ (7) ─┼──────────┼────user-space-name────)─┘
└─OUTPUT(──┼─\PRINT───┼──)─┘ └─USRSPC(───
├─\OUTFILE─┤ ├─\CURLIB/─┤
└─\USRSPC──┘ └─library/─┘
5──┬───────────────────────────┬──┬─────────────────────────────────────────────────┬───────────────────────────────────────────5
│ ┌─\YES─┐ │ │ ┌─\LIBL/───┐ │
(7, 8) ─┴─\NO──┴──)─┘ └─OUTFILE(───
└─REPLACE(───── (6) ─┼──────────┼──database-file-name──)─┘
├─\CURLIB/─┤
└─library/─┘
5──┬──────────────────────────────────────────────────────────┬────────────────────────────────────────────────────────────────5%
│ ┌─\FIRST───────────────────┐ ┌─\REPLACE─┐ │
(6) ─┴─member-to-receive-output─┴──┼──────────┼──)─┘
└─OUTMBR(───
└─\ADD─────┘
Notes:
1 This value is valid only for optical devices, not for library devices.
2 This parameter is ignored if a specific volume identifier is specified on the VOL parameter.
8 This parameter is ignored if the user space is not found in the specified library.
library. If a default library is not specified, the file is DSPOPT VOL(\ALL) DEV(\ALL)
created in library QGPL.
This command displays the volume attributes for all volumes
OUTMBR in all local optical devices and libraries.
Specifies the name of the database file member to which
the output is directed. Example 2: Displaying Attributes Using a Generic
Search
Note: This parameter is valid only if
OUTPUT(*OUTFILE) is specified. DSPOPT VOL(PAY\) DATA(\DIRATR) PATH('/\')
Element 1: Member to Receive Output
This command displays the attributes for all directories in the
*FIRST: The first member in the file receives the output. root directory of all optical volumes beginning with the char-
If OUTMBR(*FIRST) is specified and the member does acters PAY.
not exist, the system creates a member with the name of
the file specified on the OUTFILE parameter. Example 3: Displaying Attributes of a Specific Directory
member-name: Specify the file member that receives
DSPOPT VOL(VOLð1) DEV(OPTð1) DATA(\FILATR)
the output. If OUTMBR(member-name) is specified and PATH('/DIR1/DIR2/\')
the member does not exist, the system creates it.
Element 2: Action on Member This command displays the file attributes for all files in the
directory /DIR1/DIR2 of optical volume VOL01.
*REPLACE: The data currently contained in the output
file member is replaced with the output of this command. Example 4: Displaying Save and Restore Data
*ADD: The new records are added to the existing infor-
DSPOPT VOL(\MOUNTED) DEV(OPTð1) DATA(\SAVRST)
mation in the specified database file member.
PATH('/\')
Examples This command displays the save and restore data for all files
in the root directory of the optical volume mounted on device
Example 1: Displaying Attributes for All Optical Volumes OPT01.
55──DSPOPTLCK──TYPE(──┬─\VOL──┬──)──┬──────────────────────────────┬───(P) ──┬─────────────────────────┬────────────────────────────5
├─\DIR──┤ (1) ─volume-identifier──)─┘
└─VOL(─── (2) ─'path-name'──)─┘
└─PATH(───
├─\FILE─┤
└─\JOB──┘
5──┬────────────────────────┬──────────────────────────────────────────────────────────────────────────────────────────────────5%
│ ┌─\──────┐ │
└─OUTPUT(──┴─\PRINT─┴──)─┘
Notes:
1 This parameter is valid only if TYPE(*VOL), TYPE(*DIR), or TYPE(*FILE) is specified.
Purpose VOL
Specifies the volume identifier of the optical volume for
The Display Optical Locks (DSPOPTLCK) command displays which the locks are listed.
a list of locks held on an optical volume, directory, or file. If
TYPE(*JOB) is specified, this command displays a list of all PATH
jobs currently performing an optical request. The information Specifies the path name of the directory or file on the
can be printed or displayed. volume for which the locks are listed.
Note: This parameter is valid only if TYPE(*DIR) or
This command does not identify any locks to volumes, direc- TYPE(*FILE) is specified.
tories, or files which are in remote optical servers. It also
does not identify any jobs which are currently using a remote OUTPUT
optical server. Use the Display Optical Server Specifies whether the output from the command is
(DSPOPTSVR) command with TYPE(*CONV) specified to shown at the requesting workstation or printed with the
determine if any jobs are currently using a remote optical job's spooled output. More information on this param-
server. eter is in Appendix A, “Expanded Parameter
Descriptions.”
Note: To see the parameter and value descriptions for this
command, refer to the online help text. For more *: Output requested by an interactive job is shown on
information about printing the help text, refer to the display. If the command is run as part of a batch
“Printing CL Command Descriptions” in Chapter 1. job, the output is printed with the job's spooled output.
*PRINT: The output is printed with the job's spooled
Required Parameter output.
TYPE
Specifies the type of locks to be displayed or printed. Examples
*VOL: Job information and locks on the specified optical Example 1: Displaying Locks on a File
volume are displayed or printed. DSPOPTLCK TYPE(\FILE) VOLUME(VOLðð1)
*DIR: Job information and locks on the specified optical PATH('/PAYROLL/JAN1995')
directory are displayed or printed.
This command displays the locks held on the file JAN1995 in
*FILE: Job information and locks on the specified the directory /PAYROLL on the VOL001 volume.
optical file are displayed or printed.
*JOB: Job information and locks on all jobs currently Example 2: Displaying Locks for Active Jobs
performing optical requests are displayed or printed. DSPOPTLCK TYPE(\JOB)
Optional Parameters This command diplays a list of active jobs performing optical
requests.
(P) ──────────────────────────────────────────────────────────5%
55──DSPOPTSVR──┬─────────────────────┬──┬────────────────────────┬───
│ ┌─\DEST─┐ │ │ ┌─\──────┐ │
└─TYPE(──┴─\CONV─┴──)─┘ └─OUTPUT(──┴─\PRINT─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
(P) ──┬──────────────────────┬──┬────────────────────────────────┬─────────────5
55──DSPOVR──┬────────────────────────────────────┬───
│ ┌─\ALL─────────────────┐ │ │ ┌─\YES─┐ │ │ ┌─\─────────────────┐ │
└─FILE(──┼─\PRTF────────────────┼──)─┘ └─MRGOVR(──┴─\NO──┴──)─┘ └─LVL(──┼─\JOB──────────────┼──)─┘
└─overridden-file-name─┘ └─call-level-number─┘
5──┬────────────────────────┬──┬───────────────────────────────────────┬───────────────────────────────────────────────────────5%
│ ┌─\──────┐ │ │ ┌─\─────────────────────┐ │
└─OUTPUT(──┴─\PRINT─┴──)─┘ └─ACTGRP(──┴─activation-group-name─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
(P) ──────────────────────────────────────────────────────────5%
55──DSPPDGPRF──USER(──┬─\CURRENT──┬──)──┬────────────────────────┬───
└─user-name─┘ │ ┌─\──────┐ │
└─OUTPUT(──┴─\PRINT─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
┌─\LIBL/────────┐
(P) ────────────────────────────────────5
55──DSPPFM──FILE(──┼───────────────┼──physical-file-name──)──┬──────────────────────────┬───
├─\CURLIB/──────┤ │ ┌─\FIRST──────┐ │
└─library-name/─┘ └─MBR(──┼─\LAST───────┼──)─┘
└─member-name─┘
5──┬────────────────────────────────┬──────────────────────────────────────────────────────────────────────────────────────────5%
│ ┌─1─────────────┐ │
└─FROMRCD(──┼─\END──────────┼──)─┘
├─\ALLDATA──────┤
└─record-number─┘
Note:
P All parameters preceding this point can be specified in positional form.
┌─\LIBL/────────┐
(P) ────────────5%
55──DSPPGM──PGM(──┼───────────────┼──program-name──)──┬────────────────────────┬──┬────────────────────────────┬───
├─\CURLIB/──────┤ │ ┌─\──────┐ │ │ ┌─\ALL───────┐ │
└─library-name/─┘ └─OUTPUT(──┴─\PRINT─┴──)─┘ └─DETAIL(──┼─\BASIC─────┼──)─┘
├─\SIZE──────┤
├─\MODULE────┤
├─\SRVPGM────┤
├─\ACTGRPEXP─┤
├─\ACTGRPIMP─┤
└─\COPYRIGHT─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose OUTPUT
Specifies whether the output from the command is
The Display Program (DSPPGM) command displays informa- shown at the requesting workstation or printed with the
tion about a program. The display includes information about job's spooled output. More information on this param-
the compiler, the type of program, certain processing attri- eter is in Appendix A, “Expanded Parameter
butes of the program, the type of program (ILE or OPM), the Descriptions.”
size of the program, and the number of parameters that can
*: Output requested by an interactive job is shown on
be passed to the program when it is called.
the display. Output requested by a batch job is printed
Restrictions: with the job's spooled output.
1. You must have *READ authority to the program and *PRINT: The output is printed with the job's spooled
*EXECUTE authority to the library to use this command. output.
description to see the source file, library, and member program model (OPM) program results in the
names. *BASIC information being shown.
*SRVPGM: A list is shown of the service programs
bound by this program.
Examples
*ACTGRPEXP: A list is shown of the data items
exported to the activation group specified in the data Example 1: Displaying Program Information
export entry in the binding specifications.
DSPPGM PGM(LIBð1/PAYROLL)
*ACTGRPIMP: A list is shown of the imports that are
resolved by weak exports that had been exported to the This command displays information about the program
activation group directory. named PAYROLL in library LIB01. The display is shown at
the display station if requested by an interactive job, or
*COPYRIGHT: A list is shown of the copyrights for this
printed if requested by a batch job.
service program.
Note: The DETAIL values *SIZE, *MODULE, Example 2: Printing Program Information
*SRVPGM, and *COPYRIGHT are valid only for DSPPGM PGM(CUSINQ) OUTPUT(\PRINT)
integrated language environment (ILE) programs.
Specifying one of these values for an original This command displays information about a program named
CUSINQ. The library list is used to find the program, and the
information is printed.
┌─\ALL─────────────┐
│ ┌──
───────────┐ │
55──DSPPGMADP──USRPRF(──user-profile-name──)──── 6┬─\PGM────┬┴────
(P) ─OBJTYPE(──┴── (1) ┴──)──┬──────────────────────────┬────────────────5
├─\SQLPKG─┤ │ ┌─\────────┐ │
└─\SRVPGM─┘ └─OUTPUT(──┼─\PRINT───┼──)─┘
└─\OUTFILE─┘
5──┬────────────────────────────────────────────────────┬──┬───────────────────────────────────────────┬───────────────────────5%
│ ┌─\LIBL/────────┐ │ │ ┌─\FIRST──────┐ ┌─\REPLACE─┐ │
└─OUTFILE(──┼───────────────┼──database-file-name──)─┘ └─OUTMBR(──┴─member-name─┴──┼──────────┼──)─┘
├─\CURLIB/──────┤ └─\ADD─────┘
└─library-name/─┘
Notes:
P All parameters preceding this point can be specified in positional form.
1 A maximum of 3 repetitions.
Optional Parameters *LIBL: All libraries in the job's library list are
searched until the first match is found.
OBJTYPE
*CURLIB: The current library for the job is
Specifies the type of object shown.
searched. If no library is specified as the current
*ALL: All objects that adopt the user profile specified on library for the job, the QGPL library is used.
the USRPRF parameter are shown.
library-name: Specify the name of the library to be
*PGM: Only programs that adopt the specified user searched.
profile are shown.
database-file-name: Specify the name of the database
*SQLPKG: Only Structured Query Language (SQL) file.
packages that adopt the specified user profile are
shown. OUTMBR
Specifies the name of the database file member to which
the output is directed.
Element 1: Member to Receive Output *REPLACE: The system clears the existing member
and adds the new records.
*FIRST: The first member in the file receives the output.
If OUTMBR(*FIRST) is specified and the member does *ADD: The system adds the new records to the end of
not exist, the system creates a member with the name of the existing records.
the file specified on the OUTFILE parameter. If the
member exists, the user has the option of either adding
records to the end of the existing member or clearing the
Example
existing member and adding the new records. DSPPGMADP USRPRF(xxx) OUTPUT(\PRINT)
member-name: Specify the file member that receives This command directs the information about the user profile
the output. If OUTMBR(member-name) is specified and (xxx) that programs use to print the job's output spooling
the member does not exist, the system creates it. queue.
Element 2: Operation to Perform on Member
┌─\LIBL/────────┐
(P) ──OBJTYPE(─────────────────5
55──DSPPGMREF──PGM(──┼───────────────┼──┬─\ALL──────────────────┬──)──┬──────────────────────────┬───
├─\USRLIBL/─────┤ ├─generic\-program-name─┤ │ ┌─\────────┐ │
├─\CURLIB/──────┤ └─program-name──────────┘ └─OUTPUT(──┼─\PRINT───┼──)─┘
├─\ALL/─────────┤ └─\OUTFILE─┘
├─\ALLUSR/──────┤
└─library-name/─┘
┌─\PGM───────────────┐
│ ┌──
─────────────┐ │
5──┴──6─┬─\ALL────┬─┴───
(1) ─┴──)──┬──────────────────────────────────────────────────────┬──────────────────────────────────────────5
├─\SQLPKG─┤ │ ┌─\LIBL/────────┐ │
├─\SRVPGM─┤ (2) ─)─┘
└─OUTFILE(──┼───────────────┼──database-file-name───
└─\MODULE─┘ ├─\CURLIB/──────┤
└─library-name/─┘
5──┬─────────────────────────────────────────────┬─────────────────────────────────────────────────────────────────────────────5%
│ ┌─\FIRST──────┐ ┌─\REPLACE─┐ │
(3) ─┴─member-name─┴──┼──────────┼──)─┘
└─OUTMBR(───
└─\ADD─────┘
Notes:
P All parameters preceding this point can be specified in positional form.
1 A maximum of 4 repetitions
CSP *FILE, *PGM, *MSGF, *CSPMAP, and The object type of the referenced object
*CSPTBL
For files, the record contains the following additional fields:
PASCAL No information is provided for programs in
The name of the file in the program (possibly different
Pascal
from the system object name if an override was in effect
PL/I *FILE and *PGM when the program was created)
RPG *FILE, *DTAARA, *PGM The program use of the file (1=input, 2=output,
RPGLE *FILE, *PGM, *DTAARA, and *SRVPGM 4=update, 8=unspecified, or a number representing a
combination of any of these four; for example, a code of
This information can be shown, printed, or written to (stored 11 is a combination of 1, 2, and 8, which is input, output,
in) a database output file (an OUTFILE). and unspecified)
The number of record formats referenced, if any
If the information is shown or printed, a list (by library) of the
specified user-authorized programs, along with the objects The name of the record format used by the file and its
record format level identifier
The number of fields referenced for each format | QDSNX QPFRDATA QUSRBRM QUSRSYS
| QGPL QRCL QUSRIJS QUSRVxRxMx
Note: The referenced object names and libraries listed may
| QGPL38 QS36F QUSRINFSKR
be different than the actual names of the objects, | QMQMDATA QUSER38 QUSRNOTES
since this information is stored when the program is | QMQMPROC QUSRADSM QUSRRDARS
created. If the object has been moved since the
program was created, or an override was in effect Note: A different library name, of the form
during creation, the names listed may differ from the QUSRVxRxMx, can be created by the user
actual names. for each release that IBM supports. VxRxMx
is the version, release, and modification level
Restrictions: of the library.
1. The user must have object operational authority for the library-name: Specify the name of the library to be
program. searched.
2. Also, of the libraries specified by the library qualifier, *ALL: All programs in the specified library (or all the
only the libraries for which the user has read authority libraries identified in the library qualifier to which the user
are searched for the programs. has access) have their information shown.
Note: To see the parameter and value descriptions for this generic*-program-name: Specify the name of the
command, refer to the online help text. For more program or the generic name of several programs in the
information about printing the help text, refer to specified library (or all libraries identified in the library
“Printing CL Command Descriptions” in Chapter 1. qualifier) that has information shown. A generic name is
a character string of one or more characters followed by
an asterisk (*); for example, ABC*. The asterisk substi-
Required Parameters
tutes for any valid characters. A generic name specifies
PGM all objects with names that begin with the generic prefix
Specifies the qualified name of the program (or all pro- for which the user has authority. If an asterisk is not
grams) that has a list of the files and other related included with the generic (prefix) name, the system
system objects that are referenced by the program. A assumes it to be the complete object name. If the com-
specific program name or a generic program name is plete object name is specified, and multiple libraries are
specified; either type can be optionally qualified by a searched, multiple objects can be displayed only if *ALL
library name. Only the libraries in the specified library or *ALLUSR library values can be specified for the
qualifier that the user either owns or is authorized to use name. For more information on the use of generic
are searched for the program(s). names, refer to “Generic Object Names” in Chapter 2.
The name of the program can be qualified by one of the program-name: Specify the name of the program to
following library values: have information shown.
*ALL: All libraries in the system, including QSYS, *: Output requested by an interactive job is shown on
are searched. the display. Output requested by a batch job is printed
with the job's spooled output.
*ALLUSR: All user libraries are searched. All
libraries with names that do not begin with the letter *PRINT: The output is printed with the job's spooled
Q are searched except for the following: output.
#CGULIB #DFULIB #RPGLIB #SEULIB *OUTFILE: The output is directed to the database file
#COBLIB #DSULIB #SDALIB specified on the OUTFILE parameter.
Although the following Qxxx libraries are provided OBJTYPE
by IBM, they typically contain user data that Specifies the object type for which information is dis-
changes frequently. Therefore, these libraries are played.
considered user libraries and are also searched:
*PGM: Only program information is displayed.
*ALL: Program information and SQL package informa-
tion are displayed.
*SQLPKG: Only SQL package information is displayed.
*SRVPGM: Service program information is displayed. member-name: Specify the file member that receives
the output. If OUTMBR(member-name) is specified and
*MODULE: Module information is displayed.
the member does not exist, the system creates it.
OUTFILE
Element 2: Operation to Perform on Member
Specifies the qualified name of the database output file
in which the program-related information is written. *REPLACE: The system clears the existing member
and adds the new records.
When creating the database output file, the current date,
time, and system name must be included. The system *ADD: The system adds the new records to the end of
name is the name of the source system, not the target the existing records.
system. If the specified file does not exist, the system
creates a database output file and member. If the file is Examples
created, the description text is 'Outfile for DSPPGMREF'
and the public authority is *EXCLUDE. Example 1: Storing a List of Programs
Note: The format of the output file must be the same DSPPGMREF PGM(LIBRARY1/\ALL) OUTPUT(\OUTFILE)
as QWHDRPPR of the system file QADSPPGM. OUTFILE(LIB2/FILE2)
More information on the OUTFILE format is in
the DB2 for AS/400 Database Programming This command creates a list of all authorized programs found
book. in LIBRARY1, and of the files and other system objects that
the programs reference. It stores the list in a database file
The name of the database file can be qualified by one of named FILE2 in LIB2.
the following library values:
Example 2: Printing a List of Objects
*LIBL: All libraries in the job's library list are
searched until the first match is found. DSPPGMREF PGM(LIBRARY1/BILLING) OUTPUT(\PRINT)
*CURLIB: The current library for the job is This command creates a list of system objects that are refer-
searched. If no library is specified as the current enced by the BILLING program in LIBRARY1. The output is
library for the job, the QGPL library is used. spooled for printing.
library-name: Specify the name of the library to be
searched.
Additional Considerations
database-file-name: Specify the name of the database
output file in which the program-related information is When the DSPPGMREF command is entered, the library is
placed. If the specified file is not found, a file by that searched for the program or programs specified on the PGM
name is created and stored in the specified library, or in parameter; then a group of records that give system object-
*CURLIB if not qualified. This file can be used again related information about each program is created. The
when other DSPPGMREF commands are entered. The records are placed in the printer device file named
IBM-supplied database file QADSPPGM cannot be spec- QPDSPPGM. If OUTPUT(*PRINT) is specified on the
ified. command, the records are listed on the printer in the fol-
lowing order:
OUTMBR
Header information: Lists the DSPPGMREF command
Specifies the name of the database file member to which
input values.
the output is directed.
Program-related information: Lists, for each program
Element 1: Member to Receive Output
identified by the PGM parameter, all of the system
*FIRST: The first member in the file receives the output. objects (including files) that are referenced by the
If OUTMBR(*FIRST) is specified and the member does program. If more than one program is identified, the
not exist, the system creates a member with the name of beginning of the next one follows the end of the previous
the file specified on the OUTFILE parameter. If the one.
member exists, the user has the option to add records to
the end of the existing member or to clear the existing If the DSPPGMREF command is entered interactively and
member and add the new records. OUTPUT(*) is specified or assumed, the records in the
printer device file are shown instead of being printed.
┌──
─────────────────────────────────────────────────────────────────┐
55──DSPPGMVAR──PGMVAR(───6─(──┬─\CHAR──────────────┬──┬────────────────────────────┬────
(1) ─)─┴───
(2) ──)───────────────────────────────5
└─'program-variable'─┘ │ ┌──
──────────────────┐ │
6
└─(────'basing-pointer'─┴──)─┘
(P) ──┬───────────────────────────────┬──┬───────────────────────┬────────────────────────5
5──┬──────────────────────────────────┬───
│ ┌─1─────────────────┐ │ │ ┌─\DCL─────────────┐ │ │ ┌─\CHAR─┐ │
└─START(──┴─starting-position─┴──)─┘ └─LEN(──┴─displayed-length─┴──)─┘ └─OUTFMT(──┴─\HEX──┴──)─┘
5──┬────────────────────────┬──┬───────────────────────────┬──┬────────────────────────────────────────┬───────────────────────5%
│ ┌─\──────┐ │ │ ┌─\DFTPGM──────┐ │ │ ┌─\LAST──────────────────┐ │
└─OUTPUT(──┴─\PRINT─┴──)─┘ └─PGM(──┴─program-name─┴──)─┘ └─RCRLVL(──┴─recursion-level-number─┴──)─┘
Notes:
1 A maximum of 5 repetitions
2 A maximum of 10 repetitions
characters are used. An integer, MI ODV number, or a *HEX: Program variables are shown in both character
numeric variable name can be specified for a subscript. format and hexadecimal format.
For more information on the basing pointer value, refer
OUTPUT
to Appendix C, “Parameter Values Used for Testing and
Specifies whether the output from the command is
Debugging.”
shown at the requesting display station or printed with
Some examples are: the job's spooled output. More information on this
PGMVAR(('VAR1(B,5)' 'PTR2(C,P2)')) parameter is in Appendix A, “Expanded Parameter
PGMVAR((VAR2 (BASEPTRA BASEPTRB))) Descriptions.”
*: Output requested by an interactive job is shown on
the display. Output requested by a batch job is printed
Optional Parameters with the job's spooled output.
START *PRINT: The output is printed with the job's spooled
Specifies, for string variables only, the starting position in output.
the string from which its value is being displayed. If
PGM
more than one string variable is specified in the
Specifies the name of the program that contains the
PGMVAR parameter, the same starting position value is
program variables shown.
used for each one. For a bit string, the value specifies
the starting bit position; for a character string, the value *DFTPGM: The program currently specified as the
specifies the starting character position. default program has its variables shown.
1: The variable is shown from the first position through program-name: Specify the name of the program whose
the length specified on the LEN parameter. program variables are shown.
starting-position: Specify the first position in the string RCRLVL
being displayed. The START value specified must not Specifies which recursion level of the program contains
be larger than the maximum string length for any vari- the variables being shown. Recursion level 1 is the first
able specified, except that START(1) is allowed if the (or earliest) call of the program, recursion level 2 is the
maximum length for a string is zero. The LEN value, second call of the program, and so on to the last (most
plus the START position minus one, must not be greater recent) recursion level in the stack. For example, if
than the maximum string length. These checks are program A calls program B, and then program B calls
made for each string variable specified in the PGMVAR program A, a new recursion level of program A is
parameter. formed. Some high-level languages also allow recursive
procedures. For these programs, refer to the appro-
LEN
priate high-level language manual for more information.
Specifies, for string variables only, the length of the
string shown when the breakpoint is reached, starting at *LAST: The last (most recent) call of the program con-
the position specified by the START parameter. If more tains the pointer being shown.
than one string variable is specified in the PGMVAR recursion-level-number: Specify the number of the
parameter, the same value is used for each one. For a recursion level of the program containing the pointer
bit string, the value specifies the number of bits shown; being shown.
for a character string, the value specifies the number of
characters shown.
*DCL: The string variable is shown to the end of the
Examples
string or for a value of 200 bytes, whichever is less. If Example 1: Displaying Program Variables
the string variable has a maximum length of zero, only
LEN(*DCL) is allowed. DSPPGMVAR PGMVAR('&QUANT') PGM(MYPROG)
displayed-length: Specify the length of the data shown. Assuming that the program MYPROG is in debug mode, this
The length (as well as the combination of START and command shows the name and current value of the CL vari-
LEN) must be no greater than the length of the shortest able called &QUANT; its type and length are also shown.
string specified in the PGMVAR parameter.
Example 2: Displaying Program Variables
OUTFMT
DSPPGMVAR PGMVAR(TOTSALES MANHRS)
Specifies the format in which the objects are shown.
PGM(REGION) RCRLVL(1)
*CHAR: The program variables are shown in character
form. This command shows the program variables TOTSALES and
MANHRS of the first call of the program REGION.
(P) ──┬────────────────────────────────────────┬────────────────────────────────5
55──DSPPRB──┬───────────────────────────────────┬───
│ ┌─\ALL───────────────┐ │ │ ┌─\ALL───────────────────┐ │
└─PRBID(──┴─problem-identifier─┴──)─┘ │ │ ┌──
─────────────────┐ │ │
6 (1) ─┴──)─┘
└─STATUS(──┴───┬─\OPENED─────┬─┴───
├─\READY──────┤
├─\PREPARED───┤
├─\SENT───────┤
├─\ANSWERED───┤
├─\VERIFIED───┤
├─\CLOSED─────┤
└─status-type─┘
5──┬────────────────────────────────────┬───────────────────────────────────────────────────────────────────────────────────────5
│ ┌─\ALL──────────────────┐ │
│ │ ┌──
────────────────┐ │ │
6 (2)
└─SEV(──┴───severity-level─┴────┴──)─┘
5──┬──────────────────────────────────────────────────────────────────────────────────┬─────────────────────────────────────────5
│ ┌─\AVAIL─────┐ ┌─\BEGIN─────┐ │
└─PERIOD(──┴─start-time─┴──┼────────────┼──)──┬──────────────────────────────────┬─┘
├─\CURRENT───┤ │ ┌─\AVAIL───┐ ┌─\END─────┐ │
└─start-date─┘ └─(──┴─end-time─┴──┼──────────┼──)─┘
├─\CURRENT─┤
└─end-date─┘
5──┬──────────────────────────────────────────────────────────────────────┬──┬─────────────────────────────────┬────────────────5
│ ┌─\ALL──────┐ │ │ ┌─\ALL──────────┐ │
└─HARDWARE(──┴─type-code─┴──┬─────────────────────────────────────┬──)─┘ └─RESOURCE(──┴─resource-name─┴──)─┘
│ ┌─\ALL─────────┐ ┌─\ALL──────────┐ │
└─┴─model-number─┴──┼───────────────┼─┘
└─serial-number─┘
5──┬───────────────────────────────────────────────────────────────────────────────────────┬────────────────────────────────────5
│ ┌─\ALL──────────────────┐ │
└─LICPGM(──┴─licensed-program-name─┴──┬────────────────────────────────────────────┬──)─┘
│ ┌─\ALL──────────┐ ┌─\ALL────────────────┐ │
└─┴─release-level─┴──┼─────────────────────┼─┘
└─modification-number─┘
5──┬────────────────────────────────────────────────┬──┬────────────────────────────────────┬───────────────────────────────────5
│ ┌─\ALL─────────────────────────┐ │ │ ┌─\ALL──────────────────┐ │
└─FUNCTION(──┼─generic\-function-identifier─┼──)─┘ └─PGM(──┼─generic\-program-name─┼──)─┘
└─function-identifier──────────┘ └─program-name──────────┘
5──┬────────────────────────────────────────────┬──┬────────────────────────────────────────────────────────────┬───────────────5
│ ┌─\ALL────────────────────────┐ │ │ ┌─\ALL───────────────┐ ┌─\ALL───────────────┐ │
└─MSGID(──┼─generic\-message-identifier─┼──)─┘ └─ORIGIN(──┼─\NETATR────────────┼──┼────────────────────┼──)─┘
└─message-identifier──────────┘ └─network-identifier─┘ ├─\NETATR────────────┤
└─control-point-name─┘
5──┬──────────────────────────────────────────┬──┬────────────────────────────┬──┬───────────────────────────┬──────────────────5
│ ┌─\ALL──────────────────────┐ │ │ ┌─\ALL──────┐ │ │ ┌─\ALL───────┐ │
└─SRVID(──┴─service-identifier-number─┴──)─┘ └─ASNUSER(──┴─user-name─┴──)─┘ └─GROUP(──┴─group-name─┴──)─┘
5──┬───────────────────────┬──┬───────────────────────────┬──┬──────────────────────────────┬───────────────────────────────────5
│ ┌─\ALL─┐ │ │ ┌─\ALL──────┐ │ │ ┌─\────────────┐ │
└─PRBTYPE(──┼─1────┼──)─┘ └─PRBCGY(──┼─\REPORT───┼──)─┘ └─OUTPUT(──┼─\PRINT───────┼──)─┘
├─2────┤ ├─\CRITICAL─┤ (3, 4) ┘
└─\OUTFILE─────
├─3────┤ └─\LOGONLY──┘
├─4────┤
├─5────┤
└─6────┘
5──┬──────────────────────────────────────────────────────────┬──┬─────────────────────────────────────────────┬────────────────5
│ ┌─\LIBL/────────┐ │ │ ┌─\FIRST──────┐ ┌─\REPLACE─┐ │
(3, 4, 5) ─┼───────────────┼──database-file-name──)─┘ └─OUTMBR(───
└─OUTFILE(─────── (3) ─┴─member-name─┴──┼──────────┼──)─┘
├─\CURLIB/──────┤ └─\ADD─────┘
└─library-name/─┘
5──┬─────────────────────────┬─────────────────────────────────────────────────────────────────────────────────────────────────5%
│ ┌─\BASIC──┐ │
(5) ─┼─\CAUSE──┼──)─┘
└─TYPE(───
├─\FIX────┤
├─\USRTXT─┤
└─\SPTDTA─┘
Notes:
P All parameters preceding this point can be specified in positional form.
1 A maximum of 6 repetitions
2 A maximum of 3 repetitions
3 The OUTFILE and OUTMBR parameters are valid only when OUTPUT(*OUTFILE) is specified.
4 If OUTPUT(*OUTFILE) is specified, a database file name is required for the OUTFILE parameter.
5 The TYPE parameter is valid only when a value is specified for the OUTFILE parameter.
Purpose SEV
Specifies the severity level of the problem log entries
The Display Problem (DSPPRB) command shows or print being shown on the display. The severity level is
service information related to performing hardware and soft- assigned by the user when the problem is prepared for
ware maintenance. The service information, contained in the reporting. The four severity levels are:
problem log entries, are shown on the DSPPRB display,
printed with the job's output, or stored in a database file. 1 High
2 Medium
3 Low
Optional Parameters 4 None
PRBID *ALL: Problem log entries with any severity level are
Specifies the problem identifier of the problem being shown.
selected. Problems with different system origins can
severity-level: Specify at least one or as many as three
have the same identifier. This parameter can be used
of the four severity levels.
with the ORIGIN parameter to select a single problem
from a particular system origin. PERIOD
*ALL: All problem identifiers are selected. Specifies the period of time for which the data log is
printed. The following values can be coded in this
problem-identifier: Specify the 10-character problem parameter, which contains two sets of two values each
identifier of the problem being selected. (four list elements).
STATUS Element 1: Starting Time
Specifies the status of the problem log entries. The
*AVAIL: The error data that is available for the speci-
seven status types are as follows:
fied starting or ending date is printed.
*OPENED The problem is in OPENED status. The start-time: Specify the starting time of the specified
problem has been identified and a starting date for which the error data is printed. The
problem record has been created. time is specified in 24-hour format with or without a time
*READY The problem is in READY status. separator as follows:
Problem analysis information has been
With a time separator, specify a string of 5 or 8
added to the problem record.
digits, where the time separator for the job sepa-
*PREPARED The problem is in PREPARED status. rates the hours, minutes, and seconds. If you issue
The problem has been prepared for this command from the command line, the string
reporting. must be enclosed in apostrophes. If a time sepa-
*SENT The problem is in SENT status. The rator other than the separator specified for your job
problem has been sent to a service pro- is used, this command fails.
vider, but no answer has been returned. Without a time separator, specify a string of 4 or 6
*ANSWERED The problem is in ANSWERED status. digits (hhmm or hhmmss) where hh = hours, mm =
An answer was returned by the service minutes, and ss = seconds. Valid values for hh
provider or added by an operator on this range from 00 through 23. Valid values for mm and
system. ss range from 00 through 59.
*CLOSED The problem is closed. Note: If PERIOD(*BEGIN) is specified, then any time
value other than *AVAIL for start-time is ignored.
*ALL: Problem log entries with any status are shown.
*CURRENT: The logged data for the current day, and
status-type: Specify up to six status types that identify the time that has elapsed between the specified starting
the problem log entries being displayed. time and ending time for the day, is displayed.
start-date: Specify the date shown. The date must be resource-name: Specify the name of the resource for
entered in the format specified by the system values which logged entries are being displayed.
QDATFMT and, if separators are used, QDATSEP.
LICPGM
Element 3: Ending Time Specifies the name of the failing licensed program for
*AVAIL: The logged data that is available for the speci- which problem log entries are shown.
fied ending date is displayed. Element 1: Licensed Program
end-time: Specify the time that the data logging ends. *ALL: All licensed programs are shown regardless of
See the description of start-time for details about how whether any are identified as failing.
time can be specified.
Note: If *ALL is specified, any value other than *ALL for
Element 4: Ending Date release and modification is ignored.
*END: The last day on which data was logged is licensed-program-name: Specify the name of the failing
shown. If PERIOD(*END) is specified, a time value licensed program.
other than *AVAIL for end-time is ignored.
Element 2: Release Level of the Licensed Program
*CURRENT: The logged data for the current day, and
*ALL: All entries identifying failing licensed programs
the time that has elapsed between the specified starting
are shown.
time and ending time for the day, is displayed.
end-date: Specify the date that the data logging ends. release-level: Specify the release level of the failing
licensed program.
The date must be entered in the format specified by the
system values QDATFMT and, if separators are used, Element 3: Modification Number of the Release
QDATSEP.
*ALL: All entries identifying a failing licensed program
HARDWARE of the specified licensed program and release are
Specifies the name of the problem log entries identifying shown.
the failing device. modification-number: Specify the modification number of
Note: If *ALL is specified, then any value other than the release of the failing licensed program.
*ALL for model and serial number is ignored.
FUNCTION
Element 1: Machine Type Specifies the name of the function identifier for which the
problem log entries are shown.
*ALL: Entries are shown regardless of which device, if
any, is identified as failing. *ALL: Entries are shown regardless of which function
identifier, if any, is identified.
type-code: Specify the 4-character type code of the
device. generic*-function-identifier: Specify the generic name of
the function identifier. A generic name is a character
Element 2: Model Number
string of one or more characters followed by an asterisk
*ALL: All entries identifying the specified type of failing (*); for example, ABC*. The asterisk substitutes for any
device are shown. valid characters. A generic name specifies all objects
model-number: Specify the 3-character model number with names that begin with the generic prefix for which
of the device. the user has authority. If an asterisk is not included with
the generic (prefix) name, the system assumes it to be
Element 3: Serial Number
the complete object name. If the complete object name
*ALL: All entries identifying the specified type and is specified, and multiple libraries are searched, multiple
model of the failing device are shown. objects can be displayed only if *ALL or *ALLUSR library
values can be specified for the name. For more infor-
serial-number: Specify the serial number of the device
mation on the use of generic names, refer to “Generic
in one of the following formats where n is a decimal digit
Object Names” in Chapter 2.
(0-9).
function-identifier: Specify the complete function identi-
nnnnn
fier of the function. If blank characters are included, the
nnnnnnn
character string must be enclosed in apostrophes.
nn-nnnnn
nn-nnnnnnn PGM
Specifies that only problem log entries identifying the
RESOURCE
failing program are shown. For machine-detected prob-
Specifies the name of the failing resource, or all failing
lems, the failing program is identified by the possible
resources, for which problem log entries are shown.
cause with the highest probability of failure.
*ALL: Entries are shown regardless of which resource
*ALL: Entries are shown regardless of which program,
name, if any, is identified by the problem.
if any, is identified.
control-point-name: Specify the name of the control More information on this parameter is in Appendix A,
point. Only entries originating on systems with this “Expanded Parameter Descriptions.”
control point name are shown. *: Output requested by an interactive job is shown on
the display. Output requested by a batch job is printed
SRVID
with the job's spooled output.
Specifies that only problem log entries using the IBM
service-assigned number are shown. This number is *PRINT: The output is printed with the job's spooled
assigned when the problem is reported to IBM service output.
support.
*OUTFILE: The output is directed to the database file
*ALL: Entries are shown regardless of which service specified on the OUTFILE parameter.
number, if any, is assigned to the problem.
OUTFILE
service-identifier-number: Specify the service identifier Specifies the qualified name of the database file that
number. receives the output of the command. If the file does not
exist, this command creates a database file in the speci-
ASNUSER
fied library. If a file is created, the text reads "Outfile for
Specifies which problem log entries are displayed.
DSPPRB," and the authority for users other than those
*ALL: All problem log entries are shown, regardless of who have specific authority, group authority, or authority
the user name assigned to them. from an authorization list is *EXCLUDE. Refer to the
user-name: Specify the user name assigned to the
problem log entries to be displayed.
tables at the end of the TYPE parameter description for *FIX: Fixes to the problem are program temporary fix
the format used. (PTF) records.
Note: The format must be the same as that of the *USRTXT: User-supplied text, consisting of note
TYPE parameter. records, is placed in the output file.
The name of the database file can be qualified by one of *SPTDTA: Output files with supporting data identifiers
the following library values: are created.
*LIBL: All libraries in the job's library list are Basic Problem Data (*BASIC)
searched until the first match is found. The output file produced for type *BASIC has one record
*CURLIB: The current library for the job is for each problem in the problem log. Each record has a
searched. If no library is specified as the current unique problem identifier.
library for the job, the QGPL library is used. The record format is QASXPBOF. See the following
library-name: Specify the name of the library to be "DSPPRB Fields for Basic Problem Data
searched. (TYPE(*BASIC))" table for the fields in the record.
database-file-name: Specify the name of the database Table 11 (Page 1 of 3). DSPPRB Fields for Basic Problem
file to which the output of the command is written. Data (TYPE(*BASIC))
OUTMBR Field Name Length Description
Specifies the name of the database file member to which PBRCEN 1 Century that the data was
the output is directed. retrieved and placed in the output
file:
Element 1: Member to Receive Output
0 20th century
*FIRST: The first member in the file receives the output. 1 21st century
If OUTMBR(*FIRST) is specified and the member does
PBRDAT 6 Date that the data was retrieved
not exist, the system creates a member with the name of
and placed in the output file.
the file specified on the OUTFILE parameter. If the
member exists, records may be either added to the end PBRTIM 6 Time that the data was retrieved
of the member or replace existing records. and placed in the output file.
PBSYSN 8 Name of the system in which the
member-name: Specify the file member that receives
DSPPRB command is run to
the output. If OUTMBR(member-name) is specified and create this output file.
the member does not exist, the system creates it.
PBFORM 8 Record format, which is always
Element 2: Operation to Perform on Member *BASIC.
*REPLACE: The system clears the existing member PBID 10 Problem identifier.
and adds the new records. PBORG 20 System origin.
*ADD: The system adds the new records to the end of PBORGI 1 Problem origin indication:
the existing records.
L Local
TYPE R Remote
Specifies the type of problem information that is placed PBSEV 1 Problem severity levels:
in the output file. Only one type of data can be placed 1 High
in each file. More information on each value of this 2 Medium
parameter, including a table on the output record format 3 Low
for the value, is located at the end of this parameter 4 None
description. PBTYPE 1 Problem type (which identifies how
Note: This parameter is valid only when a value is the problem was detected):
specified also on the OUTFILE parameter. 1 Machine-detected
2 User-perceived
*BASIC: Basic problem data includes problem type and
3 PTF order
status; device type, model, and serial number; product
ID, contact information; and tracking data. PBSTAT 1 Problem status:
O Opened
*CAUSE: Possible problem causes include point-of-
R Ready
failure, partial, isolation, or answer cause records. P Prepared
Answer causes are used if they are available. If they S Sent
are not, isolation causes are used. If isolation causes A Answered
are not available, partial causes are used. If partial V Verified
causes are not available, then the point-of-failure causes C Closed
are used.
Table 11 (Page 2 of 3). DSPPRB Fields for Basic Problem Table 11 (Page 2 of 3). DSPPRB Fields for Basic Problem
Data (TYPE(*BASIC)) Data (TYPE(*BASIC))
Field Name Length Description Field Name Length Description
PBDESC 7 Message identifier of a message in PBFTEL2 30 Alternate fax telephone number.
the QCPFMSG message file that The number service support per-
describes the problem. sonnel should use to contact the
user's company if the primary tele-
PBPMSG 7 Message identifier of a message in
phone number is not available.
the QCPFMSG message file that
describes the reference code. PBENTR 36 Company name.
PBRFCD 4 Original reference code. PBSTR1 36 First line of street address.
PBSLID 8 Identifies the entry recorded in the PBSTR2 36 Second line of street address.
error log when the system
PBSTR3 36 Third line of street address.
detected a problem.
PBCITY 36 City and state.
PBMACH 4 Identifies the type of device with
which this problem is associated. PBCOUN 20 Country.
PBMODL 3 Identifies the model of the device PBZIP 12 ZIP code.
with which this problem is associ-
PBSNUM 10 Service assigned number.
ated.
PBEPDP 8 Identifies the program used to run
PBFEAT 4 Identifies the feature number of the
problem analysis.
device with which this problem is
associated. PBPDPE 2 Identifies the code the system
returned after problem analysis is
PBMSER 10 Identifies the serial number of the
run.
device with which this problem is
associated. PBISOS 1 Identifies the result of running
problem analysis:
PBEC 12 Identifies the engineering change
(EC) level of the device with which 1 Problem analysis was suc-
this problem is associated. cessful, the problem still
exists.
PBLPP 7 Shows the identification number of 2 Problem analysis was suc-
the program with the problem. cessful, the problem has
This number could be for a been resolved.
licensed program or for licensed 3 Problem analysis was not
internal code. successful.
PBVER 4 Identifies the version of the 4 Problem analysis was not
program with the problem. completed.
5 Problem analysis was par-
PBREL 2 Identifies the release level of the
tially completed.
program with the problem.
PBDATO 6 Date the problem was opened.
PBMDF 2 Identifies the modification level that
applies to the release level of the PBTIMO 6 Time the problem was opened.
licensed program with the problem. PBUSRO 10 User who opened the problem.
PBCNT 36 The name of the person whom PBDATA 6 Date the problem was analyzed.
service personnel should contact
to help resolve this problem. PBTIMA 6 Time the problem was analyzed.
PBTEL1 30 Primary telephone number. The PBUSRA 10 User who analyzed the problem.
number service support personnel PBDATP 6 Date the problem was prepared.
should use to contact the user's
company. PBTIMP 6 Time the problem was prepared.
PBTEL2 30 Alternate telephone number. The PBUSRP 10 User who prepared the problem.
number service support personnel PBDATS 6 Date the service request was sent.
should use to contact the user's
company if the primary telephone PBTIMS 6 Time the service request was sent.
number is not available. PBUSRS 10 User who sent the service request.
PBFTEL1 30 Primary fax telephone number. PBDATN 6 Date the service request was
The number service support per- answered.
sonnel should use to contact the
user's company. PBTIMN 6 Time the service request was
answered.
PBUSRN 10 User who answered the problem.
Table 11 (Page 3 of 3). DSPPRB Fields for Basic Problem Table 12 (Page 1 of 2). DSPPRB Fields for Possible Cause
Data (TYPE(*BASIC)) Data (TYPE(*CAUSE))
Field Name Length Description Field Name Length Description
PBDATF 6 Date fix was verified. CARCEN 1 Century that the data was
retrieved and placed in the output
PBTIMF 6 Time fix was verified.
file:
PBUSRF 10 User who verified the fix.
0 20th century
PBDATC 6 Date the problem was closed. 1 21st century
PBTIMC 6 Time the problem was closed. CARDAT 6 Date that the data was retrieved
and placed in the output file.
PBUSRC 10 User who closed the problem.
CARTIM 6 Time that the data was retrieved
PBSYMP 256 Symptom string.
and placed in the output file.
PBUSRD 10 User assigned to the problem.
CASYSN 8 Name of the system where the
PBFTRN 10 Filter assigned to the problem. DSPPRB command was run to
create this output file.
PBFTRL 10 Filter library.
CAFORM 8 Format, which is always *CAUSE.
PBFTRG 10 Group in filter assigned to the
problem. CAID 10 Problem identifier.
PBALIB 10 Library containing APAR data CAORG 20 System origin.
saved for the problem.
CALIST 1 Cause list type:
Note:
P The possible cause list was
1. All fields are of type C (character). identified when the failure
2. All dates are represented in YYMMDD format where: occurred.
L The possible cause list was
YY Year identified by problem analysis
MM Month which was not completed.
DD Day I The possible cause list was
For example 940515 represents May 15, 1994. identified by problem anal-
ysis.
3. All times are for a 24-hour clock and are represented in
A The possible cause list was
HHMMSS format where:
returned by RETAIN as result
HH Hour of a service request.
MM Minutes
CACODE 4 Cause code.
SS Seconds
CANAME 7 A message identifier of a message
For example 144526 represents 26 seconds past 2:45 p.m.
in QCPFMSG that describes a
4. The contact name, telephone numbers, company name, possible cause.
and address are only present if different than the service
contact information. CADOC 7 Message identifier of a message in
QCPFMSG that identifies the doc-
5. For those activities that can be done more than once, the ument being referenced when
date and time represent the last time the activity was done. solving this problem.
CADEVL 40 Location of the rack or system unit
Possible Causes (*CAUSE) when the device is installed.
The output file produced for type *CAUSE has one CAPRT1 12 Part 1, a part which describes a
record for each possible cause identified at the time the possible hardware problem cause.
failure was detected or as a result of running problem Up to six part numbers are pos-
analysis. The cause list type indicates when the pos- sible for a part because different
sible causes were identified and is the same for all part numbers are used to identify
the part when it has different fea-
records with a given problem identifier.
tures.
The sum of the possibilities will equal 100 percent for CAPRT2 12 Part 2
each problem identifier.
CAPRT3 12 Part 3
The record format is QSXCAOF. See the following
CAPRT4 12 Part 4
"DSPPRB Fields for Possible Cause Data
(TYPE(*CAUSE))" table for the fields in the record. CAPRT5 12 Part 5
CAPRT6 12 Part 6
Table 12 (Page 2 of 2). DSPPRB Fields for Possible Cause Table 12 (Page 2 of 2). DSPPRB Fields for Possible Cause
Data (TYPE(*CAUSE)) Data (TYPE(*CAUSE))
Field Name Length Description Field Name Length Description
CATYPE 1 Cause type: CAPLOC 25 Location of the part in the device.
Field Type (Instances) CAPCOD 4 Symptom code, also called the
A, K, N Hardware (commu- Fault Symptom Code (FSC). It is
nications controller generated by the sense bits col-
or power supply) lected in the hardware device at
C Software (OS/400) the time of failure. Only present
D Device (terminal, for cause type 'E'.
printer, or tape unit)
CASENS 64 Sense data bytes are made up of
E S/370 channel
the bits that are collected in the
attached device
hardware device to show the
G Configuration (con-
status of the device. Only present
troller description
for cause type 'E'.
parameter incorrect)
H General (modem or CAEADDR 13 Address of device where part is
cable) installed.
M Media (tape or
1-4 Identifies the device con-
diskette)
troller card.
U User (door open or
5 Separator character (-).
diskette upside
6-13 Identifies the failing device
down)
or resource.
CACHNC 3,0 The possibility that this part or
Note: All fields are of type C (character), except the CACHNC
action will correct the problem
field, which is of type P (packed decimal).
(1-100%).
CADEVN 10 Name of the device where the part
Program Fixes (*FIX)
is installed.
The output file produced for type *FIX has one record for
CAMACH 4 Type of device.
each program temporary fix (PTF) identified as a result
CAMODL 3 Model number of device. of a service call for a machine-detected or user-
CAFEAT 4 Feature number of device. perceived problem. Multiple program fix records may
CAMSER 10 Serial number of the device. have the same problem identifier.
CARSER 10 Serial number of the rack where The record format is QSXFXOF. See the following
the device is installed. "DSPPRB Fields for Program Fix Data (TYPE(*FIX))"
table for the fields in the record.
CAADDR 9 Address (1234-5678)
CALPP 7 Identifies a licensed program or
Table 13 (Page 1 of 2). DSPPRB Fields for Program Fix Data
licensed internal code. Only
(TYPE(*FIX))
present for cause type 'C'.
Field Name Length Description
CAVER 4 Version of the licensed program.
Only present for cause type 'C'. FXRCEN 1 Century that the data was
retrieved and placed in the output
CAREL 2 Release level of the licensed
file:
program. Only present for cause
type 'C'. 0 20th century
1 21st century
CAMDF 2 Modification level that applies to
the release of the licensed FXRDAT 6 Date that the data was retrieved
program. Only present for cause and placed in the output file.
type 'C'. FXRTIM 6 Time that the data was retrieved
CAMOD 10 Module in the licensed program. and placed in the output file.
Only present for cause type 'C'. FXSYSN 8 Name of the system where the
CAVOL 8 Removable media volume identi- DSPPRB command was run to
fier. Only present for cause type create this output file.
'M'. FXFORM 8 Format, which is always *FIX.
CARSRC 10 Resource name assigned to the FXID 10 Problem identifier.
device by the system.
FXORG 20 System origin.
CAPORT 2 Port where the work station cable
connects to the work station FXPTF 7 Program temporary fix (PTF)
attachment. number.
The record format is QSXTXOF. See the following SDSYSN 8 Name of the system where the
DSPPRB command was run to
"DSPPRB Fields for User Text Data (TYPE(*USRTXT))"
create this output file.
table for the fields in the record.
SDFORM 8 Format, which is always *SPTDTA.
Table 14. DSPPRB Fields for User Text Data SDID 10 Problem identifier.
(TYPE(*USRTXT))
SDORG 20 System origin.
Field Name Length Description
SDTYPE 1 Type of identifier:
TXRCEN 1 Century that the data was S Spooled file identifier
retrieved and placed in the output
file: SDNAM1 10 Identifier name 1:
0 20th century Type S Spooled file name
1 21st century SDNAM2 10 Identifier name 2:
TXRDAT 6 Date that the data was retrieved Type S Job name
and placed in the output file.
SDNAM3 10 Identifier name 3:
TXRTIM 6 Time that the data was retrieved
and placed in the output file. Type S User name
This command creates a member in the physical file licensed program identifier and program name as the prob-
NEWFILE in the current library which contains a record for able cause of the failure.
each problem log entry in the problem log.
Example 5: Displaying a List of Machine-Detected Prob-
Example 3: Displaying a List of Hardware Problems lems
DSPPRB SEV(1 2) HARDWARE(9347 ðð1 1ð-7523489) DSPPRB RESOURCE(TAPð1) MSGID(CPF6788)
This command shows a list containing problems with the This command shows a list containing machine-detected
hardware specified by the user. The user has specified that problems that were opened due to the message, CPF6788,
the command track medium-to-high levels of severity. having been sent to the system operator message queue.
The list of problems includes user-detected problems. To get
Example 4: Displaying a List of Problems That Have the user-detected problems, the user specified the resource
Been Opened name and message identifier by using the Analyze Problem
DSPPRB STATUS(\OPENED) PERIOD((\AVAIL \CURRENT) (ANZPRB) command.
(12ðððð \CURRENT)) LICPGM(5716SS1 ð3 ðð)
PGM(QNOPGM) Example 6: Displaying a List of Reported Problems
DSPPRB SRVID(12345)
This command shows a list containing problems that have
been opened during the period starting at midnight and This command shows a list containing problems that have
ending at noon on the current day, and have not yet been been reported to an IBM service support center and have
analyzed. This command also identifies the specified 12345 as the service identifier.
┌─\LIBL/────────┐
(P) ────────────────────────────5%
55──DSPPSFCFG──PSFCFG(──┼───────────────┼──PSF-configuration-name──)──┬────────────────────────┬───
├─\CURLIB/──────┤ │ ┌─\──────┐ │
└─library-name/─┘ └─OUTPUT(──┴─\PRINT─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
(P) ──┬────────────────────────────┬─────────────5
55──DSPPTF──┬──────────────────────────────────┬──┬────────────────────────────┬───
│ ┌─\ALL─────────────┐ │ │ ┌─\ALL───────┐ │ │ ┌─\ALL──────────┐ │
└─LICPGM(──┴─licensed-program─┴──)─┘ └─SELECT(──┼─\ONORDER───┼──)─┘ └─RLS(──┴─release-level─┴──)─┘
├─\PTFSAVF───┤
├─\ACTRQD────┤
└─PTF-number─┘
5──┬─────────────────────────┬──┬──────────────────────────┬──┬───────────────────────────────────────────┬─────────────────────5
│ ┌─\NO──┐ │ │ ┌─\────────┐ │ │ ┌─\LIBL/────────┐ │
└─COVERONLY(──┴─\YES─┴──)─┘ └─OUTPUT(──┼─\PRINT───┼──)─┘ └─OUTFILE(──┼───────────────┼──file-name──)─┘
└─\OUTFILE─┘ ├─\CURLIB/──────┤
└─library-name/─┘
5──┬───────────────────────────────────────────┬───────────────────────────────────────────────────────────────────────────────5%
│ ┌─\FIRST──────┐ ┌─\REPLACE─┐ │
└─OUTMBR(──┴─member-name─┴──┼──────────┼──)─┘
└─\ADD─────┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose *ALL: The status of all PTFs for the specified product is
shown.
The Display Program Temporary Fix (DSPPTF) command
*ONORDER: The PTFs that are currently on order are
shows the program temporary fixes (PTFs) for a specified
shown. This special value allows a user to get a list of
product.
PTFs that are currently on order. This special value is
Restriction: This command is shipped with public valid for PTFs both on order and on the system, that is,
*EXCLUDE authority and the QPGMR, QSYSOPR, QSRV, in the QGPL library save file or in a loaded status.
and QSRVBAS user profiles have private authorities to use *PTFSAVF: Only PTFs for which save files exist within
the command. the QGPL library are shown. This special value is useful
Note: To see the parameter and value descriptions for this to the base system user for determining which PTF save
command, refer to the online help text. For more files are no longer needed. It is also useful for the
information about printing the help text, refer to service provider for determining which PTFs can be dis-
“Printing CL Command Descriptions” in Chapter 1. tributed.
*ACTRQD: The PTFs that have actions pending are
shown. This special value is useful to the user for deter-
Optional Parameters mining which PTFs require an action to become active.
LICPGM Note: If *ACTRQD is specified, the exit programs that
Specifies the product for which PTFs are shown. When run can take a long time resulting in a delay in
LICPGM(*ALL) is specified, PTFs for all installed and the appearance of the first screen.
supported products are shown.
PTF-number: Specify the PTF identification number of
*ALL: The PTFs of all installed and supported products the PTF that is shown.
are shown.
RLS
licensed-program: Specify the product for which PTFs
Specifies the release level of the PTFs being displayed.
are shown.
*ALL: The PTFs for all releases of the supported and
SELECT installed products are displayed.
Specifies which PTF is shown for the specified product.
*ALL cannot be specified for the LICPGM parameter if a release-level: Specify the release level in VxRyMz
PTF number is specified on the SELECT parameter. format, where Vx is the version number, Ry is the
release number, and Mz is the modification level. The
When LICPGM(*ALL) and SELECT(*ALL) are specified, variables x and y can be a number from 0 through 9,
all PTFs for all installed and supported products are and the variable z can be a number from 0 through 9 or
shown. a letter from A through Z.
When LICPGM(licensed-program) and SELECT(*ALL)
are specified, PTFs for all releases of the specified pro- If the release-level specified is the release-level of the
ducts are shown. installed base option of the product, PTFs for all installed
options of the product are displayed regardless of the
release-level of the option. All PTFs for options that are *CURLIB: The current library for the job is
supported at this release-level are also displayed. searched. If no library is specified as the current
library for the job, the QGPL library is used.
If the release-level specified is not the release-level of
the installed base option of the product, only PTFs for library-name: Specify the name of the library to be
the product options that are supported or installed at that searched.
release-level are displayed.
file-name: Specify the name of the file that receives the
PTFs.
COVERONLY
OUTMBR
Specifies whether only the cover letter is displayed.
Specifies the name of the database file member to which
*NO: The cover letter is not displayed. the output is directed.
*YES: The cover letter is displayed. Element 1: Member to Receive Output
OUTPUT *FIRST: The first member in the file receives the output.
Specifies whether the output from this command is dis- If OUTMBR(*FIRST) is specified and the member does
played, printed, or directed to a database file. More not exist, the system creates a member with the name of
information on this parameter is in Appendix A, the file specified on the OUTFILE parameter.
“Expanded Parameter Descriptions.”
member-name: Specify the file member that receives
*: Output requested by an interactive job is shown on the output. If OUTMBR(member-name) is specified and
the display. Output requested by a batch job is printed the member does not exist, the system creates it.
with the job's spooled output.
Element 2: Operation to Perform on Member
*PRINT: The output is printed with the job's spooled
*REPLACE: The system clears the existing member
output. The name of the spooled file is QSYSPRT.
and adds the new records.
*OUTFILE: The output is directed to the database file
*ADD: The system adds the new records to the end of
specified on the OUTFILE parameter.
the existing records.
OUTFILE
Specifies the qualified name of the output file that is Examples
used to store the requested DSPPTF information. This
parameter is valid only if OUTPUT(*OUTFILE) is speci- Example 1: Printing Status of PTFs
fied. The model output file is QADSPPTF in library
DSPPTF LICPGM(5769SS1) OUTPUT(\PRINT)
QSYS.
The name of the file can be qualified by one of the fol- This command produces a printout containing the status of
lowing library values: PTFs for the product 5769-SS1.
*LIBL: All libraries in the job's library list are Example 2: Printing Information
searched until the first match is found. DSPPTF LICPGM(5769SS1) SELECT(SFððð34) OUTPUT(\PRINT)
(P) ──┬─────────────────────────┬──┬────────────────────────────────┬──────────────────5%
55──DSPPWRSCD──┬────────────────────────┬───
│ ┌─\──────┐ │ │ ┌─\TODAY─┐ │ │ ┌─4ð─────────────┐ │
└─OUTPUT(──┴─\PRINT─┴──)─┘ (1) ─┴─number-of-days─┴──)─┘
└─STRDATE(──┴─date───┴──)─┘ └─DAYS(───
Notes:
P All parameters preceding this point can be specified in positional form.
OUTPUT
Specifies whether the output from the command is Examples
shown at the requesting workstation or printed with the
job's spooled output. More information on this param- Example 1: Displaying Power On/Off Schedule
eter is in Appendix A, “Expanded Parameter DSPPWRSCD
Descriptions.”
*: Output requested by an interactive job is shown on This command displays the power on/off schedule.
the display. Output requested by a batch job is printed
Example 2: Printing 30 Days of Power On/Off Schedule
with the job's spooled output.
*PRINT: The output is printed with the job's spooled DSPPWRSCD OUTPUT(\PRINT) DAYS(3ð)
output.
This command prints 30 days of the power on/off schedule,
STRDATE starting with the current date.
Specifies the first date to be displayed or printed on the
power on/off schedule.
┌─\LIBL/────────┐
55──DSPRCDLCK──FILE(──┼───────────────┼──physical-file-name──)──┬──────────────────────────┬────────────────────────────────────5
├─\CURLIB/──────┤ │ ┌─\FIRST──────┐ │
└─library-name/─┘ └─MBR(──┴─member-name─┴──)─┘
(P) ──┬────────────────────────┬────────────────────────────────────────────────────────────5%
5──┬───────────────────────────────┬───
│ ┌─\ALL──────────┐ │ │ ┌─\──────┐ │
└─RCDNBR(──┴─record-number─┴──)─┘ └─OUTPUT(──┴─\PRINT─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose MBR
Specifies the name of the member in the file whose
The Display Record Locks (DSPRCDLCK) command allows record locks are shown on the display.
the user to show the current record lock status of a particular
*FIRST: The first member in the database file is used.
database physical file member. This command displays the
lock status for a particular relative record number, or the lock member-name: Specify the name of the physical file
status of all locked records in the member. member that is shown.
Note: To see the parameter and value descriptions for this RCDNBR
command, refer to the online help text. For more Specifies a particular relative record number or all
information about printing the help text, refer to records of a member.
“Printing CL Command Descriptions” in Chapter 1.
*ALL: The lock status of all records currently locked in
a physical file member is shown on the display.
Required Parameters record-number: Specify the number of the record whose
FILE lock status is shown on the display.
Specifies the qualified name of the physical file that con- OUTPUT
tains the member whose record locks are shown on the Specifies whether the output from the command is
display. shown at the requesting work station or printed with the
The name of the physical file can be qualified by one of job's spooled output. More information on this param-
the following library values: eter is in Appendix A, “Expanded Parameter
Descriptions.”
*LIBL: All libraries in the job's library list are
searched until the first match is found. *: Output requested by an interactive job is shown on
the display. Output requested by a batch job is printed
*CURLIB: The current library for the job is with the job's spooled output.
searched. If no library is specified as the current
library for the job, the QGPL library is used. *PRINT: The output is printed with the job's spooled
output.
library-name: Specify the name of the library to be
searched.
Example
physical-file-name: Specify the name of the physical file.
DSPRCDLCK FILE(MASTER/PAYROLL) MBR(\FIRST)
RCDNBR(1) OUTPUT(\)
Optional Parameters
This command shows the lock status of relative record
number 1, in the first member of the physical file named
PAYROLL in the MASTER library.
(P) ────────────────────────────────────────────────────────────────────────────────────5%
55──DSPRCYAP──┬────────────────────────┬───
│ ┌─\──────┐ │
└─OUTPUT(──┴─\PRINT─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
Restriction: You must have job control special authority to This command shows the target access path recovery times
use this command. and recovery status information for the system and config-
ured auxiliary storage pools. Output from the command is
Note: To see the parameter and value descriptions for this
shown on the workstation if the command is run interactively,
command, refer to the online help text. For more
or printed with the job's spooled output if the command is run
in batch.
(P) ─────────────────────────────5
55──DSPRDBDIRE──┬────────────────────────────────────────────────┬──┬──────────────────────────┬───
│ ┌─\ALL──────────────────────────────┐ │ │ ┌─\────────┐ │
└─RDB(──┼─generic\-relational-database-name─┼──)─┘ └─OUTPUT(──┼─\PRINT───┼──)─┘
└─relational-database-name──────────┘ └─\OUTFILE─┘
5──┬────────────────────────────────────────────────────┬──┬───────────────────────────────────────────┬───────────────────────5%
│ ┌─\LIBL/────────┐ │ │ ┌─\FIRST──────┐ ┌─\REPLACE─┐ │
└─OUTFILE(──┼───────────────┼──database-file-name──)─┘ └─OUTMBR(──┴─member-name─┴──┼──────────┼──)─┘
├─\CURLIB/──────┤ └─\ADD─────┘
└─library-name/─┘
Note:
P All parameters preceding this point can be specified in positional form.
*REPLACE: If the member exists, the system clears it Example 2: Directing Information to an Output File
and adds the new information. DSPRDBDIRE OUTPUT(\OUTFILE) OUTFILE(SAVEDIR)
*ADD: If the member exists, the system adds the new
information to the existing records. This command directs all of the relational database directory
entries to an output file named SAVEDIR. This is the usual
method for backing up the contents of the relational database
Examples directory. The entries can be restored using a CL program
that reads the information from the output file and issues Add
Example 1: Directing Information to an Output File Relational Database Directory Entry (ADDRDBDIRE) com-
DSPRDBDIRE OUTPUT(\PRINT) mands to add the information back into the relational data-
base directory.
This command directs information from all of the relational
database directory entries to a spooled file.
(P) ───────────────────────────────────────5
55──DSPRMTDFN──SYSTEM(──┬─\ANY──────────────────────┬──)──┬──────────────────────────┬───
├─\ALL──────────────────────┤ │ ┌─\────────┐ │
└─system-name──system-group─┘ └─OUTPUT(──┼─\PRINT───┼──)─┘
└─\OUTFILE─┘
5──┬───────────────────────────────────────────┬──┬───────────────────────────────────────────┬────────────────────────────────5%
│ ┌─\LIBL/────────┐ │ │ ┌─\FIRST──────┐ ┌─\REPLACE─┐ │
└─OUTFILE(──┼───────────────┼──file-name──)─┘ └─OUTMBR(──┴─member-name─┴──┼──────────┼──)─┘
├─\CURLIB/──────┤ └─\ADD─────┘
└─library-name/─┘
Note:
P All parameters preceding this point can be specified in positional form.
system-name: Specify the name of the remote system file-name: Specify the name of the output file.
to be displayed.
OUTMBR
Element 2: System Group Specifies the name of the database file member to which
system-group: Specify the group name of the remote the output is directed.
system to be displayed. Do not specify this value if the Element 1: Member to Receive Output
group name is blank.
*FIRST: The first member in the file receives the output.
If OUTMBR(*FIRST) is specified and the member does
Optional Parameters not exist, the system creates a member with the name of
the file specified on the OUTFILE parameter.
OUTPUT
Specifies whether the output from this command is dis- member-name: Specify the file member that receives
played, printed, or directed to a database file. More the output. If OUTMBR(member-name) is specified and
information on this parameter is in Appendix A, the member does not exist, the system creates it.
“Expanded Parameter Descriptions.” Element 2: Operation to Perform on Member
*: Output requested by an interactive job is shown on *REPLACE: The output data replaces existing records
the display. Output requested by a batch job is printed in the specified member.
with the job's spooled output.
*ADD: The output data is added after existing records
*PRINT: The output is printed with the job's spooled in the specified member.
output.
┌─\LIBL/────────┐
(P) ─────────────────────────────────────────────5%
55──DSPSAVF──FILE(──┼───────────────┼──file-name──)──┬────────────────────────┬───
├─\CURLIB/──────┤ │ ┌─\──────┐ │
└─library-name/─┘ └─OUTPUT(──┴─\PRINT─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
┌─\LIBL/────────┐
(P) ────────────────────────────5%
55──DSPSBSD──SBSD(──┼───────────────┼──subsystem-description-name──)──┬────────────────────────┬───
├─\CURLIB/──────┤ │ ┌─\──────┐ │
└─library-name/─┘ └─OUTPUT(──┴─\PRINT─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
Example
Required Parameters
DSPSBSD SBSD(LIB6/ORDER) OUTPUT(\)
SBSD
Specifies the qualified name of the subsystem This command (if entered from a batch job) sends a com-
description that is to be displayed. plete set of display information about the subsystem
description named ORDER (stored in LIB6 library) to the
The name of the subsystem description can be qualified
job's spooling queue for printing. The information includes
by one of the following library values:
the subsystem's attributes, all of the job entries, and all of the
*LIBL: All libraries in the job's library list are routing entries currently in the subsystem description. If the
searched until the first match is found. command is entered in an interactive job, the subsystem
description menu is shown on a display from which an option
*CURLIB: The current library for the job is
may be chosen.
searched. If no library is specified as the current
library for the job, the QGPL library is used.
(P) ─────────────────────────────────────────────────────────────────────────────────────5%
55──DSPSECA──┬────────────────────────┬───
│ ┌─\──────┐ │
└─OUTPUT(──┴─\PRINT─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose OUTPUT
Specifies whether the output from the command is dis-
The Display Security Attributes (DSPSECA) command dis- played at the requesting work station or printed with the
plays the User ID number that will be used the next time a job's spooled output.
User ID number is generated, and the group ID number that
*: Output requested by an interactive job is shown on
will be used the next time a group ID number is generated.
the display. Output requested by a batch job is printed
Note: To see the parameter and value descriptions for this with the job's spooled output.
command, refer to the online help text. For more
*PRINT: The output is printed with the job's spooled
information about printing the help text, refer to
output.
“Printing CL Command Descriptions” in Chapter 1.
Example
Optional Parameter
(P) ───────────────────────────────────────────────────────────────────────────────────5%
55──DSPSECAUD──┬────────────────────────┬───
│ ┌─\──────┐ │
└─OUTPUT(──┴─\PRINT─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose OUTPUT
Specifies whether the output from the command is
The Display Security Auditing Values (DSPSECAUD) shown at the requesting workstation or printed with the
command displays current information about the security job's spooled output. More information on this param-
audit journal and the current settings for the system values eter is in Appendix A, “Expanded Parameter
that control what is being audited on the system. Descriptions.”
Optional Parameter The current security attributes are displayed on the active
workstation.
(P) ──────────────────────────5
55──DSPSFWRSC──┬──────────────────────────┬──┬────────────────────────────────────────────────────┬───
│ ┌─\────────┐ │ │ ┌─\LIBL/────────┐ │
└─OUTPUT(──┼─\PRINT───┼──)─┘ └─OUTFILE(──┼───────────────┼──database-file-name──)─┘
└─\OUTFILE─┘ ├─\CURLIB/──────┤
└─library-name/─┘
5──┬───────────────────────────────────────────┬───────────────────────────────────────────────────────────────────────────────5%
│ ┌─\FIRST──────┐ ┌─\REPLACE─┐ │
└─OUTMBR(──┴─member-name─┴──┼──────────┼──)─┘
└─\ADD─────┘
Note:
P All parameters preceding this point can be specified in positional form.
*PRINT: The output is printed with the job's spooled Element 1: Member to Receive Output
output. *FIRST: The first member in the file receives the output.
*OUTFILE: The output is directed to the database file If OUTMBR(*FIRST) is specified and the member does
specified on the OUTFILE parameter. not exist, the system creates a member with the name of
the file specified on the OUTFILE parameter. If the
Note: If OUTPUT(*OUTFILE) is used, the name of the member exists, the records may be added to the end of
database file is required. the existing member or the existing member may be
OUTFILE cleared and the records added at the top of the member.
Specifies the qualified name of the database file to member-name: Specify the file member that receives
which the output of the command is directed. If the file the output. If OUTMBR(member-name) is specified and
does not exist, this command creates a database file in the member does not exist, the system creates it.
the specified library. If a new file is created, the system
Element 2: Operation to Perform on Member
uses the physical file QARZLCOF in library QSYS as a
model file. The file has a record format name of *REPLACE: The system clears the existing member
QARZLCGD. Field level information can be obtained and adds the new records.
using the Display File Field Description (DSPFFD) *ADD: The system adds the new records to the end of
command and specifying QARZLCOF as the file name the existing records.
and QSYS as the library. If this function creates the file,
the text says "Output file for DSPSFWRSC". The
authority for users other than those who have specific Example
DSPSFWRSC OUTPUT(\OUTFILE) OUTFILE(\CURLIB/NAMES) This command sends the output from the command to the
first member of the file NAMES in the current library. The
output replaces the information in the member.
(P) ──┬──────────────────────────┬─────────────────────────────────────────────────────5%
55──DSPSOCSTS──┬────────────────────────┬───
│ ┌─\──────┐ │ │ ┌─\BASIC─┐ │
└─OUTPUT(──┴─\PRINT─┴──)─┘ (1) ─┴─\FULL──┴──)─┘
└─DETAIL(───
Notes:
P All parameters preceding this point can be specified in positional form.
55──DSPSPLF──FILE(──spooled-file-name──)──┬────────────────────────────────────────────────────────┬────────────────────────────5
│ ┌─\─────────────────────────────────────────┐ │
└─JOB(──┴─┬─────────────────────────────┬──job-name─┴──)─┘
└─┬─────────────┬──user-name/─┘
└─job-number/─┘
(P) ──┬────────────────────┬──────────────────────────────────────────────────────────5%
5──┬─────────────────────────────────────┬───
│ ┌─\ONLY───────────────┐ │ │ ┌─\NO──┐ │
└─SPLNBR(──┼─\LAST───────────────┼──)─┘ └─FOLD(──┴─\YES─┴──)─┘
└─spooled-file-number─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose user-name: Specify the name of the user of the job that
created the spooled file.
The Display Spooled File (DSPSPLF) command shows the
job-number: Specify the number of the job that created
data records in the specified spooled file. The current con-
the spooled file.
tents of the file (data records) can be displayed for spooled
files which do not contain Advanced Function Printing* Data SPLNBR
Stream (AFPDS) data or ASCII data. The display provides Specifies the number of the job's spooled file that is
various functions to show the file and to scan for a specific being displayed. More information on this parameter is
character string. in Appendix A, “Expanded Parameter Descriptions.”
Note: To see the parameter and value descriptions for this *ONLY: One spooled file from the job has the specified
command, refer to the online help text. For more file name. The number of the spooled file is not neces-
information about printing the help text, refer to sary. If *ONLY is specified and more than one spooled
“Printing CL Command Descriptions” in Chapter 1. file has the specified file name, a message is sent.
*LAST: The highest-numbered spooled file with the
Required Parameters specified file name is displayed.
FOLD
Optional Parameters Specifies whether the records in the first display are
folded if they are longer than the length of the display
JOB line.
Specifies the qualified name of the job and consists of
*NO: The records are not folded. When the length of
as many as three elements. For example:
the record is longer than one line, the remaining posi-
job-name tions of the record are not shown.
user-name/job-name *YES: The first display shows the first record folded on
job-number/user-name/job-name one or more display lines if it is longer than one line.
*N may be used in place of the user-name element to
maintain position in the sequence. More information on Example
this parameter is in Appendix A, “Expanded Parameter
DSPSPLF FILE(QPRINT) JOB(PAYROLLð1) SPLNBR(4)
Descriptions.”
FOLD(\NO)
*: The job that issued this DSPSPLF command is the
job that created the spooled file. In this example, the spooled file QPRINT is displayed. The
file is the fourth file produced by the job PAYROLL01. The
job-name: Specify the name of the job that created the
record positions that are longer than the length of the display
spooled file.
line are truncated on the first display.
55──DSPSRVA────────────────────────────────────────────────────────────────────────────────────────────────────────────────────5%
The Display Service Attributes (DSPSRVA) command dis- There are no parameters for this command.
plays information about how the system is set up to:
Analyze problems
Notify the service provider of problems
Install a PTF
┌─\LIBL/────────┐
(P) ─┬────────────────────────┬───────────────────────────────5
55──DSPSRVPGM──SRVPGM(──┼───────────────┼──service-program-name──)────
├─\CURLIB/──────┤ │ ┌─\──────┐ │
└─library-name/─┘ └─OUTPUT(──┴─\PRINT─┴──)─┘
5──┬────────────────────────────┬──────────────────────────────────────────────────────────────────────────────────────────────5%
│ ┌─\ALL───────┐ │
└─DETAIL(──┼─\BASIC─────┼──)─┘
├─\SIZE──────┤
├─\MODULE────┤
├─\SRVPGM────┤
├─\PROCEXP───┤
├─\DTAEXP────┤
├─\ACTGRPEXP─┤
├─\ACTGRPIMP─┤
├─\SIGNATURE─┤
└─\COPYRIGHT─┘
Note:
P All parameters preceding this point can be specified in positional form.
from, use option 5=Display description to see the source *ACTGRPIMP: A list is shown of the imports that are
file, library, and member names. resolved by weak exports that had been exported to the
activation group directory.
*SRVPGM: A list of the service program objects bound
by this service program is shown. *SIGNATURE: A list of the signatures is shown. The
first signature in the list is the current signature.
*PROCEXP: A list of the procedures exported from a
service program and specified in the binding language is *COPYRIGHT: A list of the copyrights is shown.
shown. The exports are only for the current signature.
*DTAEXP: A list of the data items exported from a Example
service program and specified in the binding language is
DSPSRVPGM SRVPGM(COACH)
shown. The exports are only for the current signature.
*ACTGRPEXP: A list is shown of the data items This command displays a service program object named
exported to the activation group specified in the data COACH.
export entry in the binding specifications.
(P) ──┬────────────────────────────┬───────────────────5%
55──DSPSRVSTS──┬────────────────────────────────────────────────────────┬───
│ ┌─\─────────────────────────────────────────┐ │ │ ┌─\SELECT─┐ │
└─JOB(──┴─┬─────────────────────────────┬──job-name─┴──)─┘ └─DUPJOBOPT(──┴─\MSG────┴──)─┘
└─┬─────────────┬──user-name/─┘
└─job-number/─┘
Note:
P All parameters preceding this point can be specified in positional form.
(P) ──┬─────────────────────┬──┬───────────────────────────┬───────────────────────────5%
55──DSPSYSSTS──┬────────────────────────┬───
│ ┌─\──────┐ │ │ ┌─\NO──┐ │ │ ┌─\PRV──────┐ │
└─OUTPUT(──┴─\PRINT─┴──)─┘ └─RESET(──┴─\YES─┴──)─┘ └─ASTLVL(──┼─\USRPRF───┼──)─┘
├─\BASIC────┤
├─\INTERMED─┤
└─\ADVANCED─┘
Note:
P All parameters preceding this point can be specified in positional form.
(P) ────────────────────────────────────────────────────5%
55──DSPSYSVAL──SYSVAL(──system-value-name──)──┬────────────────────────┬───
│ ┌─\──────┐ │
└─OUTPUT(──┴─\PRINT─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
┌─\──────┐
55──DSPS36──OUTPUT(──┴─\PRINT─┴──)─────────────────────────────────────────────────────────────────────────────────────────────5%
(P) ─┬────────────────────────────────┬──┬─────────────────────────────────────┬────────────────5
55──DSPTAP──DEV(──device-name──)────
│ ┌─\MOUNTED──────────┐ │ │ ┌─\ALL─────────────────┐ │
└─VOL(──┴─volume-identifier─┴──)─┘ └─LABEL(──┴─data-file-identifier─┴──)─┘
5──┬──────────────────────────────────────┬──┬───────────────────────┬──┬──────────────────────────┬────────────────────────────5
│ ┌─1────────────────────┐ │ │ ┌─\LABELS─┐ │ │ ┌─\────────┐ │
└─SEQNBR(──┴─file-sequence-number─┴──)─┘ └─DATA(──┴─\SAVRST─┴──)─┘ └─OUTPUT(──┼─\PRINT───┼──)─┘
└─\OUTFILE─┘
5──┬─────────────────────────┬──┬────────────────────────────────────────────────────┬──────────────────────────────────────────5
│ ┌─\REWIND─┐ │ │ ┌─\LIBL/────────┐ │
└─ENDOPT(──┴─\UNLOAD─┴──)─┘ └─OUTFILE(──┼───────────────┼──database-file-name──)─┘
├─\CURLIB/──────┤
└─library-name/─┘
5──┬───────────────────────────────────────────┬───────────────────────────────────────────────────────────────────────────────5%
│ ┌─\FIRST──────┐ ┌─\REPLACE─┐ │
└─OUTMBR(──┴─member-name─┴──┼──────────┼──)─┘
└─\ADD─────┘
Note:
P All parameters preceding this point can be specified in positional form.
SEQNBR the file does not exist, this command creates a database
Specifies, for volumes with multiple files, the sequence file in the specified library. If a new file is created, the
number of the data file on tape whose label information system uses QATADOF in QSYS as a model with the
is displayed. If LABEL(*ALL) is specified or assumed, all format name of QTADOUTF. This parameter is valid
files following the file specified by SEQNBR are also dis- only when OUTPUT(*OUTFILE) and DATA(*LABELS) is
played after the specified file. specified.
1: The data file being displayed is the first file (or the database-file-name: Specify the name of the database
only file) on the tape. If LABEL(*ALL) is specified, all file file to be used.
labels are displayed, and no verification of label
OUTMBR
sequence numbers is done.
Specifies the name of the database file member to which
If a specific LABEL identifier is specified, it is compared the output is directed when OUTPUT(*OUTFILE) is
with the label identifier of the data file with the specified specified.
sequence number (SEQNBR). If the identifiers do not
Element 1: Member to Receive Output
match, an error message is sent. If LABEL(*ALL) is
specified, all file labels whose sequence numbers are *FIRST: The first member in the file receives the output.
equal to or greater than the value entered are displayed. If OUTMBR(*FIRST) is specified and the member does
not exist, the system creates a member with the name of
file-sequence-number: Specify the sequence number of
the file specified on the OUTFILE parameter.
the file that is used. Valid values range from 1 through
16777215. member-name: Specify the name of the file member
that is to receive the output. If OUTMBR(member-name)
DATA
is specified and the member does not exist, the system
Specifies the type of information that is displayed.
creates it.
*LABELS: The volume label and data file labels are
Element 2: Operation to Perform on Member
displayed.
*REPLACE: The existing records in the specified data-
*SAVRST: The tape contains save and restore data.
base file member are replaced by the new records.
Summary information is shown for the command and
each saved object. This option is valid only if the data *ADD: The system adds the new records at the end of
file was created using one of the CL save commands. the existing member.
OUTPUT ENDOPT
Specifies whether the output from the command is dis- Specifies the operation that is automatically performed
played at the requesting work station or printed with the on the tape volume after the operation ends. If more
job's spooled output. More information on this param- than one volume is included, this parameter applies only
eter is in Appendix A, “Expanded Parameter to the last tape volume used; all other tape volumes are
Descriptions.” rewound and unloaded when the end of the tape is
reached.
*: Output requested by an interactive job is shown on
the display. Output requested by a batch job is printed *REWIND: The tape is automatically rewound, but not
with the job's spooled output. unloaded, after the operation has ended.
*PRINT: The output is printed with the job's spooled *UNLOAD: The tape is automatically rewound and
output. unloaded after the operation ends.
55──DSPTAPCGY──┬────────────────────────────┬──┬────────────────────────────────────────────────────┬───────────────────────────5
│ ┌─\────────┐ │ │ ┌─\LIBL/────────┐ │
(P)┘ └─OUTFILE(──┼───────────────┼──database-file-name──)─┘
└─OUTPUT(──┼─\PRINT───┼──)───
└─\OUTFILE─┘ ├─\CURLIB/──────┤
└─library-name/─┘
5──┬───────────────────────────────────────────┬───────────────────────────────────────────────────────────────────────────────5%
│ ┌─\FIRST──────┐ ┌─\REPLACE─┐ │
└─OUTMBR(──┴─member-name─┴──┼──────────┼──)─┘
└─\ADD─────┘
Note:
P All parameters preceding this point can be specified in positional form.
55──DSPTAPCTG──DEV(──library-device-name──)──┬────────────────────────────────────────────┬─────────────────────────────────────5
│ ┌─\ALL──────────────────────────┐ │
└─CTG(──┼─generic\-cartridge-identifier─┼──)─┘
│ ┌──
──────────────────────┐ │
└──6─cartridge-identifier─┴───
(1) ───┘
5──┬─────────────────────────────────────────────────┬──┬──────────────────────────┬────────────────────────────────────────────5
│ ┌─\ALL──────────┐ ┌─\CURRENT────┐ │ │ ┌─\────────┐ │
└─CGY(──┬─┼─\NOSHARE──────┼──┼─────────────┼─┬──)─┘ └─OUTPUT(──┼─\PRINT───┼──)─┘
│ ├─\IPL──────────┤ ├─\ALL────────┤ │ └─\OUTFILE─┘
│ ├─\NL───────────┤ └─system-name─┘ │
│ ├─\SYSGEN───────┤ │
│ ├─\CNV──────────┤ │
│ └─category-name─┘ │
├─\SHARE4ðð──────────────────────────┤
├─\INSERT────────────────────────────┤
└─\EJECT─────────────────────────────┘
5──┬────────────────────────────────────────────────────┬──┬───────────────────────────────────────────┬───────────────────────5%
│ ┌─\LIBL/────────┐ │ │ ┌─\FIRST──────┐ ┌─\REPLACE─┐ │
└─OUTFILE(──┼───────────────┼──database-file-name──)─┘ └─OUTMBR(──┴─member-name─┴──┼──────────┼──)─┘
├─\CURLIB/──────┤ └─\ADD─────┘
└─library-name/─┘
Note:
1 A maximum of 40 repetitions.
viously with the Create Tape Category (CRTTAPCGY) created, the system uses QATAVOF in QSYS as a
command. model with the format name of QTAVOLOF.
Element 2: Category System Note: This parameter is valid only when
OUTPUT(*OUTFILE) is specified.
This element identifies the system to which the category
belongs. The system name is obtained from the The name of the database file can be qualified by one of
pending system name field of a Display Network Attri- the following library values:
butes (DSPNETA) command. If there is no pending
*LIBL: All libraries in the job's library list are
system name, the current system name attribute is used.
searched until the first match is found.
Attention
*CURLIB: The current library for the job is
If the system name is changed, the category infor- searched. If no library is specified as the current
mation associated with all tape cartridges in library library for the job, the QGPL library is used.
devices owned by the system are no longer valid.
library-name: Specify the name of the library to be
searched.
*CURRENT: The category belongs to the system cur-
rently running this command. database-file-name: Specify the name of the database
file to be used.
*ALL: All systems that own categories available to the
system running this command are used. OUTMBR
system-name: Specify the name of the system to which Specifies the name of the database file member to which
the category belongs. the output is directed when OUTPUT(*OUTFILE) is
specified.
Single Values:
Element 1: Member to Receive Output
*SHARE400: The cartridge identifiers in the
*SHARE400 category are displayed. A cartridge in this *FIRST: The first member in the file receives the output.
category can be shared with other systems attached to If this value is specified and the member does not exist,
the same device. the system creates a member with the name of the file
specified on the OUTFILE parameter.
*INSERT: The cartridge identifiers in the *INSERT cate-
gory are displayed. A cartridge in this category has member-name: Specify the name of the file member
been placed in the library device, but its identifier has that is to receive the output. If OUTMBR(member-name)
not been added to the system. is specified and the member does not exist, the system
creates it.
*EJECT: The cartridge identifiers in the *EJECT cate-
gory are displayed. A cartridge in this category has had Element 2: Operation to Perform on Member
its identifier removed from the system and is no longer *REPLACE: The existing records in the specified data-
usable. base file member are replaced by the new records.
OUTPUT *ADD: The system adds the new records at the end of
Specifies whether the output from the command is dis- the existing member.
played at the requesting work station, printed to an
output file, or printed with the job's spooled output.
Examples
*: The output is displayed (if requested by an interactive
job) or printed with the job's spooled output (if requested Example 1: Displaying the Tape Cartridges in the
by a batch job). *SHARE400 Category
*PRINT: The output is printed with the job's spooled DSPTAPCTG DEV(LIBð1) CGY(\SHARE4ðð) OUTPUT(\)
output.
This command displays the attributes of all tape cartridges in
*OUTFILE: The output is directed to a database file the *SHARE400 category on the work station display.
specified on the OUTFILE parameter. The file must have
the same format as database file QSYS/QATAVOF. Example 2: Displaying the Tape Cartridge for VOL3
OUTFILE DSPTAPCTG DEV(LIBð1) CTG(VOL3) OUTPUT(\)
Specifies the qualified name of the database file to CGY(\ALL)
which the information about the tape volumes is
This command displays the attributes of the cartridge identi-
directed. If the file does not exist, this command creates
fier VOL3.
a database file in the specified library. If a new file is
55──DSPTAPSTS──┬────────────────────────────┬──┬──────────────────────────┬─────────────────────────────────────────────────────5
│ ┌─\ALL────────┐ │ │ ┌─\────────┐ │
(P)┘ └─OUTPUT(──┼─\PRINT───┼──)─┘
└─DEV(──┴─device-name─┴──)───
└─\OUTFILE─┘
5──┬────────────────────────────────────────────────────┬──┬───────────────────────────────────────────┬───────────────────────5%
│ ┌─\LIBL/────────┐ │ │ ┌─\FIRST──────┐ ┌─\REPLACE─┐ │
└─OUTFILE(──┼───────────────┼──database-file-name──)─┘ └─OUTMBR(──┴─member-name─┴──┼──────────┼──)─┘
├─\CURLIB/──────┤ └─\ADD─────┘
└─library-name/─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose OUTFILE
Specifies the qualified name of the database file to
The Display Tape Status (DSPTAPSTS) command does the which the information about the tape volumes is
following: directed. If the file does not exist, this command creates
Displays slot information associated with the library a database file in the specified library. If a new file is
device. created, the system uses QATAIOF in QSYS as a model
with the format name of QTAIOUTF. This parameter is
Displays tape device information about the tape devices valid only when OUTPUT(*OUTFILE) is specified.
attached to the library device.
database-file-name: Specify the name of the database
Note: To see the parameter and value descriptions for this file to be used.
command, refer to the online help text. For more
information about printing the help text, refer to OUTMBR
“Printing CL Command Descriptions” in Chapter 1. Specifies the name of the database file member to which
the output is directed when OUTPUT(*OUTFILE) is
specified.
Optional Parameters
Element 1: Member to Receive Output
DEV
*FIRST: The first member in the file receives the output.
Specifies the name of the device for which information is
If OUTMBR(*FIRST) is specified and the member does
displayed.
not exist, the system creates a member with the name of
*ALL: Specifies that all library devices defined through the file specified on the OUTFILE parameter.
Create Device Media Library (CRTDEVMLB) command
member-name: Specify the name of the file member
are displayed.
that is to receive the output. If OUTMBR(member-name)
device-name: Specify the device name. The device is specified and the member does not exist, the system
name must be a library device name or a random creates it.
access cartridge loader(RACL) device name. The
Element 2: Operation to Perform on Member
device name must already be known to the system by
Create Device Media Library (CRTDEVMLB) command. *REPLACE: The existing records in the specified data-
base file member are replaced by the new records.
OUTPUT
Specifies whether the output from the command is dis- *ADD: The system adds the new records at the end of
played at the requesting workstation, printed to an output the existing member.
file, or printed with the job's spooled output.
*: The requested output is shown on the display. If this Example
value is specified for a batch job, the effect is the same
DSPTAPSTS DEV(LIBð1) OUTPUT(\)
as if *PRINT were entered.
*PRINT: The requested output is written to a spooled This command displays the valid information about this
file, which is found in the job's output queue. library device to the workstation display.
*OUTFILE: The output is directed to a database file
specified on the OUTFILE parameter. The file must have
the same format as database file QATAIOF.
(P) ──┬──────────────────────────────────┬────────────────────────────────────────────────5%
55──DSPTRC──┬────────────────────────┬───
│ ┌─\──────┐ │ │ ┌─\DFTPGM─────────────┐ │
└─OUTPUT(──┴─\PRINT─┴──)─┘ └─PGM(──┼─\ALL────────────────┼──)─┘
│ ┌──
──────────────┐ │
└──6─program-name─┴───
(1) ─┘
Notes:
P All parameters preceding this point can be specified in positional form.
1 A maximum of 20 repetitions
(P) ──┬─────────────────────┬──────────────────────────────────────────────────────────5%
55──DSPTRCDTA──┬────────────────────────┬───
│ ┌─\──────┐ │ │ ┌─\NO──┐ │
└─OUTPUT(──┴─\PRINT─┴──)─┘ └─CLEAR(──┴─\YES─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
Optional Parameters This command shows all of the recorded trace data at the
requesting display station. All of the trace statements in the
OUTPUT trace range and the values of the associated program vari-
Specifies whether the output from the command is dis- ables are displayed. The trace data is not cleared after it
played at the requesting display station or printed with has been displayed because CLEAR(*NO) is assumed.
55──DSPTM──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────5%
Purpose
The Display Trademarks (DSPTM) command displays a list
of trademarks that appear in the names of licensed products.
(P) ─┬────────────────────────┬──────────────────────────────────────────────────5%
55──DSPUDFS──UDFS(──'file-system-path-name'──)────
│ ┌─\──────┐ │
└─OUTPUT(──┴─\PRINT─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
Required Parameter *PRINT: The output is printed with the job's spooled
output. The output is printed with the job's spooled
UDFS output.
Specifies the path name of the user-defined file system
to be displayed. It must be (or resolve to a path name)
of the form /dev/QASPXX/name.udfs, where the XX is
Example
one of the valid user Auxiliary Storage Pool (ASP) DSPUDFS UDFS('/dev/QASPð5/joe.udfs')
numbers on the system, and name is the name of the
UDFS. All other parts of the path name must appear as This command displays the attributes of a user-defined file
in the example above. system (UDFS) named joe in the user auxiliary storage pool
(ASP) 5.
(P) ──┬────────────────────────┬──┬────────────────────────┬───────────5%
55──DSPUSRPMN──┬────────────────────────────────────────┬───
│ ┌─\CURRENT─────────────────┐ │ │ ┌─\TO───┐ │ │ ┌─\──────┐ │
└─USER(──┼─\ALL─────────────────────┼──)─┘ └─GRANTED(──┴─\FROM─┴──)─┘ └─OUTPUT(──┴─\PRINT─┴──)─┘
│ ┌──
───────────────────┐ │
└──6─user-profile-name─┴───
(1) ─┘
Notes:
1 A maximum of 300 repetitions
(P) ──┬──────────────────────────┬───────────────────5
55──DSPUSRPRF──USRPRF(──┬─\ALL───────────────┬──)──┬───────────────────────┬───
├─generic\-user-name─┤ │ ┌─\BASIC──┐ │ │ ┌─\────────┐ │
└─user-name──────────┘ └─TYPE(──┼─\ALL────┼──)─┘ └─OUTPUT(──┼─\PRINT───┼──)─┘
├─\CMDAUT─┤ └─\OUTFILE─┘
├─\DEVAUT─┤
├─\OBJAUT─┤
├─\OBJOWN─┤
├─\OBJPGP─┤
└─\GRPMBR─┘
5──┬────────────────────────────────────────────────────┬──┬───────────────────────────────────────────┬───────────────────────5%
│ ┌─\LIBL/────────┐ │ │ ┌─\FIRST──────┐ ┌─\REPLACE─┐ │
└─OUTFILE(──┼───────────────┼──database-file-name──)─┘ └─OUTMBR(──┴─member-name─┴──┼──────────┼──)─┘
├─\CURLIB/──────┤ └─\ADD─────┘
└─library-name/─┘
Note:
P All parameters preceding this point can be specified in positional form.
*ALL: All of the information in the user profile is dis- If a new file is created and *OBJOWN is speci-
played. fied on the Type of information prompt (TYPE
parameter) the system uses QADSPUPO in
*CMDAUT: The control language (CL) commands, to
QSYS with a format name QSYDSUPO as a
which the user has specific authority, are displayed.
model.
*DEVAUT: The system devices to which the user has
If a new file is created and *OBJPGP is specified
specific authority are displayed.
on the Type of information prompt (TYPE
*OBJAUT: The total number and the names of the parameter) the system uses QADSPUPG in
objects to which the user has specific authority (except QSYS with a format name QSYDSUPG as a
those authorized for public use), the user's authority for model.
those objects, and the object types are displayed. Com-
The name of the database file can be qualified by one of
mands and devices are included if *OBJAUT is speci-
the following library values:
fied.
*OBJOWN: For each object owned by the user oper- *LIBL: All libraries in the job's library list are
ating under the user profile, the total number of owned searched until the first match is found.
objects and the object names, the types, and the *CURLIB: The current library for the job is
libraries in which the objects reside are displayed. searched. If no library is specified as the current
*OBJPGP: Displays the total number of objects the library for the job, the QGPL library is used.
user is the primary group for, the object names, the type, library-name: Specify the name of the library to be
the library the object resides in, and the primary group searched.
authority.
database-file-name: Specify the name of the database
*GRPMBR: The members of a group are displayed. file.
This display is available only if the user profile being dis-
played is a group profile. OUTMBR
Specifies the name of the database file member to which
OUTPUT the output is directed.
Specifies whether the output from the command is
shown at the requesting workstation or printed with the Element 1: Member to Receive Output
job's spooled output. More information on this param- *FIRST: The first member in the file receives the output.
eter is in Appendix A, “Expanded Parameter If OUTMBR(*FIRST) is specified and the member does
Descriptions.” not exist, the system creates a member with the name of
*: Output requested by an interactive job is shown on the file specified on the OUTFILE parameter. If the
the display. Output requested by a batch job is printed member exists, the user can choose to either add
with the job's spooled output. records to the end of the existing member or to clear the
existing records in the member and then add the new
*PRINT: The output is printed with the job's spooled
records.
output.
member-name: Specify the file member that receives
*OUTFILE: The output is directed to the database file
the output. If OUTMBR(member-name) is specified and
specified on the OUTFILE parameter.
the member does not exist, the system creates it.
OUTFILE Element 2: Operation to Perform on Member
Specifies the qualified name of the database file to
*REPLACE: The system clears the existing member
which the output of the display is directed. If the file
and adds the new records.
does not exist, this command creates a database file in
the specified library. If this function creates the file, the *ADD: The system adds the new records to the end of
text reads 'Outfile for DSPUSRPRF', and the public the existing records.
authority is *EXCLUDE.
Note: If a new file is created and *BASIC is specified Examples
on the Type of information prompt (TYPE
parameter) the system uses QADSPUPB in Example 1: Displaying Basic Information
QSYS with a format name QSYDSUPB as a DSPUSRPRF USRPRF(THSMITH)
model.
If a new file is created and *OBJAUT is specified This command shows the basic portion of the user profile
on the Type of information prompt (TYPE named THSMITH because TYPE(*BASIC) is assumed. The
parameter) the system uses QADSPUPA in commands, devices, and objects that the user is authorized
QSYS with a format name QSYDSUPA as a to use are not displayed. Because OUTPUT(*) is also
model. assumed, the operational information is either displayed or
printed, depending on where the command is submitted.
Example 2: Printing a List of Objects This command causes the list of objects that are owned by
DSPUSRPRF USRPRF(RTJOHNSON) TYPE(\OBJOWN) the user named RTJOHNSON to be printed. The list con-
OUTPUT(\PRINT) tains the object names, object types, and the names of the
libraries where the objects are located.
(P) ─────────────────────────────────────────────────────5%
55──DSPUSRPRTI──┬─────────────────────────┬──┬────────────────────────┬───
│ ┌─\CURRENT──┐ │ │ ┌─\──────┐ │
└─USER(──┴─user-name─┴──)─┘ └─OUTPUT(──┴─\PRINT─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose OUTPUT
Specifies whether the output from the command is
The Display User Print Information (DSPUSRPRTI) shown at the requesting workstation or printed with the
command displays the user print information for the specified job's spooled output. More information on this param-
user profile. eter is in Appendix A, “Expanded Parameter
Note: To see the parameter and value descriptions for this Descriptions.”
command, refer to the online help text. For more *: Output requested by an interactive job is shown on
information about printing the help text, refer to the display. Output requested by a batch job is printed
“Printing CL Command Descriptions” in Chapter 1. with the job's spooled output.
*PRINT: The output is printed with the job's spooled
Optional Parameters output.
USER
Specifies the name of the user whose print information is Example
displayed. DSPUSRPRTI USER(FEIST)
*CURRENT: The user profile that is currently running is
This command displays the user print information for user
used.
profile FEIST.
user-name: Specify the name of the user whose user
print information is displayed.
(P) ────────────────────────────────────────────────────────────────────────────────────5%
55──DSPWSUSR──┬────────────────────────┬───
│ ┌─\──────┐ │
└─OUTPUT(──┴─\PRINT─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
(P) ─┬──────────────────────┬───────────────────────────────────────5
55──DUPDKT──FROMDEV(──device-name──)──TODEV(──device-name──)────
│ ┌─\NO──┐ │
└─RGZVOL(──┴─\YES─┴──)─┘
5──┬──────────────────────────────────┬────────────────────────────────────────────────────────────────────────────────────────5%
│ ┌─1────────────────┐ │
└─COPIES(──┴─number-of-copies─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
TODEV Examples
Specifies the name of the device to which the diskette is
being copied. Example 1: Copying Diskette Contents
DUPDKT FROMDEV(DKT1) TODEV(DKT2)
Optional Parameters
This command copies the entire contents of the diskette in
RGZVOL device DKT1 onto the diskette in device DKT2.
Specifies whether to delete the unused space between
files to allow space for additional files to be written on Example 2: Copying Diskette Contents
the diskette. DUPDKT FROMDEV(DKT2) TODEV(DKT2)
*NO: The unused space remains as it exists on the
This command copies the entire contents of the diskette in
input diskette. If no deleted sectors are found, the
device DKT2, prompts for the next diskette being inserted in
output diskette is an exact copy of the input diskette.
device DKT2, and copies the contents on that diskette.
*YES: The unused space between files is moved to the
end of the last file, making all files on the output diskette Example 3: Compressing Unused Space
connected. If unused space between files currently DUPDKT FROMDEV(DKT2) TODEV(DKT1) RGZVOL(\YES)
exists, the files on the output diskette resides at different
physical locations. This command copies the contents of the diskette in device
DKT2 to the diskette in device DKT1. The unused space of
COPIES the data area is compressed at the end of the diskette. If
Specifies, for spooled files, the number of copies being unused space exists between files on the input diskette, the
printed. files on the output diskette reside at different physical
1: One copy of the output is printed. locations.
number-of-copies: Specify the number of diskette copies
to make. Valid values range from 2 through 999.
(P) ─────5
55──DUPOPT──FROMVOL(──from-volume-identifier──)──TOVOL(──to-volume-identifier──)──NEWVOL(──┬─\TOVOL────────────────┬──)────
└─new-volume-identifier─┘
5──┬───────────────────────┬───────────────────────────────────────────────────────────────────────────────────────────────────5%
│ ┌─\NO──┐ │
(1) ─┴─\YES─┴──)─┘
└─CLEAR(───
Notes:
1 This parameter is ignored if the volume is WORM media.
Purpose NEWVOL
Specifies the new volume identifier of the to-volume after
The Duplicate Optical (DUPOPT) command creates a dupli- the duplication is complete.
cate optical volume. The duplicate volume is identical to the
*TOVOL: The volume identifier does not change.
original volume except for the volume identifier and the time
it was created. new-volume-identifier: Specify a new volume identifier.
(P) ─┬───────────────────────────────────────────┬──────────────────5
55──DUPTAP──FROMDEV(──device-name──)──TODEV(──device-name──)────
│ ┌─\MOUNTED─────────────────┐ │
│ │ ┌──
───────────────────┐ │ │
6 (1) ─┴──)─┘
└─FROMVOL(──┴───volume-identifier─┴───
5──┬─────────────────────────────────────────┬──┬──────────────────────────────┬──┬────────────────────────────┬────────────────5
│ ┌─\MOUNTED─────────────────┐ │ │ ┌─\DEVTYPE──┐ │ │ ┌─\FROMFILE─┐ │
└─TOVOL(──┼─\FROMVOL─────────────────┼──)─┘ └─TODENSITY(──┼─\CTGTYPE──┼──)─┘ └─COMPACT(──┼─\YES──────┼──)─┘
│ ┌──
───────────────────┐ │ ├─16ðð──────┤ └─\NO───────┘
└──6─volume-identifier─┴───
(1) ─┘ ├─32ðð──────┤
├─625ð──────┤
├─\FMT348ð──┤
├─\FMT349ðE─┤
├─\FMT357ð──┤
├─\FMT357ðE─┤
├─\FMT359ð──┤
├─\QIC12ð───┤
├─\QIC525───┤
├─\QIC1ððð──┤
├─\QIC2GB───┤
├─\QIC3ð4ð──┤
├─\QIC5ð1ð──┤
├─\FMT2GB───┤
├─\FMT5GB───┤
└─\FMT7GB───┘
5──┬────────────────────────┬──┬────────────────────────────────────────────────────────────────────┬───────────────────────────5
│ ┌─\ALL────┐ │ │ ┌─\FIRST───────────────┐ ┌─\LAST────────────────┐ │
└─FILES(──┴─\ACTIVE─┴──)─┘ └─FROMSEQNBR(──┼─\ALL─────────────────┼──┼──────────────────────┼──)─┘
└─file-sequence-number─┘ ├─\ONLY────────────────┤
└─file-sequence-number─┘
5──┬────────────────────────────────────────┬──┬───────────────────────────────────────────────────────────────┬────────────────5
│ ┌─\FROMSEQ─────────────┐ │ │ ┌─\SYSCOPY───────────────────────────────────┐ │
└─TOSEQNBR(──┼─\END─────────────────┼──)─┘ └─USRLBLPGM(──┼─\NONE──────────────────────────────────────┼──)─┘
└─file-sequence-number─┘ │ ┌─\LIBL/────────┐ │
└─┼───────────────┼──user-label-program-name─┘
├─\CURLIB/──────┤
└─library-name/─┘
5──┬─────────────────────────────┬──┬───────────────────────────┬──────────────────────────────────────────────────────────────5%
│ ┌─\REWIND─┐ │ │ ┌─\UNLOAD─┐ │
└─FROMENDOPT(──┼─\UNLOAD─┼──)─┘ └─TOENDOPT(──┼─\REWIND─┼──)─┘
└─\LEAVE──┘ └─\LEAVE──┘
Notes:
1 A maximum of 50 repetitions
Purpose second part of the file to the end of the tape is not
allowed. You must duplicate both parts of the file at the
The Duplicate Tape (DUPTAP) command copies the con- same time by specifying multiple volumes on the
tents of one tape to another tape. FROMVOL parameter.
Notes: Note: To see the parameter and value descriptions for this
command, refer to the online help text. For more
1. The density field in the file header labels is updated to information about printing the help text, refer to
reflect the true density. “Printing CL Command Descriptions” in Chapter 1.
2. Byte 80 in the volume label of a tape written on device
type 6157 is reset from a 'Q' to a blank.
Required Parameters
Restrictions: FROMDEV
1. The user must have two tape drives or a tape media Specifies the name of the device from which the tape is
library device with two tape resources to use this copied.
command.
TODEV
2. A file that spans volumes must have both partial files Specifies the name of the device to which the tape is
duplicated at the same time. That is, duplicating a tape copied.
that ends in a partial file, followed by appending the
Optional Parameters *ONLY: Only the file specified in the starting file
sequence are duplicated. If *ALL is specified in the first
FROMVOL element, then this parameter is ignored.
Specifies the volume identifier of the tape being dupli-
file-sequence-number: Specify the ending file sequence
cated, or indicates that the tape currently on the mag-
number of the range to be duplicated. The valid range
netic tape device is being duplicated.
of sequence numbers is 1 through 65535.
Note: If the tape device is contained in a library device,
then the volume specified should be the cartridge TOSEQNBR
identifier to be mounted and used. Specifies which sequence number the data files are to
be copied to.
*MOUNTED: The volume currently placed in the device
is used. *FROMSEQ: The data files are duplicated to the same
file sequences as are specified in the from file sequence
volume-identifier: Specify the identifier of the labeled number parameter.
volume being duplicated. If the tape placed on the spec-
ified device has a different volume identifier than speci- *END: The data files are added to the logical end of
fied, or if it is an unlabeled volume, an error message is tape. The next valid sequence number is used.
sent. file-sequence-number: Specify the sequence number in
which the data file will be copied to. This value is not
TOVOL
allowed if the device does not have overwriting capabili-
Specifies the volume identifiers of the tapes to be
ties and the value specified is not the next logical value
created (destination volumes).
to be used at the end of the logical tape volume. The
Note: If the tape device is contained in a library device, valid range of sequence numbers is 1 through 65535.
then the volume specified should be the cartridge The duplication begins at the specified file.
identifier to be mounted and used.
TODENSITY
*MOUNTED: The volume currently placed in the device Specifies the density or format in which to write the data
is used. For a media library device, the volume to be to the device specified on the TODEV parameter.
used is the next cartridge in the category mounted by
the Set Tape Category (SETTAPCGY) command. *DEVTYPE: The data written on the tape volume is
based on the device type.
*FROMVOL: The volume label of the tape currently
mounted on the source device is used to initialize the *CTGTYPE: The data written on the tape volume is
tape on the output device. based on the cartridge type (the type of tape cartridge).
If the device does not support special cartridge type
volume-identifier: Specify the identifier to use on the information, *DEVTYPE is used.
output volume.
Tape Device Default Density (bpi)
FILES 2440 6250
Specifies which data files are copied. 3422 6250
*ALL: All data files on the tape volume are copied. 3430 6250
3480 *FMT3480
*ACTIVE: Only data files with an expiration date later
3490E *FMT3490E
than the current system date are copied.
3570-BXX *FMT3570
FROMSEQNBR 3570-CXX *FMT3570E
Specifies which data file sequence numbers are to be 3590 *FMT3590
copied. 6335 *QIC3040
6341 *QIC120
Element 1: Starting file sequence number
6342 *QIC525
*FIRST: All files starting with the first file sequence are 6343 *QIC1000
duplicated. 6344 *QIC2GB
*ALL: All files are duplicated. 6346 *QIC120
6347 *QIC525
file-sequence-number: Specify the starting file sequence 6348 *QIC1000
| number to be duplicated. The valid range of sequence 6349 *QIC2GB
| numbers is 1 through 16777215. Only the files in the 6366 *QIC120
specified sequence number range are duplicated. 6368 *QIC1000
Element 2: Ending file sequence number 6369 *QIC2GB
6378 *QIC525
*LAST: All files ending with the last file sequence are
6379 *QIC1000
duplicated.
6380 *QIC2GB
6385 *QIC5010
user-label-program-name: Specify the name of the user *LEAVE: The tape does not rewind or unload after the
program that processes the user tape labels. operation ends. It remains at the current position on the
tape drive.
FROMENDOPT
Specifies whether the tape volume placed on the device
specified on the FROMDEV parameter is rewound or Examples
rewound and unloaded after the operation is complete.
Example 1: Duplicating a single volume to a single
*REWIND: The tape is automatically rewound, but not volume
unloaded, after the operation has ended.
DUPTAP FROMDEV(TAPEð1) TODEV(TAPEð2)
*UNLOAD: The tape is automatically rewound and
unloaded after the operation ends. This command duplicates the tape volume mounted on
*LEAVE: The tape does not rewind or unload after the device TAPE01 onto the tape volume mounted on device
operation ends. It remains at the current position on the TAPE02.
tape drive.
Example 2: Appending a volume set to the end of a
TOENDOPT single volume
Specifies whether the tape volume placed in the device DUPTAP FROMDEV(TAPEð1) TODEV(TAPEð2)
specified on the TODEV parameter is rewound, or FROMVOL( VOLðð1 VOLðð2) TOVOL(VOLABC)
rewound and unloaded after the operation is complete. FROMSEQNBR(\ALL) TOSEQNBR(\END)
*UNLOAD: The tape is automatically rewound and
This command duplicates all files from the tape volumes
unloaded after the operation ends.
VOL001 and VOL002 onto the end of the to-volume
*REWIND: The tape is automatically rewound, but not VOLABC on device TAPE02.
unloaded, after the operation has ended.
(P) ─────────────────────────────────────────────────────────────────────────────5%
55──EDTAUTL──AUTL(──authorization-list-name──)────
Note:
P All parameters preceding this point can be specified in positional form.
┌─\LIB─┐
(P) ────────────────────────────────────────────────────────────────────────────────────────5%
55──EDTBCKUPL──BCKUPL(──┴─\FLR─┴──)────
Note:
P All parameters preceding this point can be specified positionally.
Purpose BCKUPL
Specifies the backup list to be changed.
The Edit Backup List (EDTBCKUPL) command allows the
*LIB: The library backup list is changed.
user to select libraries and folders for backup. More informa-
tion on backup is in the Backup and Recovery book. *FLR: The folder backup list is changed.
Note: To see the parameter and value descriptions for this
command, refer to the online help text. For more Example
information about printing the help text, refer to EDTBCKUPL BCKUPL(\LIB)
“Printing CL Command Descriptions” in Chapter 1.
This command displays the library backup list stored in user
index QUSRSYS/QEZBACKUPL, and allows the user to
Required Parameters
change it.
55──EDTCPCST───────────────────────────────────────────────────────────────────────────────────────────────────────────────────5%
(P) ─┬──────────────────────────────┬──────────────────────────────────5%
55──EDTDLOAUT──DLO(──┬─\SYSOBJNAM───────────────────┬──)────
├─\ROOT────────────────────────┤ │ ┌─\NONE───────┐ │
└─document-library-object-name─┘ (1) ─┴─folder-name─┴──)───┤
├─FLR(───
└─SYSOBJNAM(───(2) ─object-name──)─┘
Notes:
P All parameters preceding this point can be specified in positional form.
The authority given to the users with no specific *NONE: A folder name is not specified. If DLO(name)
authority for the document or folder is specified and the object is located in a folder,
FLR(*NONE) cannot be specified.
Access codes can be shown by pressing a function key
folder-name: Specify the name of the folder that con-
Restrictions: tains the object. The name can consist of a series of
folder names if the folder containing the object is located
1. You must have *ALL authority to the document or folder
in another folder. Up to 63 characters can be specified.
to change the authority or *ALLOBJ special authority.
2. You must have authority to use the ADDDLOAUT, SYSOBJNAM
CHGDLOAUT, and the RMVDLOAUT commands to use Specifies the system object name of the folder or docu-
this command. ment. This parameter is valid only when
DLO(*SYSOBJNAM) is specified. Ten characters must
3. You must have *ALLOBJ special authority to change the be specified.
*ROOT folder public authority.
Note: To see the parameter and value descriptions for this
Example
command, refer to the online help text. For more
information about printing the help text, refer to EDTDLOAUT DLO(DOCA) FLR(MYFLR)
“Printing CL Command Descriptions” in Chapter 1.
This command allows the user of this command to change
the list of authorized users and their authorities to the docu-
Required Parameters ment library object named DOCA in folder MYFLR. The user
of this command must have *ALL authority to the object or
DLO be the owner of the object.
Specifies the name of the document or folder that is
changed.
(P) ──┬───────────────────────┬─────────────────────────5%
55──EDTDOC──┬────────────────────────────┬──┬──────────────────────────┬───
│ ┌─\PRV──────────┐ │ │ ┌─\PRV────────┐ │ │ ┌─\YES─┐ │
└─DOC(──┴─document-name─┴──)─┘ └─FLR(──┴─folder-name─┴──)─┘ └─EXITPNL(──┴─\NO──┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
DOC
Specifies the name of the document to edit. Example
*PRV: The name used in the previous session is used. EDTDOC DOC(TASK4) FLR(INSTTXT)
document-name: Specify the name of the document that This command displays the document TASK4 of the folder
is edited. INSTTXT, and allows the user to edit the document TASK4.
FLR
Specifies the name of the folder that contains the docu-
ment.
┌─\LIBL/────────┐
(1) ─IGCDCT(──┼───────────────┼──dictionary-name──)────
55──EDTIGCDCT─── (P) ─┬────────────────────────────────┬─────────────────────────5%
├─\CURLIB/──────┤ │ ┌─\ALL────────────┐ │
└─library-name/─┘ └─ENTRY(──┼─generic\-string─┼──)─┘
└─specific-string─┘
Notes:
1 DBCS systems only
55──EDTLIBL────────────────────────────────────────────────────────────────────────────────────────────────────────────────────5%
┌─\LIBL/────────┐
(1) ─object-type──)────
55──EDTOBJAUT──OBJ(──┼───────────────┼──object-name──)──OBJTYPE(─── (P) ─────────────────────────────────────────5%
├─\CURLIB/──────┤
└─library-name/─┘
Notes:
1 A list of the valid OS/400 object types for this command is in Appendix A.
Purpose OBJ
Specifies the qualified name of the object for which the
The Edit Object Authority (EDTOBJAUT) command displays authorized users and their authorities are to be shown.
the list of authorized users of an object and their associated
The name of the object can be qualified by one of the
authorities. If you own the object or have *ALLOBJ special
following library values:
authority, you can add, change, or remove authority for the
object. If you have object management authority for the *LIBL: All libraries in the job's library list are
object, you can remove your specific authorities or grant or searched until the first match is found.
remove them for other users.
*CURLIB: The current library for the job is
The following are displayed for the specified object: searched. If no library is specified as the current
library for the job, the QGPL library is used.
the object name
library-name: Specify the name of the library to be
the name of the library containing the object searched.
the name of the object's owner, the object's type, and a
object-name: Specify the name of the object for which
list of all the users who are authorized to use the object
its authorized users and their authorities are to be
the authorities that each user has for the object shown.
If an object does not have an owner name associated with it, OBJTYPE
no authorities for the object are shown. Specifies the object type of the object that is to have its
authorized users and their authorities shown. Any one
Restrictions: of the operating system object types can be specified.
1. The user must have object management authority to the For example, to display a list of users authorized to use
object to use this command. a file, specify the value *FILE. More information on this
parameter is in Appendix A, “Expanded Parameter
2. If the object is a file, the user must have object opera- Descriptions.”
tional and object management authorities.
Note: To see the parameter and value descriptions for this
Example
command, refer to the online help text. For more
information about printing the help text, refer to EDTOBJAUT OBJ(ARLIB/PROG1) OBJTYPE(\PGM)
“Printing CL Command Descriptions” in Chapter 1.
This command causes the list of authorized users and their
authorities for the object named PROG1 to be shown, but
Required Parameters only if the user has object management authority for the
object. PROG1 is a program (*PGM) located in the library
named ARLIB.
(P) ─────────────────────────────────────────────5%
55──EDTQST──┬──────────────────────────────────┬──┬───────────────────────────┬───
│ ┌─\SELECT───────────┐ │ │ ┌─\QSTLIB──────┐ │
└─QSTDB(──┴─question-database─┴──)─┘ └─LIB(──┴─library-name─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
55──EDTRBDAP───────────────────────────────────────────────────────────────────────────────────────────────────────────────────5%
55──EDTRCYAP───────────────────────────────────────────────────────────────────────────────────────────────────────────────────5%
┌─\LIBL/────────┐ ┌─\ALL─────────┐
(P) ───────────────────────────────────────────────────────────────5%
55──EDTS36PGMA──PGM(──┼───────────────┼──┴─program-name─┴──)────
├─\CURLIB/──────┤
└─library-name/─┘
Note:
P All parameters preceding this point can be specified in positional form.
PGM
Specifies the qualified name of the program having its Example
attributes updated. EDTS36PGMA PGM(RPGLIB/\ALL)
The name of the program can be qualified by one of the
This command shows the program attributes of all the pro-
following library values:
grams in RPGLIB and allows them to be changed.
(P) ───────────────────5%
55──EDTS36PRCA──MBR(──┬─\ALL──────────────────┬──)──┬───────────────────────────────────────────────────┬───
└─procedure-member-name─┘ │ ┌─\LIBL/────────┐ ┌─QS36PRC──────────┐ │
└─FILE(──┼───────────────┼──┴─source-file-name─┴──)─┘
├─\CURLIB/──────┤
└─library-name/─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose FILE
Specifies the qualified name of the source physical file
The Edit System/36 Procedure Attributes (EDTS36PRCA) that contains the procedure members to be updated.
command presents the attributes of the specified procedure
The name of the file can be qualified by one of the fol-
on your display for you to change. The attributes of a speci-
lowing library values:
fied procedure or of all procedures in the specified file can be
changed. *LIBL: All libraries in the job's library list are
Note: To see the parameter and value descriptions for this searched until the first match is found.
command, refer to the online help text. For more *CURLIB: The current library for the job is
information about printing the help text, refer to searched. If no library is specified as the current
“Printing CL Command Descriptions” in Chapter 1. library for the job, the QGPL library is used.
library-name: Specify the name of the library to be
Required Parameters searched.
(P) ──────────────────────5%
55──EDTS36SRCA──MBR(──┬─\ALL───────────────┬──)──┬───────────────────────────────────────────────────┬───
└─source-member-name─┘ │ ┌─\LIBL/────────┐ ┌─QS36SRC──────────┐ │
└─FILE(──┼───────────────┼──┴─source-file-name─┴──)─┘
├─\CURLIB/──────┤
└─library-name/─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose FILE
Specifies the qualified name of the source physical file
The Edit System/36 Source Attributes (EDTS36SRCA) containing the source members.
command presents the attributes of the specified source
The name of the source physical file can be qualified by
member on your display for you to change. The attributes of
one of the following library values:
a specified source member or of all source members in the
specified file can be changed. *LIBL: All libraries in the job's library list are
Note: To see the parameter and value descriptions for this searched until the first match is found.
command, refer to the online help text. For more *CURLIB: The current library for the job is
information about printing the help text, refer to searched. If no library is specified as the current
“Printing CL Command Descriptions” in Chapter 1. library for the job, the QGPL library is used.
library-name: Specify the name of the library to be
Required Parameters searched.
(P) ─────────────────────────────────────────────────────────────────────────────────5%
55──EDTWSOAUT──WSOTYPE(──┬─\TPLWRKARA─┬──)────
├─\WRKARA────┤
├─\TPLPRTOL──┤
├─\PRTOL─────┤
├─\TPLTPRTL──┤
├─\PRTL──────┤
├─\TPLOUTQ───┤
├─\TPLOUTQL──┤
├─\OUTQL─────┤
├─\TPLJOBL───┤
├─\JOBL──────┤
├─\TPLJOBQ───┤
├─\TPLJOBLOG─┤
├─\JOBLOG────┤
├─\TPLJOBQL──┤
├─\JOBQL─────┤
├─\TPLMSGL───┤
├─\MSGL──────┤
├─\TPLMSGQ───┤
├─\TPLMSGSND─┤
├─\MSGSND────┤
├─\TPLSGNUSL─┤
├─\SGNUSL────┤
├─\TPLOBJL───┤
├─\OBJL──────┤
├─\TPLLIBSL──┤
├─\LIBSL─────┤
├─\TPLLIB────┤
├─\TPLLAUNCH─┤
├─\LAUNCH────┤
└─\PRSSET────┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose Restrictions:
1. The user must have object management authority to the
The Edit Workstation Object Authority (EDTWSOAUT)
object to use this command.
command shows the list of authorized users of a workstation
object and the users' associated authorities. Workstation 2. If the object is a file, the user must have object opera-
objects are used by the OS/400 Graphical Operations tional and object management authorities to use this
program. If you own the object or are the security officer, command.
you can add, change, or remove authority for the object. If Note: To see the parameter and value descriptions for this
you have object management authority for the object, you command, refer to the online help text. For more
can remove your specific authorities or grant or remove them information about printing the help text, refer to
for other users. “Printing CL Command Descriptions” in Chapter 1.
The following are shown for the specified object:
The object name Required Parameter
The name of the library containing the object WSOTYPE
The name of the object owner, the object’s type, and a Specifies the name of the workstation object for which
list of all the users who are authorized to use the object specific authorities are to be shown or edited.
The authorities that each user has for the object
The special values for this parameter are described in
If an object does not have an owner name associated with it, the following table.
no authorities for the object are shown.
Example
Special Value Workstation Objects EDTWSOAUT WSOTYPE(\TPLMSGQ)
*TPLWRKARA Work area template
This command shows the list of authorized users to the
*WRKARA Work area objects message queue template.
*TPLPRTOL Printer output list template
*PRTOL Printer output list objects
*TPLTPRTL Printer list template
*PRTL Printer list objects
*TPLOUTQ Output queue template
*TPLOUTQL Output queue list template
*OUTQL Output queue list objects
*TPLJOBL Job list template
*JOBL Job list objects
*TPLJOBQ Job queue template
*TPLJOBLOG Job log template
*JOBLOG Job log objects
*TPLJOBQL Job queue list template
*JOBQL Job queue list objects
*TPLMSGL Message list template
*MSGL Message list objects
*TPLMSGQ Message queue template
*TPLMSGSND Message sender template
*MSGSND Message sender
*TPLSGNUSL Signed-on user list template
*SGNUSL Signed-on user list objects
*TPLOBJL Object list template
*OBJL Object list objects
*TPLLIBSL Library list template
*LIBSL Library list objects
*TPLLIB Library template
*TPLLAUNCH Job submitter template
*LAUNCH Job submitter objects
*PRSSET Personal setting objects
(P) ────────────────────────────────────────────5%
55──EJTEMLOUT──┬─EMLDEV(──emulation-device-description-name──)─────────────────┬───
└─EMLLOC(──emulation-location-name──)──PRTDEV(──printer-name──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose Example
EJTEMLOUT EMLDEV(HOSTPRT1)
The Eject Emulation Output (EJTEMLOUT) command fin-
ishes the current emulation output, and then ejects to a new This command closes the printer file in the printer emulation
page. It forces the last data received from the host system job using the emulation device HOSTPRT1, forcing the latest
to the spooled file or printer by closing the printer file and data from the host system out to the spooled file or printer.
then reopening another, so that more data can be spooled or
printed. If SCHEDULE(*FILEEND) is specified on the Create
Printer File (CPTPRTF) command, printing starts. The Additional Considerations
request may not take effect immediately, because the printer
utility must complete printing a transmission block from the You must use care when running this command. Before
host system before doing this function. See “Additional Con- entering the command, you should look at the printed output
siderations” at the end of this command description for more (if SPOOL(*NO) was specified) or use the Display Spooled
information about running this command. File (DSPSPLF) command to look at the spooled file (if
SPOOL(*YES) was specified), to determine whether the
More information about device emulation is available in the printer data is at a logical breaking point. If this function is
3270 Device Emulation Support book. requested when printer emulation is in the middle of a group
of print data from the host system, the group is split into sep-
Note: To see the parameter and value descriptions for this
arate printer files on the system.
command, refer to the online help text. For more
information about printing the help text, refer to The effect of this command on the printer emulation output
“Printing CL Command Descriptions” in Chapter 1. varies, depending on the values specified for the SPOOL and
SCHEDULE parameters on the printer file.
Required Parameters The possible values and their conditions are:
EMLDEV SPOOL(*NO): All the data received from the host
Specifies the name of the printer emulation device system is printed, and the printer moves to the top of the
requested to receive data from the host system. The next page.
printer emulation job using this device is informed of the
request and closes the printer file. This forces all of the SPOOL(*YES) and SCHEDULE(*IMMED): If a writer is
data received from the host system to the spooled file or active to the output queue and is printing this file, all the
printer. The printer file is then reopened and printer data received from the host system is printed, and the
emulation continues. To use this function, the user must printer moves to the top of the next page. If a writer is
be authorized to the device. not active (printing this file), the effect is the same as if
SCHEDULE(*FILEEND) was specified. Another printer
EMLLOC file is opened on the output queue.
Specifies the remote location name associated with this
SPOOL(*YES) and SCHEDULE(*FILEEND): The status
session. This name is defined during configuration and
of the printer file on the output queue changes from
refers to the remote location where communication takes
open to ready to print. If a writer is active, the data can
place. This value must be the same as that specified for
be printed. Another printer file is opened on the output
the Start Printer Emulation (STRPRTEML) command.
queue.
PRTDEV SPOOL(*YES) and SCHEDULE(*JOBEND): The status
Specifies the name of the printer device that is used to of the printer file on the output queue changes from
print the spooled output. This value must match the open to closed. The file is not ready to print until the
value specified on the Start Printer Emulation end of the job is reached. Another printer file is opened
(STRPRTEML) command. This parameter must be on the output queue.
specified when the EMLLOC parameter is specified.
(P) ───────────────────────────────────────────────────────────────────────────────────────────5%
55──ELSE──┬─────────────────────┬───
└─CMD(──CL-command──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
Note: To see the parameter and value descriptions for this DCL (Declare CL Variable)
command, refer to the online help text. For more DCLF (Declare File)
information about printing the help text, refer to
another ELSE command
“Printing CL Command Descriptions” in Chapter 1.
In addition, the MONMSG command cannot be specified
as the next command after the ELSE command.
Optional Parameters
CMD Examples
Specifies the command or commands (in a Do group) to
be processed if the result of evaluating the expression Example 1: Using Else and If Commands
on the corresponding IF command is false. If the
IF (&A \GT &B) THEN(CHGVAR VAR(&A) VALUE(&B))
command specified in this parameter is a DO command,
ELSE (CHGVAR &B &A)
all of the commands specified within the Do group are
considered to be part of the command specified by the If the value of &A is greater than the value of &B, &A is set
parameter. If no command is specified, no action is equal to &B. If &A is less than or equal to &B, the test result
taken for a false condition. is false. The CHGVAR command on the ELSE command is
If the command specified by the CMD keyword is not processed, and the value of &B is set to the same value as
coded on the same line as the keyword, the left paren- &A. (Refer to the CHGVAR (Change Variable) command for
thesis following CMD must be coded on the same line, the description of the command and its parameters.)
followed by a + or - to show continuation. The
Example 2: Nested Levels of Commands
IF COND(&A \EQ &B) + This example shows the use of nested levels of IF com-
THEN(IF (&C \EQ &D) + mands where an ELSE command is associated with each IF.
THEN(IF (&C \EQ &F) THEN(DO))) The use of the ELSE commands makes the nested levels of
CMD1 IF commands easier to identify.
CMD2
ENDDO
ELSE CMDX
ELSE CMDY
ELSE DO
┌─\PA1─┐
(P) ──PRTKEY(──┴─\PA2─┴──)──────────────────────5%
55──EMLPRTKEY──┬─EMLDEV(──emulation-device-description-name──)─────────────────┬───
└─EMLLOC(──emulation-location-name──)──PRTDEV(──printer-name──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
55──//ENDBCHJOB────────────────────────────────────────────────────────────────────────────────────────────────────────────────5%
55──ENDCLNUP───────────────────────────────────────────────────────────────────────────────────────────────────────────────────5%
(P)─┬─────────────────────────┬──┬─────────────────────────────┬──────────────────────────────────────────────────5%
55──ENDCMNSVR───
│ ┌─\CNTRLD─┐ │ │ ┌─\NOMAX─────┐ │
(1) ─┴─delay-time─┴──)─┘
└─OPTION(──┴─\IMMED──┴──)─┘ └─DELAY(───
Notes:
1 This parameter is valid only when OPTION(*CNTRLD) is specified.
(P) ───────────────────────────────────────────────────5%
55──ENDCMNTRC──CFGOBJ(────configuration-name────)──CFGTYPE(──┬─\LIN─┬──)────
├─\NWI─┤
└─\NWS─┘
Note:
P All parameters preceding this point can be specified in positional form.
QSRV
Note: To see the parameter and value descriptions for this
Example
command, refer to the online help text. For more ENDCMNTRC CFGOBJ(\QESLINE) CFGTYPE(\LIN)
information about printing the help text, refer to
“Printing CL Command Descriptions” in Chapter 1. This command ends the communications trace of line
description QESLINE.
55──ENDCMTCTL──────────────────────────────────────────────────────────────────────────────────────────────────────────────────5%
(P) ───────────────────────────────────────────────────────────────────────5%
55──ENDCPYSCN──┬────────────────────────────────────┬───
│ ┌─\REQUESTER─────────┐ │
└─SRCDEV(──┴─source-device-name─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose SRCDEV
Specifies the name of the display station that is currently
The End Copy Screen (ENDCPYSCN) command ends the having its screen images copied. If no display station
copy screen image operation. This command can be name is specified, processing for the requesting display
entered from any display station capable of command entry. station is canceled.
Note: The target display station also stops the copy screen *REQUESTER: The source display station that
image operation when the user presses the System requested the command is used.
Request key and types ENDCPYSCN (End Copy
source-device-name: Specify the display station name
Screen command) on the command line. No param-
whose screen images are being copied.
eters can be specified.
Note: To see the parameter and value descriptions for this
command, refer to the online help text. For more Example
information about printing the help text, refer to ENDCPYSCN SRCDEV(CHARLIE)
“Printing CL Command Descriptions” in Chapter 1.
The command sends a message to 'CHARLIE' (the source
display station). The message indicates the copy screen
Optional Parameters image operation is about to end. The target work station
display is restored to the same display image that was
shown before the operation started. The sign-on display is
normally shown.
(P) ────────────────────────────────────────────────────────────────────────────────────5%
55──ENDCTLRCY──CTL(──controller-name──)────
Note:
P All parameters preceding this point can be specified in positional form.
55──ENDDBG─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────5%
55──ENDDBGSVR──────────────────────────────────────────────────────────────────────────────────────────────────────────────────5%
55──ENDDBMON──┬────────────────────────────────────────────────────────┬───(P) ──┬─────────────────────────┬───────────────────────5%
│ ┌─\─────────────────────────────────────────┐ │ │ ┌─\BLANK─┐ │
(1) ───────────────────────────────────┼──)─┘
└─JOB(──┼─\ALL─── └─COMMENT(──┴─text───┴──)─┘
└─┬─────────────────────────────┬──job-name─┘
└─┬─────────────┬──user-name/─┘
└─job-number/─┘
Notes:
1 This value is valid only if JOB(*ALL) was specified using the STRDBMON command.
job-name This command ends database monitoring for all jobs on the
user-name/job-name system.
job-number/user-name/job-name
Example 2: Ending Database Monitoring for a Specific
*N may be used in place of the user-name element to Job
maintain position in the sequence. More information on ENDDBMON JOB(\)
(P) ────────────────────────────────────────────────────────────────────────────────────────5%
55──ENDDEVRCY──DEV(──device-name──)────
Note:
P All parameters preceding this point can be specified in positional form.
┌─\CNTRLD─┐ ┌─3ð─────────┐
55──ENDDIRSHD──OPTION(──┴─\IMMED──┴──)──DELAY(──┴─delay-time─┴──)──────────────────────────────────────────────────────────────5%
55──ENDDO──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────5%
When Do groups are nested, each group must have its own See the examples for the DO and IF commands.
ENDDO command at its end. Every ENDDO command must
| Notes:
| 1 A maximum of 16 repetitions.
| P All parameters preceding this point can be specified in positional form.
| Restrictions: | This command allows the user to end the disk reorganization
| function for ASP 1.
| You must have *ALLOBJ special authority to use this
| command. | Example 2: Ending Disk Reorganization for all ASPs
| ENDDSKRGZ ASP(\ALL)
| Optional Parameters
| This command allows the user to end the reorganization
| ASP | function for each ASP that is currently being reorganized.
| Specifies for which auxiliary storage pools the disk reor-
| ganization function is to be ended.
(P) ──┬───────────────────────────────────┬──┬──────────────────────┬──────────5%
55──ENDGRPJOB──┬────────────────────────────────┬───
│ ┌─\──────────────┐ │ │ ┌─\PRV───────────┐ │ │ ┌─\NOLIST─┐ │
└─GRPJOB(──┴─group-job-name─┴──)─┘ └─RSMGRPJOB(──┴─group-job-name─┴──)─┘ └─LOG(──┴─\LIST───┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose When the only job in a group is ending, one of two situ-
ations can occur:
The End Group Job (ENDGRPJOB) command ends a single
job in a group and resumes another job in the group. (Issue The ending group job is part of a secondary job
the Sign Off (SIGNOFF) command to end all jobs in a pair. In this case, the other job in the secondary job
group.) The user can specify the following: pair is resumed, and control is passed back to that
job.
Which job in the group is ended
The ending group job is not part of a secondary job
Which job in the group gains control (this is valid only pair. In this case, the sign-on display is shown at
when a job is ending itself) the work station (if the work station entry for the
Whether the job ended has a job log spooled to an work station device in the subsystem specifies
output queue *SIGNON).
Note: The job that issues the ENDGRPJOB command can *NOLIST: An intermediate representation of the
only end itself or some other job in the group to program listing is not created.
which this job belongs. To end a job outside the
*LIST: The information in the job log is spooled to an
group, the END Job (ENDJOB) command must be
output queue.
used.
Note: To see the parameter and value descriptions for this
command, refer to the online help text. For more Examples
information about printing the help text, refer to Example 1: Ending Group Job that Issued Command
“Printing CL Command Descriptions” in Chapter 1.
ENDGRPJOB GRPJOB(\) LOG(\PRINT) RSMGRPJOB(GROUPJOB1)
Optional Parameters This command ends the job that is currently running. Its job
log is spooled to an output file for printing. When the job
GRPJOB completes running, group job GROUPJOB1 becomes the
Specifies the group job name of the job that is ended. active job in the group.
*: This special value ends the group job that issued the
ENDGRPJOB command. Example 2: Printing Output of Ended Job
group-job-name: Specify the group job name of the job ENDGRPJOB GRPJOB(GROUPJOB2) LOG(\PRINT)
that is ended.
Assume that the job issuing the ENDGRPJOB command is
RSMGRPJOB group job GROUPJOB1, which wants to end GROUPJOB2.
Specifies the group job name of the job that is to be Group job GROUPJOB2 ends. Its job log is spooled to an
resumed after the active job in the group has ended. output file for printing.
This parameter is valid only when the job that issues this
command is ending itself. Example 3: Ending a Job That's Part of a Secondary Job
Pair
*PRV: The group job most recently active is resumed.
ENDGRPJOB GRPJOB(\) LOG(\NOLIST)
group-job-name: Specify the group job name of the job
that gains control after the active job in the group ends. Assume that the job issuing the ENDGRPJOB command is
the only job in the group and is part of a secondary job pair.
LOG The job issuing the command ends. The job's job log is not
Specifies whether the job log of the ending group is spooled to an output file. When the job ends, the other job
spooled to an output queue. in the secondary job pair is resumed.
(P) ─────────────────────────────────────────────────────────────────────────5%
55──ENDHOSTSVR──SERVER(──┬─\ALL───────────────┬──)────
│ ┌──
─────────────┐ │
6 (1) ─┘
└──┬─\CENTRAL──┬┴───
├─\DATABASE─┤
├─\DTAQ─────┤
├─\FILE─────┤
├─\NETPRT───┤
├─\RMTCMD───┤
├─\SIGNON───┤
└─\SVRMAP───┘
Notes:
| 1 A maximum of 8 repetitions.
P All parameters preceding this point can be specified in positional form.
A request to end *ALL host server daemons will end any Examples
active daemons.
Example 1: Ending All Host Server Daemons
Note: To see the parameter and value descriptions for this ENDHOSTSVR SERVER(\ALL)
command, refer to the online help text. For more
information about printing the help text, refer to This command ends all active server daemons and the
“Printing CL Command Descriptions” in Chapter 1. server mapper daemon. Any active connections to client
applications with the server jobs are unaffected. Ending all
host server daemons prevents any subsequent client con-
Required Parameters nection requests from succeeding.
SERVER
Specifies the server daemons to be ended. Example 2: Ending Specific Server Daemons
*ALL: All of the server daemons and the server mapper ENDHOSTSVR SERVER(\CENTRAL \SVRMAP)
daemon are ended.
This command ends the central server daemon and the
*CENTRAL: The central server daemon in the server mapper daemon. Both daemon jobs run in the
QSYSWRK subsystem, if active, is ended. QSYSWRK subsystem.
55──//ENDINP───────────────────────────────────────────────────────────────────────────────────────────────────────────────────5%
(P)──────────────────────────────────────────────────────────────────────────────5%
55──ENDIPIIFC──INTNETADR(──internet-address──)───
Note:
P All parameters preceding this point can be specified in positional form.
(P)──────────────────────────────────────────────────────────────────────────────5%
55──ENDIPSIFC──INTNETADR(──internet-address──)───
Note:
P All parameters preceding this point can be specified in positional form.
Purpose INTNETADR
Specifies the internet address of an active (started) inter-
The End IP over SNA Interface (ENDIPSIFC) command is face that had previously been added to the IP SNA con-
used to end an AF_INET sockets over SNA interface (an IP figuration with the Add IP over SNA Interface
address by which this local host is known on the SNA trans- (ADDIPSIFC) CL command. The internet address is
port). specified in the form nnn.nnn.nnn.nnn, where nnn is a
Note: Ending an interface causes all routes associated with decimal number ranging from 0 through 255. If the
this interface to be deactivated immediately unless internet address is entered from a command line, the
there are other active interfaces that the routes can address must be enclosed in apostrophes.
switch to.
Note: To see the parameter and value descriptions for this Example
command, refer to the online help text. For more
ENDIPSIFC INTNETADR('9.5.1.248')
information about printing the help text, refer to
“Printing CL Command Descriptions” in Chapter 1. This command deactivates (ends) the interface with IP
address 9.5.1.248 and
Required Parameter
55──ENDIPX─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────5%
(P) ───────────────────────────────────────────────────────────────────────────5%
55──ENDIPXCCT──CCTNAME(────IPX-circuit-name────)────
Note:
P All parameters preceding this point can be specified in positional form.
55──ENDJOB──JOB(────┬─────────────────────────────┬──job-name────)──┬─────────────────────────┬─────────────────────────────────5
└─┬─────────────┬──user-name/─┘ │ ┌─\CNTRLD─┐ │
└─job-number/─┘ └─OPTION(──┴─\IMMED──┴──)─┘
(P) ──┬────────────────────────────────────────┬────────────────────5
5──┬─────────────────────────────┬──┬───────────────────────┬───
│ ┌─3ð─────────┐ │ │ ┌─\NO──┐ │ │ ┌─\SAME──────────────────┐ │
(1) ─┴─delay-time─┴──)─┘ └─SPLFILE(──┴─\YES─┴──)─┘
└─DELAY(─── └─LOGLMT(──┼─\NOMAX─────────────────┼──)─┘
└─maximum-logged-entries─┘
5──┬─────────────────────────────┬──┬────────────────────────────┬─────────────────────────────────────────────────────────────5%
│ ┌─\NONE───┐ │ │ ┌─\SELECT─┐ │
└─ADLINTJOBS(──┼─\GRPJOB─┼──)─┘ └─DUPJOBOPT(──┴─\MSG────┴──)─┘
└─\ALL────┘
Notes:
1 This parameter is valid only when OPTION(*CNTRLD) is specified.
*IMMED: The job ends immediately and the system per- 1. If the value specified is greater than the number of
forms end-of-job cleanup. System cleanup can take messages written at the time the command is
from a brief amount of time to several minutes. issued, messages continue to be written until the
new limit is reached.
Note: This value is recommended only if specifying the
*CNTRLD value has been unsuccessful. When 2. If the value specified is less than the number of
you specify the *IMMED value, you can get messages already written to the spooled file, a
undesirable results, for example, from data that message indicating that the limit has been reached
has been partially updated. is immediately put in the spooled file as the last
entry. The remaining messages on the queue are
DELAY
ignored.
Specifies the amount of time (in seconds) that the job
has to complete its end-of-job processing during a con- 3. If 0 (zero) is specified before any messages are
trolled end. If the end-of-job processing is not com- written to the spooled file, no job log is produced for
pleted before the end of the delay time, the job is ended the job that is ending.
immediately, and only system cleanup is performed.
*SAME: The value does not change. If no logging limit
The delay time does not start until the job becomes has been established previously for the job, the system
active if the job is suspended because of one of the fol- uses the *NOMAX value.
lowing conditions:
*NOMAX: There is no maximum number of message
The system request option 1 is selected. entries logged. All messages on the job message queue
The job is held by the Hold Job (HLDJOB) are written to the job log.
command. maximum-logged-entries: Specify the maximum number
The job is transferred by the Transfer Secondary of messages written to the job log.
Job (TFRSECJOB) command.
The job is transferred by the Transfer Group Job ADLINTJOBS
(TFRGRPJOB) command. Specifies whether additional interactive jobs associated
with the job specified in the JOB parameter are being
Note: This parameter is valid only when ended. The additional interactive jobs can be group jobs
OPTION(*CNTRLD) is specified. or all jobs associated with the work station (group and
30: A maximum delay time of 30 seconds is allowed for secondary jobs) where the job specified in the JOB
cleanup before the job is ended. parameter is running. The job specified in the JOB
parameter does not have to be the active job. A job
delay-time: Specify the maximum amount of delay time name entered on the JOB parameter must resolve to a
(in seconds) before the job is ended. Valid values range
single interactive job for this parameter to be used. If
from 1 through 999999 seconds. For additional informa-
the job is not an interactive job, an error message is
tion on the use of the DELAY parameter for ending an
sent.
end-of-file delay job, refer to the EOFDLY (End of File
Delay) parameter of the Override Database File *NONE: Only the job specified in the JOB parameter is
(OVRDBF) command. ended.
*GRPJOB: If the job specified in the JOB parameter is
SPLFILE
a group job, all jobs associated with the group are
Specifies whether to delete the spooled files created by
ended. If the job is not a group job, the job specified in
this job. Regardless of whether the spooled files are
the JOB parameter is ended.
deleted, the job logs related to the spooled files are kept.
*ALL: All interactive jobs running on the work station
*NO: The spooled files are not deleted. They are kept
associated with the job specified in the JOB parameter
for normal processing by a writer.
are ended, including group jobs and secondary jobs.
*YES: The spooled files are deleted.
DUPJOBOPT
LOGLMT Specifies the action taken when duplicate jobs are found
Specifies the logging limit, which is the maximum by this command.
number of message entries that are written to the job log
*SELECT: The selection display is shown when dupli-
printer file (QPJOBLOG) from the message queue of an
cate jobs are found during an interactive session. Other-
ending job.
wise, a message is issued.
If a job to be ended with this command is already
*MSG: A message is issued when duplicate jobs are
ending, the value specified on this parameter can
found.
change the logging limit of the job that is ending. The
following are examples of how the logging limit can be
changed: Examples
Example 1: Ending a Job Immediately
(P) ─┬────────────────────────────┬───────────────────────5%
55──ENDJOBABN──JOB(────┬─────────────────────────────┬──job-name────)────
└─┬─────────────┬──user-name/─┘ │ ┌─\SELECT─┐ │
└─job-number/─┘ └─DUPJOBOPT(──┴─\MSG────┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose Before ending the job abnormally, you should verify that
no logical unit of work is in an in doubt state due to a
The End Job Abnormal (ENDJOBABN) command ends a job two-phase commit operation that is in progress. If it is,
that cannot be ended successfully by running the End Job then pending committable changes at this system will
(ENDJOB) command with OPTION(*IMMED) specified. The not be committed or rolled back. Therefore, database
ENDJOBABN command cannot be issued against a job until integrity may not be maintained on all related systems.
10 minutes have passed following the request for immediate For specific instructions on how to determine these con-
ending. This allows sufficient time for normal job ending ditions, and for a description of all the impacts of ending
functions to occur. this job abnormally under these conditions, see the
Backup and Recovery book.
When the ENDJOBABN command is issued, most of the
end-of-job processing is bypassed (including spooling of the Making database files available for use by others
job log, the end of job display for interactive jobs, and the Releasing file locks
end-of-job processing for the specific functions that are being
performed). The part of the end-of-job processing that is This command fails to end a job or takes more than five
attempted is allowed only five minutes to complete. If it does minutes to do so in the following situations:
not do so in five minutes, the job is forced to end at that When the job runs under a subsystem monitor that is
point. Because some of the job cleanup is not performed, hung, is abnormally slow, or has ended abnormally (the
the ENDJOBABN command should only be used when a job subsystem monitor performs part of the ending function).
that is in the process of immediate ending does not finish
ending and resources in use by the job are needed by When the machine interface (MI) instruction running in
another job or by the system. When the ENDJOBABN the job is hung or is abnormally slow. The job cannot
command is used, some resources in use by the ended job end until the MI instruction that is currently running com-
may be left unavailable until the next IPL. pletes or reaches a point of interruption.
system in which the job is running and the delay More information on this parameter is in Appendix A,
time ends “Expanded Parameter Descriptions.”
When the End Subsystem (ENDSBS) command job-name: Specify the name of the job to be ended.
with OPTION(*IMMED) is issued against the sub-
user-name: Specify the name of the user of the job to
system in which the job is running
be ended.
When the End System (ENDSYS) command with
job-number: Specify the number of the job to be ended.
OPTION(*IMMED) is issued, or OPTION(*CNTRLD)
is issued and the delay time ends DUPJOBOPT
Specifies the action taken when duplicate jobs are found
Note: To see the parameter and value descriptions for this
by this command.
command, refer to the online help text. For more
information about printing the help text, refer to *SELECT: The selection display is shown when dupli-
“Printing CL Command Descriptions” in Chapter 1. cate jobs are found during an interactive session. Other-
wise, a message is issued.
Required Parameters *MSG: A message is issued when duplicate jobs are
found.
JOB
Specifies the name of the job to be ended. If no job
qualifier is given, all of the jobs currently in the system Example
are searched for the simple job name. If more than one ENDJOBABN JOB(ððð31ð/SMITH/PAYROLL)
of the specified names are found, a qualified job name
must be specified to distinguish them. This command ends the batch job 000310/SMITH/PAYROLL
after the failure of an earlier attempt to end it with the
A job identifier is a qualified name with up to three ele-
ENDJOB command. The ENDJOBABN command can be
ments. For example:
issued only after waiting at least ten minutes for the job to
job-name end after issuing the ENDJOB command.
user-name/job-name
job-number/user-name/job-name
(P) ───────────5%
55──ENDJRNAP──FILE(──┬─\ALL────────────────────────────────┬──)──┬──────────────────────────────────────────────┬───
│ ┌──
──────────────────────────────┐ │ │ ┌─\FILE───────────────────────────┐ │
│ │ ┌─\LIBL/────────┐ │ │ │ │ ┌─\LIBL/────────┐ │ │
└──6─┼───────────────┼──file-name─┴───
(1) ─┘ └─JRN(──┴─┼───────────────┼──journal-name─┴──)─┘
├─\CURLIB/──────┤ ├─\CURLIB/──────┤
└─library-name/─┘ └─library-name/─┘
Notes:
1 A maximum of 50 repetitions
(P) ───────────5%
55──ENDJRNPF──FILE(──┬─\ALL────────────────────────────────┬──)──┬──────────────────────────────────────────────┬───
│ ┌──
──────────────────────────────┐ │ │ ┌─\FILE───────────────────────────┐ │
│ │ ┌─\LIBL/────────┐ │ │ │ │ ┌─\LIBL/────────┐ │ │
└──6─┼───────────────┼──file-name─┴───
(1) ─┘ └─JRN(──┴─┼───────────────┼──journal-name─┴──)─┘
├─\CURLIB/──────┤ ├─\CURLIB/──────┤
└─library-name/─┘ └─library-name/─┘
Notes:
1 A maximum of 50 repetitions
Restrictions:
Optional Parameter
1. Members in the files specified on the command cannot
be in use for any reason at the time the command is JRN
running. Specifies the qualified name of the journal to which
changes in the files are currently being journaled.
2. Overrides are not applied to the files listed in the FILE
parameter. *FILE: The journal is determined by the system from
the specified file names.
3. If FILE(*ALL) is specified, a journal name must be speci-
fied. The name of the journal can be qualified by one of the
following library values:
4. If a journal name and a list of file names are specified,
all files must be currently journaled to the indicated *LIBL: All libraries in the job's library list are
journal. searched until the first match is found.
| 5. This command cannot be used on or with a remote *CURLIB: The current library for the job is
| journal. searched. If no library is specified as the current
Note: To see the parameter and value descriptions for this library for the job, the QGPL library is used.
command, refer to the online help text. For more library-name: Specify the name of the library to be
information about printing the help text, refer to searched.
“Printing CL Command Descriptions” in Chapter 1.
journal-name: Specify the name of the journal to which
the indicated files are currently being journaled.
Required Parameter
FILE Example
Specifies a maximum of 50 qualified names of the phys- ENDJRNPF FILE(MYLIB/MYFILE)
ical files for which changes are no longer being jour-
naled. This command stops the journaling of all changes to all
members of file MYFILE in library MYLIB. Changes made
after this command is run are not journaled.
(P) ─────────────────────────────────────────────────────────────────────────────────────────5%
55──ENDLINRCY──LINE(──line-name──)────
Note:
P All parameters preceding this point can be specified in positional form.
(P) ─┬──────────────────────────┬──┬─────────────────────────┬──────────────────5
55──ENDMOD──RMTLOCNAME(──remote-location-name──)────
│ ┌─\LOC────────┐ │ │ ┌─\NETATR───┐ │
└─DEV(──┴─device-name─┴──)─┘ └─MODE(──┼─\ALL──────┼──)─┘
├─BLANK─────┤
└─mode-name─┘
5──┬─────────────────────────────────────────┬──┬─────────────────────────────────────┬──┬─────────────────────────┬───────────5%
│ ┌─\LOC────────────────┐ │ │ ┌─\LOC──────────────┐ │ │ ┌─\NO──┐ │
└─LCLLOCNAME(──┼─\NETATR─────────────┼──)─┘ └─RMTNETID(──┼─\NETATR───────────┼──)─┘ └─CPLPNDRQS(──┴─\YES─┴──)─┘
└─local-location-name─┘ ├─\NONE─────────────┤
└─remote-network-ID─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose MODE
Specifies the mode that is ended.
The End Mode (ENDMOD) command ends (deactivates) a
*NETATR: The mode name specified in the network
single mode or all active modes for a specific advanced
attributes is used.
program-to-program communications (APPC) remote
location. The mode remains inactive until a Start Mode *ALL: All modes currently active by the remote location
(STRMOD) command is run to start the mode. This are ended.
command can be used to end all the sessions for a particular BLANK: The mode name consisting of 8 blank charac-
remote location and to cause an active switched connection ters is used.
to disconnect. The user can also specify how activities that
have been requested on the remote system but have not yet mode-name: Specify a mode name for the device.
been performed are to be handled. LCLLOCNAME
Specifies the local location name.
The APPC Programming book has more information on the
ENDMOD command. *LOC: The device associated with the remote location
is used. If several devices are associated with the
Restriction: This command cannot be used to end (deacti- remote location, the system determines which device is
vate) Client Access/400 mode (QPCSUPP) at a remote used.
location.
*NETATR: The LCLLOCNAME value specified in the
Note: To see the parameter and value descriptions for this system network attributes is used.
command, refer to the online help text. For more
local-location-name: Specify the local location name.
information about printing the help text, refer to
“Printing CL Command Descriptions” in Chapter 1. RMTNETID
Specifies the remote network ID used with the remote
location.
Required Parameters
*LOC: The remote network identifier (ID) associated
RMTLOCNAME with the remote location is used. If several remote
Specifies the remote location name for one or more network IDs are associated with the remote location, the
modes which are being ended. system determines which remote network ID is used.
*NETATR: The LCLLOCNAME value specified in the
Optional Parameters system network attributes is used.
DEV *NONE: No remote network identifier (ID) is used.
Specifies the device description name used with the remote-network-ID: Specify the name of the remote
remote location. network ID used.
*LOC: The device associated with the remote location
CPLPNDRQS
is used. If several devices are associated with the
Specifies how the remote location processes all pending
remote location, the system determines which device is
user work before ending the mode.
used.
*NO: Requested activities currently in progress at the
device-name: Specify the name of the device for which
remote location can complete; activities that have been
one or more modes are being ended.
requested, but not started at the remote location will not Example
be performed.
ENDMOD RMTLOCNAME(APPCRLOC) MODE(APPCMOD)
*YES: All requested activities are allowed to complete
before the mode is ended. This command ends a mode named APPCMOD for remote
location APPCRLOC.
(P) ──────────────────────────────────────────────────────5%
55──ENDMSF──┬─────────────────────────┬──┬───────────────────────────┬───
│ ┌─\CNTRLD─┐ │ │ ┌─3ð─────────┐ │
└─OPTION(──┴─\IMMED──┴──)─┘ └─DELAY(──┴─delay-time─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
┌─\LIBL/────────┐
(P) ────────────────────────────────────────────────5%
55──ENDM36──M36(──┼───────────────┼──machine-name──)──┬────────────────────┬───
├─\CURLIB/──────┤ │ ┌─\NO──┐ │
└─library-name/─┘ └─DUMP(──┴─\YES─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
┌─\ALL─┐
(P) ─┬─────────────────────────────────────┬────────────────────────────────────────────────5%
55──ENDNFSSVR──SERVER(──┼─\RPC─┼──)────
├─\BIO─┤ │ ┌─3ð──────────────┐ │
├─\SVR─┤ └─ENDJOBTIMO(──┼─\NOMAX──────────┼──)─┘
├─\MNT─┤ └─'timeout-value'─┘
├─\NSM─┤
└─\NLM─┘
Note:
P All parameters preceding this point can be specified in positional form.
You should use SERVER(*ALL), which will end the daemons *RPC: The NFS Remote Procedure Call (RPC) binder
in the following order. (This order is the recommended order daemon is ended.
for ending the Network File System daemons.) *BIO: All NFS block I/O daemons that are running are
The network lock manager (NLM) daemon ended.
The network status monitor (NSM) daemon *SVR: All NFS server daemons that are running are
The mount (MNT) daemon ended.
The server (SVR) daemon
*MNT: The NFS mount daemon is ended.
The block I/O (BIO) daemon
The Remote Procedure Call (RPC) binder daemon *NSM: The NFS network status monitor daemon is
ended.
If you are choosing to end just one daemon, be sure you
understand the appropriate order for ending NFS daemons *NLM: The NFS network lock manager daemon is
and the possible consequences of ending deamons in an ended.
order other than that specified above. For more information
about ending NFS daemons, see the OS/400 Network File
System Support book.
Optional Parameter
ENDJOBTIMO
If you attempt to end a daemon or daemons that are not Specifies the number of seconds to wait for each
running, they will not cause the command to fail, and it will daemon to successfully end. If a daemon has not ended
continue to end other daemons you have requested to end. within the timeout value, the command will fail.
To determine if an NFS daemon is running, use the Work 30: Wait 30 seconds for the daemon job to end.
with Active Jobs (WRKACTJOB) command and look in the *NOMAX: Wait forever for daemons to end; do not
subsystem QSYSWRK for existence of the following jobs: timeout.
QNFSRPCD The RPC binder daemon
timeout-value: Specify the number of seconds to wait
QNFSBIOD The block I/O (BIO) daemon
QNFSNFSD The server (SVR) daemon for each daemon to end before timing out and failing the
QNFSMNTD The mount (MNT) daemon command. Valid values range from 1 to 3600 seconds.
QNFSNSMD The network status monitor (NSM) daemon
QNFSNLMD The network lock manager (NLM) daemon
Examples
Restriction: You must have *IOSYSCFG special authority
Example 1: End All Daemons
to use this command.
ENDNFSSVR SERVER(\ALL)
Note: To see the parameter and value descriptions for this
command, refer to the online help text. For more This command ends all NFS daemon jobs that are running.
information about printing the help text, refer to
“Printing CL Command Descriptions” in Chapter 1. Example 2: End a Single Daemon
ENDNFSSVR SERVER(\MNT) ENDJOBTIMO(\NOMAX)
This command ends the NFS mount daemon, and waits running, and other daemons have been ended in the appro-
forever for it to end. The mount daemon was previously priate order.
(P) ────────────────────────────────────────────────────────────5%
55──ENDNWIRCY──NWID(────network-interface-description-name────)────
Note:
P All parameters preceding this point can be specified in positional form.
(P) ─┬─────────────────────────┬───────────────────────────5
55──ENDNWSAPP──NWSAPP(──┬─\NOTES────┬──)──NWS(────network-server────)────
├─\FIREWALL─┤ │ ┌─\CNTRLD─┐ │
└─\FLOWMARK─┘ └─OPTION(──┴─\IMMED──┴──)─┘
5──┬───────────────────────────┬──┬────────────────────────────┬──┬─────────────────────────────────────────┬───────────────────5
│ ┌─3ð─────────┐ │ │ ┌─\ALL─────┐ │ │ ┌─EXMDB──────────────────┐ │
(1) ─┼─\NTSSVR──┼──)─┘ └─FLMDB(───
└─DELAY(──┴─delay-time─┴──)─┘ └─NTSFCN(─── (2) ─┴─FlowMark-database-name─┴──)─┘
├─\MAIL────┤
├─\DIRSHD──┤
├─\DBINTEG─┤
└─\CALCNN──┘
5──┬─────────────────────────┬─────────────────────────────────────────────────────────────────────────────────────────────────5%
│ ┌─\YES─┐ │
(2) ─┴─\NO──┴──)─┘
└─FLMOSDB(───
Notes:
1 This parameter is valid only when NWSAPP(*NOTES) is specified.
NWS NTSFCN
Specifies the name of the network server on which the Specifies which Lotus Notes functions are to be ended.
application is currently started. Note: This parameter is valid only when
NWSAPP(*NOTES) is specified.
Optional Parameters *ALL: The Notes server and all IBM AS/400 integration
functions are ended.
OPTION
Specifies that the integration function is either ended in a *NTSSVR: The Notes server is ended. The mail inte-
controlled manner, which lets the program perform end- gration function is also ended if it is active.
of-job processing, or it is ended immediately. In either *MAIL: The IBM AS/400 mail integration function is
ended. The Notes server is not ended.
*DIRSHD: The IBM AS/400 directory shadowing inte- *NO: Do not end the ObjectStore database server.
gration function is ended. The Notes server is not
ended.
*DBINTEG: The IBM DB2 for OS/400 integration func- Examples
tion is ended. The Notes server is not ended.
Example 1: Ending the Lotus Notes Server Application
*CALCNN: The IBM Lotus calendar conversion for
ENDNWSAPP NWSAPP(\NOTES) NWS(DEPT44C)
office vision integration function is ended. The Notes
server is not ended. This command ends the Lotus Notes server application on
FLMDB the network server named DEPT44C in a controlled manner.
Specifies the name of the FlowMark database to be The IBM AS/400 mail, directory shadowing, and DB2 for
ended. OS/400 integration functions are also ended.
Note: This parameter is valid only when Example 2: Ending the Firewall Server Application
NWSAPP(*FLOWMARK) is specified. ENDNWSAPP NWSAPP(\FIREWALL) NWS(FIREWALL)
EXMDB: The EXMDB database is ended.
This command ends the Firewall server application on the
FlowMark-database-name: Specify the name of a network server named FIREWALL.
FlowMark database to be ended.
Example 3: Ending the FlowMark Server Application
FLMOSDB
Specifies that the FlowMark ObjectStore server is to be ENDNWSAPP NWSAPP(\FLOWMARK) NWS(FMSVR) OPTION(\CNTRLD)
ended. FLMOSDB(\YES)
Note: This parameter is valid only when This command ends the FlowMark server application and
NWSAPP(*FLOWMARK) is specified. FlowMark database EXMDB on network server FMSVR in a
*YES: End the ObjectStore database server. controlled manner.
(P) ─────────────────────────────────────────────────────────────────────────────────────5%
55──ENDPASTHR──┬──────────────────────┬───
│ ┌─\NOLIST─┐ │
└─LOG(──┴─\LIST───┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
(P) ──┬──────────────────────────┬──┬─────────────────────────┬─────────────────5
55──ENDPEX──┬───────────────────────────────────┬───
│ (1) ─────────┐
┌─\SELECT─── │ │ ┌─\END─────┐ │ │ ┌─\LIB──┐ │
└─SSNID(──┴─session-identifier─┴──)─┘ (2) ─┼─\FILE─┼──)─┘
└─OPTION(──┴─\SUSPEND─┴──)─┘ └─DTAOPT(───
└─\DLT──┘
5──┬───────────────────────────────────────┬──┬──────────────────────────────────────┬──────────────────────────────────────────5
│ ┌─QPEXDATA──────────┐ │ │ ┌─\SSNID───────────┐ │
(2, 3) ─┴─data-library-name─┴──)─┘ └─DTAMBR(─────
└─DTALIB(───── (2, 3) ─┴─data-member-name─┴──)─┘
5──┬────────────────────────────────────────────────────────────┬──┬────────────────────────┬──┬──────────────────────────┬────5%
│ ┌─QPEXDATA──────────┐ ┌─\SSNID─────────┐ │ │ ┌─\NO──┐ │ │ ┌─\BLANK────────┐ │
(2, 4) ─┴─data-library-name─┴──┴─data-file-name─┴──)─┘ └─RPLDTA(───
└─DTAFILE(───── (2) ─┴─\YES─┴──)─┘ └─TEXT(──┴─'description'─┴─┘
Notes:
1 *SELECT is only valid if ENDPEX command is being run interactively.
*FILE: All of the collected performance data for the data-library-name: Specify the name of the library to
session is stored in a single physical file. This option is store the collected data. If the library does not exist, the
used if the collected information will be sent to IBM for command will terminate in an error condition. After the
analysis. library is created, retry the command.
*DLT: The collected performance data for the session is *SSNID: The name specified for the SSNID parameter
to be deleted from the system. is used when creating the file to contain the collected
performance data.
DTALIB
Specifies the name of the library that contains the set of data-file-name: Specify the name to use when creating
database files where the collected performance data is the file to contain the collected performance data.
stored.
RPLDTA
Note: This parameter is valid only if the user specified Specifies whether to replace the data in an existing file
DTAOPT(*LIB). member with the new performance data. If DTAMBR
was specified and a member with the same name
QPEXDATA: The QPEXDATA library is the recom-
already exists in any of the performance explorer data-
mended library for storing data collected with the perfor-
base files in the specified library (DTALIB parameter),
mance explorer tool. The first time the performance
this parameter controls whether the member data is
explorer tool is used, this library is created for the user,
replaced. If DTAFILE was specified, the file already
and a set of database files to store the information is
exists, and the file has a member with the same name
created in that library.
as the file, this parameter controls whether the data in
library-name: Specifies the name of the library in which that file member is replaced.
to store the collected data. If the library does not exist,
*NO: If a member already exists with the same name,
the command will terminate in an error condition. After
an error message is sent to the user. This prevents the
the library is created, retry the command. If the library
user from inadvertently writing over existing data.
specified does not already have the performance
explorer database files, they are created and the data is *YES: If a member already exists with the same name,
stored. the old data is lost and is replaced by the new data.
DTAMBR TEXT
Specifies the name to be used for the database file Specifies the text that briefly describes the type of data
members where the collected performance data is collected. More information on this parameter is in
stored. If a member does not exist by the specified Appendix A, “Expanded Parameter Descriptions.”
name, it is created.
*BLANK: Text is not specified.
Note: This parameter is valid only when DTAOPT(*LIB)
'description': Specify no more than 50 characters of text,
is specified.
enclosed in apostrophes.
*SSNID: The member name is the same as the value
specified for the SSNID parameter.
Examples
member-name: Specify the member name to use when
storing the collected data in performance explorer data- Example 1: End a Session and Save the Data
base files. ENDPEX SSNID(TEST3) OPTION(\END)
DTAFILE DTAOPT(\LIB) DTAMBR(SYS1DATA)
Specifies the name of a database physical file to store
This command ends the performance explorer session
the collected performance data. If a file does not exist
named TEST3 and saves the data in a set of database files
by the specified name, it is created.
in library QPEXDATA. The member name to be used for
Note: This parameter is valid only if DTAOPT(*FILE) is each file is SYS1DATA.
specified.
Example 2: End a Session and Delete the Data
QPEXDATA: The QPEXDATA library is the recom-
mended library for storing data collected by the perfor- ENDPEX SSNID(TESTRUN) OPTION(\END) DTAOPT(\DLT)
mance explorer tool. The first time the performance
This command ends the performance explorer session
explorer tool is used, this library is created for the user.
named TESTRUN and deletes the collected performance
data.
55──ENDPFRCOL──────────────────────────────────────────────────────────────────────────────────────────────────────────────────5%
Purpose Example
ENDPFRCOL
The End Performance Collection (ENDPFRCOL) command
stops the automatic collection of performance data that is This command stops the collection of performance data.
defined on the Work with Performance Collection
(WRKPFRCOL) command.
(P) ──────────────────────────5%
55──ENDPFRMON──┬───────────────────────┬──┬──────────────────────────────────────────────────────┬───
│ ┌─\SAME─┐ │ │ ┌─\SAME───────────────────────────────┐ │
└─DMPTRC(──┼─\YES──┼──)─┘ └─EXITPGM(──┼─\NONE───────────────────────────────┼──)─┘
└─\NO───┘ │ ┌─\LIBL────────┐ │
└─┼──────────────┼──user-exit-program─┘
├─\CURLIB──────┤
└─library-name─┘
Note:
P All parameters preceding this point can be specified in positional form.
55──ENDPGM─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────5%
┌─\LIBL/────────┐
55──ENDPJ──SBS(──subsystem-name──)──PGM(──┼───────────────┼──program-name──)──┬─────────────────────────┬───────────────────────5
├─\CURLIB/──────┤ │ ┌─\CNTRLD─┐ │
└─library-name/─┘ └─OPTION(──┴─\IMMED──┴──)─┘
(P) ──┬────────────────────────────────────────┬─────────────────────5%
5──┬───────────────────────────┬──┬───────────────────────┬───
│ ┌─3ð─────────┐ │ │ ┌─\NO──┐ │ │ ┌─\SAME──────────────────┐ │
└─DELAY(──┴─delay-time─┴──)─┘ └─SPLFILE(──┴─\YES─┴──)─┘ └─LOGLMT(──┼─\NOMAX─────────────────┼──)─┘
└─maximum-logged-entries─┘
Note:
P All parameters preceding this point can be specified in positional form.
of the delay time, the job is immediately ended. (Only rest of the messages on the queue are ignored. If the
end-of-job processing is performed.) limit is set to zero before any messages are written to
the spooled file, no job log is produced for the ended
30: Up to 30 seconds of delay time is allowed for
job.
cleanup before the job is ended.
*SAME: The value does not change.
delay-time: Specify the maximum delay time (in
seconds) before the job is ended. Valid values range *NOMAX: There is no limit on the number of messages
from 1 through 999999 seconds. For additional informa- being logged. Messages on each job message queue
tion on ending an end-of-file delay job, refer to the are written to the log of each job.
EOFDLY parameter in the Override Database File
maximum-logged-entries: Specify the maximum number
(OVRDBF) command description.
of messages being written to the job log for each job.
SPLFILE This value is the maximum if it is entered before the job
Specifies whether spooled files created by the job are log contains that many messages. Otherwise, the limit
retained for normal processing by a writer or are deleted. merely stops the process of writing any more messages
to the job log. If zero is specified before any messages
*NO: The spooled files created by the job being ended
are written to the log, no job log is produced.
are retained for normal processing by a writer.
*YES: The spooled files created by the job being ended
are deleted. The job log is not deleted.
Examples
LOGLMT Example 1: Ending a Job Immediately
Specifies the maximum number of entries in the ENDPJ SBS(SBS1) PGM(PJLIB/PJPGM) OPTION(\IMMED)
message queue of the job being ended that are written SPLFILE(\YES)
to the job log. This parameter can be used to limit the
number of messages written to the job log printer file, This command ends all jobs associated with prestart job
QPJOBLOG, for a job that is ended. This option is par- entry PJPGM in subsystem SBS1 immediately. Spooled
ticularly useful when a job is ended and its message output produced by these prestart jobs is deleted and the job
queue contains an excessive number of entries. log is saved.
If this command is used to change the message logging Example 2: Delaying a Job End
limit while the messages for the ended job are being
ENDPJ SBS(SBS2) PGM(PJPGM2) OPTION(\CNTRLD)
written to the spooled file, and if the new limit is greater
DELAY(5ð) SPLFILE(NO)
than the number written at the time the command is
entered, messages continue to be written until the new This command ends all the jobs associated with prestart job
limit is reached. If the new limit is less than the number entry PJPGM2 in subsystem SBS2. Spooled output for
of messages already written to the spooled file, a these prestart jobs is saved for normal processing by the
message indicating that the limit is reached is imme- spooling writer. The jobs have 50 seconds to perform any
diately put in the spooled file as the last entry, and the cleanup routines, after which they are immediately ended.
(P) ────────────────────────────────────────────5%
55──ENDPRTEML──┬─EMLDEV(──emulation-device-description-name──)─────────────────┬───
└─EMLLOC(──emulation-location-name──)──PRTDEV(──printer-name──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
(P) ────────────────────────────────────────────────────────────────────────────────────5%
55──ENDRCV──┬──────────────────────────┬───
│ ┌─\FILE───────┐ │
└─DEV(──┴─device-name─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose DEV
Specifies the name of the display device for which the
The End Receive (ENDRCV) command is used to end request for input is being ended.
(cancel) a request for input made by a previously issued
*FILE: The name of the device having the response
Receive File (RCVF) or Send/Receive File (SNDRCVF)
from it ended is contained in the device file that was
command that had WAIT(*NO) specified. The ENDRCV
declared in the FILE parameter of the Declare File
command ends an input request even if the user enters the
(DCLF) command. If the device file has more than one
requested data at the display station at the same time that
device name specified in it, *FILE cannot be specified.
the command is processed. If the requested data is entered
and is being sent to the program when the end receive oper- device-name: Specify the name of the display device
ation is performed, the entered data is lost. If there is no from which a response is being ended.
outstanding input request, the command is ignored.
(P) ───────────────────────────────────────────────────────────────5%
55──ENDRDR──RDR(──reader-name──)──┬─────────────────────────┬───
│ ┌─\CNTRLD─┐ │
└─OPTION(──┴─\IMMED──┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
55──ENDRMTSPT──┬──────────────────────┬────────────────────────────────────────────────────────────────────────────────────────5%
│ ┌─\NO──┐ │
└─DLTLIB(──┴─\YES─┴──)─┘
(P) ───────────────────────────────────────────────────────────────────────────────5%
55──ENDRQS──┬───────────────────────────────┬───
│ ┌─\PRV──────────┐ │
└─RQSLVL(──┴─request-level─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
(1) ──)──┬─────────────────────────┬───
55──ENDSBS──SBS(──┬─\ALL───────────┬─── (P) ──┬───────────────────────────┬───────────────────────5
└─subsystem-name─┘ │ ┌─\CNTRLD─┐ │ │ ┌─\NOLIMIT───┐ │
└─OPTION(──┴─\IMMED──┴──)─┘ └─DELAY(──┴─delay-time─┴──)─┘
5──┬─────────────────────────────────────────┬─────────────────────────────────────────────────────────────────────────────────5%
| │ ┌─\DFT─────────────────┐ │
| │ │ ┌──
───────────────┐ │ │
| 6 (2)
└─ENDSBSOPT(──┴───┬─\NOJOBLOG─┬─┴────┴──)─┘
| ├─\CHGPTY───┤
| └─\CHGTSL───┘
Notes:
1 SBS(*ALL) is not valid in a pass-through job or in a work station function job.
| 2 A maximum of 3 repetitions
cleanup (end of job processing). The applications have | *NOJOBLOG: No joblogs will be created for jobs that
the amount of time specified on the DELAY parameter to | are ended due to this command being invoked. This
complete cleanup before the job is ended. | includes subsystem monitor jobs and all user jobs in the
| subsystem. This option can significantly reduce the
*IMMED: The jobs are ended immediately and the
| amount of time necessary to complete the ENDSBS
system performs end-of-job cleanup. System cleanup
| command. However, if a problem occurs in a job, there
can take from a brief amount of time to several minutes.
| will be no joblog to record the problem, which may make
Note: This value is recommended only if specifying the | problem diagnosis difficult or impossible.
*CNTRLD value has been unsuccessful. When
| *CHGPTY: The CPU priority of jobs that are ending is
you specify the *IMMED value, you can get
| changed to a higher value (worse priority). The
undesirable results, for example, from data that
| remaining active jobs on the system may have better
has been partially updated.
| performance when *CHGPTY is specified. However,
DELAY | jobs that are ending may take longer to finish. This
Specifies the amount of time (in seconds) allowed in | option is ignored if the subsystem is ending controlled.
which to complete a controlled subsystem end operation. | But if the DELAY time limit expires, this option will take
If this amount of time is exceeded, any jobs still running | affect immediately.
in the subsystem are ended immediately.
| *CHGTSL: The timeslice of jobs that are ending is
*NOLIMIT: The amount of time in which to complete a | changed to a lower value. The remaining active jobs on
controlled end operation is not limited. | the system may have better performance when
| *CHGTSL is specified. However, jobs that are ending
delay-time: Specify the number of seconds in which the
| may take longer to finish. This option is ignored if the
end operation is completed. Valid values range from 1
| subsystem is ending controlled. But if the DELAY time
through 99999 seconds.
| limit expires, this option will take affect immediately.
| ENDSBSOPT
| Note:Specifying *CHGPTY and *CHGTSL will reduce the
| Specifies the options to take when ending the active
| impact on other active jobs on the system, but this may
| subsystems. In general, specifying these options will
| cause undesirable delays if there are active workstations
| improve the performance of the ENDSBS command.
| that were allocated to the ending subsystem. It may
| Each option has certain side effects that you need to
| take longer for those workstations to have their signon
| analyze before using that option.
| screens re-displayed since the job using the display
| This parameter has no effect on jobs that are already in | must end before the workstation is ready to be allocated
| the ending status. | to another subsystem.
| *DFT: The subsystems will end with no special ending
| options. Example
| Joblogs will be produced. ENDSBS SBS(QBATCH) OPTION(\CNTRLD) DELAY(6ð)
| The run priority will not change. This command ends all active jobs in the QBATCH sub-
| The timeslice value will not change. system and ends the subsystem. The active jobs are
allowed 60 seconds to perform application-provided
end-of-job processing.
55──ENDSRVJOB──────────────────────────────────────────────────────────────────────────────────────────────────────────────────5%
Purpose QPGMR
QSYSOPR
The End Service Job (ENDSRVJOB) command ends the
remote job service operation. This command stops the QSRV
service operation that began when the Start Service Job QSRVBAS
(STRSRVJOB) command was entered.
There are no parameters for this command.
Restrictions:
1. If tracing or debugging is active in the serviced job when
Example
this command is entered, the remote service operation is
not ended. ENDSRVJOB
2. This command is shipped with public *EXCLUDE This command stops the service operation of the job cur-
authority. rently being serviced.
3. The following user profiles have private authorities to
use the command:
(P) ──┬───────────────────────────┬──┬─────────────────────────────────────────┬─────────5%
55──ENDSYS──┬─────────────────────────┬───
| │ ┌─\CNTRLD─┐ │ │ ┌─\NOLIMIT───┐ │ │ ┌─\DFT─────────────────┐ │
| └─OPTION(──┴─\IMMED──┴──)─┘ └─DELAY(──┴─delay-time─┴──)─┘ │ │ ┌──
───────────────┐ │ │
| 6 (1) ─┴──)─┘
└─ENDSBSOPT(──┴───┬─\NOJOBLOG─┬─┴───
| ├─\CHGPTY───┤
| └─\CHGTSL───┘
Notes:
P All parameters preceding this point can be specified in positional form.
| 1 A maximum of 3 repetitions
55──ENDS36─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────5%
Purpose Example
ENDS36
The End System/36 (ENDS36) command allows the user to
end the System/36 Environment session that was started This command immediately ends the System/36 Environment
with a Start System/36 (STRS36) command. session and any programs or procedures that are running in
the System/36 Environment. If the ENDS36 command is in a
There are no parameters for this command.
procedure or in a program, the statements following the
command are ignored.
(P) ──┬──────────────────────┬────────────────5%
55──ENDTCP──┬─────────────────────────┬──┬───────────────────────────────────────┬───
│ ┌─\IMMED──┐ │ └─DELAY(────delay-time,-if-\cntrld────)─┘ │ ┌─\YES─┐ │
└─OPTION(──┴─\CNTRLD─┴──)─┘ └─ENDSVR(──┴─\NO──┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
A job is submitted to the QSYSWRK subsystem that will, It does not notify an application that is actively using
after the time indicated in the DELAY parameter value a TCP/IP connection that TCP/IP processing will be
has expired, do an ENDTCP *IMMED operation. ended.
Applications that use the Pascal API must always Example 2: Ending TCP/IP in a Controlled Time
be ended and restarted whenever TCP/IP pro-
ENDTCP OPTION(\CNTRLD) DELAY(12ð)
cessing is ended and restarted.
*YES The ENDTCP command ends all TCP/IP applica- This command ends all TCP/IP processing after 120 seconds
tion servers prior to ending TCP/IP processing. *NO have expired. During this time, new TCP/IP processing is
The ENDTCP command does not end any TCP/IP appli- not allowed.
cation server jobs when it ends TCP/IP processing.
Example 3: Ending TCP/IP Immediately Without Ending
Note: ENDTCP ENDSVR(*NO) can be used to end TCP/IP Application Servers
processing without disturbing the operation of jobs ENDTCP \IMMED ENDSVR(\NO)
using AnyNet. TCP/IP processing will be ended,
however TCP/IP application servers that are using This command ends all TCP/IP processing on the AS/400
AnyNet will continue to function. system immediately. However, any TCP/IP application
servers (FTP, SMTP, and so on) that are active are not
If both TCP/IP and AnyNet are inactive, use the End ended when TCP/IP processing is ended.
TCP/IP Server (ENDTCPSVR) command to end
TCP/IP application server jobs.
55──ENDTCPCNN──PROTOCOL(──┬─\UDP─┬──)──LCLINTNETA(──┬─\──────────────────────┬──)──LCLPORT(────local-port────)──────────────────5
└─\TCP─┘ └─local-internet-address─┘
(P) ────────────────────────────────────────5%
5──┬─────────────────────────────────────────────┬──┬──────────────────────────────┬───
└─RMTINTNETA(──┬─\───────────────────────┬──)─┘ └─RMTPORT(──┬─\───────────┬──)─┘
└─remote-internet-address─┘ └─remote-port─┘
Note:
P All parameters preceding this point can be specified in positional form.
Examples This command closes the UDP socket using local port 596
and local internet address 9.130.28.144. The TCP/IP pro-
Example 1: Ending a TCP Connection tocol stack ends all activity on the connection and returns the
ENDTCPCNN PROTOCOL(\TCP) resources to the free storage pools.
LCLINTNETA('9.5.1.1ð9') LCLPORT(13ð54)
RMTINTNETA('9.13ð.28.144') RMTPORT(23) Example 3: Ending a LISTEN State TCP Socket
ENDTCPCNN PROTOCOL(\TCP)
This command ends the TCP connection between local port LCLINTNETA(\) LCLPORT(5ð23)
13054 for local internet address 9.5.1.109 and remote port RMTINTNETA(\) RMTPORT(\)
23 for remote internet address 9.130.28.144. The TCP/IP
protocol stack ends all activity on the connection and returns This command ends the TCP socket that is listening on local
the resources to the free storage pools. port 5023. The application that created this socket did not
specify a local internet address. The socket is closed and
Example 2: Closing a UDP Socket the local port is made available for use by another applica-
ENDTCPCNN PROTOCOL(\UDP) tion.
LCLINTNETA('9.13ð.28.144') LCLPORT(596)
(P) ─────────────────────────────────────────────────────────────────────────────5%
55──ENDTCPIFC──INTNETADR(──internet-address──)────
Note:
P All parameters preceding this point can be specified in positional form.
(P) ──────────────────────────────5%
55──ENDTCPPTP──CFGPRF(──┬─\ALL────────────────────────────────┬──)──┬────────────────────────┬───
├─generic\-configuration-profile-name─┤ │ ┌─\ANY──┐ │
└─configuration-profile-name──────────┘ └─OPRMODE(──┼─\ANS──┼──)─┘
└─\DIAL─┘
Note:
P All parameters preceding this point can be specified in positional form.
Examples
Required Parameter
Example 1: End a TCP/IP point-to-point session job.
CFGPRF
ENDTCPPTP CFGPRF(DIALPRF)
Specifies which point-to-point TCP/IP sessions job or
jobs should be ended. This command ends the point-to-point TCP/IP session job
*ALL: All currently active point-to-point TCP/IP sessions that is using configuration profile DIALPRF. The operating
jobs operating in the mode specified by the OPRMODE mode (OPRMODE) value will default to *ANY so the oper-
parameter are ended. ating mode is not used in deciding whether to end the
session job.
generic*-configuration-profile-name: Specify the generic
name of the point-to-point TCP/IP configuration profile. Example 2: End all answer (*ANS) mode TCP/IP point-
A generic name is a character string of one or more to-point session jobs.
characters followed by an asterisk (*); for example,
ABC*. If a generic name is specified, then all profiles ENDTCPPTP CFGPRF(\ALL) OPRMODE(\ANS)
with names that begin with the generic name are ended.
This command ends all active or activating point-to-point
If an asterisk is not included, the name is assumed to be
answer mode (*ANS) TCP/IP session jobs.
a complete point-to-point TCP/IP configuration profile
name. All currently active point-to-point TCP/IP session Example 3: End all TCP/IP point-to-point session jobs.
jobs using the profiles indicated and operating in the
ENDTCPPTP CFGPRF(\ALL)
mode specified by the OPRMODE parameter are ended.
configuration-profile-name: Specify the name of a This command ends all active or activating point-to-point
TCP/IP point-to-point configuration profile. The active TCP/IP session jobs.
point-to-point session job using this profile is ended.
Example 4: End all TCP/IP point-to-point session jobs
starting with XYZ.
Optional Parameter ENDTCPPTP CFGPRF(XYZ\)
OPRMODE
Specifies the operating mode of the TCP/IP point-to- This command ends all active or activating point-to-point
point session job to be ended. This value must match TCP/IP session jobs that have profiles that begin with XYZ.
Example 5: End an answer mode TCP/IP point-to-point This command will end the point-to-point TCP/IP session job
session job using a specific profile name. using profile DIALPRF if this profile is defined to run in
ENDTCPPTP CFGPRF(DIALPRF) OPRMODE(\ANS) answer mode. If the profile is defined to run in dial mode
then no action will be taken.
| *DDM: The program that listens for DDM and DRDA *ADMIN: The administration HTTP server will be ended.
| connect requests and dispatches pre-started jobs to The administration server is an instance of the HTTP
| service them is ended. server that allows administration of certain AS400 func-
tions using a web browser.
*TELNET: All TELNET server jobs are ended.
Example 1: Ending All TCP/IP Servers This command ends the TCP/IP LPD application server jobs.
This command ends all active TCP/IP application server jobs ENDTCPSVR SERVER(\HTTP) HTTPSVR(http1)
running in the QSYSWRK subsystem.
This command ends the TCP/IP HTTP application server
Example 2: Ending the LPD Servers instance named 'http1'.
55──ENDTIESSN──────────────────────────────────────────────────────────────────────────────────────────────────────────────────5%
Purpose Example
ENDTIESSN
The End Technical Information Exchange Session
(ENDTIESSN) command allows the user to disconnect the This command ends the TIE function by disconnecting the
communications line used for TIE batch commands. communications line used for TIE batch commands.
There are no parameters for this command.
55──ENDTRPMGR──────────────────────────────────────────────────────────────────────────────────────────────────────────────────5%
Purpose
The End Trap Manager (ENDTRPMGR) command allows
you to end the OS/400 SNMP Manager Framework trap
manager job.
55──ENDUSF─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────5%
Purpose Example
ENDUSF
The End Ultimedia System Facilities (ENDUSF) command
ends the Ultimedia Facilities server and router programs, This command ends the Ultimedia System Facilities program.
QUMBVSERVR and QUMBVROUTR, in the QSYSWRK sub-
system of the operating system.
(P) ──────────────────────────────────────────────────────────5%
55──ENDWTR──WTR(──┬─\ALL────────┬──)──┬──────────────────────────┬───
├─\SYSVAL─────┤ │ ┌─\CNTRLD──┐ │
└─writer-name─┘ └─OPTION(──┼─\IMMED───┼──)─┘
└─\PAGEEND─┘
Note:
P All parameters preceding this point can be specified in positional form.
(1) ─'object-link-path-name'──)────
55──RMVLNK──OBJLNK(─── (P) ──────────────────────────────────────────────────────────────────────────5%
Notes:
1 You can specify a pattern for this path name.
5──┬───────────────────────────────────────────────────────────────────────────────────────────────────────────┬───────────────5%
│ ┌─\DFT─────────────────────────────────────────────────────────────────────────────────────┐ │
│ │ ┌──
───────────────────────────────────────────────────────────────────────────────────┐ │ │
│ │ │ ┌─\BINARY────────┐ ┌─\ASCII──────────────┐ ┌─\SYNC──┐ │ │ │
6 (3) (4)
└─HOSTOPT(──┴───(────'host-name'────┼─\ASCII─────────┼──┼─\JOBCCSID───────────┼──┴─\ASYNC─┴─────)─┴────┴──)─┘
├─\JOBCCSID──────┤ └─path-name-code-page─┘
└─data-code-page─┘
Notes:
1 A value other than *NONE must be specified for either OPTIONS or DIR.
2 A directory path name is not allowed when '-A' is specified in the OPTIONS parameter value.
3 Write mode
4 A maximum of 10 repetitions.
EXPORTFS Command
For the description of the EXPORTFS command, see the CHGNFSEXP (Change Network File System Export) command
description.
(P) ─┬────────────────────────────────────────────────────────┬─────────────────────────────────5
55──FILDOC──TYPE(──┬─\FILE──┬──)────
├─\IDP───┤ │ ┌─\NONE─────────────────────────────────┐ │
└─\DSTID─┘ │ │ ┌─\LIBL/────────┐ │ │
└─DOCFILE(──┴─┼───────────────┼──database-file-name─┴──)─┘
├─\CURLIB/──────┤
└─library-name/─┘
5──┬─────────────────────────────┬──┬────────────────────────────────┬──┬───────────────────────────────────────────────┬───────5
│ ┌─\FIRST──────┐ │ │ ┌─\NONE───────────┐ │ │ ┌─\NONE─────────────────────┐ │
└─DOCMBR(──┴─member-name─┴──)─┘ └─DSTID(──┴─distribution-ID─┴──)─┘ └─DSTIDEXN(───(1) ─┴─distribution-ID-extension─┴──)─┘
5──┬────────────────────┬──┬────────────────────────────────────────────────────────────────────┬───────────────────────────────5
│ ┌─\NO──┐ │ │ ┌─\NONE────────────────┐ ┌─\ENDOFDAY────────────┐ │
└─KEEP(──┼─\YES─┼──)─┘ └─DSTEXPDATE(──┼─\CURRENT─────────────┼──┴─dist-expiration-time─┴──)─┘
└─\REF─┘ └─dist-expiration-date─┘
5──┬──────────────────────────────────────┬──┬──────────────────────────────┬──┬────────────────────────────┬───────────────────5
│ ┌─\CURRENT──────────────┐ │ │ ┌─\NONE─────────┐ │ │ ┌─\NONE───────┐ │
└─USRID(──┴─user-ID──user-address─┴──)─┘ └─TODOC(──┴─document-name─┴──)─┘ └─TOFLR(──┴─folder-name─┴──)─┘
5──┬────────────────────────────────────┬──┬─────────────────────────────────┬──────────────────────────────────────────────────5
│ ┌─\NONE─────────┐ │ │ ┌─\NONE──────────────┐ │
(6) ──)─┤ │
├─SENSITIV(──┼─\PERSONAL─────┼─── │ ┌──
─────────────┐ │ │
│ ├─\PRIVATE──────┤ 6 (2)
│ └─ACC(──┴───access-code─┴────┴──)─┘
│ └─\CONFIDENTIAL─┘ │
│ ┌─\NO──┐ │
(6)
└─PERSONAL(──┴─\YES─┴─────)──────────┘
5──┬──────────────────────────────────────────────────────────────────┬──┬──────────────────────────────────┬───────────────────5
│ ┌─\NONE────────────────────────────────────────────┐ │ │ ┌─\NONE──────────────┐ │
│ │ ┌──
───────────────────────────────────────────┐ │ │ └─AUTL(──┴─authorization-list─┴──)─┘
│ │ │ ┌─\EXCLUDE─┐ │ │ │
└─USRAUT(──┴──6─(──┬─\PUBLIC───────────┬──┼─\USE─────┼──)─┴───
(2) ─┴──)─┘
└─user-profile-name─┘ ├─\CHANGE──┤
├─\ALL─────┤
└─\AUTL────┘
5──┬──────────────────────┬──┬────────────────────────────────────────────────────────┬──┬─────────────────────────────┬────────5
│ ┌─\NO──┐ │ │ ┌─\NONE─────────────────────────────────┐ │ │ ┌─\FIRST──────┐ │
(3) ───────────────────────────┼──)─┘ └─IDPMBR(──┴─member-name─┴──)─┘
└─ALWRPL(──┴─\YES─┴──)─┘ └─IDPFILE(──┼─\DOCFILE───
(4) ──────────────────────────┤
├─\DSTIDIDP───
│ ┌─\LIBL/────────┐ │
└─┼───────────────┼──database-file-name─┘
├─\CURLIB/──────┤
└─library-name/─┘
5──┬───────────────────────────────────────┬──┬───────────────────────────────┬──┬──────────────────────────────────────┬───────5
│ (5) ──────────────┐
┌─\DFT─── │ │ ┌─\DFT──────────┐ │ │ ┌─\DFT───────────────────┐ │
└─DOCTYPE(──┼─\FFT─────────────────┼──)─┘ └─SYSCOD(──┴─'system-code'─┴──)─┘ └─DOCD(──┴─'document-description'─┴──)─┘
├─\RFT─────────────────┤
└─document-type-number─┘
5──┬──────────────────────────────────────────┬──┬──────────────────────────────────┬───────────────────────────────────────────5
│ ┌─\NONE────────────────────┐ │ │ ┌─\NONE────────────┐ │
└─AUTHOR(──┼─\USRID───────────────────┼──)─┘ └─DOCCLS(──┴─'document-class'─┴──)─┘
│ ┌──
───────────────────┐ │
└──6─'document-author'─┴───
(7) ─┘
5──┬──────────────────────────────────────────┬──┬────────────────────────────────────────────┬─────────────────────────────────5
│ ┌─\NONE───────────────────────┐ │ │ ┌─\NONE─────────────────────┐ │
│ │ ┌──
──────────────────────┐ │ │ └─SUBJECT(──┼─\DOCD─────────────────────┼──)─┘
6 (7)
└─KWD(──┴───'document-parameter'─┴────┴──)─┘ │ ┌──
────────────────────┐ │
└──6─'document-subject'─┴───
(7) ─┘
5──┬─────────────────────────────────┬──┬──────────────────────────────────────────────┬────────────────────────────────────────5
│ ┌─\NONE──────────┐ │ │ ┌─\NONE──────────────────────┐ │
(8) ─┴─'filing-cabinet-reference'─┴──)─┘
└─DOCDATE(──┼─\CURRENT───────┼──)─┘ └─FILCAB(───
└─'date-written'─┘
5──┬─────────────────────────────────────────┬──┬──────────────────────────────────┬──┬──────────────────────────────┬──────────5
│ ┌─\NONE───────────────────┐ │ │ ┌─\NONE───────────┐ │ │ ┌─\NONE─────┐ │
│ │ ┌──
──────────────────┐ │ │ └─EXPDATE(──┴─expiration-date─┴──)─┘ └─REFERENCE(──┴─reference─┴──)─┘
└─CPYLST(──┴──6─'recipient-name'─┴───
(7) ─┴──)─┘
5──┬──────────────────────────────┬──┬──────────────────────────────────────┬──┬────────────────────────────────┬───────────────5
│ ┌─\NONE───────┐ │ │ ┌─\NONE────────────────┐ │ │ ┌─\NONE─────────┐ │
└─ACTDATE(──┼─\CURRENT────┼──)─┘ └─STATUS(──┴─'status-of-document'─┴──)─┘ └─CMPDATE(──┼─\CURRENT──────┼──)─┘
└─action-date─┘ └─date-complete─┘
5──┬──────────────────────────┬──┬────────────────────────────────────────────────────┬─────────────────────────────────────────5
│ ┌─\NONE───┐ │ │ ┌─\SYSVAL──────────────────────────┐ │
└─PROJECT(──┴─project─┴──)─┘ └─DOCCHRID(──┼─\DEVD────────────────────────────┼──)─┘
└─graphic-character-set──code-page─┘
5──┬────────────────────────────────────────┬──┬────────────────────────────────────────┬───────────────────────────────────────5
│ ┌─\JOB────────────────┐ │ │ ┌─\JOB───────────────┐ │
└─DOCLANGID(──┴─language-identifier─┴──)─┘ └─DOCCNTRYID(──┴─country-identifier─┴──)─┘
5──┬──────────────────────────────────────────────────────┬────────────────────────────────────────────────────────────────────5%
│ ┌─\SYSVAL──────────────────────────┐ │
(9) ─┼─\DEVD────────────────────────────┼──)─┘
└─CMDCHRID(───
└─graphic-character-set──code-page─┘
Notes:
1 This parameter is valid only when TYPE(*IDP) is specified.
2 A maximum of 50 repetitions
7 A maximum of 50 repetitions
9 This parameter applies to the following parameters: DSTID, USRID, SYSCOD, DOCD, AUTHOR, DOCCLS, KWD,
user is granted with the Grant User Permission but is unavailable to users who are working on your
(GRTUSRPMN) command. If a user files a document behalf (even though it may be available to them when
on behalf of another user's user ID, the other user is the they are not working on your behalf). This parameter is
owner of the document. replaced by SENSITIV but the PERSONAL parameter
can still be used. However, because this parameter may
*CURRENT: The user profile that is currently running is
be removed in a later release, whenever possible use
used.
the SENSITIV parameter.
Element 1: User ID
*NO: The document is not filed as personal. This value
user-ID: Specify the user ID of the user for whom the will map to SENSITIV(*NONE).
document is filed.
*YES: The document is filed as personal. This value
Element 2: User Address will map to SENSITIV(*PRIVATE).
user-address: Specify the user address of the user for ACC
whom the document is filed.
Specifies the access codes that are used with this docu-
TODOC ment. Access codes are specified to allow groups of
Specifies the name of the newly filed document. users access to the document. Access codes must be
added on the system with the Add Access Code
*NONE: The newly filed document does not have a
(ADDACC) command.
user-defined document name and is not filed in a folder.
Up to 12 characters can be specified. This document *NONE: No access codes are assigned to this docu-
name must not exist in the folder into which the docu- ment. Authority for this document is controlled by the
ment is being filed. values specified in the AUTUSR and AUTL parameters.
document-name: Specify the name of the document that access-code: Specify the access codes, ranging from 1
is filed. through 2047, that control who can use the document.
Up to 50 access codes can be specified. Access code 0
TOFLR gives *USE authority to all users. Other access codes
Specifies the name of the folder that contains the docu- specified must exist on the system.
ment being filed. TOFLR can be specified only when
TODOC is also specified. USRAUT
Specifies the users that can access the document and
*NONE: The newly filed document does not have a
the authority each user has. This parameter is used to
user-assigned name and is not filed in another folder.
change the effect of the authorization list for this docu-
folder-name: Specify the name of the folder to contain ment by giving more users authority to the document,
the document being filed. A folder name can consist of removing a user's authority for the document, or
a series of folder names (FLR1/FLR2/and so forth) if the changing the user's authority.
document is being filed in a folder that is contained in
*NONE: No users have specific authority to access the
another folder. Up to 63 characters can be specified.
document.
SENSITIV Element 1: Users Affected by Authority Level
Specifies the level of sensitivity defined by the X.400 Change
standard. The four levels include no sensitivity, per-
*PUBLIC: The users who do not have specific authority
sonal, private and company confidential. Any document
to the document, who are not on the authorization list,
marked as private is still available to users who are
and whose users profile group does not have any spe-
normally authorized to it, but is unavailable to users who
cific authority to the document are given authority.
are working on your behalf (even though it may be avail-
able to them when they are not working on your behalf). user-profile-name: Specify the user profile names of one
or more users that are being granted authority.
*NONE: The document has no sensitivity restrictions.
Element 2: User Authority Levels
*PERSONAL: The document is intended for the user as
an individual. *EXCLUDE: The user cannot access the file document.
*PRIVATE: The document contains information that *USE: The user can perform basic operations on the file
should be accessed only by the owner. document, such as running a program or reading a file.
The user cannot change the file document. *USE
*CONFIDENTIAL: The document contains information
authority provides object operational authority, read
that should be handled according to company proce-
authority, and execute authority.
dures.
*CHANGE: The user can perform all operations on the
PERSONAL
object except those limited to the owner or controlled by
Specifies whether the document is being filed as a per-
object existence authority and object management
sonal document. Any document marked as private is
authority. The user can change and perform basic func-
still available to users who are normally authorized to it,
tions on the object. Change authority provides object library-name: Specify the name of the library to be
operational authority and all data authority. searched.
*ALL: All authority allows the user to perform all oper- database-file-name: Specify the name of the database
ations on the document except those limited to the file that contains the IDP information. The document
owner. In addition to the functions allowed with use profile database file can be a user-defined file or the
(*USE) and change (*CHANGE) authorities, the user can output file specified on the Receive Distribution
control the document's existence and specify the security (RCVDST) or Retrieve Document (RTVDOC) com-
for the document. The user can transfer ownership of mands. If an output file is specified, only the document
the document. profile record format is read from the output file and the
*AUTL: The authority of the authorization list specified prefix is removed from the data. If the user specifies
in the AUTL parameter is used for the document. AUTL this parameter, the remaining parameters after IDPMBR
is valid only if *PUBLIC is also specified. parameter are ignored except for the DOCCHRID and
CMDCHRID parameters. More information on defining
AUTL the format of database files (output files) is in the DB2
Specifies that the authority for the document named in for AS/400 Database Programming book.
the TODOC parameter comes from the authorization list.
IDPMBR
*NONE: An authorization list is not specified.
Specifies the interchange document file member name
authorization-list: Specify the name of the authorization that is filed. This parameter is used only when IDPFILE
list whose authority is used for the document. (database-file-name) is also specified.
*NO: The document content of the document being filed *DFT: The system creates the appropriate document
cannot be replaced. type identifier depending on where the data comes from.
Document Description only the first 44 characters are used in the document
Type name. If TYPE(*DSTID) is specified, the document
65262 IBM S/38 revisable document (RFTS38) description specified when the distribution is used.
If TYPE(*IDP) is specified, the document type is 15 'document-description': Specify the description of the
(printed document). document. Up to 44 characters can be specified.
refers to the printed document. This parameter is date-complete: Specify the date when the action is com-
required if TYPE(*IDP) and IDPFILE(*NONE) is speci- pleted. The date must be entered in the format specified
fied. by the system value QDATFMT.
*NONE: No filing cabinet reference is defined for this PROJECT
document. Specifies the project with which the document is associ-
'filing-cabinet-reference': Specify text that describes ated.
where the printed document is located. Up to 60 char- *NONE: No project field is included in the interchange
acters can be specified. document profile.
CPYLST project: Specify the text that describes the project of the
Specifies the names of the users who receive this docu- document. Up to 10 characters can be specified.
ment.
DOCCHRID
*NONE: No copy list is included for this document. Specifies the character identifier (graphic character set
'recipient-name': Specify the names of the users who and code page) for the data being filed. The character
receive the document. Up to 50 names can be specified identifier is related to the display device that was used to
and each name can have up to 60 characters. create the data being filed. More information about
character identifier processing is in the DB2 for AS/400
EXPDATE Database Programming book.
Specifies the date on which the document is no longer
*SYSVAL: The system determines the graphic char-
needed.
acter set and code page values for the command param-
*NONE: No expiration date is specified. eters from the QCHRID system values.
expiration-date: Specify an expiration date. The date *DEVD: The system determines the graphic character
must be entered in the format specified by the system set and code page values for the command parameter
value QDATFMT. from the display device description where the command
is entered. This option is valid only when specified from
REFERENCE
an interactive job. If this value is specified in an interac-
Specifies a reference associated with the document.
tive CL program or a batch job, an error message is
*NONE: No reference field is included in the inter- sent.
change document profile.
Element 1: Character Set
reference: Specify the text that describes the reference
associated with the document. Up to 60 characters can
graphic-character-set: Specify the graphic character set
values used to create the data being filed.
be used.
Element 2: Code Page
ACTDATE
Specifies the date when the requested action is due. code-page: Specify the code page value used to create
the command parameters. Valid values range from 1
*NONE: No due date is specified.
through 999.
*CURRENT: The current date is used.
DOCLANGID
action-date: Specify the value that is used as the action Specifies the language identifier being placed in this
due date. The date must be entered in the format speci- document's interchange document profile (IDP). This
fied by the system value QDATFMT. parameter is ignored if the IDPFILE parameter is speci-
fied.
STATUS
Specifies the user-defined status (In Process, Pending *JOB: The language identifier specified for the job in
Approval, or Retired). which this command is entered is used.
*NONE: No status is included in the interchange docu- language-identifier: Specify the language identifier.
ment profile. More information on valid language identifiers is in the
'status-of-document': Specify text that describes the National Language Support book.
status of the document. Up to 20 characters can be DOCCNTRYID
specified. Specifies the country identifier being placed in this docu-
ment's interchange document profile (IDP). This param-
CMPDATE
eter is ignored if the IDPFILE parameter is specified.
Specifies the date when the requested action is com-
pleted. *JOB: The country identifier specified for the job in
which this command is entered is used.
*NONE: No completion date is included.
*CURRENT: The current date is used.
country-identifier: Specify an ISO 3166 Alpha-2 code
from the country code table. More information on this
parameter is in Appendix A, “Expanded Parameter SNA Distribution Services book contains the
Descriptions.” character set and code page table for '930 500'.
This value translates the USRID parameter to This command files a distribution document in the document
character set and code page of '930 500'. The library QDOC in document DST0201 and folder FLRDST.
The document class is changed in the distribution document,
and the second distribution that was sent to the user is filed.
┌──
─────────────────────────┐
55──GENCAT──CLGFILE(──'catalog-file-path-name'──)──SRCFILE(───6─'source-file-path-name'─┴───
(1) ──)────
(P) ──────────────────────────────5
5──┬───────────────────────────────────────┬──)──┬───────────────────────────────────────┬──)───────────────────────────────────5
│ ┌─\SRCCCSID──────────────┐ │ │ ┌─\SRCFILE───────────────┐ │
└─CLGCCSID(──┼─\JOB───────────────────┼─┘ └─SRCCCSID(──┼─\JOB───────────────────┼─┘
└─coded-character-set-ID─┘ └─coded-character-set-ID─┘
5──┬─────────────────────────────┬──┬─────────────────────────────────────────┬──┬─────────────────────────────────┬───────────5%
│ ┌─\BLANK────────┐ │ │ ┌─\INDIR──────────────────┐ │ │ ┌─\INDIR─────────────┐ │
└─TEXT(──┴─'description'─┴──)─┘ └─DTAAUT(──┼─\RWX────────────────────┼──)─┘ └─OBJAUT(──┼─\NONE──────────────┼─┘
├─\RW─────────────────────┤ ├─\ALL───────────────┤
├─\RX─────────────────────┤ │ ┌──
─────────────┐ │
├─\WX─────────────────────┤ └──6┬─\OBJEXIST─┬┴───
(2) ─┘
├─\R──────────────────────┤ ├─\OBJMGT───┤
├─\W──────────────────────┤ ├─\OBJALTER─┤
├─\X──────────────────────┤ └─\OBJREF───┘
├─\EXCLUDE────────────────┤
├─\NONE───────────────────┤
└─authorization-list-name─┘
Notes:
1 A maximum of 300 repetitions.
2 A maximum of 4 repetitions.
GENCAT Command
For the description of the GENCAT command, see the MRGMSGCLG (Merge Message Catalog) command description.
┌─\LIBL/────────┐
(P) ───────────────────────────────────────5%
55──GO──MENU(──┼───────────────┼──┬─\ALL───────────────┬──)──┬──────────────────────┬───
├─\CURLIB/──────┤ ├─menu-name──────────┤ │ ┌─\YES─┐ │
├─\USRLIBL/─────┤ └─generic\-menu-name─┘ └─RTNPNT(──┴─\NO──┴──)─┘
├─\ALL/─────────┤
├─\ALLUSR/──────┤
└─library-name/─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose MENU
Specifies the qualified name of the menu being run.
The Go to Menu (GO) command allows the user to specify
The name of the menu can be qualified by one of the
either a particular menu or a generic menu name. The user
following library values:
may optionally specify whether or not to return to the menu
or display from which the command is entered after running *LIBL: All libraries in the job's library list are
the menu specified by the GO command. searched until the first match is found.
Using the Previous and Exit Keys *CURLIB: The current library for the job is
searched. If no library is specified as the current
A menu is placed on an internal menu stack before it is run. library for the job, the QGPL library is used.
If a stack is not available for the menu, one is created. *USRLIBL: Only the libraries in the user portion of
When the Cancel key is pressed for a menu, the previous the job's library list are searched.
menu in the stack is shown. Each menu stack is ten ele-
ments (menus) deep. When the eleventh menu is placed on *ALL: All libraries in the system, including QSYS,
the menu stack, the first, or oldest, menu is removed from are searched.
the stack. This menu cannot be returned to by using the *ALLUSR: All user libraries are searched. All
Cancel key. libraries with names that do not begin with the letter
Q are searched except for the following:
Pressing the Exit key returns the user to the last display or
#CGULIB #DFULIB #RPGLIB #SEULIB
menu from which a GO command was entered with
#COBLIB #DSULIB #SDALIB
RTNPNT(*YES). (Note that *YES is the default value for the
optional RTNPNT parameter.) The display that the user is Although the following Qxxx libraries are provided
returned to is found by removing menus from the menu stack by IBM, they typically contain user data that
until a return point is found. This process may also cause a changes frequently. Therefore, these libraries are
program in the call stack to return to its calling program considered user libraries and are also searched:
unless the program is a return point. | QDSNX QPFRDATA QUSRBRM QUSRSYS
| QGPL QRCL QUSRIJS QUSRVxRxMx
Pressing either the Exit or Cancel key while viewing help for | QGPL38 QS36F QUSRINFSKR
a menu returns the user to the menu. | QMQMDATA QUSER38 QUSRNOTES
| QMQMPROC QUSRADSM QUSRRDARS
Restrictions:
Note: A different library name, of the form
1. The user must have *USE authority for the menu and its QUSRVxRxMx, can be created by the user
display and message files or program (whichever for each release that IBM supports. VxRxMx
applies) to use this command. is the version, release, and modification level
2. The user must also have *USE authority for the library of the library.
where the menu is located. library-name: Specify the name of the library to be
Note: To see the parameter and value descriptions for this searched.
command, refer to the online help text. For more
*ALL: A list of all menus in the given library are pre-
information about printing the help text, refer to
sented to allow the selection of the menu to be run.
“Printing CL Command Descriptions” in Chapter 1.
menu-name: Specify the name of the menu being run.
ABC*. The asterisk substitutes for any valid characters. *YES: The display where the command is entered is
A generic name specifies all objects with names that shown when the Exit key is pressed.
begin with the generic prefix for which the user has
*NO: The display where the command is entered is not
authority. If an asterisk is not included with the generic
shown when the Exit key is pressed.
(prefix) name, the system assumes it to be the complete
object name. If the complete object name is specified,
and multiple libraries are searched, multiple objects can Example
be specified only if *ALL or *ALLUSR library values can GO MENU(PERSMENU)
be specified for the name. For more information on the
use of generic names, refer to “Generic Object Names” This command runs a menu called PERSMENU, located in a
in Chapter 2. library found by searching the library list (*LIBL default
value).
Optional Parameter If the Exit key is pressed while PERSMENU is being shown,
the display where the GO command was entered (*YES
RTNPNT default value on the RTNPNT parameter) is shown.
Specifies whether the display where the command is
entered is returned to when the Exit key is pressed.
(1) ─command-label──)────
55──GOTO──CMDLBL(─── (P) ──────────────────────────────────────────────────────────────────────────────────────5%
Notes:
1 A variable cannot be coded on this parameter.
┌──
───────────────────┐
55──GRTACCAUT─── 6─user-profile-name─┴───
(2) ─ACC(──┬─\REFUSER───────────┬──)──USER(─── (1) ──)────
(P) ────────────────────────────────────────5
│ ┌──
─────────────┐ │
6 (1) ─┘
└───access-code─┴───
5──┬────────────────────────────────────────────┬──────────────────────────────────────────────────────────────────────────────5%
│ ┌─\NONE───────────────────┐ │
(3) ─┴─based-on-user-profile───
└─REFUSER(─── (4) ┴──)─┘
Notes:
1 A maximum of 300 repetitions
Example 1: Granting Authority to Multiple Users This command grants access code authority to JOE based
on TOM's authority. For example, if JOE currently has
GRTACCAUT ACC(3 3ð 6ð) USER(SAM LARRY)
authority to access codes 1, 12, and 50, and TOM currently
This command gives authority to access codes 3, 30, and 60 has authority to access codes 8 and 9, the GRTACCAUT
to SAM and LARRY. command authorizes JOE to access codes 1, 8, 9, 12, and
50.
Example 2: Granting Authority Based on Another User
┌─\LIBL/────────┐
(1, 2) ─┬─\ALL───
55──GRTOBJAUT──OBJ(──┼───────────────┼──┬─\ALL─────────────────┬──)──OBJTYPE(───── (3) ─────┬──)───────────────────────────5
├─\CURLIB/──────┤ ├─object-name──────────┤ └─object-type─┘
├─\USRLIBL/─────┤ └─generic\-object-name─┘
├─\ALL/─────────┤
├─\ALLUSR/──────┤
└─library-name/─┘
(4) ─┬─\PUBLIC──────────────────┬──)──┬─────────────────────────────────────┬─┬───
5──┬─USER(─── (P) ──┬───────────────────────┬───
(8) ──────5%
│ │ ┌──
───────────────────┐ │ │ ┌─\CHANGE──────────────┐ │ │ │ ┌─\NO──┐ │
│ └──6─user-profile-name─┴───
(5) ─┘ (6) ─┼─\ALL─────────────────┼──)─┘ │
└─AUT(─── └─REPLACE(──┴─\YES─┴──)─┘
│ ├─\USE─────────────────┤ │
│ ├─\EXCLUDE─────────────┤ │
│ ├─\AUTL────────────────┤ │
│ │ ┌──
───────────────┐ │ │
│ 6 (7)
└───┬─\OBJALTER─┬─┴────┘ │
│ ├─\OBJEXIST─┤ │
│ ├─\OBJMGT───┤ │
│ ├─\OBJOPR───┤ │
│ ├─\OBJREF───┤ │
│ ├─\ADD──────┤ │
│ ├─\DLT──────┤ │
│ ├─\EXECUTE──┤ │
│ ├─\READ─────┤ │
│ └─\UPD──────┘ │
├─AUTL(──authorization-list-name──)─────────────────────────────────────────────────┤
│ ┌─\LIBL/────────┐ │
└─REFOBJ(──┼─\CURLIB/──────┼──object-name──)──┬───────────────────────────────────┬─┘
└─library-name/─┘ │ ┌─\OBJTYPE──────┐ │
└─REFOBJTYPE(──┴─object-type─── (1) ┴──)─┘
Notes:
1 A list of the valid OS/400 object types for this command is in Appendix A.
3 OBJTYPE(*ALL) is not valid if one of the following library names is specified: *LIBL, *USRLIBL, *ALL, *ALLUSR.
4 Positional order is USER, AUT, AUTL, REFOBJ, REFOBJTYPE. Only one of USER, AUTL, or REFOBJ can be specified.
5 A maximum of 50 repetitions
6 AUT(*AUTL) is valid only if USER(*PUBLIC) is specified. It is not valid if the object type is *USRPRF.
8 REPLACE is valid only if USER is specified. It is not valid with the AUTL or REFOBJ parameter.
When granting authority to users, the REPLACE parameter *CURLIB: The current library for the job is
indicates whether the authorities you specify replace the searched. If no library is specified as the current
user's existing authorities. The default value of library for the job, the QGPL library is used.
REPLACE(*NO) gives the authority that you specify, but it
*USRLIBL: Only the libraries in the user portion of
does not remove any authority that is greater than you speci-
the job's library list are searched.
fied, unless you are granting *EXCLUDE authority.
REPLACE(*YES) removes the user's current authorities, then *ALL: All libraries on the system are searched.
grants the authority that you specify. *ALLUSR: All user libraries are searched. All
libraries with names that do not begin with the letter
When granting authority with a reference object, this
Q are searched except for the following:
command gives the authority that you specify, but it does not
remove any authority that is greater than you specified, #CGULIB #DFULIB #RPGLIB #SEULIB
unless you are granting *EXCLUDE authority. #COBLIB #DSULIB #SDALIB
Although the following Qxxx libraries are provided
Restrictions: by IBM, they typically contain user data that
1. This command must get an exclusive lock on a database changes frequently. Therefore, these libraries are
file before read or object operational authority can be considered user libraries and are also searched:
given to a user. | QDSNX QPFRDATA QUSRBRM QUSRSYS
2. If a user requests authority for another specified user to | QGPL QRCL QUSRIJS QUSRVxRxMx
| QGPL38 QS36F QUSRINFSKR
a device currently in use by another authorized user,
| QMQMDATA QUSER38 QUSRNOTES
authority to the device is not given.
| QMQMPROC QUSRADSM QUSRRDARS
3. Object type *AUTL cannot be specified.
Note: A different library name, of the form
4. AUT(*AUTL) is valid only with USER(*PUBLIC). QUSRVxRxMx, can be created by the user
5. A user must either be the owner of the object or have for each release that IBM supports. VxRxMx
*ALL authority to use the AUTL parameter. is the version, release, and modification level
of the library.
6. The user must have object management authority to the
object. library-name: Specify the name of the library to be
searched.
7. If the object is a file, the user must have object opera-
tional and object management authorities. *ALL: All objects of the specified type (OBJTYPE)
found in the search have specific authorities granted. A
8. For display stations or for work station message queues
specific library name must be specified.
associated with the display station, if this command is
not entered at the device for which authorities are being object-name: Specify the name of the object for which
granted, it should be preceded by the Allocate Object specific authorities are given to one or more users.
(ALCOBJ) command and followed by the Deallocate generic*-object-name: Specify the generic name of the
Object (DLCOBJ) command. object. A generic name is a character string of one or
Note: To see the parameter and value descriptions for this more characters followed by an asterisk (*); for example,
command, refer to the online help text. For more ABC*. The asterisk substitutes for any valid characters.
information about printing the help text, refer to A generic name specifies all objects with names that
“Printing CL Command Descriptions” in Chapter 1. begin with the generic prefix for which the user has
authority. If an asterisk is not included with the generic
(prefix) name, the system assumes it to be the complete
Required Parameters object name. If the complete object name is specified,
OBJ and multiple libraries are searched, multiple objects can
Specifies the qualified name of the objects for which be granted only if *ALL or *ALLUSR library values can
specific authorities are given to one or more users or to be specified for the name. For more information on the
an authorization list. A specific object name or a generic use of generic names, refer to “Generic Object Names”
object name can be qualified by a library name. More in Chapter 2.
information on this parameter is in Appendix A, OBJTYPE
“Expanded Parameter Descriptions.” Specifies the object type of the object for which specific
The name of the object can be qualified by one of the authorities are given to the specified users or to an
following library values: authorization list. More information on this parameter is
in Appendix A, “Expanded Parameter Descriptions.”
*LIBL: All libraries in the job's library list are
searched until the first match is found. *ALL: Specific authorities for all object types (except
*AUTL) are given to the specified users or to the authori-
zation list.
object-type: Specify the specific object type of the object *CHANGE: The user can perform all operations on the
for which specific authorities are given to the specified object except those limited to the owner or controlled by
users. object existence authority and object management
authority. The user can change and perform basic func-
USER
tions on the object. Change authority provides object
Specifies the user names of one or more users to whom
operational authority and all data authority.
authorities for the named object are being given. If user
names are specified, the authorities are given specif- *ALL: The user can perform all operations except those
ically to those users. Authority given by this command limited to the owner or controlled by authorization list
can be revoked specifically by the Revoke Object management authority. The user can control the object's
Authority (RVKOBJAUT) command. existence, specify the security for the object, change the
object, and perform basic functions on the object. The
*PUBLIC: Users are authorized to use the object as
user also can change ownership of the object.
specified in the AUT parameter when they do not have
authority specifically given to them for the object, are not *USE: The user can perform basic operations on the
on the authorization list or one of their groups does not object, such as run a program or display the contents of
have any authority or is not on the authorization list. a file. The user is prevented from changing the object.
Users who do not have any authority, or whose groups Use authority provides object operational authority, read
are not on the authorization list, are authorized to use authority, and execute authority.
the object as specified in the AUT parameter. *EXCLUDE: The user cannot access the object.
user-profile-name: Specify the user names of one or *AUTL: The public authority of the authorization list
more users who have specific authority for the object. specified in the AUTL parameter is used for the public
Up to 50 user profile names can be specified. authority for the object.
AUTL A maximum of ten of the following values can be speci-
Specifies the name of the authorization list whose users fied:
are given authority for the object specified in the OBJ
*OBJALTER: Object alter authority provides the
parameter.
authority needed to alter the attributes of an object. If
REFOBJ the user has this authority on a database file, the user
Specifies the name of the object being queried to obtain can add and remove triggers, add and remove referen-
authorization information. Those authorizations are tial and unique constraints, and change the attributes of
given to the object specified by the OBJ parameter. the database file. If the user has this authority on an
Users authorized to the referenced object are authorized SQL package, the user can change the attributes of the
in the same manner to the object for which authority is SQL package. This authority is currently only used for
being given. If the referenced object is secured by an database files and SQL packages.
authorization list, that authorization list secures the *OBJEXIST: Object existence authority provides the
object specified in the OBJ parameter. Specify the authority to control the object's existence and ownership.
name of the object. This authority is necessary for users who want to delete
The name of the save file can be qualified by one of the the object, free storage of the object, perform save and
following library values: restore operations for the object or transfer ownership of
an object. (If a user has special save system authority
*LIBL: All libraries in the job's library list are (*SAVSYS), object existence authority is not required.)
searched until the first match is found. Object existence authority is required to create an object
*CURLIB: The current library for the job is that has been named by an authority holder.
searched. If no library is specified as the current *OBJMGT: Object management authority provides the
library for the job, the QGPL library is used. authority to specify the security for the object, move or
library-name: Specify the name of the library to be rename the object, and add members to database files.
searched. *OBJOPR: Object operational authority provides
authority to look at the description of an object and use
the object as determined by the data authorities that the
Optional Parameters user has to the object.
AUT *OBJREF: Object reference authority provides the
Specifies the authority given to users specified on the authority needed to reference an object from another
USER parameter. Users must have *AUTLMGT object such that operations on that object may be
authority to manage the authorization list. More informa- restricted by the other object. If the user has this
tion on this parameter is in Appendix A, “Expanded authority on a physical file, the user can add referential
Parameter Descriptions.” constraints in which the physical file is the parent. This
authority is currently only used for database files.
*ADD: Add authority provides the authority to add Example 3: Granting Authority to Users on Authori-
entries to an object (for example, job entries to a queue zation List
or records to a file). GRTOBJAUT OBJ(MYLIB/PRGM3) OBJTYPE(\PGM)
*DLT: Delete authority allows the user to remove AUTL(KLIST)
entries from an object, for example, remove messages
from a message queue or records from a file. This command gives to users the authority specified for them
on authorization list KLIST for the object named PRGM3.
*EXECUTE: Execute authority provides the authority The object is a program located in library MYLIB.
needed to run a program or locate an object in a library.
*READ: Read authority provides the authority needed to
get the contents of an entry in an object.
*UPD: Update authority provides the authority needed
to change the entries in an object.
REFOBJTYPE
Specifies the object type of the referenced object
(REFOBJ parameter).
*OBJTYPE: The object type of the referenced object is
the same type as the object being given authority
(OBJTYPE parameter).
object-type: Specify the type of the object. Any one of
the operating system object types can be specified.
REPLACE
Specifies whether the authorities replace the user's
current authorities.
*NO: The authorities are given to the user, but no
authorities are removed, unless you are granting
*EXCLUDE authority.
*YES: The user's current authorities are removed, then
the authorities are given to the user.
Examples
Example 1: Granting Authority to All Users
GRTOBJAUT OBJ(USERLIB/PROGRAM1) OBJTYPE(\PGM)
USER(\PUBLIC)
(P) ─────────────────────────────────────────────────────────────────5%
55──GRTUSRAUT──USER(──user-name──)──REFUSER(──user-name──)────
Note:
P All parameters preceding this point can be specified in positional form.
Notes:
1 A maximum of 300 repetitions
Purpose TOUSER
Specifies the name of the user profile that is permitted to
The Grant User Permission (GRTUSRPMN) command gives work on behalf of the user specified in the FORUSER
permission to a user to handle documents and folders or to parameter. Access is restricted to objects that are not
perform tasks on behalf of another user. Access is restricted personal. The user profile must exist at the time the
to documents, folders, and mail that is not personal. For command is run, and the user must be enrolled in the
example, user A gives user B the ability to work on behalf of system distribution directory before running the
user A. User B is now allowed to obtain, file, delete, retrieve, command.
list, distribute, cancel, and search a document library on
behalf of user A; however, user B is not allowed to obtain
any of user A's personal mail or get any of user A's private Optional Parameters
documents or folders from the library. FORUSER
Specifies the name of the user profile that the user spec-
The users specified must be enrolled in the system distribu-
ified in the TOUSER parameter works on behalf of. The
tion directory before using this command. To enroll a user,
user must be enrolled in the system distribution directory
use the Work with Directory Entries (WRKDIRE) command.
before running the command.
Restriction: The user must have *ALLOBJ authority to grant *CURRENT: The user profile that is currently running is
permission for a user to work on behalf of another user. used.
Additional information on giving document authority is in the user-profile-name: Specify the name of the user profile.
SNA Distribution Services book.
Note: To see the parameter and value descriptions for this Example
command, refer to the online help text. For more GRTUSRPMN TOUSER(JUDY) FORUSER(PEGGY)
information about printing the help text, refer to
“Printing CL Command Descriptions” in Chapter 1. JUDY is the administrative assistant for an executive. This
command allows JUDY to work with documents or folders for
PEGGY that are not personal.
Required Parameters
55──GRTWSOAUT──WSOTYPE(──┬─\TPLWRKARA─┬──)──────────────────────────────────────────────────────────────────────────────────────5
├─\WRKARA────┤
├─\TPLPRTOL──┤
├─\PRTOL─────┤
├─\TPLTPRTL──┤
├─\PRTL──────┤
├─\TPLOUTQ───┤
├─\TPLOUTQL──┤
├─\OUTQL─────┤
├─\TPLJOBL───┤
├─\JOBL──────┤
├─\TPLJOBQ───┤
├─\TPLJOBLOG─┤
├─\JOBLOG────┤
├─\TPLJOBQL──┤
├─\JOBQL─────┤
├─\TPLMSGL───┤
├─\MSGL──────┤
├─\TPLMSGQ───┤
├─\TPLMSGSND─┤
├─\MSGSND────┤
├─\TPLSGNUSL─┤
├─\SGNUSL────┤
├─\TPLOBJL───┤
├─\OBJL──────┤
├─\TPLLIBSL──┤
├─\LIBSL─────┤
├─\TPLLIB────┤
├─\TPLLAUNCH─┤
├─\LAUNCH────┤
└─\PRSSET────┘
(P) ────────────────────────────────────────5%
5──┬─USER(──┬─\PUBLIC──────────────────┬──)──┬───────────────────────────────────┬─┬───
│ │ ┌──
───────────────────┐ │ │ ┌─\CHANGE──────────────┐ │ │
│ └──6─user-profile-name─┴───
(1) ─┘ └─AUT(──┼─\ALL─────────────────┼──)─┘ │
│ ├─\USE─────────────────┤ │
│ ├─\EXCLUDE─────────────┤ │
│ (2)
├─\AUTL────────────────┤ │
│ │ ┌──
───────────────┐ │ │
│ 6 (3)
└───┬─\OBJALTER─┬─┴────┘ │
│ ├─\OBJEXIST─┤ │
│ ├─\OBJMGT───┤ │
│ ├─\OBJOPR───┤ │
│ ├─\OBJREF───┤ │
│ ├─\ADD──────┤ │
│ ├─\DLT──────┤ │
│ ├─\EXECUTE──┤ │
│ ├─\READ─────┤ │
│ └─\UPD──────┘ │
├─AUTL(──authorization-list-name──)─────────────────────────────────────────────┤
└─REFWSO(──same-values-as-WSOTYPE──)────────────────────────────────────────────┘
Notes:
1 A maximum of 50 repetitions.
USER
Specifies the user profile names of one or more users to
whom authorities for the named object are being given.
If user names are specified, the authorities are given
specifically to those users. Authority given by this
command can be revoked specifically by the Revoke
Workstation Object Authority (RVKWSOAUT) command.
*PUBLIC: All users of the system, who do not have
authority specifically given to them for the object, who
are not on the authorization list, whose user group does
not have any authority, or whose user group is not on
the authorization list, are authorized to use the object as
specified on the AUT parameter.
user-profile-name: Specify the user profile names of one referential and unique constraints, and change the
or more users who have specific authority for the object. attributes of the database file. If the user has this
A maximum of 50 user profile names can be specified. authority on an SQL package, the user can change
the attributes of the SQL package. This authority is
AUTL
currently only used for database files and SQL
Specifies the name of the authorization list whose
packages.
members are given authority for the object specified on
the WSOTYPE parameter. *OBJEXIST: Object existence authority provides
the authority to control the object’s existence and
REFWSO ownership. This authority is necessary for users
Specifies the name of the workstation object being who want to delete the object, free storage of the
queried to obtain authorization information. Those object, perform save and restore operations for the
authorizations are given to the object specified on the object, or transfer ownership of the object. (If a
WSOTYPE parameter. Users authorized to the refer- user has special save system authority (*SAVSYS),
enced object are authorized in the same manner to the object existence authority is not required.) Object
object for which authority is being given. If the refer- existence authority is required to create an object
enced object is secured by an authorization list, that that has been named by an authority holder.
authorization list secures the object specified on the
WSOTYPE parameter. Specify the name of the object. *OBJMGT: Object management authority provides
the authority to specify the security for the object,
move or rename the object, and add members to
Optional Parameter database files.
AUT *OBJOPR: Object operational authority provides
Specifies the authority given to users specified on the authority to look at the description of an object and
USER parameter. Users must have *AUTLMGT use the object, as determined by the data authori-
authority to manage the authorization list. ties that the user has to the object.
*CHANGE: The user can perform all operations on the *OBJREF: Object reference authority provides the
object except those limited to the owner or controlled by authority needed to reference an object from
object existence authority and object management another object such that operations on that object
authority. The user can change and perform basic func- may be restricted by the other object. If the user
tions on the object. Change authority provides object has this authority on a physical file, the user can
operational authority and all data authority. add referential constraints in which the physical file
is the parent. This authority is currently only used
*ALL: The user can perform all operations except those
for database files.
limited to the owner or controlled by authorization list
management authority. The user can control the object's *ADD: Add authority provides the authority to add
existence, specify the security for the object, change the entries to an object (for example, job entries to a
object, and perform basic functions on the object. The queue or records to a file).
user also can change ownership of the workstation *DLT: Delete authority allows the user to remove
object. entries from an object, for example, remove mes-
*USE: The user can perform basic operations on the sages from a message queue or records from a file.
workstation object, such as running a program or *EXECUTE: Execute authority provides the
reading a file. The user cannot change the workstation authority needed to run a program or to locate an
object. *USE authority provides object operational object in a library.
authority, read authority, and execute authority.
*READ: Read authority provides the authority
*EXCLUDE: The user cannot access the workstation needed to get the contents of an entry in an object
object. or to run a program.
*AUTL: The public authority of the authorization list *UPD: Update authority provides the authority
specified on the AUTL parameter is used for the public needed to change the entries in an object.
authority for the object.
A maximum of ten of the following values can be
specified:
Example
*OBJALTER: Object alter authority provides the GRTWSOAUT WSOTYPE(\TPLWRKARA) AUTL(KLIST)
authority needed to alter the attributes of an object.
This command gives authority to the work are template to the
If the user has this authority on a database file, the
users with authority specified for them on the authorization
user can add and remove triggers, add and remove
list KLIST.
(P) ────────────────────────────────────────────────────────────5%
55──HLDCMNDEV──DEV(──device-name──)──┬─────────────────────────┬───
│ ┌─\CNTRLD─┐ │
└─OPTION(──┴─\IMMED──┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
Restriction: This command is shipped with public Specify the name of the device (as specified in the
*EXCLUDE authority and the QPGMR, QSYSOPR, QSRV, device description) whose communications capability is
and QSRVBAS user profiles have private authorities to use suspended.
the command.
Note: To see the parameter and value descriptions for this Optional Parameters
command, refer to the online help text. For more
information about printing the help text, refer to OPTION
“Printing CL Command Descriptions” in Chapter 1. Specifies the manner in which communications with this
device is held.
*CNTRLD: The specified device is not capable of com-
Required Parameters munications at the next OPEN or ACQUIRE operation.
DEV *IMMED: The specified device is not capable of com-
Specifies the name of the device whose communications munications at the next READ, WRITE, OPEN, or
are held. Devices whose communications are held are: ACQUIRE operation.
DEV Value Device
3180 Display station Example
3277 Display station
HLDCMNDEV DEV(WSPRð5)
3278 Display station
3279 Display station This command holds the communications capability of the
3287 Printer (work station) device WSPR05 at the time of the next OPEN or ACQUIRE
5219 Printer (work station) operation.
5224 Printer (work station)
(P) ───────────────────────────────────────────────────────5%
55──HLDDSTQ──DSTQ(──distribution-queue-name──)──PTY(──┬─\NORMAL─┬──)────
(1) ┘
└─\HIGH───
Notes:
1 This value is not valid for a SystemView distribution services (SVDS) type of distribution queue.
(P) ────────────────────────────────5
55──HLDJOB──JOB(────┬─────────────────────────────┬──job-name────)──┬───────────────────────┬───
└─┬─────────────┬──user-name/─┘ │ ┌─\NO──┐ │
└─job-number/─┘ └─SPLFILE(──┴─\YES─┴──)─┘
5──┬────────────────────────────┬──────────────────────────────────────────────────────────────────────────────────────────────5%
│ ┌─\SELECT─┐ │
└─DUPJOBOPT(──┴─\MSG────┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose job-name
user-name/job-name
The Hold Job (HLDJOB) command makes a job ineligible for job-number/user-name/job-name
processing by the system. The job is held until it is: More information on this parameter is in Appendix A,
“Expanded Parameter Descriptions.”
Released by the Release Job (RLSJOB) command
Cleared by the Clear Job Queue (CLRJOBQ) command job-name: Specify the name of the job being held.
Ended by the End Job (ENDJOB) command user-name: Specify the name of the user of the job
Ended (while the job is active) by the End Subsystem being held.
(ENDSBS) command, the End System (ENDSYS)
command, or the Power Down System (PWRDWNSYS) job-number: Specify the number of the job being held.
command
Optional Parameters
If the job is not run before the OS/400 system is ended, the
queue can be cleared (and the job ended) when the OS/400 SPLFILE
system is started again. The specified job to be held can be Specifies whether spooled files created by the job being
on the job queue or on the output queues, or it can be active held are also held.
in a subsystem. This command also specifies whether the
*NO: The spooled files produced by the job are not
job's spooled files are held.
held.
Note: If you use this command to hold a job that has exclu-
*YES: The spooled files produced by the job are also
sive access to any resources on the system, these
held.
resources are not available to other jobs. Other jobs
which require access to those resources will either DUPJOBOPT
fail or wait indefinitely. Specifies the action taken when duplicate jobs are found
by this command.
Restriction: The job must belong to the user issuing the
command, or the user must have job control authority *SELECT: The selection display is shown when dupli-
(*JOBCTL). cate jobs are found during an interactive session. Other-
wise, a message is issued.
Note: To see the parameter and value descriptions for this
command, refer to the online help text. For more *MSG: A message is issued when duplicate jobs are
information about printing the help text, refer to found.
“Printing CL Command Descriptions” in Chapter 1.
Examples
Required Parameter Example 1: Making a Job Ineligible for Processing
JOB HLDJOB JOB(PAYROLL) SPLFILE(\YES)
Specifies the qualified name of the job being held. If no
job qualifier is given, all of the jobs currently in the This command makes the job named PAYROLL ineligible for
system are searched for the job name. If more than one processing. All spooled files for this job are also held.
of the specified names are found, a qualified job name
must be specified. Example 2: Holding a Job that has a Duplicate Name
HLDJOB JOB(DEPTXYZ/PAYROLL)
A job identifier is a special value or a qualified name
with up to three elements. For example: This command holds the job named PAYROLL submitted by
a user operating under the user profile DEPTXYZ. The qual-
ified form of the job name is used when jobs with duplicate
names exist in the system. Spooled files are not held.
┌─\LIBL/────────┐
(P) ───────────────────────────────────────────────────────────────────5%
55──HLDJOBQ──JOBQ(──┼───────────────┼──job-queue-name──)────
├─\CURLIB/──────┤
└─library-name/─┘
Note:
P All parameters preceding this point can be specified in positional form.
┌─\ONLY────────┐
(P) ─ENTRYNBR(──┼─\ALL─────────┼──)──────────────────────────────────────────────5%
55──HLDJOBSCDE──JOB(──┬─\ALL──────────────┬──)────
├─job-name──────────┤ └─entry-number─┘
└─generic\-job-name─┘
Note:
P All parameters preceding this point can be specified in positional form.
┌─\LIBL/────────┐
(P) ────────────────────────────────────────────────────────────────5%
55──HLDOUTQ──OUTQ(──┼───────────────┼──output-queue-name──)────
├─\CURLIB/──────┤
└─library-name/─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose OUTQ
Specifies the qualified name of the output queue.
The Hold Output Queue (HLDOUTQ) command prevents all
The name of the output queue can be qualified by one
currently waiting spooled files, and all spooled files that are
of the following library values:
added to the output queue after the command is issued, from
being processed by a spooling writer. The HLDOUTQ *LIBL: All libraries in the job's library list are
command has no effect on jobs that are running and adding searched until the first match is found.
spooled files to the queue or on the spooled file being
*CURLIB: The current library for the job is
produced by a spooling writer at the time the command is
searched. If no library is specified as the current
issued. When the spooling writer completes all copies of the
library for the job, the QGPL library is used.
current output file, it cannot begin the output for any other
files until the queue is released. library-name: Specify the name of the library to be
searched.
The spooled files are held until a Release Output Queue
(RLSOUTQ) command is issued. Otherwise, the output output-queue-name: Specify the name of the output
queue can be cleared with the Clear Output Queue queue.
(CLROUTQ) command or a specific file can be deleted by
the DLTSPLF command. Example
Note: To see the parameter and value descriptions for this HLDOUTQ OUTQ(QPRINT)
command, refer to the online help text. For more
information about printing the help text, refer to This command prevents the processing of the spooled files
“Printing CL Command Descriptions” in Chapter 1. on the QPRINT queue and any spooled files added to the
queue. They are held until the queue is released or cleared.
A specific job (with its spooled files) can also be ended with
Required Parameters the ENDJOB command, which removes the spooled files
from the output queue.
(P) ───────────────────────────────────────────────────────────────────────────────────────────5%
55──HLDRDR──RDR(──reader-name──)────
Note:
P All parameters preceding this point can be specified in positional form.
Purpose RDR
Specifies the name of the spooling reader being held.
The Hold Reader (HLDRDR) command immediately stops
the activity of the specified spooling reader. The reader is
not ended, and its associated input device is not made avail- Example
able to the system. The reader remains inactive until a HLDRDR RDR(QDKT)
Release Reader (RLSRDR) or End Reader (ENDRDR)
command is issued. Data is not lost when the reader is held. This command causes the diskette reader QDKT to imme-
diately stop reading data. To release the reader, so that it
Note: To see the parameter and value descriptions for this can continue to read data, a Release Reader (RLSRDR)
command, refer to the online help text. For more command must be entered. If the End Reader (ENDRDR)
information about printing the help text, refer to command is used, the reader is stopped and the job that was
“Printing CL Command Descriptions” in Chapter 1. being read in is lost because no job entry was added to the
job queue.
Required Parameters
55──HLDSPLF──FILE(──┬─\SELECT───────────┬──)────────────────────────────────────────────────────────────────────────────────────5
└─spooled-file-name─┘
5──┬────────────────────────────────────────────────────────────────────────────────────────────────┬───────────────────────────5
│ ┌─\─────────────────────────────────────────┐ ┌─\ONLY───────────────┐ │
(P) ┤
├─JOB(──┴─┬─────────────────────────────┬──job-name─┴──)──SPLNBR(──┼─\LAST───────────────┼──)────
│ └─┬─────────────┬──user-name/─┘ └─spooled-file-number─┘ │
│ └─job-number/─┘ │
│ ┌─\CURRENT──┐ │
└─SELECT(──┼─\ALL──────┼──┬───────────────────────────────────────────────────┬──)───────────────┘
└─user-name─┘ │ ┌─\ALL────────┐ │
└─┼─\OUTQ───────┼──┬──────────────────────────────┬─┘
└─device-name─┘ │ ┌─\ALL──────┐ ┌─\ALL──────┐ │
└─┼─\STD──────┼──┼───────────┼─┘
└─form-type─┘ └─user-data─┘
5──┬──────────────────────────┬────────────────────────────────────────────────────────────────────────────────────────────────5%
│ ┌─\IMMED───┐ │
└─OPTION(──┴─\PAGEEND─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose FILE
Specifies the name of the spooled file to be held.
The Hold Spooled File (HLDSPLF) command stops the spec-
*SELECT: All spooled files that meet the selection
ified spooled file from additional processing by a spooling
requirements specified in the SELECT keyword are held.
writer. If the file is being produced on an output device, the
This value is mutually exclusive with the JOB and
writer stops processing that file and gets the next file to be
SPLNBR parameters. Specifying *SELECT causes the
processed. When the file is released and again selected for
JOB and SPLNBR parameters to be ignored.
output, it is again processed starting at the beginning. If
several copies are being produced for the file when it is held, spooled-file-name: Specify the name of the spooled file
the incomplete copy is again produced from the beginning to be held.
along with the remaining copies that follow it.
If the specified file is still receiving records from a program Optional Parameters
that is running when the file is held, the program that is JOB
running is unaware that the file is on hold. Also, if the held Specifies the name of the job that created the file being
file is part of a job that produces other spooled files, they can held. If no job qualifier is given, all of the jobs currently
be processed before the held file is released. The held file in the system are searched for the simple job name.
remains on the output queue and it appears to be the only
file produced by the job. A job identifier is a special value or a qualified name
with up to three elements. For example:
The file is held until one of the following commands is job-name
entered: the RLSSPLF (Release Spooled File), the \
DLTSPLF (Delete Spooled File), the ENDJOB (End Job) with user-name/job-name
keyword SPLFILE(*YES) specified, or the CLROUTQ (Clear job-number/user-name/job-name
Output Queue) command. If the file is released before the More information on this parameter is in Appendix A,
writer begins producing it, the file is produced in its normal “Expanded Parameter Descriptions.”
order within the group of files for the job. Production of a
job's output is not delayed because some of its files are *: The job that issued this HLDSPLF command is the
being held. job that produced the file being held.
Note: To see the parameter and value descriptions for this job-name: Specify the name of the job that created the
command, refer to the online help text. For more file being held.
information about printing the help text, refer to user-name: Specify the name of the user of the job that
“Printing CL Command Descriptions” in Chapter 1. created the file being held.
job-number: Specify the number of the job that created
Required Parameters the file being held.
(P) ──────────────────────────────────────────────────────────────5%
55──HLDWTR──WTR(──writer-name──)──┬──────────────────────────┬───
│ ┌─\IMMED───┐ │
└─OPTION(──┼─\CNTRLD──┼──)─┘
└─\PAGEEND─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose another I/O request to get the next block from the file
being spooled to the device. If *IMMED is specified, the
The Hold Writer (HLDWTR) command stops the specified writer stops only after it has written the last record in the
writer at the end of a record, at the end of a spooled file, or block being processed, which (for diskette output) is a
at the end of a printed page. If multiple copies of a file are complete diskette record being written on diskette.
produced, the writer can be held at the end of the copy cur-
When *IMMED is specified for printed output, the writer
rently being produced. The writer is not ended and the
stops anywhere within or at the end of a print line or at
device is not made available to the system. The writer
the end of a complete block, which may not be at the
remains inactive until a RLSWTR (Release Writer) or
end of a line. This is because some data records (which
ENDWTR (End Writer) command is issued. Data is not lost
are blocked to improve performance) may be split in two,
when the writer is held.
with the first part of a record at the end of one block and
Note: To see the parameter and value descriptions for this the last part of the record at the beginning of the next
command, refer to the online help text. For more block. If only one copy of the file is being produced or if
information about printing the help text, refer to the last copy is being produced, the entry for the file is
“Printing CL Command Descriptions” in Chapter 1. removed from the output queue when the output is com-
pleted.
Required Parameters *CNTRLD: The job is ended in a controlled manner.
This allows the program to perform cleanup (end-of-job
WTR processing).
Specifies the name of the spooling writer being held.
Specify the name of the spooling writer. *PAGEEND: The writer is held at the end of a page.
This value is valid only when the spooling writer is a
printer writer.
Optional Parameters
OPTION Example
Specifies when the spooling writer should stop producing HLDWTR WTR(PRINTER) OPTION(\CNTRLD)
output.
*IMMED: The writer stops immediately after it has This command stops the writer named PRINTER at the end
written the last record, in the current block of records, to of the current file. The writer is held until an RLSWTR
the output device. Each time the writer finishes (Release Writer) or ENDWTR (End Writer) command is
producing a block of records on a device, it makes issued.
IF (If) Command
Pgm: B,I
(P) ──────────────────────────────────────────────────────────────5%
55──IF──COND(──logical-expression──)──┬──────────────────────┬───
└─THEN(──CL-command──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
If any part of the command specified by the THEN IF &LOG1 THEN(IF (&A \GT 1ð) THEN(GOTO X))
parameter continues on the next line, a continuation ELSE(GOTO Y)
character (+ or -) must be specified. ELSE DO
If a DO command is specified, only the DO command (group of CL commands)
(not the commands specified within the Do group) is ENDDO
within the parentheses. For example:
IF COND(&A \EQ &B) THEN(DO) This is an example of nested IF commands. If &LOG1 has a
CMD1 logical value of 1 (true) and if &A is greater than 10, a
CMD2 branch is made to label X. If &LOG1 has a logical value of 1
and &A is not greater than 10, a branch is made to label Y.
If &LOG1 has a logical value of 0 (false), &A is not compared
ENDDO to 10. Instead, the DO group of the second ELSE command
If no command is specified on the THEN parameter (a is processed.
null THEN) and the ELSE command immediately follows
IF &TEST THEN( +
it, the ELSE is processed if the IF expression is false DO)
and it is skipped if the expression is true. CHGVAR &A (&A + 1)
Any CL command can be specified on the THEN param- GOTO X
eter, except the following commands: ENDDO
ELSE
ELSE DO
PGM, ENDPGM CHGVAR &B (&B + 1)
ENDDO CALL EXTPGM (&B)
MONMSG ENDDO
DCL, DCLF
This example shows how the THEN parameter can be con-
The command can be another IF, unless there are tinued on the next line. If &TEST has a logical value of 1,
already ten levels of nested IF and ELSE commands. the Do group specified in the THEN parameter is processed.
Otherwise, the Do group specified by the ELSE command is
processed.
Examples
IF COND(&A \EQ &B) THEN(GOTO X) IF (&A \EQ YES)
IF (&A \EQ &B) THEN(GOTO X) DO
IF (&A \EQ &B) (GOTO X) CHGVAR &B 1
CHGVAR &C 'Z'
IF COND(&A \EQ &B) THEN(GOTO X) ENDDO
The examples above show a number of different ways the IF This example shows a Do group as the THEN parameter.
command can be specified to test a condition and branch to The two Change Variable (CHGVAR) commands are pro-
a label. In each of these examples, if &A equals &B, control cessed if, in the relational expression, &A is equal to YES.
passes to a CL command that has a label named X.
IF %SWITCH(1ðXXXX1ð) THEN(GOTO X)
IF COND(&TESTSW) THEN(CHGVAR VAR(&A) VALUE(23))
This example shows how the built-in function %SWITCH is
If &TESTSW has a logical value of 1 (true), the CHGVAR used to test the eight job switches in a job. Refer to the end
command is processed to set &A to decimal 23; if &TESTW of Chapter 3, “Expressions in CL Commands” for a complete
has a logical value of 0 (not true), the Change Variable description of %SWITCH. In this example, job switches 1, 2,
(CHGVAR) command is not processed. 7, and 8 are tested for the values indicated in the 8-character
IF ((&ALPHA \EQ &BETA) \AND \NOT &GAMMA) THEN(RETURN) mask. If switches 1 and 7 contain 1s and switches 2 and 8
contain 0s, then the program branches to the command
If the value of &ALPHA equals the value of &BETA and if having the label X. If any of the four switches do not contain
&GAMMA is a logical 0, then return to the program that the value indicated, the branch does not occur.
called this CL program.
55──INSFLMSVR──NWSD(────network-server-description-name────)──RSRCNAME(────resource-name────)───────────────────────────────────5
┌─15ðð──────────────────┐
(P) ───5
5──ADPTADR(────local-adapter-address────)──TCPPORTCFG(──port──internet-address──subnet-mask──┴─max-transmission-unit─┴──)────
5──┬─────────────────────────────────────┬──┬────────────────────────────────────────────┬──────────────────────────────────────5
│ ┌─\NONE───────────────┐ │ │ ┌─\NWSD──────────────────┐ │
└─TCPRTE(──┴─next-hop-IP-address─┴──)─┘ └─TCPHOSTNAM(──┴─TCP/IP-local-host-name─┴──)─┘
5──┬────────────────────────────────────────┬──┬───────────────────────────────────────┬──┬─────────────────────────┬───────────5
│ ┌─\SYS───────────────┐ │ │ ┌─\SYS───────────────┐ │ │ ┌─4M───┐ │
└─TCPDMNNAME(──┴─TCP/IP-domain-name─┴──)─┘ └─TCPNAMSVR(──┴─TCP/IP-name-server─┴──)─┘ └─LINESPEED(──┼─16M──┼──)─┘
└─\NWI─┘
5──┬──────────────────────────────────┬──┬───────────────────────────────────────────────────┬──────────────────────────────────5
│ ┌─\PRIMARY─────────┐ │ │ ┌─\NWSD─────────────────────────────┐ │
└─LNGVER(──┴─language-version─┴──)─┘ └─NWSSTG(──┴─network-server-storage-space-name─┴──)─┘
5──┬────────────────────────────────────────────────────┬──┬──────────────────────┬──┬─────────────────────────────┬───────────5%
│ ┌─5ðð───────────────────────────────┐ │ │ ┌─\YES─┐ │ │ ┌─\BLANK────────┐ │
└─NWSSIZE(──┴─network-server-storage-space-size─┴──)─┘ └─VRYCFG(──┴─\NO──┴──)─┘ └─TEXT(──┴─'description'─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
RSRCNAME
This command will create a network server description
Specifies the resource name that identifies the hardware
(*NWSD) object of type *BASE, the token-ring line
that the *NWSD object represents.
description (*LIND) object, the network storage space
(*NWSSTG) object, and add the server storage link. Note: Use the Work with Hardware Resources
(WRKHDWRSC) command with *CMN specified
If the following CL commands invoked by the INSFLMSVR for the TYPE parameter to help determine the
command have an error, the INSFLMSVR command will not resource name. Specify the resource name of
run successfully: the communications adapter. The resource
CRTNWSD name consists of the FSIOP resource name.
CRTLINTRN
ADPTADR
INSNWSAPP
Specifies the local system's token-ring adapter address.
Commands called by INSNWSAPP
– CRTNWSSTG adapter-address: Specify the adapter address to use.
– ADDNWSSTGL The adapter address must be in the range of
– VRYCFG 400000000000-7FFFFFFFFFFF. See the ADPTADR
documentation in the Communications Configuration
Restrictions: book to understand this value.
The Port number value specifies the FSIOP port number Alphabetical characters A through Z
to be configured. Specify one of the following values: Digits 0 through 9
Minus sign (-)
1: FSIOP port number 1 is configured. 2: FSIOP port
number 2 is configured. Note: These characters are all invariant characters.
Element 2: Internet address *NWSD: Specifies that the host name for the FSIOP is
IP-address: Specify the IP (internet) address for the port the same as the name specified for the NWSD param-
in the form, nnn.nnn.nnn.nnn, where nnn is a decimal eter on this command.
number ranging from 0 through 255. The IP address host-name: Specify a host name to be associated with
selected must be unique across all *NWSD objects and the FSIOP.
the AS/400 TCP/IP configuration. See the TCP/IP
Fastpath Setup book for general information about TCPDMNNAME
internet addresses. Specifies the local domain name associated with the
FSIOP. A domain name can be a text string having 2 to
Element 3: Subnet mask
255 characters. Domain names consist of one or more
subnet-mask: Specifies the subnet mask for the IP labels separated by periods. Each label can contain up
address. to 63 characters. The following characters are allowed
in domain names:
Element 4: Maximum transmission unit
1500: The maximum transmission unit (MTU) of the Alphabetical characters A through Z
interface is 1500 bytes. Digits 0 through 9
Minus sign (-)
maximum-transmission-unit: Specifies the maximum Period (.). Periods are only allowed when they sep-
transmission unit (MTU) of the interface, in bytes.
arate labels of domain style name.
*SYS: Specifies that the local domain name for the VRYCFG
FSIOP should be the same value as is configured for the Specify whether to vary on the NWSD created by this
AS/400 system. command.
*YES: The network server description (*NWSD) created
TCPNAMSVR
by this command will be varied on using the Vary Con-
Specifies the internet address of the name server
figuration (VRYCFG) command.
system that is used by the FSIOP. Typically, this is the
same value as it is for the AS/400 system. *NO: The network server description (*NWSD) created
by this command will not be varied on.
*SYS: The name server system used by the FSIOP
should be the same as for the AS/400 system. TEXT
*NONE: There is no name server to be used by the Specifies the description text to be associated with the
FSIOP. network server description (*NWSD).
name-server-address: Specify an internet address for *BLANK: No description text will be associated with the
the name server system to be used by the FSIOP. network server description.
LINESPEED
'description': Specify no more than 50 characters of text,
enclosed in apostrophes.
Specifies the line speed in bits per second (bps). The
possible values are:
4M: The line speed is four million bits per second. Example
16M: The line speed is sixteen million bits per second. INSFLMSRV NWSD(FMSVR) RSRCNAME(CCð2)
ADPTADR(4ðððððððððð1)
*NWI: The line speed used is for a network interface. TCPPORTCFG(1 '9.5.13.11' '255.255.255.128' 15ðð)
TCPRTE('9.5.3.1')
LNGVER
TEXT('FlowMark Server Network Descriptor')
Specifies the language version of the network server.
*PRIMARY: The language version for the currently This command does the following:
installed primary national language is used. Creates a network server description (*NWSD) named
language-version: Specify the language version of the FMSRV of type *BASE and is associated with the
network server product to be used. The language must resource named CC02.
be one of the installed versions of the network server Creates token ring line description (*LIND) named
product. Use the Work with Licensed Programs FMSVR using adapter address 400000000001.
(LICPGM) menu to determine the installed languages.
Configures port 1 with IP address 9.5.13.11 with a
NWSSTG subnet mask of 255.255.255.128 and a maximum trans-
Specifies the name of the network server storage space mission unit (MTU) of 1500 bytes.
that will be created. The storage space cannot already
The server uses the primary language, and the default
exist.
country code and code page associated with that lan-
*NWSD: Specifies the name of the client storage space guage.
will be the same as the NWSD name.
The network server storage space (*NWSSTG) FMSVR
network-server-storage-space-name: Specify the is created for the network server and is linked and
network storage space name to be used. Maximum assigned drive letter K.
length of the storage space name is 10 characters.
The network server is varied on.
Starts SRVIFS on the FSIOP.
(1) ───drive-letter────)───
55──INSNWSAPP──NWSAPP(──┬─\NOTES────┬──)──NWS(────network-server────)──DRVLTR(─── (P)────────────────────────5
├─\FIREWALL─┤
└─\FLOWMARK─┘
5──┬──────────────────────┬──┬─────────────────────────────┬──┬──────────────────────┬──────────────────────────────────────────5
│ ┌─\NO──┐ │ │ ┌─\NWS────────┐ │ │ ┌─\YES─┐ │
└─CRTDRV(──┴─\YES─┴──)─┘ └─FILSVR(──┴─file-server─┴──)─┘ └─VRYCFG(──┴─\NO──┴──)─┘
5──┬────────────────────────────────────────────────┬──┬────────────────────────────────────────────────────┬───────────────────5
│ ┌─\GEN─────────────────────────┐ │ │ ┌─\NWSAPP─────────────────────────┐ │
(2) ─┴─network-server-storage-space─┴──)─┘ └─NWSSIZE(───
└─NWSSTG(─── (2) ─┴─storage-space-size-in-megabytes─┴──)─┘
5──┬───────────────────────────────┬──┬───────────────────────────────┬──┬─────────────────────────────────────┬────────────────5
│ ┌─\NWSAPP─┐ │ │ ┌─\BLANK────────┐ │ │ ┌─'\NOTES'──────────┐ │
(2, 3, 4) ─┼─\HPFS───┼──)─┘ └─TEXT(───
└─FORMAT(─────── (2) ─┴─'description'─┴──)─┘ └─NTSDIR(───
(5) ─┴─'Notes-directory'─┴──)─┘
└─\FAT────┘
5──┬─────────────────────────────────────────────┬─────────────────────────────────────────────────────────────────────────────5%
│ ┌─'\NOTES\DATA'──────────┐ │
(5) ─┴─'Notes-data-directory'─┴──)─┘
└─NTSDTADIR(───
Notes:
1 DRVLTR(K) required when NWSAPP(*FIREWALL) is specified.
NWSSTG
Specifies the name of the network server storage space *NWSAPP: The format of the network server storage
that will be created. The storage space cannot already space that is created is based on the application speci-
exist. fied on the NWSAPP parameter.
Note: This parameter is valid only when For application *NOTES, the format will be HPFS.
CRTDRV(*YES) is specified.
*GEN: The name of the network server storage space For application *FIREWALL, the format will be HPFS.
is generated by the system using the network server
name and appending a number to make a unique name.
network-server-storage-space: Specify the network For application *FLOWMARK, the format will be HPFS.
server storage space name to be used. Maximum
length of the storage space name is 10 characters.
(P) ─┬──────────────────────────────────┬───────────5
55──INSPTF──LICPGM(──┬─\ALL─────────────────────────────────────────────┬──)────
│ ┌──
───────────────────────────────────────────┐ │ │ ┌─\SERVICE────────────┐ │
6 (1) ─┘
└───(──licensed-program──┬─release-level─┬──)─┴─── └─DEV(──┼─tape-device-name────┼──)─┘
└─\ONLY─────────┘ └─optical-device-name─┘
5──┬──────────────────────────┬──┬─────────────────────┬────────────────────────────────────────────────────────────────────────5
│ ┌─\SRVATT──┐ │ │ ┌─\NO──┐ │
└─INSTYP(──┼─\DLYIPL──┼──)─┘ └─HIPER(──┴─\YES─┴──)─┘
├─\DLYALL──┤
├─\IMMONLY─┤
└─\IMMDLY──┘
5──┬────────────────────────────────────────────────────────────────────────┬──┬─────────────────────────┬──────────────────────5
│ ┌──
───────────────────────────────────────────────────┐ │ │ ┌─\REWIND─┐ │
└─OMIT(─────6─(──licensed-program──PTF-ID──┬─release-level─┬──)─┴───
(2) ────)─┘ └─ENDOPT(──┼─\LEAVE──┼──)─┘
└─\ONLY─────────┘ └─\UNLOAD─┘
5──┬────────────────────────┬──────────────────────────────────────────────────────────────────────────────────────────────────5%
│ ┌─\IPLA─┐ │
└─RESTART(──┼─\SYS──┼──)─┘
└─\FULL─┘
Notes:
1 A maximum of 300 repetitions.
2 A maximum of 50 repetitions.
INSPTF does not support loading PTFs from tape for pro-
ducts that have multiple releases installed on the system. If
PTFs for such a product exist on the tape, the INSPTF will Optional Parameters
not load those PTFs and will return an error.
DEV
Note: To see the parameter and value descriptions for this Specifies the device from which the PTFs are loaded.
command, refer to the online help text. For more The device name must already be known on the system
information about printing the help text, refer to by a device description.
“Printing CL Command Descriptions” in Chapter 1.
*SERVICE: The PTFs sent from the service support
system are loaded.
Required Parameter tape-device-name: Specify the name of the tape device
LICPGM from which the PTFs are loaded.
Specifies the product ID, version, release, and modifica- optical-device-name: Specify the name of the optical
tion level of the products for which PTFs should be device that supports the CD-ROM media class from
installed. which the PTFs are installed.
*ALL: The available PTFs for all installed products are
installed. This must be the first and only value if speci-
fied. All values specified after it are ignored.
| This command will search the media for PTFs for the This command will load all PTFs for the products that are
| V4R2M0 Performance Tools product in the HIPER section. installed on the system, from the device TAP01. All PTFs in
Each PTF that can be applied immediately will be. Delayed loaded status on the system that can be applied immediately
PTFs will be loaded, but not marked for apply. will be. No delayed PTFs will be set for apply.
55──INZDKT──DEV(──device-name──)──┬───────────────────────────────────┬──┬────────────────────────────────────┬─────────────────5
│ ┌─\NONE─────────────┐ │ │ ┌─\BLANK───────────┐ │
└─NEWVOL(──┴─volume-identifier─┴──)─┘ └─NEWOWNID(──┴─owner-identifier─┴──)─┘
(P) ──┬─────────────────────┬──┬───────────────────────┬─────────────────5%
5──┬────────────────────────┬──┬──────────────────────┬───
│ ┌─\DATA───┐ │ │ ┌─\STD─┐ │ │ ┌─\YES─┐ │ │ ┌─\EBCDIC─┐ │
(1) ─┼─1───────┼──)─┘ └─SCTSIZ(──┼─128──┼──)─┘
└─FMT(─── └─CHECK(──┴─\NO──┴──)─┘ └─CODE(──┴─\ASCII──┴──)─┘
├─2───────┤ ├─256──┤
├─2D──────┤ ├─512──┤
├─\DATA2──┤ └─1ð24─┘
└─\SAVRST─┘
Notes:
1 If FMT(*SAVRST) is specified, CODE(*ASCII) cannot be specified.
IBM-supplied diskettes are initialized before they are shipped owner-identifier: Specify up to 14 uppercase alphabetic
to a customer. A diskette should be reinitialized when: or numeric characters that identify the new owner of the
diskette. Even if the value is enclosed in apostrophes,
Its format is changed.
no lowercase letters, embedded blanks, or special char-
The sequence of the records on the diskette is changed
acters can be used. If fewer than 14 characters are
(they can only be sequential).
specified, the field is left-justified and padded on the
A defect has occurred in one or two tracks.
right with blanks.
The diskette has been exposed to a strong magnetic
field. FMT
Specifies the format to use to initialize the diskette.
One INZDKT command can initialize only one diskette at a Either *DATA, *DATA2, 1, 2, or 2D can be specified if
time. the diskette will contain data files that are in the basic,
Note: When initializing diskettes with labels that are not IBM H, I, or System/36 environment exchange formats. The
standard labels, specify CHECK(*NO). basic exchange format has a set of requirements that
ensures that a diskette can be exchanged between
systems that are capable of using both the IBM diskette
Required Parameters types 1 or 2. *SAVRST (type E general data exchange)
DEV must be specified if the diskette is used in the AS/400
Specifies the name of the device in which the diskette system or System/38 save and restore operations; that
being initialized is placed. is, if their data files will contain saved objects. *SAVRST
is also a valid format for the System/36 save and restore
operations, and it is the preferred format to use.
*DATA: A one- or two-sided diskette is formatted with Table 16, at the end of this command description,
single-density recording. shows the valid sector sizes.
1: A one-sided diskette is formatted with single-density Format for 8-inch diskette.
recording.
Table 17, at the end of this command description,
2: A two-sided diskette is formatted with single-density shows the format for 5.25-inch diskette
recording.
The following chart shows which exchange types can be
2D: A two-sided diskette is formatted with double- used for each sector size.
density recording.
*DATA2: A two-sided diskette is formatted with double- Exchange
Type 128 256 512 1024
density recording (as if 2D is specified).
Basic X
*SAVRST: A two-sided diskette is formatted with
double-density recording. This format is required if the H X1
diskette is used in a save and restore operation. I X X X X
Notes: SAVRST X
S/36-S/R X X X X
1. Because *DATA2, *SAVRST, and 2D specify that
1 H is used only as the exchange type if the diskette is
the diskette is used for double-density recording, it
initialized with double-density recording (FMT(*DATA2)
is recommended that a type 2D diskette be used,
or FMT(2D)).
rather than a type 2. A type 2D diskette is made for
double-density recording, whereas a type 2 is made
for single-density recording and is more prone to
CHECK
media errors if used for double-density recording.
Specifies whether a check is made for active files (files
2. If FMT(*SAVRST) is specified, CODE(*ASCII) having an expiration date greater than the system date).
cannot be specified.
*YES: A check is performed on files whose labels are in
SCTSIZ cylinder 0 only. File labels in an extended file label area
Specifies the number of bytes per sector with which are not checked. If any active files are found, an oper-
each track is initialized. ator message is sent. The operator can continue initial-
ization (active files are destroyed), or end the
*STD: A standard sector size, based on the value of the
initialization of that diskette.
FMT parameter, is used. Such as the following:
*NO: Diskette initialization proceeds without a check for
SCTSIZ active files.
FMT (*STD)
*DATA 128 CODE
1 128 Specifies the character code used. The code can be
2 128 either extended binary-coded decimal interchange code
2D 256 (*EBCDIC) or the American National Standard Code for
*DATA2 256 Information Interchange (*ASCII).
*SAVRST 1024 *EBCDIC: The volume label is written in EBCDIC and is
128: Each track is initialized with 128 bytes per sector. an IBM standard label; subsequent data must also be
written in EBCDIC.
256: Each track is initialized with 256 bytes per sector.
*ASCII: The volume label is written in ASCII and is an
512: Each track is initialized with 512 bytes per sector. IBM standard label in the same format as the EBCDIC
1024: Each track is initialized with 1024 bytes per label; subsequent data must also be written in ASCII. If
sector. FMT(*SAVRST) is specified, *ASCII cannot be specified.
This command initializes the diskette device DKT1. The This command initializes the diskette in device DKT2 to the
diskette is checked for active files (CHECK(*YES) is save and restore format. The diskette is initialized with the
assumed). The diskette is formatted for basic data exchange NEWVOL parameter of SAVE. The owner identifier field has
files (FMT(*DATA) is assumed). The volume label has DON written into it.
ORIGIN written in the volume identifier field and DEPT504
written in the owner identifier field.
(P) ─┬───────────────────────┬───────────────────────────────────────────────────5%
55──INZDSTQ──DSTQ(──distribution-queue-name──)────
│ ┌─\NO────┐ │
└─CLEAR(──┼─\YES───┼──)─┘
└─\PURGE─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose the language used for the work station), the internal
value for a distribution queue name may differ from the
The Initialize Distribution Queue (INZDSTQ) command resets characters shown on the Work with Distribution Queue
the status of a distribution queue and the entries on the (WRKDSTQ) command. An error may be reported if the
queue. It also optionally clears all distributions on the queue. character-string value specified for the DSTQ parameter
This command applies to both the normal and high priority does not match the rules for an internal distribution
sections of the specified queue. queue value or if it does not match the internal value for
any defined distribution queue (ignoring case differ-
Attention: ences).
Initializing a distribution queue can result in the loss or dupli- Note: To see the parameter and value descriptions for this
cation of distributions in the network, depending on the status command, refer to the online help text. For more
of the distributions in transit at the time this command is run. information about printing the help text, refer to
“Printing CL Command Descriptions” in Chapter 1.
Initializing a distribution queue includes the following:
If a SNADS (Systems Network Architecture (SNA) distri- Required Parameter
bution services) sender job is active for the queue, the
job is ended. This job cancelation takes effect imme- DSTQ
diately. Distribution queues being sent are interrupted. Specifies the name of the distribution queue to initialize.
If the queue type is a SystemView distribution services The queue must be previously configured using the Con-
(SVDS) queue type and a receiver job is active for this figure Distribution Services (CFGDSTSRV) or the Add
connection, the job is ended. This job cancelation takes Distribution Queue (ADDDSTQ) command.
effect immediately. All partially received distributions are
discarded.
Optional Parameters
If the distribution queue is to be cleared, all distributions
on the queue are deleted as specified on the CLEAR CLEAR
parameter. Specifies whether distributions on the queue are deleted.
If the queue is not cleared, the distributions on the
Attention:
queue that do not have "Held" status are set to "Ready".
Distributions with a status of "Held" remain held. Using the *PURGE value results in the loss of distribu-
The queue status is set to "Ready" unless the queue is tions with no trace.
in the "Held" status. *NO: Distributions on the queue are not deleted.
If the QSNADS system is active, a SNADS sender job is
submitted for the queue following the same rules used to *YES: Distributions on the queue are deleted. Each
start the QSNADS subsystem. deleted distribution is logged and, if the distribution origi-
nator requested notification, a notification is sent to the
Distribution queue names are translated to the graphic char- originator or to the report destination specified in the dis-
acter set and code page 930 500, using the job's coded char- tribution.
acter set identifier (CCSID). Note: System Network Architecture distribution services
(SNADS) status distributions and distribution
Restrictions:
reports are used to report information about a
1. This command is shipped with public *EXCLUDE distribution back to the originator. Status report
authority, and the QPGMR and QSYSOPR user profiles distributions never result in another status report
have private authorities to use the command. distribution. If a status report distribution is
2. Messages that report errors about distribution queues deleted, no notification is sent.
may display or print different characters than the user
*PURGE: Distributions on the queue are deleted.
entered for the distribution queue name because of
Deleted distributions are not logged and no notification is
internal system transformations. Similarly (depending on
sent to the originator or to the report destination speci- Example 2: Initializing and Clearing a Distribution Queue
fied in the distribution. INZDSTQ DSTQ('ERRORQ') CLEAR(\YES)
(P) ────────────────────────────────────────────5
55──INZOPT──VOL(──volume-identifier──)──┬───────────────────────────────────────┬───
│ ┌─\VOL──────────────────┐ │
└─NEWVOL(──┴─new-volume-identifier─┴──)─┘
5──┬────────────────────────────────────────────┬──┬─────────────────────┬──┬─────────────────────────────┬─────────────────────5
│ ┌─95────────────────────┐ │ │ ┌─\YES─┐ │ │ ┌─\BLANK────────┐ │
(1) ─┴─volume-full-threshold─┴──)─┘ └─CHECK(──┴─\NO──┴──)─┘ └─TEXT(──┴─'description'─┴──)─┘
└─THRESHOLD(───
5──┬────────────────────────┬──┬──────────────────────┬────────────────────────────────────────────────────────────────────────5%
│ ┌─\PRIMARY─┐ │ │ ┌─\CALC─┐ │
└─TYPE(──┴─\BACKUP──┴──)─┘ └─CCSID(──┼─5ðð───┼──)─┘
└─85ð───┘
Notes:
1 This parameter is ignored and the threshold is set to 99 percent when TYPE(*BACKUP) is specified.
55──INZPCS──┬────────────────────────────────┬──┬─────────────────────────────────┬──┬──────────────────────────────────┬───────5
│ ┌─\DFT──────────┐ │ │ ┌─\DFT─────────────┐ │ │ ┌─\DFT─────────────┐ │
└─KBDTYPE(──┴─keyboard-type─┴──)─┘ └─ASCII(──┴─code-page-number─┴──)─┘ └─EBCDIC(──┴─code-page-number─┴──)─┘
(P) ──────────────────────────────────────────────────────────────────────────────5%
5──┬─────────────────────────────────────────┬───
│ ┌─\DFT──────────────────┐ │
└─LANGUAGE(──┴─language-feature-code─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
Table 18 (Page 2 of 2). Keyboard Mapping *DFT: The primary language of Client Access is pro-
Language/Country Iden- ASCII cessed.
tifier Device
Group language-feature-code: Specify the language feature
Sweden SWB B code of the language to process. Values are listed
Sweden Multinational SWI B below:
Switzerland/French SFI B
Multinational Table 19. Language Feature Identifiers
Switzerland/German SGI B Language Identifier
Multinational Arabic 2954
Thai THB Belgium Dutch 2963
Turkey (Qwerty) TKB Belgium French 2966
Turkey (F) TRB Brazilian Portuguese 2980
Ukraine UAB Canadian French 2981
United Kingdom UKB A, B Croatian 2912
United Kingdom Multinational UKI A, B Czech 2975
United States/Canada USB A, B, C Danish 2926
United States/Canada USI A, B, C Dutch 2923
Multinational English 2924
Urdu PKB English U/L (DBCS) 2984
Vietnam VNB English Uppercase 2950
Languages of the former YGI English Uppercase/DBCS) 2938
Yugoslavia Farsi 2998
Note: Finnish 2925
1
French 2928
The GNB code is the current identifier for Greece. The
French-MNCS 2940
GKB code was used prior to V2R1, and continues to be
German 2929
supported, but provides fewer characters than the recom-
German-MNCS 2939
mended GNB code.
Greek 2957
Hebrew 2961
Note: For example, KBDTYPE(USB) indicates a key- Hungarian 2976
board using the United States/Canada character Icelandic 2958
set. Italian 2932
Italian-MNCS 2942
ASCII Japanese (DBCS) 2962
Specifies the ASCII code page number to use. Korean (DBCS) 2986
*DFT: The default PC code page number is used. Norwegian 2933
Polish 2978
When the command is run for the first time, the default
Portuguese 2922
value is 437 for keyboard types USB and USI and 850 Portuguese-MNCS 2996
for most others. When the command is run after the first Russian 2979
time, the default value takes the value specified at the Slovakian 2994
previous running of the command. Slovenian 2911
Spanish 2931
code-page-number: Specify the ASCII code page
Swedish 2937
number to use. Thai 2972
Traditional Chinese (DBCS) 2987
EBCDIC
Turkish 2956
Specifies the EBCDIC (or host) code page number to
use.
*DFT: The default system code page number is used. Example
When the command is first run, the default value comes INZPCS
from the code page portion of the system value
QCHRID. When the command is run after the first time, This command copies or merges all machine readable infor-
the default takes the value specified in the previous mation (MRI) into personal computer programs. The default
running of the command. keyboard type used is determined from the system value
QKBDTYPE. A default ASCII code page is selected based
code-page-number: Specify the 3-character EBCDIC (or on the KBDTYPE. This is usually 850 for keyboard types
host code) page number to use. other than USB or USI. The EBCDIC code page number is
LANGUAGE determined from the system value QCHRID.
Specifies the language feature identifier (ID) of the sec-
ondary language to be processed.
┌─\LIBL/────────┐
55──INZPFM──FILE(──┼───────────────┼──physical-file-name──)──┬────────────────────────────────────────┬─────────────────────────5
├─\CURLIB/──────┤ │ ┌─\FIRST────────────────────┐ │
└─library-name/─┘ └─MBR(──┼─\LAST─────────────────────┼──)─┘
└─physical-file-member-name─┘
(P) ──┬────────────────────────────────┬────────────────────────────────────────────────────────────5%
5──┬───────────────────────┬───
│ ┌─\DFT─┐ │ │ ┌─\NXTINCR──────┐ │
└─RECORDS(──┴─\DLT─┴──)─┘ └─TOTRCDS(──┴─total-records─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
*LIBL: All libraries in the job's library list are *NXTINCR: The number of records in the member is
searched until the first match is found. increased to extend the file to the next allocation incre-
ment. If the member is empty, records are added to
*CURLIB: The current library for the job is meet the first allocation specified for the member. If
searched. If no library is specified as the current SIZE(*NOMAX) is specified when the file is created,
library for the job, the QGPL library is used. *NXTINCR is not valid.
(P)─┬─────────────────────────────────────────────────────┬──────────────────────────────────────────────────────────5%
55──INZSYS───
│ ┌─\SYSOPR───────────────────────────────┐ │
│ │ ┌─\LIBL/────────┐ │ │
└─MSGQ(──┴─┼───────────────┼──message-queue-name─┴──)─┘
├─\CURLIB/──────┤
└─library-name/─┘
Note:
P All parameters preceding this point can be specified in positional form.
(P) ──────────5
55──INZTAP──DEV(──device-name──)──┬───────────────────────────────────────┬──┬────────────────────────────────────┬───
│ ┌─\NONE─────────────────┐ │ │ ┌─\BLANK───────────┐ │
└─NEWVOL(──┼─\CTGID────────────────┼──)─┘ └─NEWOWNID(──┴─owner-identifier─┴──)─┘
└─new-volume-identifier─┘
5──┬────────────────────────────────┬──┬───────────────────────┬──┬────────────────────────────┬──┬───────────────────────┬─────5
│ ┌─\MOUNTED──────────┐ │ │ ┌─\YES───┐ │ │ ┌─\DEVTYPE──┐ │ │ ┌─\EBCDIC─┐ │
└─VOL(──┴─volume-identifier─┴──)─┘ └─CHECK(──┼─\NO────┼──)─┘ └─DENSITY(──┼─\CTGTYPE──┼──)─┘ └─CODE(──┴─\ASCII──┴──)─┘
└─\FIRST─┘ ├─16ðð──────┤
├─32ðð──────┤
├─625ð──────┤
├─\FMT348ð──┤
├─\FMT349ðE─┤
├─\FMT357ð──┤
├─\FMT357ðE─┤
├─\FMT359ð──┤
├─\QIC12ð───┤
├─\QIC525───┤
├─\QIC1ððð──┤
├─\QIC2GB───┤
├─\QIC3ð4ð──┤
├─\QIC5ð1ð──┤
├─\FMT2GB───┤
├─\FMT5GB───┤
└─\FMT7GB───┘
5──┬─────────────────────────┬──┬─────────────────────┬────────────────────────────────────────────────────────────────────────5%
│ ┌─\REWIND─┐ │ │ ┌─\NO──┐ │
└─ENDOPT(──┴─\UNLOAD─┴──)─┘ └─CLEAR(──┴─\YES─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
*FMT3490E: The format of this tape is FMT3490E. The *REWIND: The tape is automatically rewound, but not
data density on this tape volume is formatted to support unloaded, after the operation has ended.
a 3490E device. This density is used for 1/2 inch car- *UNLOAD: The tape is automatically rewound and
tridge tapes. unloaded after the operation ends.
*FMT3570: The format of this tape is FMT3570. The CLEAR
data format is written on the tape volume with a 3570 Specifies whether all previous labels and data are
device. deleted from the tape when it is initialized. If the volume
*FMT3570E: The format of this tape is FMT3570E. The must be cleared of all data, it is spaced from the location
data format is written on the tape volume with a 3570E of the initializing volume label or tape markers to the end
device. of the tape marker.
*FMT3590: The format of this tape is FMT3590. The *NO: The existing data is not deleted. Even though the
data format is written on the tape volume with a 3590 existing data is not deleted, the data on the volume is
device. This density is used for 1/2 inch cartridge tapes. not accessible after the volume has been initialized.
*QIC120: The format of this tape is QIC120, which is *YES: After the beginning of the tape has been initial-
used for 1/4 inch cartridge tapes that can hold 120 ized, the remaining data on the tape is deleted. The
megabytes of data. *YES value is needed only if there are security concerns
with old data. If *YES is specified, the initialize opera-
*QIC525: The format of this tape is QIC525, which is
tion can take a long time.
used for 1/4 inch cartridge tapes that can hold 525
megabytes of data.
*QIC1000: The format of this tape is QIC1000, which is Example
used for 1/4 inch cartridge tapes that can hold 1200 INZTAP DEV(TAPE1) NEWVOL(Tðð1ðð) CHECK(\NO)
megabytes of data. CODE(\ASCII) ENDOPT(\UNLOAD)
This command initializes the volume on the tape device field). Once the volume has been initialized, the tape is
named TAPE1 using the ASCII character code. Its new rewound and unloaded. Any previous data beyond the new
volume identifier is T00100, regardless of whether it contains volume label is not deleted, but is no longer accessible.
a valid volume identifier or files that have not ended (active
IPXPING Command
IPXPING Command
For the description of the IPXPING command, see the VFYIPXCNN (Verify IPX Connection) command description.
(1, 5) ─┬─\ALL──────────────────────────────────┬──)────
55──LNKDTADFN──OPTION(──┬─\LINK───┬──)──FILE(───── (P) ─────────────────────────────5
└─\UNLINK─┘ │ ┌─\LIBL/────────┐ │
└─┼───────────────┼──database-file-name─┘
├─\CURLIB/──────┤
└─library-name/─┘
5──┬──────────────────────────────────────┬──┬─────────────────────────────────┬──┬───────────────────────────┬────────────────5%
(2, 5) ─data-dictionary-name──)─┘ └─DFN(───
└─DTADCT(───── (3) ─file-definition-name──)─┘ │ ┌─\FIRST─┐ │
(4) ─┴─date───┴──)─┘
└─CRTDATE(───
Notes:
1 FILE(*ALL) is not valid with OPTION(*LINK).
2 DTADCT is required with OPTION(*LINK), and is required with FILE(*ALL) for OPTION(*UNLINK).
5 FILE name and DTADCT name cannot be used together for OPTION(*UNLINK).
(P) ─┬───────────────────────────────────┬──┬─────────────────────────────────┬─────────5
55──LODPTF──LICPGM(──licensed-program──)────
│ ┌─\SERVICE─────────────┐ │ │ ┌─\SEARCH─────────┐ │
└─DEV(──┼─\SAVF────────────────┼──)─┘ └─SEQNBR(──┴─sequence-number─┴──)─┘
├─diskette-device-name─┤
├─tape-device-name─────┤
└─optical-device-name──┘
5──┬─────────────────────────┬──┬─────────────────────────────────────┬──┬───────────────────────────────────────────────┬──────5
│ ┌─\REWIND─┐ │ │ ┌─\FIRST──────────┐ │ │ ┌─\LIBL/────────┐ │
(1, 2) ─┼─\SELECT─────────┼──)─┘ └─SAVF(───
└─ENDOPT(──┼─\LEAVE──┼──)─┘ └─PATHID(───── (3) ─┼───────────────┼──save-file-name──)─┘
└─\UNLOAD─┘ └─path-identifier─┘ ├─\CURLIB/──────┤
└─library-name/─┘
5──┬───────────────────────────────────┬──┬──────────────────────────┬──┬──────────────────────┬────────────────────────────────5
│ ┌─\ALL──────────────┐ │ │ ┌─\APYPERM─┐ │ │ ┌─\YES──┐ │
│ │ ┌──
────────────┐ │ │ └─SPRPTF(──┴─\NOAPY───┴──)─┘ └─COVER(──┼─\NO───┼──)─┘
6 (4)
├─SELECT(──┴───PTF-number─┴────┴──)─┤ └─\ONLY─┘
│ ┌──
────────────┐ │
6 (4) ──)───────┘
└─OMIT(────PTF-number─┴───
5──┬────────────────────────────┬──────────────────────────────────────────────────────────────────────────────────────────────5%
│ ┌─\ONLY─────────┐ │
└─RLS(──┴─release-level─┴──)─┘
Notes:
P All parameters preceding this point can be specified in positional form.
Purpose DEV
Specifies the device from which the PTFs are loaded.
The Load Program Temporary Fix (LODPTF) command The device name must already be known on the system
loads program temporary fixes (PTFs) for a specified product by a device description.
from a diskette, tape, CD-ROM, or save file into the product
*SERVICE: The PTFs sent from the service support
PTF library. Each PTF contains one or more objects,
system are loaded.
including programs, that can be applied to a product by the
Apply Program Temporary Fix (APYPTF) command. *SAVF: The PTFs are loaded from a save file. If
*SAVF is specified, a save file name must be specified
Only the PTFs for a single product, such as Operating on the SAVF parameter.
System/400, can be loaded at a time. Not all of the PTFs for
diskette-device-name: Specify the name of the diskette
the specified program must be loaded, because specific
device from which the PTFs are loaded.
PTFs can be selected or omitted and loaded.
tape-device-name: Specify the name of the tape device
Restriction: This command is shipped with public from which the PTFs are loaded.
*EXCLUDE authority and the QSRV user profile has private
optical-device-name: Specify the name of the optical
authority to use the command.
device that supports the CD-ROM media class from
Note: To see the parameter and value descriptions for this which the PTFs are loaded.
command, refer to the online help text. For more
information about printing the help text, refer to SEQNBR
“Printing CL Command Descriptions” in Chapter 1. Specifies the sequence number on the tape volume
where the load operation begins to load the PTF data.
Note: This parameter is valid only if a tape device
Required Parameter name is specified on the DEV parameter.
LICPGM *SEARCH: The tape volume is searched for the first
Specifies the 7-character identifier of the product for program temporary fix (PTF) file for the specified
which the PTFs are loaded. licensed program.
sequence-number: Specify the sequence number of the
Optional Parameters PTF file being loaded. This sequence number must
| exist on the tape. Valid values range from 1 to *CURLIB: The current library for the job is
| 16777215. searched. If no library is specified as the current
library for the job, the QGPL library is used.
ENDOPT
Specifies the operation that is automatically performed library-name: Specify the name of the library to be
on the tape volume after the operation ends. If more searched.
than one volume is included, this parameter applies only
save-file-name: Specify the save file name from which
to the last tape volume used; all other tape volumes are
the PTFs are loaded.
rewound and unloaded when the end of the tape is
reached. SELECT
Specifies which of the PTFs for the specified product are
Note: This parameter is valid only if a tape device
loaded. The OMIT parameter cannot be specified if
name is specified on the DEV parameter.
SELECT is specified with PTF numbers.
*REWIND: The tape is automatically rewound, but not
Note: Permanently removed PTFs will be ignored when
unloaded, after the operation has ended.
SELECT(*ALL) and DEV(*SERVICE) are speci-
*LEAVE: The tape does not rewind or unload after the fied. To load removed PTFs, specify the PTF
operation ends. It remains at the current position on the number on the SELECT parameter.
tape drive.
*ALL: All the PTFs for the specified product are loaded.
*UNLOAD: The tape is automatically rewound and
unloaded after the operation ends.
PTF-number: Specify the PTF identification numbers
(up to 50) of the single PTFs being loaded.
PATHID
OMIT
Specifies the number that identifies a file on the
Specifies that all PTFs, except those specified in this
CD-ROM volume that contains the PTFs to be loaded.
parameter, are loaded. Specify the PTF numbers of the
The PTF files for each product and release that exist on
PTFs that are omitted when the rest are loaded. Up to
the CD-ROM media have a path identifier number to
50 PTF numbers can be specified. The OMIT parameter
allow the files to be processed in a specific order. Only
cannot be specified if single PTF numbers are specified
the PTFs from the specified path identifier are loaded on
on the SELECT parameter.
your system.
Note: This parameter is valid only if a CD-ROM device SPRPTF
name is specified on the DEV parameter. Specifies which operation is performed for temporarily
applied PTFs that are superseded by PTFs encountered
*FIRST: The CD-ROM volume is searched for the first by this load operation.
PTF file for the specified product and release, according
to the search dependency specified on the SELECT *APYPERM: For the specified product, any PTFs that
parameter. are temporarily applied and are superseded by PTFs
contained on the PTF media, are automatically perma-
When a specific PTF identifier is specified on the nently applied before loading the superseding PTFs. If
SELECT parameter, the first occurrence of the the superseded PTFs have any prerequisite PTFs, they
specified PTF is loaded. are also permanently applied by this operation.
When *ALL is specified on the SELECT parameter, *NOAPY: The load operation stops when temporarily
the existing PTF file with the lowest path identifier is applied PTFs are being superseded by PTFs contained
loaded. on the PTF medium. The temporarily applied PTFs that
are superseded must be permanently applied (APYPTF
*SELECT: A list of the PTF files that exist on the
command) or removed (RMVPTF command) before the
CD-ROM device that match the product and release is
LODPTF command can be processed again.
shown. You can select the specific file from which PTFs
are loaded. This value cannot be selected in a batch COVER
environment. Specifies whether to copy the cover letter for the PTF
path-identifier: Specify the path identifier of the existing into a physical file.
PTF file from which to load the PTF data. Note: This parameter is valid only when a tape device
name or optical device name is specified on the
SAVF
DEV parameter.
Specifies the qualified name of the save file from which
the PTFs are loaded. *YES: After the PTF is loaded, the cover letter is copied
into a physical file.
The name of the save file can be qualified by one of the
following library values: *NO: The cover letter is not copied into a physical file.
*LIBL: All libraries in the job's library list are *ONLY: The cover letter is copied into a physical file
searched until the first match is found. but the PTF is not loaded. If the SEQNBR parameter is
specified, it must contain the sequence number of the If the release-level specified is not the release-level of
file that contains the PTF. the base option of the product, only PTFs for the options
installed at that release-level are loaded.
RLS
Specifies the release level of the PTFs being loaded.
*ONLY: This value is only valid when one release of the Example
product's base option is installed on the system. PTFs
for all installed options of the product will be loaded Example 1: Omitting PTFs
regardless of the release-level of the option. LODPTF LICPGM(5769SS1)
OMIT(SFðððð3 SFðððð8 SFðððð14)
release-level: Specify the release level in VxRyMz
This command loads all of the PTFs from the service support
format, where Vx is the version number, Ry is the
system (*SERVICE) for the product 5769-SS1 except
release number, and Mz is the modification level. The
SF00003, SF00008, and SF000014. The Apply Program
variables x and y can be a number from 0 through 9,
Temporary Fix (APYPTF) command can then be used to
and the variable z can be a number from 0 through 9 or
apply these PTFs to the OS/400 system product.
a letter from A through Z.
Example 2: Selecting PTFs
If the release-level specified is the release-level of the LODPTF LICPGM(5769SS1) DEV(OPTð1)
base option of the product, PTFs for all installed options SELECT(SFðððð9 SFððð1ð)
of the product are loaded regardless of the release-level
of the option. This command loads the PTFs named SF00009 and
SF00010 from the CD-ROM device named OPT01. The
Apply Program Temporary Fix (APYPTF) command can then
be used to apply these PTFs to the OS/400 system product.
(P) ───────────────────────────────────────────5%
55──LODQSTDB──┬──────────────────────────────────┬──┬───────────────────────────┬───
│ ┌─\SELECT───────────┐ │ │ ┌─QUSRSYS──────┐ │
└─QSTDB(──┴─question-database─┴──)─┘ └─LIB(──┴─library-name─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
(P) ──┬───────────────────────────────────┬──┬───────────────────────────────┬──────5%
55──LODRUN──┬──────────────────────────────┬───
│ ┌─\TAP────────────┐ │ │ ┌─\FIRST──────────┐ │ │ ┌─/──────────────┐ │
└─DEV(──┼─\DKT────────────┼──)─┘ (1) ─┼─\SEARCH─────────┼──)─┘ └─DIR(───
└─SEQNBR(─── (2) ─┴─directory-name─┴──)─┘
├─\OPT────────────┤ └─sequence-number─┘
├─tape-device─────┤
├─diskette-device─┤
└─CD-ROM-device───┘
Notes:
1 This parameter is valid only when DEV(*TAP) is specified.
this fails, the program is restored, but all public and command to save any other necessary applications, pro-
private authorities are revoked and ownership of the grams, or libraries to the tape or diskette. This step is
program is transferred to the QDFTOWN user profile. optional and is used to save applications that the
The LODRUN command does not transfer control to QINSTAPP program restores to the user's system when
the QINSTAPP program in this case. the LODRUN command is run.
The user supplying the QINSTAPP program is responsible If the QINSTAPP program is saved to tape, the tape is
for writing and supporting it. The QINSTAPP program is not not rewound after the QINSTAPP program is restored;
supplied by IBM. The program can be designed to accom- the application or series of applications that the
plish many different tasks. For example, the program could: QINSTAPP program restores to the user's system
should be next on the tape.
Restore and run other programs or applications
Note: To see the parameter and value descriptions for this
Restore a library command, refer to the online help text. For more
Delete another program or application information about printing the help text, refer to
“Printing CL Command Descriptions” in Chapter 1.
Create specific environments
Apply fixes to existing applications
Optional Parameters
The QINSTAPP program is run only once each time the DEV
LODRUN command is entered. The LODRUN command Specifies the I/O device from which the program is
passes only one parameter (DEV), which specifies the device loaded.
from which the QINSTAPP program is restored. The
QINSTAPP program should not attempt to use the LODRUN *TAP: The program is loaded from the default tape
command again. This will have unpredictable results. device connected to the system.
*DKT: The program is loaded from the default diskette
In addition to writing the QINSTAPP program, the user sup- device connected to the system.
pling the program is responsible for providing the user with
the media containing the program. To distribute the program *OPT: The program is loaded from the default CD-ROM
on a tape, diskette, or CD-ROM, do the following: device connected to the system.
1. Prepare the tape or diskette. For tape, use the Initialize tape-device: Specify the name of the tape device from
Tape (INZTAP) command. For diskette, use the Ini- which the program is loaded onto the system.
tialize Diskette (INZDKT) command with FMT(*SAVRST) diskette-device: Specify the name of the diskette unit
specified. from which the program is loaded onto the system.
Note: For optical, the program must first be saved to CD-ROM-device: Specify the name of the CD-ROM
tape to later be transferred onto CD-ROM. See device from which the program is loaded onto the
the Central Site Distribution book for full details system.
on mastering CD-ROM.
SEQNBR
2. Use the Create Duplicate Object (CRTDUPOBJ) Specifies, only when tape is used, the sequence number
command to create the QINSTAPP program into the used for the restore operation.
QTEMP library.
*FIRST: The volume on a tape device is searched
3. Use the Save Object (SAVOBJ) command to save the starting from the first data file for a data file with an iden-
QINSTAPP program from QTEMP to the desired tape tifier that is a match for the QTEMP label. When the
device or diskette unit. The program must be the only first match is found, the object is restored.
object in the media file that contains it. Specify the fol-
lowing: *SEARCH: The volume on a tape device is searched
starting from the first data file beyond the current tape
LIB(QTEMP) position for a data file with an identifier that is a match
LABEL(*LIB) for the QTEMP label. When a match is found, the object
is restored.
CLEAR(*ALL)
| sequence-number: Specify the sequence number of the
Specifying LABEL(*LIB) ensures that the label will be
| file. Valid values range from 1 through 16777215.
QTEMP. If the QINSTAPP program is being saved to a
tape device, and if additional applications, programs, or DIR
libraries will be saved to tape, ENDOPT(*LEAVE) also Specifies, only when CD-ROM is used, the directory
must be specified. The correct value for the TGTRLS used for the restore operation. If the file named QTEMP
parameter must also be entered if the target release is is found in the specified directory, the object is restored.
not the default, *CURRENT.
/: The root directory (/) is used.
4. Use the Save Object (SAVOBJ), Save Library
(SAVLIB), or Save License Program (SAVLICPGM)
directory-name: Specify the directory to search for a file library QTEMP. Control is then transferred to the restored
named QTEMP. program. If the sequence number is not found, an escape
message is sent. If the file label at that sequence number is
not QTEMP, an escape message is sent.
Examples
Example 3: Restoring the Program QINSTAPP from
Example 1: Restoring a Program from Tape
CD-ROM
LODRUN DEV(TAPð1)
LODRUN DEV(\OPT) DIR(/APP1/INST)
This command restores the program object from the tape on
This command restores the program object QINSTAPP from
device TAP01 to the library QTEMP. Control is then trans-
the CD-ROM on device OPT01 to the library QTEMP. The
ferred to the restored program.
filename for the QTEMP library on the CD-ROM is
Example 2: Restoring the Program QINSTAPP from Tape /APP1/INST/QTEMP. Control is then transferred to the
restored program. If the file is not found, an escape
LODRUN DEV(TAPð1) SEQNBR(5) message is sent.
This command restores the program object QINSTAPP from
the tape at sequence number 5 on device TAP01 to the
(P) ─┬─────────────────────────────────────────┬──────────────────────────────────────────5
55──MD──DIR(──'directory-path-name'──)────
│ ┌─\INDIR──────────────────┐ │
└─DTAAUT(──┼─\RWX────────────────────┼──)─┘
├─\RW─────────────────────┤
├─\RX─────────────────────┤
├─\WX─────────────────────┤
├─\R──────────────────────┤
├─\W──────────────────────┤
├─\X──────────────────────┤
├─\EXCLUDE────────────────┤
├─\NONE───────────────────┤
└─authorization-list-name─┘
5──┬──────────────────────────────────────┬──┬──────────────────────────────┬──────────────────────────────────────────────────5%
│ ┌─\INDIR───────────────┐ │ │ ┌─\SYSVAL─┐ │
(2) ─┼─\NONE───┼──)─┘
└─OBJAUT(──┼─\NONE────────────────┼──)─┘ └─CRTOBJAUD(───
├─\ALL─────────────────┤ ├─\USRPRF─┤
│ ┌──
───────────────┐ │ ├─\CHANGE─┤
6 (1)
└───┬─\OBJEXIST─┬─┴────┘ └─\ALL────┘
├─\OBJMGT───┤
├─\OBJALTER─┤
└─\OBJREF───┘
Notes:
P All parameters preceding this point can be specified in positional form.
1 A maximum of 4 repetitions.
DTAAUT OBJAUT
Specifies the public data authority given to the user for Specifies the public object authority given to users for
the directory. the directory.
*INDIR: The authority for the directory being created is *INDIR: The object authority is based on the authority
determined by the directory it is being created in. The for the directory where this directory is being created. If
directory immediately preceding the new directory deter- the value *INDIR is specified for either the OBJAUT
mines the authority. A directory created in the root is parameter or the DTAAUT parameter, then *INDIR must
assigned the public authority given to objects in the root be specified for both parameters.
directory. A directory created in QDLS for a folder
*NONE: None of the other object authorities (existence,
defaults to *EXCLUDE for a first level folder. If created
management, alter or reference) are given to the users.
in the second level or greater, the authority of the pre-
If *EXCLUDE or an authorization list is specified for the
vious level is used. The QOpenSys and root file
DTAAUT parameter, *NONE must be specified. This
systems use the parent directory's DTAAUT value. If the
value cannot be used with the DTAAUT value of *NONE.
value *INDIR is specified for either the OBJAUT param-
eter or the DTAAUT parameter, then *INDIR must be *ALL: All of the other object authorities (existence,
specified for both parameters. management, alter, and reference) are given to the
users.
*RWX: The user can change the object and perform
basic functions on the object except those limited to the You can specify up to four of the following values:
owner or controlled by object existence, object manage- *OBJEXIST: The user is given object existence
ment, object alter and object reference authority. *RWX authority to the object. The user can control existence
provides object operational authority and all data authori- and ownership, delete, free storage of the object,
ties. perform save/restore operations and transfer ownership
*RW: The user can view and modify the contents of an of the object.
object. *RW authority provides object operational *OBJMGT: The user is given object management
authority and data read, add, update and delete authori- authority to the object. With this authority the user can
ties. specify security for the object, move or rename the
*RX: The user can perform basic operations on the object and add members to database files.
object, such as run a program or display the contents of *OBJALTER: The user is able to alter the attributes of
a file. The user is prevented from changing the object. the objects. On a database file, the user can add and
*RX authority provides object operational authority and remove triggers, add and remove referential and unique
read and execute authorities. constraints, and change the attributes of the database
*WX: The user can modify the contents of an object file. With this authority on an SQL package, the user
and run a program or search a library or directory. *WX can change the attributes of the SQL package. Cur-
authority provides object operational, and data add, rently, this authority is used only for database files and
update, delete, and execute authorities. SQL packages.
*R: The user can view the contents of an object. *R *OBJREF: The user is given object reference authority
authority provides object operational authority and data to objects. Used only for database files, the user can
read authority. refer to an object from another object such that oper-
ations on that object may be restricted by the other
*W: The user can modify the contents of an object. *W
object. On a physical file, the user can add a referential
authority provides object operational authority and data
constraint in which the physical file is the parent.
add, update, and delete authorities.
CRTOBJAUD
*X: The user can run a program or search a library or
Specifies the auditing value of objects created in this
directory. *X authority provides object operational
directory.
authority and data execute authority.
Note: This parameter is ignored when using this
*EXCLUDE: The user cannot access the PTFs being
command in QDLS. No error message is sent
loaded. The OBJAUT value must be *NONE, if this
and the directory is created.
special value is used.
*SYSVAL: The object auditing value for the objects in
*NONE: The user is given no data authorities to the
the directory is determined by the system auditing value
objects. This value cannot be used with OBJAUT value
(QAUDLVL).
of *NONE.
*NONE: Using or changing this object will not cause an
authorization-list-name: Specify the name of the authori-
audit entry to be sent to the security journal.
zation list used. The format of the authorization list
name remains the current ten-character format. The *USRPRF: The user profile of the user accessing this
OBJAUT value must be *NONE, if this special value is object is used to determine if an audit record will be sent
used. for this access. The OBJAUD keyword of the
(P) ─┬─────────────────────────────────────────┬───────────────────────────────────────5
55──MKDIR──DIR(──'directory-path-name'──)────
│ ┌─\INDIR──────────────────┐ │
└─DTAAUT(──┼─\RWX────────────────────┼──)─┘
├─\RW─────────────────────┤
├─\RX─────────────────────┤
├─\WX─────────────────────┤
├─\R──────────────────────┤
├─\W──────────────────────┤
├─\X──────────────────────┤
├─\EXCLUDE────────────────┤
├─\NONE───────────────────┤
└─authorization-list-name─┘
5──┬──────────────────────────────────────┬──┬───────────────────────────────┬─────────────────────────────────────────────────5%
│ ┌─\INDIR───────────────┐ │ │ ┌─\SYSVAL─┐ │
(2) ──)─┘
└─OBJAUT(──┼─\NONE────────────────┼──)─┘ └─CRTOBJAUD(──┼─\NONE───┼───
├─\ALL─────────────────┤ ├─\USRPRF─┤
│ ┌──
───────────────┐ │ ├─\CHANGE─┤
6 (1)
└───┬─\OBJEXIST─┬─┴────┘ └─\ALL────┘
├─\OBJMGT───┤
├─\OBJALTER─┤
└─\OBJREF───┘
Notes:
P All parameters preceding this point can be specified in positional form.
1 A maximum of 4 repetitions.
*INDIR: The authority for the directory being created is *INDIR: The object authority is based on the authority
determined by the directory it is being created in. The for the directory where this directory is being created. If
directory immediately preceding the new directory deter- the value *INDIR is specified for either the OBJAUT
mines the authority. A directory created in the root is parameter or the DTAAUT parameter, then *INDIR must
assigned the public authority given to objects in the root be specified for both parameters.
directory. A directory created in QDLS for a folder
*NONE: None of the other object authorities (existence,
defaults to *EXCLUDE for a first level folder. If created
management, alter or reference) are given to the users.
in the second level or greater, the authority of the pre-
If *EXCLUDE or an authorization list is specified for the
vious level is used. The QOpenSys and root file
DTAAUT parameter, *NONE must be specified. This
systems use the parent directory's DTAAUT value. If the
value cannot be used with the DTAAUT value of *NONE.
value *INDIR is specified for either the OBJAUT param-
eter or the DTAAUT parameter, then *INDIR must be *ALL: All of the other object authorities (existence,
specified for both parameters. management, alter, and reference) are given to the
users.
*RWX: The user can change the object and perform
basic functions on the object except those limited to the You can specify up to four of the following values:
owner or controlled by object existence, object manage- *OBJEXIST: The user is given object existence
ment, object alter and object reference authority. *RWX authority to the object. The user can control existence
provides object operational authority and all data authori- and ownership, delete, free storage of the object,
ties. perform save/restore operations and transfer ownership
*RW: The user can view and modify the contents of an of the object.
object. *RW authority provides object operational *OBJMGT: The user is given object management
authority and data read, add, update and delete authori- authority to the object. With this authority the user can
ties. specify security for the object, move or rename the
*RX: The user can perform basic operations on the object and add members to database files.
object, such as run a program or display the contents of *OBJALTER: The user is able to alter the attributes of
a file. The user is prevented from changing the object. the objects. On a database file, the user can add and
*RX authority provides object operational authority and remove triggers, add and remove referential and unique
read and execute authorities. constraints, and change the attributes of the database
*WX: The user can modify the contents of an object file. With this authority on an SQL package, the user
and run a program or search a library or directory. *WX can change the attributes of the SQL package. Cur-
authority provides object operational, and data add, rently, this authority is used only for database files and
update, delete, and execute authorities. SQL packages.
*R: The user can view the contents of an object. *R *OBJREF: The user is given object reference authority
authority provides object operational authority and data to objects. Used only for database files, the user can
read authority. refer to an object from another object such that oper-
ations on that object may be restricted by the other
*W: The user can modify the contents of an object. *W
object. On a physical file, the user can add a referential
authority provides object operational authority and data
constraint in which the physical file is the parent.
add, update, and delete authorities.
CRTOBJAUD
*X: The user can run a program or search a library or
Specifies the auditing value of objects created in this
directory. *X authority provides object operational
directory.
authority and data execute authority.
Note: This parameter is ignored when using this
*EXCLUDE: The user cannot access the object. The
command in QDLS. No error message is sent
OBJAUT value must be *NONE, if this special value is
and the directory is created.
used.
*SYSVAL: The object auditing value for the objects in
*NONE: The user is given no data authorities to the
the directory is determined by the system auditing value
objects. This value cannot be used with OBJAUT value
(QAUDLVL).
of *NONE.
*NONE: Using or changing this object will not cause an
authorization-list-name: Specify the name of the authori-
audit entry to be sent to the security journal.
zation list used. The format of the authorization list
name remains the current ten-character format. The *USRPRF: The user profile of the user accessing this
OBJAUT value must be *NONE, if this special value is object is used to determine if an audit record will be sent
used. for this access. The OBJAUD keyword of the
CHGUSRAUD command is used to turn on auditing for a
OBJAUT
specific user.
Specifies the public object authority given to users for
the directory.
Example
┌──
────────────────────┐
55──MONMSG──MSGID(─── 6─message-identifier─┴───
(1) ── (3) ──)──┬───────────────────────────────────┬──┬────────────────────────┬─── (P) ───────5%
│ ┌─\NONE───────────┐ (2) ─CL-command──)─┘
│ └─EXEC(───
(1) ─┴─comparison-data─┴──)─┘
└─CMPDTA(───
Notes:
1 A variable cannot be coded on this parameter.
2 If this MONMSG command is specified immediately after the PGM command or the last DCL command, only the GOTO
Purpose control returns to the program that called the program that
contains the MONMSG command.
The Monitor Message (MONMSG) command is used to
monitor escape, notify, and status messages sent to the If one or more MONMSG commands are placed at the begin-
program message queue of the program in which the ning of the program, immediately following the declare com-
command is being used. Completion and diagnostic mes- mands or the PGM command if there are no declare
sages cannot be monitored. commands, they monitor messages sent by all of the com-
mands in the program (maximum of 100). This is called a
When the MONMSG command is compiled in a control lan- program-level MONMSG command. If any message sent by
guage (CL) program, it establishes a monitor for the arrival of any command in the program meets the conditions specified
the specified messages. The command monitors the mes- in any one of the program-level MONMSG commands, the
sages for the condition specified by the comparison data corresponding action specified in the same command is
given in the command. If a message meeting the conditions taken.
arrives on the message queue, the CL command specified
on the MONMSG command is processed. The action taken by a command-level MONMSG command
overrides a program-level MONMSG command.
Up to 1000 MONMSG commands can be specified in a
program to monitor the arrival of messages for specific condi- If a command is coded for the EXEC parameter on a
tions or for a group of conditions. Specific message identi- MONMSG command that is placed at the beginning of a
fiers or generic message identifiers can be monitored. More program, only the GOTO command can be used, and it must
information on the escape, notify, and status messages, and specify the label for the command to which control is to be
their identifiers, that can be sent by the CL commands, is in passed if a monitored message occurs. If a command is not
the Programming Reference Summary book. coded for the EXEC parameter, monitored messages are
ignored.
The MONMSG command can be coded following most com-
mands in a CL program. A MONMSG command that is not Restrictions:
placed at the beginning of the program applies only to the 1. This command is valid only in CL programs.
immediately preceding command; this is called a command- 2. It can be coded after the last declare command (if
level MONMSG command. The command-level MONMSG declare commands are used), following the PGM
command monitors only messages sent by the previous command that begins the program, or it can be coded
command. If the message sent by that command meets the following any command allowed in CL programs, except
conditions specified in the MONMSG command, the action for the following: DO, ELSE, ENDDO, ENDPGM,
specified in the same MONMSG command is taken. As GOTO, IF, or RETURN. Note that if another program
many as 100 MONMSG commands, coded immediately after sends a message that is monitored by this command, a
a command, can monitor the messages sent by that return cannot be made to that program.
command.
Note: To see the parameter and value descriptions for this
When the action specified in the MONMSG command has command, refer to the online help text. For more
been performed, and that action does not end with a GOTO information about printing the help text, refer to
or RETURN command, control returns to the command in the “Printing CL Command Descriptions” in Chapter 1.
program that follows the command that sent the message. If
the action ends with a GOTO command, control branches to
Required Parameters
the command in the program specified in the GOTO
command. If the action ends with a RETURN command,
*NONE: No comparison data is specified; if the Example 2: Monitoring Messages Sent by a Single
message in the program's message queue is from a Command
command that this command is monitoring, and if it has
CHGVAR VAR(&A) VALUE(&A / &B)
the specified identifier, the action specified by EXEC is
MONMSG MSGID(MCH1211) EXEC(CHGVAR VAR(&A) VALUE(1))
taken.
comparison-data: Specify a character string of no more In this example, the MONMSG command follows a Change
than 28 characters, enclosed in apostrophes if neces- Variable (CHGVAR) command and, therefore, is only moni-
sary, that is compared with the same number of charac- toring messages sent by the CHGVAR command. The MI
escape message MCH1211 is sent to this program's command is monitoring for this condition; when it receives
message queue when a division by zero is attempted. the message, the second CHGVAR command is processed.
Because MSGID(MCH1211) is specified, the MONMSG In this command, the variable &A is set to a value of 1.
(P) ───────────────────5
55──MOUNT──TYPE(──┬─\NFS─────┬──)──MFS(──'file-system-path-name'──)──MNTOVRDIR(──'directory-path-name'──)────
├─\UDFS────┤
└─\NETWARE─┘
5──┬─────────────────────────────────┬──┬─────────────────────────────────────────────────────────────┬────────────────────────5%
│ ┌─\DFT───────────┐ │ │ ┌─\BINARY────────┐ ┌─\ASCII──────────────┐ │
(1) ─┼─\ASCII─────────┼──┼─\JOBCCSID───────────┼──)─┘
└─OPTIONS(──┴─'options-list'─┴──)─┘ └─CODEPAGE(───
├─\JOBCCSID──────┤ └─path-name-code-page─┘
└─data-code-page─┘
Notes:
P All parameters preceding this point can be specified in positional form.
MOUNT Command
For the description of the MOUNT command, see the ADDMFS (Add Mounted File System) command description.
(1) ─'object-path-name-'──)──┬──────────────────────────────────────┬───
55──MOV──OBJ(─── (P) ──┬───────────────────────────────┬─────────5
│ ┌─.─────────────────────┐ │ │ ┌─\OBJ──────┐ │
├─TODIR(──┴─'directory-path-name'─┴──)─┤ └─TOCODEPAGE(──┼─\CALC─────┼──)─┘
└─TOOBJ(──'object-path-name'──)────────┘ └─code_page─┘
5──┬─────────────────────────┬─────────────────────────────────────────────────────────────────────────────────────────────────5%
│ ┌─\BINARY─┐ │
└─DTAFMT(──┴─\TEXT───┴──)─┘
Notes:
1 You can specify a pattern for this path name only if you specify the TODIR parameter.
Purpose 2. Some objects are restricted and are not moved. The
physical file systems return an error for these objects.
The Move (MOV) command moves an object from the direc-
3. The directory to which the object is being moved must
tory it is in to a different directory. If the TODIR parameter is
not already contain the name supplied in the TOOBJ
used, the object is moved to another directory and the object
parameter (or in the case where TODIR is used, the
keeps the same name. If the TOOBJ parameter is used the
name supplied in OBJ cannot exist in TODIR).
object is also renamed.
4. Only objects that are a byte stream file type move
If the original object is a read-only file (a file that has the PC between file systems.
read-only attribute flag turned on), the MOV command oper-
5. A directory cannot be moved to a subordinate directory.
ates as follows:
6. Database file members cannot be moved.
1. If the original file can be deleted (that is, the read-only
bit can be turned off for the file), the move will succeed, 7. You cannot move objects in QSYS.LIB or QDLS
retaining the read-only attribute of the file. between auxiliary storage pools (ASPs).
2. If the original file cannot be deleted, (for example, a 8. The MOV command does not copy the private authori-
CD-ROM file), the move operation will fail and a ties for objects when moving from one file system to
message will be issued indicating that the source is another file system.
read-only. Note: To see the parameter and value descriptions for this
command, refer to the online help text. For more
| When moving a file within a file system, the Last access
information about printing the help text, refer to
| date/time, the Data change date/time and the Attribute
“Printing CL Command Descriptions” in Chapter 1.
| change date/time are preserved in the new file. If the file is
| moved outside of the original file system to the the "root" (/),
| QOpenSys, QDLS, or UDFS file systems, the Attribute Required Parameter
| change date/time is changed to the current time. In the case
| of moving to a database file member (*MBR) in the OBJ
| QSYS.LIB file system, the Data change date/time is updated Specifies the path name of the object or pattern to be
| as well. moved.
The object path name can be either a simple name or a
This command can also be issued using the following alter- name that is qualified with the name of the directory in
native command name: which the object is located. A pattern can be specified
MOVE in the last part of the path name. An asterisk (*)
matches any number of characters and a question mark
For more information about integrated file system commands, (?) matches a single character. If the path name is qual-
see the Integrated File System Introduction book. ified or contains a pattern, it must be enclosed in apos-
trophes. For more information on specifying path
Restrictions: names, refer to Chapter 2, “Path Names (*PNAME).”
1. The user must have object management authority for the Note: An object name pattern can only be used when
object moved, delete and read authority to the directory the TODIR parameter is used.
the object is currently in, and add and read authority to
the directory to which the object is being moved.
Execute authority is required for all path prefixes.
Optional Parameters
55──MOVDOC──FROMDOC(──┬─\SYSOBJNAM────┬──)──┬───────────────────────────────────────┬──┬────────────────────────────┬───────────5
└─document-name─┘ │ ┌─\NONE───────┐ │ │ ┌─\NONE───────┐ │
└─┬─FROMFLR(──┴─folder-name─┴──)──────┬─┘ └─TOFLR(──┴─folder-name─┴──)─┘
└─SYSOBJNAM(──system-object-name──)─┘
5──┬───────────────────────────────┬───────────────────────────────────────────────────────────────────────────────────────────5%
│ ┌─\SAME─────────┐ │
└─RENAME(──┴─document-name─┴──)─┘
*SAME: The value does not change. This command moves DOC1 from FLR1 to FLR2 and keeps
the name DOC1.
document-name: Specify the new name of the docu-
ment in the TOFLR folder.
Example 3: Moving and Renaming a Document
MOVDOC FROMDOC(DOC1) FROMFLR(FLR1) TOFLR(FLR2)
Examples RENAME(DOC2)
Example 1: Adding a Folderless Document This command moves DOC1 from FLR1 to FLR2 and
MOVDOC FROMDOC(\SYSOBJNAM) FROMFLR(\NONE) TOFLR(FLR1) renames it DOC2.
RENAME(DOC1) SYSOBJNAM(CNTR192366)
Example 4: Moving a Document and Making It
This command, whose system object name is CNTR192366, Folderless
adds a folderless document to FLR1 and names it DOC1. MOVDOC FROMDOC(DOC1) FROMFLR(FLR1) TOFLR(\NONE)
Example 2: Moving a Document and Keeping its Name This command moves DOC1 from FLR1 and changes it to a
MOVDOC FROMDOC(DOC1) FROMFLR(FLR1) TOFLR(FLR2) folderless document.
RENAME(\SAME)
(1) ─'object-path-name-'──)──┬──────────────────────────────────────┬───
55──MOVE──OBJ(─── (P) ──┬───────────────────────────────┬────────5
│ ┌─.─────────────────────┐ │ │ ┌─\OBJ──────┐ │
├─TODIR(──┴─'directory-path-name'─┴──)─┤ └─TOCODEPAGE(──┼─\CALC─────┼──)─┘
└─TOOBJ(──'object-path-name'──)────────┘ └─code_page─┘
5──┬─────────────────────────┬─────────────────────────────────────────────────────────────────────────────────────────────────5%
│ ┌─\BINARY─┐ │
└─DTAFMT(──┴─\TEXT───┴──)─┘
Notes:
1 You can specify a pattern for this path name only if you specify the TODIR parameter.
Purpose 2. Some objects are restricted and are not moved. The
physical file systems return an error for these objects.
This command is an alias for the Move (MOV) command and
3. The directory to which the object is being moved must
can also be issued using the following alternative command
not already contain the name supplied in the TOOBJ
name:
parameter (or in the case where TODIR is used, the
MOV name supplied in OBJ cannot exist in TODIR).
The Move (MOVE) command moves an object from the 4. Only objects that are a byte stream file type move
directory it is in to a different directory. If the TODIR param- between file systems.
eter is used, the object is moved to another directory and the 5. A directory cannot be moved to a subordinate directory.
object keeps the same name. If the TOOBJ parameter is
6. Database file members cannot be moved.
used the object is also renamed.
7. You cannot move objects in QSYS.LIB or QDLS
If the original object is a read-only file (a file that has the PC between auxiliary storage pools (ASPs).
read-only attribute flag turned on), the MOV command oper-
8. The MOVE command does not copy the private authori-
ates as follows:
ties for objects when moving from one file system to
1. If the original file can be deleted (that is, the read-only another file system.
bit can be turned off for the file), the move will succeed,
Note: To see the parameter and value descriptions for this
retaining the read-only attribute of the file.
command, refer to the online help text. For more
2. If the original file cannot be deleted, (for example, a information about printing the help text, refer to
CD-ROM file), the move operation will fail and a “Printing CL Command Descriptions” in Chapter 1.
message will be issued indicating that the source is
read-only.
Required Parameter
| When moving a file within a file system, the Last access
OBJ
| date/time, the Data change date/time and the Attribute
Specifies the path name of the object or pattern to be
| change date/time are preserved in the new file. If the file is
moved.
| moved outside of the original file system to the the "root" (/),
| QOpenSys, QDLS, or UDFS file systems, the Attribute The object path name can be either a simple name or a
| change date/time is changed to the current time. In the case name that is qualified with the name of the directory in
| of moving to a database file member (*MBR) in the which the object is located. A pattern can be specified
| QSYS.LIB file system, the Data change date/time is updated in the last part of the path name. An asterisk (*)
| as well. matches any number of characters and a question mark
(?) matches a single character. If the path name is qual-
For more information about integrated file system commands, ified or contains a pattern, it must be enclosed in apos-
see the Integrated File System Introduction book. trophes. For more information on specifying path
names, refer to Chapter 2, “Path Names (*PNAME).”
Restrictions:
Note: An object name pattern can only be used when
1. The user must have object management authority for the the TODIR parameter is used.
object moved, delete and read authority to the directory
the object is currently in, and add and read authority to
the directory to which the object is being moved.
Optional Parameters
Execute authority is required for all path prefixes.
┌─\LIBL/────────┐
(1) ─object-type──)──TOLIB(──┬─\CURLIB──────┬──)────
55──MOVOBJ──OBJ(──┼───────────────┼──object-name──)──OBJTYPE(─── (P) ───────────────5%
├─\CURLIB/──────┤ └─library-name─┘
└─library-name/─┘
Notes:
1 A list of the valid OS/400 object types for this command is in Appendix A.
Purpose OBJ
Specifies the qualified name of the object being moved
The Move Object (MOVOBJ) command removes an object to another library. (If no library qualifier is given, *LIBL
from its currently assigned library and places it in a different is used to find the object.) The object name should be
library. The type of the object moved is specified in the qualified to ensure that the correct object is moved.
OBJTYPE parameter.
The name of the object can be qualified by one of the
When this command is used to move an object, the save and following library values:
restore information is removed from the object description. *LIBL: All libraries in the job's library list are
searched until the first match is found.
Restrictions:
*CURLIB: The current library for the job is
1. The user who submits this command must have object
searched. If no library is specified as the current
management authority for the object moved, delete and
library for the job, the QGPL library is used.
execute authority to the library the object is currently in,
and add and read authority to the library to which the library-name: Specify the name of the library to be
object is being moved. searched.
2. Libraries, user profiles, edit descriptions, line
object-name: Specify the name of the object that is
descriptions, control unit descriptions, device
moved.
descriptions, journals, and journal receivers cannot be
moved. OBJTYPE
3. The following objects cannot be moved: the system Specifies the type of the object moved to another library.
operator message queue QSYSOPR, all work station More information on this parameter is in Appendix A,
user message queues, and the system log QHST. “Expanded Parameter Descriptions.”
4. The library to which the object is being moved must not
Note: Journal and journal receiver objects are moved
already contain an object of the same name and type as
only from library QRCL to the library where they
the object being moved.
were originally allocated. An attempt to move
5. The user space (*USRSPC), user index (*USRIDX), and
objects of these types from or to any other library
user queue (*USRQ) user domain objects can only be
generates an error message.
moved into libraries that are permitted in the system
value QALWUSRDMN (allow user objects in library). TOLIB
However, if the user object was created in the system Specifies the name of the library to which the object is
domain, it is not restricted. moved. Library QTEMP cannot be specified.
6. Objects cannot be moved to the to library if the object
and the to library are in different auxiliary storage pools *CURLIB: The object is moved to the current
(ASPs). An error message is issued when the object library. If no library is specified as the current
cannot be moved. You can move save files that are in a library for the job, the QGPL library is used.
user ASP to libraries that are in the system ASP. library-name: Specify the name of the library to
Note: To see the parameter and value descriptions for this which the object is moved.
command, refer to the online help text. For more
information about printing the help text, refer to
Examples
“Printing CL Command Descriptions” in Chapter 1.
Example 1: Moving an Object from the General Purpose
Required Parameters Library
MOVOBJ OBJ(QGPL/X) OBJTYPE(\PGM) TOLIB(MY)
The general purpose library is searched for the program MOVOBJ OBJ(\LIBL/Y) OBJTYPE(\FILE) TOLIB(Z)
(*PGM) object X. Before X is moved to MY library, the user
profile of the user submitting the command is checked for (1) or
object operational and management authority for the object,
MOVOBJ Y \FILE Z
(2) add and execute authority for MY library, and (3) delete
and read authority for the library from which the object X is The library list (*LIBL) is used to locate the file named Y. If
moved. After this command is run, object X is no longer in more than one object with the same name exists in the
the QGPL library. libraries making up the library list, the first object found via
the library list for which the user has object operational
Example 2: Moving an Object from a Library in the
authority is moved to library Z.
Library List
┌──
─────────────────────────┐
55──MRGMSGCLG──CLGFILE(──'catalog-file-path-name'──)──SRCFILE(───6─'source-file-path-name'─┴───
(1) ──)────
(P) ───────────────────────────5
5──┬───────────────────────────────────────┬──)──┬───────────────────────────────────────┬──)───────────────────────────────────5
│ ┌─\SRCCCSID──────────────┐ │ │ ┌─\SRCFILE───────────────┐ │
└─CLGCCSID(──┼─\JOB───────────────────┼─┘ └─SRCCCSID(──┼─\JOB───────────────────┼─┘
└─coded-character-set-ID─┘ └─coded-character-set-ID─┘
5──┬─────────────────────────────┬──┬─────────────────────────────────────────┬──┬─────────────────────────────────┬───────────5%
│ ┌─\BLANK────────┐ │ │ ┌─\INDIR──────────────────┐ │ │ ┌─\INDIR─────────────┐ │
└─TEXT(──┴─'description'─┴──)─┘ └─DTAAUT(──┼─\RWX────────────────────┼──)─┘ └─OBJAUT(──┼─\NONE──────────────┼─┘
├─\RW─────────────────────┤ ├─\ALL───────────────┤
├─\RX─────────────────────┤ │ ┌──
─────────────┐ │
├─\WX─────────────────────┤ └──6┬─\OBJEXIST─┬┴───
(2) ─┘
├─\R──────────────────────┤ ├─\OBJMGT───┤
├─\W──────────────────────┤ ├─\OBJALTER─┤
├─\X──────────────────────┤ └─\OBJREF───┘
├─\EXCLUDE────────────────┤
├─\NONE───────────────────┤
└─authorization-list-name─┘
Notes:
1 A maximum of 300 repetitions.
2 A maximum of 4 repetitions.
Purpose CLGFILE
Specifies the path name of the message catalog to be
The Merge Message Catalog (MRGMSGCLG) command changed or created. All directories in a stream file path
merges message text from one or more source files name must exist. If no stream file exists with the speci-
(SRCFILE parameter) with message text in the specified fied path name, a message catalog with the specified file
message catalog (CLGFILE parameter). If the catalog speci- name is created. If the path name is in the QSYS file
fied does not already exist, it will be created using values system, the file must exist. If a file member in the QSYS
specified for the CLGCCSID, DTAAUT, and OBJAUT param- file system does not exist, it is created. Source physical
eters. If the catalog already exists, the CCSID, DTAAUT, and files with multiple data fields are not supported.
OBJAUT attributes of the existing message catalog will be
used. SRCFILE
Specifies the path name of the source file that contains
You can specify up to 300 message text source files. the message text to be merged into the message
Message text source files are processed in the sequence catalog. If the file is from the QSYS file system, then it
specified. Each successive source file modifies the catalog. must be a database source physical file.
If a message number in the source file already exists in the Note: If the source file is not a record file, then each
message catalog, the new message text defined in the line in the source file must have been terminated
source file replaces the old message text in the message with a newline or linefeed character when the
catalog file. If a message number in the source file does not source file was created.
already exist in the message catalog, the message informa-
tion is added to the message catalog. CLGCCSID
Specifies the coded character set ID (CCSID) in which to
This command can also be issued using the following alter- store the message text in the message catalog. If the
native command name: message catalog is a stream file, the CCSID value
GENCAT entered is used to set the stream file's attributes. Use
Work with Object Links (WRKLNK command) to display
Note: To see the parameter and value descriptions for this the CCSID of a message catalog. Use Display file
command, refer to the online help text. For more Description (DSPFD command) to determine the CCSID
information about printing the help text, refer to of a message catalog in the QSYS file system.
“Printing CL Command Descriptions” in Chapter 1.
*SRCCCSID: Special value indicating that the CCSID
will be determined from the value specified for the
Required Parameters source file CCSID (SRCCSID parameter).
*JOB: Special value indicating the job CCSID is used *R: *R authority allows the user to view the contents of
for the catalog information. If the job CCSID is 65535, an object. *R authority provides object operational
the job default CCSID is used. authority and data read authority.
coded-character-set-ID: Specify the CCSID used for the *W: *W authority allows the user to modify the contents
catalog information. The values 0, 65534, and 65535 of an object. *W authority provides object operational
are not valid. authority and data add, update, and delete authorities.
*X: *X authority allows the user to run a program or
Optional Parameters search a library or directory. *X authority provides object
operational authority and data execute authority.
SRCCCSID
Specifies the coded character set ID (CCSID) of the *EXCLUDE: Exclude authority prevents the user from
source file. If the source file is a stream file, the CCSID accessing the object. The OBJAUT value must be
equivalent of the code page will be used. *NONE if this special value is used.
*SRCFILE: Special value indicating that the CCSID will *NONE: The users will not be given any of the data
be determined from the CCSID of the first source file authorities to the objects. This value cannot be used
(SRCFILE parameter). If the source file is a stream file, with OBJAUT value of *NONE.
then the CCSID equivalent of the stream file code page authorization-list-name: Specify the name of the authori-
attribute will be used. zation list used.
*JOB: Special value indicating the job CCSID is used OBJAUT
for the CCSID of the source file. If the job CCSID is Specifies the authorities given users to the object.
65535, the job default CCSID is used.
*INDIR: The object authority is based on the authority
coded-character-set-ID: Specify the CCSID of the for the directory where this object is being created. If
source file. The values 0, 65534, and 65535 are not *INDIR is used for DTAAUT, it is also required for
valid. OBJAUT.
DTAAUT *NONE: None of the other object authorities (existence,
Specifies the public authority given users for the data in management, alter, or reference) will be given to the
the object created. users. If *EXCLUDE or an authorization list name is
*INDIR: The authority for the object being created is specified for the DTAAUT parameter, this value must be
determined by the directory it is being created in. If specified.
*INDIR is used for DTAAUT, it is also required for *ALL: All of the other object authorities (existence,
OBJAUT. management, alter, and reference) will be given to the
*RWX: The users are given *RWX authority to the users.
objects. *RWX authority allows the user to perform all Or specify up to four (4) of the following values:
operations on the object except those limited to the
*OBJEXIST: The users will be given object existence
owner or controlled by object existence, object manage-
authority to the object.
ment, object alter, and object reference authority. The
user can change the object and perform basic functions *OBJMGT: The users will be given object management
on the object. *RWX authority provides object opera- authority to the object.
tional authority and all the data authorities. *OBJALTER: The users will be given object alter
*RX: *RX authority allows the user to perform basic authority to the object.
operations on the object, such as run a program or *OBJREF: The users will be given object reference
display the contents of a file. The user is prevented authority to the object.
from changing the object. *RX authority provides object
operational authority and read and execute authorities. TEXT
Specifies the text that briefly describes the message
*RW: *RW authority allows the user to view the con-
catalog. More information on this parameter is in
tents of an object and modify the contents of an object.
Appendix A, “Expanded Parameter Descriptions.”
*RW authority provides object operational authority and
data read, add, update, and delete authorities. Note: Assigning text to objects is dependent on the
support provided by the file system or object type used
*WX: *WX authority allows the user to modify the con-
for the message catalog.
tents of an object and run a program or search a library
or directory. *WX authority provides object operational *BLANK: Text is not specified.
authority and data add, update, delete, and execute 'description': Specify no more than 50 characters of text,
authorities. enclosed in apostrophes.
┌─\LIBL/────────┐ ┌─\LIBL/────────┐
(P) ───────────5
55──MRGMSGF──FROMMSGF(──┼───────────────┼──message-file-name──)──TOMSGF(──┼───────────────┼──message-file-name──)────
├─\CURLIB/──────┤ ├─\CURLIB/──────┤
└─library-name/─┘ └─library-name/─┘
5──┬───────────────────────────────────────────────────────┬──┬───────────────────────────────────────────┬────────────────────5%
│ ┌─\NONE────────────────────────────────┐ │ │ ┌─\ALL──────────────────────┐ │
│ │ ┌─\LIBL/────────┐ │ │ │ │ ┌──────────────────────┐ │ │
6 (1)
└─RPLMSGF(──┴─┼───────────────┼──message-file-name─┴──)─┘ ├─SELECT(──┴───message-identifier─┴────┴──)─┤
├─\CURLIB/──────┤ │ ┌─\NONE─────────────────────┐ │
└─library-name/─┘ │ │ ┌──
────────────────────┐ │ │
6 (1)
└─OMIT(──┴───message-identifier─┴────┴──)───┘
Notes:
1 A maximum of 50 repetitions
Before the command is processed, messages can be in the message-file-name: Specify the name of the message
from-message file (FROMMSGF), in the to-message file file to use.
(TOMSGF), or in both files, but not in the replaced-message TOMSGF
file (RPLMSGF). The three possibilities result in the fol- Specifies the qualified name of the message file into
lowing when the MRGMSGF command is processed: which the messages from the FROMMSGF are being
When the messages are only in the FROMMSGF, they merged.
are added to the TOMSGF The name of the to-message file can be qualified by one
When the messages are only in the TOMSGF, they of the following library values:
remain in the TOMSGF
When the messages are in both the FROMMSGF and *LIBL: All libraries in the job's library list are
the TOMSGF, the messages in the TOMSGF are first searched until the first match is found.
saved into the RPLMSGF (if a replace-message file is *CURLIB: The current library for the job is
specified); then the messages in the TOMSGF are searched. If no library is specified as the current
replaced by the messages in the FROMMSGF library for the job, the QGPL library is used.
Restriction: The user must have *USE authority to the library-name: Specify the name of the library to be
from-message file (FROMMSGF); use, add, and delete searched.
authorities to the to-message file (TOMSGF); and use and
message-file-name: Specify the name of the message
add authorities to the replace-message file (RPLMSGF).
file to use.
Note: To see the parameter and value descriptions for this
command, refer to the online help text. For more
information about printing the help text, refer to Optional Parameters
“Printing CL Command Descriptions” in Chapter 1. RPLMSGF
Specifies the qualified name of the message file that will
Required Parameters receive replaced messages (before the messages are
replaced) from the to-message file (TOMSGF parameter)
FROMMSGF when the to-message and from-message files are
Specifies the qualified name of the message file from merged with the merge message file (MRGMSGF)
which the messages are being merged. command.
The name of the from-message file can be qualified by
one of the following library values:
*NONE: A message file is not used to receive replaced Table 20. Contents of the Files Before the Merge
messages. Message File A Message File B
The name of the message-file can be qualified by one of ABC1234 ’text A4’ ABC1233 ’text B3’
the following library values: ABC1236 ’text A6’ ABC1234 ’text B4’
ABC1237 ’text A7’ ABC1235 ’text B5’
*LIBL: All libraries in the job's library list are ABC1238 ’text A8’ ABC1236 ’text B6’
searched until the first match is found.
*CURLIB: The current library for the job is Below are the two message files after the MRGMSGF
searched. If no library is specified as the current command is processed. Notice that messages ABC1234
library for the job, the QGPL library is used. and ABC1236 are in both files. When the merge occurs, the
library-name: Specify the name of the library to be message text from file A (text A4 and A6 respectively)
searched. replaces the message text in file B (text B4 and B6 respec-
tively).
message-file-name: Specify the name of the message
file to use. Table 21. Contents of the Files After the Merge
Message File A Message File B
SELECT
Specifies a list of the IDs of messages to be merged into ABC1234 ’text A4’ ABC1233 ’text B3’
the to-message file (TOMSGF parameter) from the from- ABC1236 ’text A6’ ABC1234 ’text A4’
ABC1237 ’text A7’ ABC1235 ’text B5’
message file (FROMMSGF parameter). All other mes-
ABC1238 ’text A8’ ABC1236 ’text A6’
sages in the from-message file are not merged. ABC1237 ’text A7’
Note: This parameter cannot be specified if the OMIT ABC1238 ’text A8’
parameter is specified.
Example 2: Merging Two Files with Replace File Option
*ALL: All messages in the from-file are merged into the
to-file. In the example below, messages that are replaced in the
message-identifier: Specify up to 50 IDs of the mes- to-file are saved to a separate file before being replaced.
sages to be merged. MRGMSGF FROMMSGF(A) TOMSGF(B) RPLMSGF(C)
OMIT Table 22. Contents of the Files Before the Merge
Specifies a list of the IDs of messages that are not
merged into the to-message file (TOMSGF parameter) Message File A Message File B Message File C
from the from-message file (FROMMSGF parameter). ABC1234 ’text A4’ ABC1233 ’text B3’
All other message IDs in the from-message file are ABC1236 ’text A6’ ABC1234 ’text B4’
merged. ABC1237 ’text A7’ ABC1235 ’text B5’
ABC1238 ’text A8’ ABC1236 ’text B6’
Note: This parameter cannot be specified if the
SELECT parameter is specified.
Below are the two message files after the MRGMSGF
*NONE: All messages in the from-file are merged into command is processed. Notice that messages ABC1234
the to-file. and ABC1236 are in both files. When the merge occurs, the
message-identifier: Specify up to 50 IDs of messages text from these two messages is first moved to file C (text B4
that are not being merged. and B6 respectively). Then, message text from file A (text
A4 and A6 respectively) replaces the message text in file B
(text B4 and B6 respectively).
Examples
Table 23. Contents of the Files After the Merge
The examples below show how the merge files look before Message File A Message File B Message File C
and after the MRGMSGF command is run. ABC1234 ’text A4’ ABC1233 ’text B3’ ABC1234 ’text B4’
ABC1236 ’text A6’ ABC1234 ’text A4’ ABC1236 ’text B6’
Example 1: Merging Two Files ABC1237 ’text A7’ ABC1235 ’text B5’
ABC1238 ’text A8’ ABC1236 ’text A6’
In the following example, two files are merged. ABC1237 ’text A7’
MRGMSGF FROMMSGF(A) TOMSGF(B) ABC1238 ’text A8’
┌─\LIBL/────────┐
(P) ──┬─────────────────────────┬─────────────────5
55──MRGTCPHT──FROMFILE(──┼───────────────┼──)──┬──────────────────────────────┬───
├─\CURLIB/──────┤ │ ┌─\FIRST──────┐ │ │ ┌─\AS4ðð─┐ │
├─library-name/─┤ └─FROMMBR(──┼─\LAST───────┼──)─┘ └─FILEFMT(──┼─\AIX───┼──)─┘
└─from-file─────┘ └─from-member─┘ └─\NIC───┘
5──┬───────────────────────┬───────────────────────────────────────────────────────────────────────────────────────────────────5%
│ ┌─\NO──┐ │
└─REPLACE(──┴─\YES─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
*NIC: The physical file member to be merged with the MRGTCPHT FROMFILE(AS4ððFILE) REPLACE(\YES)
local host table is *NIC format.
This command replaces the contents of
REPLACE QUSRSYS/QATOCHOST.HOSTS with the contents of the
Specifies whether the physical file member is to be first member of physical file AS400FILE. The first member of
merged with or replaces the local host table. physical file AS400FILE is in AS/400 host table format.
*NO: The physical file member is merged with the local
Example 2: Merging Local Host Table
host table.
MRGTCPHT FROMFILE(HOSTLIB/NICFILE)
*YES: The physical file member replaces the local host FROMMBR(NEWHOSTS) FILEFMT(\NIC)
table.
This command merges the current contents of the local host
table with the contents of the NEWHOSTS member of phys-
Examples ical file NICFILE in library HOSTLIB. The physical file is in
*NIC format. The records are converted from *NIC format to
Example 1: Replacing Local Host Table *AS400 format by this command.
NETSTAT Command
NETSTAT Command
For a description of the NETSTAT command, see the WRKTCPSTS (Work with TCP/IP Network Status) command
description.
┌─\LIBL/────────┐
55──OPNDBF──FILE(──┼───────────────┼──file-name──)──OPTION(──┬─\INP─┬──)──┬──────────────────────────┬──────────────────────────5
├─\CURLIB/──────┤ ├─\OUT─┤ │ ┌─\FIRST──────┐ │
└─library-name/─┘ └─\ALL─┘ └─MBR(──┼─\LAST───────┼──)─┘
└─member-name─┘
(P) ──┬──────────────────────────┬──┬────────────────────────────────────────┬─────────5
5──┬─────────────────────────────────────┬───
│ ┌─\FILE────────────────┐ │ │ ┌─\FILE────┐ │ │ ┌─\NO───────────────────┐ │
└─OPNID(──┴─open-identifier-name─┴──)─┘ └─ACCPTH(──┴─\ARRIVAL─┴──)─┘ └─SEQONLY(──┼─\YES──────────────────┼──)─┘
└─┬───────────────────┬─┘
└─number-of-records─┘
5──┬──────────────────────┬──┬──────────────────────────────┬──┬─────────────────────────┬──┬─────────────────────────┬────────5%
│ ┌─\NO──┐ │ │ ┌─\ACTGRPDFN─┐ │ │ ┌─\NORMAL─┐ │ │ ┌─\NO──┐ │
└─COMMIT(──┴─\YES─┴──)─┘ └─OPNSCOPE(──┼─\ACTGRP────┼──)─┘ └─TYPE(───(1) ─┴─\PERM───┴──)─┘ └─DUPKEYCHK(──┴─\YES─┴──)─┘
└─\JOB───────┘
Notes:
1 This parameter is not valid when the OPNSCOPE parameter is specified.
Restrictions: file-name: Specify the name of the file that contains the
member being opened.
1. The user must have object operational authority to the
database file, and add, update, delete, or read authority, OPTION
or some combination of this authority on the physical Specifies the options used to open a file. The options
files containing the data to be accessed. If the data is chosen on the first full open operation of a file are not
accessed by opening the physical file, the user must changed on subsequent shared options.
have object operational authority to the physical file. If
*INP: The file is opened for input operations only.
the data is accessed by opening a logical file over the
physical file, object operational authority to the logical file *OUT: The file is opened for output operations only.
is required; object operational authority to the physical *ALL: The file is opened for all options (input, output,
file is not required. update, and delete).
*FILE: The file name is used for the open operation *ACTGRPDFN: The scope of the open operation is
identifier. determined by the activation group of the program that
called the OPNDBF command processing program. If
open-identifier-name: Specify the name of this open the activation group is the default activation group, the
operation. scope is the call level of the caller. If the activation
ACCPTH group is a non-default activation group, the scope is the
Specifies the access path to use for this open operation. activation group of the caller.
*FILE: The file access path is used. If the file is keyed, *ACTGRP: The scope of the open data path (ODP) is
the keyed access path is used; otherwise, the arrival the activation group. Only those shared opens from the
sequence path is used. same activation group can share this ODP. This ODP is
not reclaimed until the activation group is deactivated, or
*ARRIVAL: The arrival sequence access path is used. until the Close File (CLOF) command closes the acti-
If the file is keyed, the keyed access path is ignored. vation group.
More information on arrival sequence processing is in
the DB2 for AS/400 Database Programming book. *JOB: The scope of the open is the job in which the
open occurs.
SEQONLY
Specifies, for database files whose records are normally TYPE
processed in sequential order, whether sequential-only Specifies the recursion level at which the reclaim
processing is used on the file. This parameter also resources function (RCLRSC) is effective.
specifies the number of records transferred as a group *NORMAL: The reclaim resources function is allowed to
to or from the database file if sequential-only processing close the file if the program ends without doing a close
is used. If an override specifying SEQONLY is in effect, operation.
it takes precedence over what is specified on this
*PERM: The file remains open until it is closed by using
parameter. More information on sequential-only pro-
the Close File (CLOF) command, or until the job ends.
cessing is in the SEQONLY parameter description on
The open data path (ODP) remains in existence even if
the Override with Database File (OVRDBF) command,
RCLRSC is used.
and in the DB2 for AS/400 Database Programming book.
*NO: The database file does not use sequential-only DUPKEYCHK
processing. Specifies whether duplicate key feedback should be
returned on I/O operations. Duplicate key feedback
*YES: The database file uses sequential-only pro- should only be requested for those files that are pro-
cessing. cessed by COBOL programs since this is the only high-
number-of-records: The file uses sequential-only pro- level language that uses the feedback. Duplicate key
cessing. This parameter value indicates the number of feedback should be requested only when it will be used
records the database blocks up in its internal buffer by the COBOL application, since providing it can cause
before accessing the data in the member. Specifying a performance degradation. More information on dupli-
this number is not required. If this value is not specified, cate key feedback is in the DB2 for AS/400 Database
the database chooses a default value. If this command Programming book.
*NO: Duplicate key feedback is not returned on I/O OPNDBF FILE(MASTER/PAYROLL) OPTIONS(\INP)
operations.
This command opens the first member in the file PAYROLL
*YES: Duplicate key feedback is returned on I/O oper-
for input processing. The open identifier associated with this
ations.
open operation has the file name as its identifier. If the file is
specified as SHARE(*YES), subsequent open operations of
Example the file PAYROLL (such as in an application program)
perform more efficiently and use the same ODP.
┌──
────────────────────────────────────────────────────────────────────────┐
│ ┌─\LIBL/────────┐ ┌─\FIRST─┐ ┌─\ONLY──────────────┐ │
55──OPNQRYF──FILE───── 6
(1, 2) ─(────(──┼───────────────┼──file-name──┼─\LAST──┼──┴─record-format-name─┴──)─┴───
(3) ──)──────────────────────5
├─\CURLIB/──────┤ └─member─┘
└─library-name/─┘
(P) ──┬───────────────────────────────────────────────────────────────────────────────────┬─────5
5──┬────────────────────────────┬───
│ ┌─\INP─┐ │ │ ┌─\FILE─────────────────────────────────────────────────────────┐ │
└─OPTION──(──┬─┼─\OUT─┼─┬──)─┘ │ │ ┌─\LIBL/────────┐ ┌─\ONLY──────────────┐ │ │
│ ├─\UPD─┤ │ (1)
└─FORMAT────(──┴─┼───────────────┼──database-file-name──┴─record-format-name─┴─┴──)─┘
│ └─\DLT─┘ │ ├─\CURLIB/──────┤
└─\ALL─────┘ └─library-name/─┘
5──┬─────────────────────────────────────┬──────────────────────────────────────────────────────────────────────────────────────5
│ ┌─\ALL──────────────┐ │
└─QRYSLT──(──┴─'query-selection'─┴──)─┘
5──┬──────────────────────────────────────────────────────────────────────────────────────────┬─────────────────────────────────5
│ ┌─\NONE────────────────────────────────────────────────────────────────┐ │
(4) ─(──┼─\FILE────────────────────────────────────────────────────────────────┼──)─┘
└─KEYFLD───
│ ┌──
───────────────────────────────────────────────────────────────┐ │
└──6─(──qualified-key-field-name──┬───────────────────────────┬──)─┴───
(5) ─┘
│ ┌─\ASCEND──┐ │
└─┴─\DESCEND─┴──┬─────────┬─┘
└─\ABSVAL─┘
5──┬─────────────────────────────────────────────┬──────────────────────────────────────────────────────────────────────────────5
│ ┌─\NONE────────────────┐ │
(6) ─(──┼─\ALL─────────────────┼──)─┘
└─UNIQUEKEY───
└─number-of-key-fields─┘
5──┬──────────────────────────────────────────────────────────────────────────────────────────────────┬─────────────────────────5
│ ┌─\NONE────────────────────────────────────────────────────────────────────────┐ │
│ │ ┌──
───────────────────────────────────────────────────────────────────────┐ │ │
└─JFLD───── 6
(7, 8) ─(──┴───(──qualified-from-field-name──┬──────────────────────────────────┬──)─┴───
(9) ─┴──)─┘
│ ┌─\EQ─┐ │
└─qualified-to-field-name──┼─────┼─┘
├─\GT─┤
├─\LT─┤
├─\NE─┤
├─\GE─┤
└─\LE─┘
5──┬───────────────────────────────┬──┬───────────────────────────┬──┬────────────────────────────────────────────────┬─────────5
│ ┌─\NO──────┐ │ │ ┌─\ANY──┐ │ │ ┌─\NONE────────────────────────┐ │
(8) ─(──┼─\YES─────┼──)─┘ └─JORDER───
└─JDFTVAL─── (8) ─(──┴─\FILE─┴──)─┘ │ │ ┌──
───────────────────────┐ │ │
└─\ONLYDFT─┘ 6 (9)
└─GRPFLD──(──┴───qualified-group-field─┴────┴──)─┘
5──┬─────────────────────────────────────┬──────────────────────────────────────────────────────────────────────────────────────5
│ ┌─\ALL──────────────┐ │
└─GRPSLT──(──┴─'group-selection'─┴──)─┘
5──┬───────────────────────────────────────────────────────────────────────────────────────────┬────────────────────────────────5
│ ┌─\NONE───────────────────────────────────────────────────────────────────┐ │
│ │ ┌──
──────────────────────────────────────────────────────────────────┐ │ │
└─MAPFLD──(──┴──6─mapped-field-name──'mapped-field-definition'──┤ MAPFLD Details ├─┴───
(9) ─┴──)─┘
5──┬───────────────────────────┬──┬───────────────────────────────────────┬─────────────────────────────────────────────────────5
│ ┌─\NO──┐ │ │ ┌─\FILE────────────────┐ │
└─IGNDECERR──(──┴─\YES─┴──)─┘ └─OPNID──(──┴─open-identifier-name─┴──)─┘
5──┬────────────────────────────────────────────────┬──┬───────────────────────────┬──┬─────────────────────────────────┬───────5
│ ┌─\YES─┐ │ │ ┌─\NO──┐ │ │ ┌─\ACTGRPDFN─┐ │
(10) ─(──┴─\YES─┴──)─┘ └─OPNSCOPE(────
└─SEQONLY──(──┬─┴──────┴──number-of-records─┬──)─┘ └─COMMIT──── (11) ─┼─\ACTGRP────┼──)─┘
└─\NO─────────────────────────┘ └─\JOB───────┘
5──┬───────────────────────────┬──┬────────────────────────────────┬────────────────────────────────────────────────────────────5
│ ┌─\NO──┐ │ │ ┌─\YES──────┐ │
└─DUPKEYCHK──(──┴─\YES─┴──)─┘ └─ALWCPYDTA──(──┼─\NO───────┼──)─┘
└─\OPTIMIZE─┘
5──┬─────────────────────────────────────────────────────────┬──┬────────────────────────┬──────────────────────────────────────5
│ ┌─\ALLIO──────────────────────────────┐ │ │ ┌─\NO──┐ │
└─OPTIMIZE──(──┴─┬─\FIRSTIO─┬────number-of-records───┴──)─┘ └─OPTALLAP(──┴─\YES─┴──)─┘
└─\MINWAIT─┘
5──┬───────────────────────────────────────────────┬──┬────────────────────────────┬──┬─────────────────────────────┬──────────5%
│ ┌─\JOB──────────────────────────┐ │ │ ┌─\NORMAL─┐ │ │ ┌─\JOB────────┐ │
(12) ─(──┴─\PERM───┴──)─┘ └─LANGID(──┴─language-ID─┴──)─┘
└─SRTSEQ(──┼─\HEX──────────────────────────┼──)─┘ └─TYPE────
├─\LANGIDUNQ────────────────────┤
├─\LANGIDSHR────────────────────┤
│ ┌─\LIBL/────────┐ │
└─┼─\CURLIB/──────┼──table-name─┘
└─library-name/─┘
MAPFLD Details:
├──┬───────────────────────────────────────────────────────────────────────────────────────────────────┬────────────────────────┤
│ ┌─\CALC─────┐ │
└─field-type──┼───────────┼──┬────────────────────────────────────────────────────────────────────┬─┘
├─\GRAPHIC──┤ └─field-length──┬──────────────────────────────────────────────────┬─┘
└─\VGRAPHIC─┘ └─field-decimals──┬──────────────────────────────┬─┘
│ ┌─\CALC───────┐ │
└─field-CCSID──┼─────────────┼─┘
├─\HEX────────┤
└─CCSID-value─┘
Notes:
1 When more than one FILE (file, library, member, record format) is specified, FORMAT(*FILE) cannot be specified.
2 When more than one FILE is specified, JFLD(*NONE) is allowed only when the default is specified for JDFTVAL and
JORDER.
3 A maximum of 32 repetitions
4 KEYFLD(*FILE) is not allowed whenever a value other than the default is specified on the GRPFLD or GRPSLT parameters.
5 A maximum of 50 repetitions
7 When more than one FILE (file, library, member, record format) is specified, FORMAT(*FILE) cannot be used.
8 When more than one FILE is specified, JFLD(*NONE) is allowed only when the default is specified for JDFTVAL and
JORDER.
9 A maximum of 50 repetitions
10 COMMIT(*NO) is required whenever a value other than the default is specified on the GRPFLD or GRPSLT parameters.
the open query file open data path (ODP), the query file *LIBL: All libraries in the job's library list are
does not open and an escape message is sent. searched until the first match is found.
3. Each subsequent shared open operation must use the
*CURLIB: The current library for the job is
same open options (such as SEQONLY) that are in
searched. If no library is specified as the current
effect when the OPNQRYF command is run.
library for the job, the QGPL library is used.
4. Some system functions (such as the Display Physical
File Member (DSPPFM) and Copy File (CPYF) com- library-name: Specify the name of the library to be
mands) do not share an existing open data path. The searched.
OPNQRYF command cannot be used with those func-
file-name: Specify the files, members, and record
tions.
formats that are processed.
5. The file opened with the OPNQRYF command cannot be
used in programs written in BASIC because BASIC does Element 1: Member Values
not share an existing open data path. *FIRST: The oldest member created is used.
6. Users of this command must have the following authori-
*LAST: The newest member created is used.
ties:
Execute authority for any library that is needed to member: Specify the file member name.
locate the files specified on the FILE and FORMAT
Element 2: Record Format Values
parameters
Object operational authority and one or more of the *ONLY: Only the record format in the file is used. If no
following data authorities for any physical file or record format name is specified, *ONLY is the default. If
logical file specified on the FILE parameter: the file has more than one record format, a record
– Read authority if the file is opened for input format name is specified.
(using option *INP) record-format-name: Specify the name of the record
– Add authority if the file is opened for output format that is used. The record format must exist in the
(using option *OUT) database file specified in the first part of the FILE
– Update authority if the file is opened for parameter.
updates (using option *UPD)
When more than one file, file member, and record format
– Delete authority if the file is opened for
is specified, the query joins field values to create a
deletions (using option *DLT)
single set of records. Any file specified in the list may
– Read, add, update, and delete authority if the
be a physical, join logical, or SQL view. More informa-
file is opened for all I/O operations (using option
tion on SQL views is in the DB2 for AS/400 SQL Refer-
*ALL)
Object operational authority for any file specified on
ence book. The maximum number of physical file
members that can be joined by a single query is 32.
the FORMAT parameter
This limit includes the based-on physical file members
Use authority for any translate tables specified on
for any join logical file member or SQL view member
the MAPFLD parameter (using option *USE)
specified on the FILE parameter. The limit also includes
Notes: each separate occurrence of the same physical file
member when it is specified more than once in the list,
1. The Copy from Query File (CPYFRMQRYF) command
either directly by name or by being referred to through a
can be used to copy data from a data path opened with
logical file member.
the OPNQRYF command.
2. More information about the OPNQRYF command is in
the DB2 for AS/400 Database Programming book.
Optional Parameters
OPTION
Specifies the open option used for the query file. The
Required Parameter
options chosen on the first full open operation of a file
FILE are not changed on subsequent shared open operations.
Specifies one or more files, members, and record The user can specify either OPTION(*ALL) or up to four
formats that are processed by the open query file of the following values in any order:
command. All files specified must be physical files,
*INP: Open the file for input. OPTION(*INP) is the only
logical database files, or Distributed Data Management
value allowed if join processing or group processing is
(DDM) files. If DDM files are used, all files they refer to
requested, if UNIQUEKEY processing is specified, or if
must be on the same target system, and the target
all the fields in the open query file record format (speci-
system must be an IBM AS/400 system or IBM
fied on the FORMAT parameter) are for input-only use.
System/38.
*OUT: Open the file for output. In some high-level lan-
The name of the file can be qualified by one of the fol-
guages, output to certain files (such as files defined as
lowing library values:
'direct access' in the high-level language program) is
done by using a combination of input and updates.
All key fields for an open query file must appear in the *ASCEND: The part of the key defined by the specified
query records processed through the file. The fields key field is ordered by ascending key values.
named in the record format identified on the FORMAT
*DESCEND: The part of the key defined by the speci-
parameter must include all key fields for the open query
fied key field is ordered by descending key values.
file, even if KEYFLD(*FILE) is specified to use the
existing access path of a keyed file. Element 3: Order by Absolute Value
*NONE: Key fields are not used to arrange the query *ABSVAL: The part of the key defined by the specified
records; therefore, any arrangement is acceptable. It is key field is arranged by the absolute value of the key
possible for the system to display query records in dif- field. *ABSVAL is specified together with either
ferent arrangements if the same query is run twice, *ASCEND or *DESCEND, but it is ignored if the key field
based on such factors as the current number of records is not numeric. If *ABSVAL is not specified, the records
in the file members being queried. KEYFLD(*NONE) are arranged by the signed value of a numeric key field.
allows the system more flexibility than other KEYFLD
UNIQUEKEY
values to improve the performance record processing
Specifies whether the query is restricted to records with
through the open query file.
unique key values, and specifies how many of the key
*FILE: The query records have the same arrangement fields must be unique. If *ALL or number-of-key-fields is
as the first file, file member, and record format specified specified, null values are considered to be equal.
on the FILE parameter. KEYFLD(*FILE) is specified
*NONE: None of the key fields specified on the
even if the first file in the list has only an arrival
KEYFLD parameter must be unique. All query records
sequence access path, in which case the query record
are available through the open query file, regardless of
arrangement matches the arrival sequence of the first
key value.
file, file member, and record format specified on the
FILE parameter. *ALL: All key fields specified on the KEYFLD parameter
must be unique. If there are multiple query records with
When KEYFLD(*FILE) is specified and a sort sequence
the same values for all of the key fields, only the first
other than *HEX has been specified on the SRTSEQ
such record is available through the open query file.
parameter, you may receive your records in an order
that does not reflect the true file order. If this is a key number-of-key-fields: Specify the number of key fields
file, the query's sort sequence is applied to the key fields that must be unique. This value must be no larger than
of the file and an informational message is sent. If the the number of key fields determined by the KEYFLD
file has a sort sequence table or an alternative collating parameter. If there are multiple query records with the
sequence table, it is ignored for the ordering. This same value for the specified number of consecutive key
allows users to indicate which fields to apply a sort fields, only the first such record is available through the
sequence to without having to list all the field names. If open query file.
a sort sequence is not specified for the query, the query
JFLD
is ordered as in releases previous to V2R3M0.
Specifies whether the query joins records from multiple
Element 1: Qualified Key Field Values file members, and specifies how to join field values from
the files, members, and record formats specified on the
qualified-key-field-name: Specify one or more field
FILE parameter in constructing the query records.
names (up to 50 field names can be entered) used to
define a keyed access path to arrange the query The first file, member, and record format specified on the
records. Each field name is qualified with either a file FILE parameter is called the join primary, and all other
name or number that indicates which element in the list elements specified on the FILE parameter are called join
of files, members, and record formats specified on the secondaries. The JFLD parameter specifies a list con-
FILE parameter contains the field. The special value taining pairs of field names, where the first field in each
*MAPFLD is also used to qualify the field name if the pair provides a value that is used to select records in a
field is defined on the MAPFLD parameter. join secondary that has the same value in the second
field name of the pair.
Each field name on the KEYFLD parameter must be a
field name that is defined in the query records specified The join from-field and to-field may be simple or mapped
on the FORMAT parameter. For example, if the value fields (specified on the MAPFLD parameter), but a field
*MAPFLD is specified on the KEYFLD parameter, the that depends on an aggregate function (either directly in
name of the mapped field must be defined in the query its definition or indirectly by referring to a mapped field)
records specified on the FORMAT parameter. The sum cannot be used.
of the lengths of all key fields cannot be more than
The join from-field and to-field are not required to have
10,000 bytes. In addition, if the sum of the lengths of
identical field attributes, but numeric fields cannot be
the key fields is greater than 2000 bytes, *INP must be
mixed with character or double-byte character set
specified on the OPTION parameter.
(DBCS) fields, and character fields cannot be mixed with
Element 2: Key Field Order DBCS-only field types. If the fields do not have identical
attributes, the system converts them to identical attri-
butes for join processing. This change uses a packed *MAPFLD is used to qualify the field name if the field is
decimal format if both fields are fixed-point numeric defined on the MAPFLD parameter.
fields, or floating-point format if either field is of the
A join to-field is either a simple field or a mapped field
floating-point type. The change for fixed-point numeric
defined on the MAPFLD parameter. If JDFTVAL(*YES)
fields aligns the decimal points and pads with zeros.
or JDFTVAL(*ONLYDFT) is specified, it must depend
Numeric-type change truncates fractional digits if more
only on fields contained in a single join secondary. If the
than 31 total digits are required for fixed-point numbers,
join secondary is a join logical file, only fields contained
or drops some of the least significant digits if more than
in the primary physical file member for the join logical file
15 total digits are required for floating-point numbers.
are components of the join to-field. The sum of the
Character and DBCS-open fields are changed by
lengths of all to-fields for each join secondary (after
padding the shorter field with blanks. DBCS-either fields
change, if the from-field and to-field attributes are not
are padded with blanks if the field contains SBCS data
identical) cannot be more than 2000 bytes unless
or padded with double-byte blanks if the field contains
JDFTVAL(*NO) is specified. Up to 50 join field pairs are
DBCS data. DBCS-only fields are padded with double-
specified.
byte blanks.
Element 3: Join Operators
If more than one file is specified on the FILE parameter,
and if the JDFTVAL(*NO) value and JORDER(*ANY) join-operator: Specifies the type of join operation that is
value are specified, the system takes information from performed for the specified from-field and to-field. If
the JFLD and QRYSLT parameters and derives the final JDFTVAL(*NO) and JORDER(*ANY) are specified, or if
join specifications. If a file is specified on the FILE more than one join field pair is specified, a different join
parameter and the file is not referred to by the QRYSLT operator may be specified for each pair. If
or JFLD parameters, all records for that file are logically JDFTVAL(*YES), JDFTVAL(*ONLYDFT), or
joined to all other records created from the other files JORDER(*FILE) is specified, then only one join operator
specified on the FILE parameter. may be specified, regardless of the join pairs.
qualified-to-field-name: Specify a field name used to If the FILE parameter includes any join logical or SQL
select records from a join secondary file, file member, views, all join files must be compatible with the
and record format in constructing the query records. JDFTVAL value. If the data description specification
The field name is qualified with either a file name or (DDS) used to create a queried join logical file does not
number that indicates which element in the list of files, contain the JDFTVAL keyword, JDFTVAL(*NO) must be
file members, and record formats specified on the FILE specified. If any join logical file specified on the FILE
parameter contains the field. The special value parameter has the JDFTVAL keyword, then all join
logical files for this open query file must be created by
using the JDFTVAL keyword, and JDFTVAL(*YES) must records (after join processing, if required) selected by
be used. If any files are SQL views, then the QRYSLT parameter. The group is defined by the
JDFTVAL(*NO) is required. collection of records that has the same set of values for
the fields specified in the record format identified on the
If the JDFTVAL parameter is not compatible with the
FORMAT parameter. If no field names are specified and
attributes of the join logical files or SQL views being pro-
group processing is required, the whole file is considered
cessed, the join view files specified on the FILE param-
to be one group. Each query record that is created is
eter can be replaced with their based-on physical file
either made available through the open query file or is
members. The correct, additional from-field and to-field
discarded, depending on the selection values specified
pairs can be provided on the JFLD parameter to join
on the GRPSLT parameter. All null values within a
records from the physical file members in any way.
grouping column are considered equal. To ensure an
If more than one file is specified on the FILE parameter, ascending sequence, the KEYFLD parameter must also
and if either JDFTVAL(*YES) or JDFTVAL(*ONLYDFT) be specified.
is specified, the system uses the join fields as specified
*NONE: Fields are not used to form groups. If the
on the JFLD parameter as the final join specifications.
grouping function is required (because selection values
*NO: Default values are not used to construct join query are specified on the GRPSLT parameter, or an aggre-
records. gate function is used by a field specified on the MAPFLD
*YES: Creates all records for the join operation, parameter), records selected by the values specified on
including those produced both with and without default the QRYSLT parameter are handled as a single group.
values. If *YES is specified, no SQL views are allowed. qualified-group-field: Specify one or more field names
*ONLYDFT: Creates only the records produced by (up to 50) to group the query results. Each field name
using default values in constructing the join operation. may be qualified with either a file name or number to
This option is used to include only exception records in indicate which element in the list of files, members, and
the records available through the open query file. If record formats specified on the FILE parameter contains
*ONLYDFT is specified, no join logical files or SQL the field. The special value *MAPFLD may also be used
views can be specified on the FILE parameter. to qualify the field name if the field is defined on the
MAPFLD parameter.
JORDER
A grouping field defined on the MAPFLD parameter
Specifies, for a join query, whether the join order must
cannot refer to an aggregate function in its definition
match the order specified on the FILE parameter. If the
(either directly, or indirectly through the use of another
join order is varied, the query records are created in a
field specified on the MAPFLD parameter). The sum of
different arrangement. If the value specified for the
the lengths of all grouping fields cannot exceed 2000
JDFTVAL parameter is *YES or *ONLYDFT, the
bytes.
JORDER parameter is ignored. The order specified on
the FILE parameter is always preserved, because GRPSLT
changing the join order can change which records are Specifies the selection values used after grouping to
returned when JDFTVAL processing is required. determine which records are available through the open
If more than one file is specified in the FILE parameter query file.
and JORDER(*FILE) is specified, the system uses the *ALL: All records defined by the grouping function
join fields as specified on the JFLD parameter as the described in the GRPFLD parameter description are
final join specifications. selected.
*ANY: Any join file order is allowed, and any such 'group-selection': Specify an expression (up to 2000
arrangement may be used by the system to create the characters enclosed in apostrophes) that describes the
result records. It is possible for a query to return result values used to determine which records are selected.
records in a different arrangement if the same query is Any logical expression formed from relations (such as
run twice, consecutively (based on factors such as the *EQ and *NE) of field and constant values or functions
current number of records in the files being queried). of field and constant values are specified. Only grouping
JORDER(*ANY) allows the system more flexibility to fields (specified on the GRPFLD parameter), constants,
improve the performance of processing records through aggregate functions (such as %AVG and %STDDEV),
the open query file than any other JORDER parameter and mapped fields (specified on the MAPFLD param-
value. eter) that are composed of grouping fields and aggre-
*FILE: The order of the file, file member, and record gate functions can be referred to in any relation. At
format elements specified on the FILE parameter are least one field must be specified in each relation. Refer
preserved in the join operation. to the “Expressions” section of “Additional Consider-
ations” on page P3-485 of this command description for
GRPFLD a complete list of the operators used for this parameter.
Specifies the field name or names used to group query
For example, to select all records for which the value of
results. One query record is created for each group of
grouping field OVRDUE is greater than or equal to 10,
and the average value of field CREDIT in each group is field-type: Specify the field type for this mapped field, or
less than 100, specify the following: specify *CALC to allow the system to calculate appro-
GRPSLT('OVRDUE>=1ð \AND %AVG(CREDIT)<1ðð') priate attributes (including field type) for the mapped
field. *CALC is the default if no field type value is speci-
Each field name may be qualified with either a file name fied.
or number that indicates which element in the list of files,
file members, and record formats specified on the FILE When *CALC is used, the field attributes are determined
parameter contains the field. The special value, in one of two ways. The attributes either match the field
*MAPFLD, may also be used to qualify the field name if definition in the record format identified on the FORMAT
the field is defined on the MAPFLD parameter. parameter, or (if the field is not in the record format on
the FORMAT parameter) the attributes are calculated
MAPFLD based on the expression specified in the mapped-field
Specifies the definition of query fields that are either definition for this field. If the mapped field is used in the
mapped to, or derived from, other fields. MAPFLD is record format identified on the FORMAT parameter,
generally not needed if the field names specified on either use *CALC or specify attributes (field type, field
other OPNQRYF command parameters are simple field length, and field decimals) identical to those of the field
names that exist in only one of the file, file member, and in the record format specified on the FORMAT param-
record format elements specified on the FILE parameter. eter.
*NONE: Mapped fields are not needed. All field names The field type must be valid for the final result of the
specified on other parameters exist in some record expression specified on the mapped-field definition.
format specified on the FILE parameter. Character and numeric types are only mixed if the
Element 1: Mapped Field numeric type is in zoned decimal format and the field
length and the length of the expression result are the
mapped-field-name: Specify the simple field name used same.
on any other OPNQRYF command parameter that must
refer to this mapped field. A qualified name is not The following are the only DBCS mappings allowed on
allowed for the first part of the MAPFLD parameter list the MAPFLD parameter:
item. All specified mapped-field-name values must be From character to DBCS-open type
unique. Refer to the “Expressions” section of “Additional From character to DBCS-either type
Considerations” on page P3-485 of this command From character to DBCS-graphic type
description for a complete list of the operators used for From character to UCS2 graphic type
this parameter. From HEX to DBCS-open type
Element 2: Field Definition Expression From HEX to DBCS-either type
From HEX to DBCS-only type
'mapped-field-definition': Specify an expression (up to
From HEX to DBCS-graphic type
256 characters enclosed in apostrophes) that defines the
From HEX to UCS2-graphic type
mapped field in terms of other fields that either exist in
From DBCS-either to DBCS-open type
only one of the file, file member, and record format ele-
From DBCS-either to HEX type
ments specified on the FILE parameter, or are defined
From DBCS-either to DBCS-graphic type
by some other mapped field definition appearing earlier
From DBCS-either to DBCS-either type
in the MAPFLD list. Either numeric operations or string
From DBCS-open to DBCS-open type
operations are allowed, depending on the data type of
From DBCS-open to character type
the fields used in the definition. Refer to the
From DBCS-open to DBCS-graphic type
“Expressions” section of “Additional Considerations” on
From DBCS-open to HEX type
page P3-485 of this command description for a complete
From DBCS-open to UCS2 graphic type
list of the operators used for this parameter.
From DBCS-only to DBCS-only type
For example, to define a mapped field named WHSPAR From DBCS-only to DBCS-open type
as the concatenation of the field WHRSE with the first From DBCS-only to DBCS-either type
10 characters of field PART, specify the following: From DBCS-only to DBCS-graphic type
MAPFLD((WHSPAR 'WHRSE \CAT %SST(PART 1 1ð)')) From DBCS-only to HEX type
From DBCS-graphic to DBCS-only type
Each field name is qualified with either a file name or a From DBCS-graphic to DBCS-open type
number that indicates which element in the list of files, From DBCS-graphic to DBCS-either type
file members, and record formats specified on the FILE From DBCS-graphic to DBCS-graphic type
parameter contains the field. The special value From DBCS-graphic to UCS2-graphic type
*MAPFLD is also used to qualify the field name if the From UCS2-graphic to HEX type
field is defined in an earlier list item on the MAPFLD From UCS2-graphic to DBCS-open type
parameter. From UCS2-graphic to character type
Element 3: Mapped Field Type From UCS2-graphic to DBCS-graphic type
From UCS2-graphic to UCS2-graphic type
The Query Field Structure table (see Table 24) shows IGNDECERR
the allowable field type and external field length values. Specifies whether the system ignores decimal data
It also shows the default field length and decimal posi- errors during query file processing.
tions and the internal field length (in bytes) for each type *NO: The system does not ignore decimal data errors.
of field.
*YES: The system ignores decimal data errors. When
Element 4: Length
errors in decimal data are encountered, the invalid sign
field-length: Specify the field length in number of digits and/or digits are automatically changed to valid values.
for a numeric field, number of bytes for a character or
OPNID
DBCS field, or number of characters for a graphic field.
Specifies the identifier used to name the query file so it
A field length must be an even value for DBCS-only and
is referred to by the Close File (CLOF) command when it
DBCS-either field types. The range of valid lengths for
is closed or by the Position Database File (POSDBF)
each field type is shown in the Query Field Structure
command when it is opened. The identifier must differ
table. A field length value is specified if *CALC is used
from the OPNID associated with any other file which was
for the field type.
previously opened by using the OPNDBF command or
Element 5: Decimal Positions OPNQRYF command, and which is not yet closed.
field-decimals: Specify the number of decimal positions *FILE: The name of the first or only file specified on the
for a numeric field, expressed as a number of decimal FILE parameter is used for the open query file identifier.
digits, that is no larger than the total number of digits
specified for the field length. If no value is given, the
open-identifier-name: Specify the name to associate
with this open query file.
default value is assumed to be zero. A field decimal's
value must not be specified for a binary or character SEQONLY
field, or if *CALC is specified for the field type. Specifies whether sequential-only processing is used for
Element 6: CCSID Value the query file, and also specifies the number of records
that can be processed as a group when read or write
field-CCSID: Specify the CCSID (character code set operations are performed on the open query file. The
identifier) being assigned to the mapped field being
open query file open data path (ODP) uses a different
created. This parameter is valid only for fixed- or
SEQONLY value than the one specified on this param-
variable-length character, DBCS, or hexadecimal fields,
eter. It depends on other parameter values specified on
or for *CALC fields that result in one of these types. If
the OPNQRYF command. A message is sent if the
no value is specified, the CCSID is determined based on
SEQONLY value is changed. More information about
the CCSIDs of the fields and/or literal values specified
sequential-only processing is in the SEQONLY param-
on the MAPFLD definition.
eter description on the OVRDBF (Override Database
Literal values in the MAPFLD definition are tagged with File) command, and in the DB2 for AS/400 Database
the job default CCSID. However, if the MAPFLD defi- Programming book.
nition consists of only a literal value and the user speci-
Element 1: Sequential-Only Processing is Used
fies a field CCSID value, the literal will be tagged with
that CCSID. This allows the user to tag a literal with a *YES: The open query file uses sequential-only pro-
CCSID other than the job default CCSID. cessing. Number of records can be specified with this
value.
Note: Normally, *HEX and *VHEX fields do not have an
associated CCSID. Because of this, the data in Element 2: Number of Records That can be Pro-
the field is treated the same regardless of the cessed
default CCSID of the system that the data is number-of-records: Specify the number of records that
being used on. However, if the user specifies a are processed as a group when read or write operations
CCSID for a *HEX or *VHEX field, the CCSID are performed with the open query file. If no number-of-
overrides the hexadecimal attribute of the field records value is specified, the system calculates the
(causing the field to be treated as number of records processed as a group.
*CHAR/*VCHAR), and the data in the field may
Other Single Values
be treated differently if it is moved to a system
that has a different default CCSID. *NO: The file does not use sequential-only processing.
For more information on CCSIDs, see the National Lan- COMMIT
guage Support book. Specifies whether the SQL statements are run under
An example of the MAPFLD parameter, showing the use commitment control.
of field-type, field-length, field-decimals, and field-CCSID, Before a database file is opened under commitment
is as follows: control, the user must ensure that all files in the commit-
MAPFLD((UNTPRICE 'TOTPRICE / UNTCOUNT' \DEC 7 2) ment transaction are journaled. If only the after images
(SHORTSTR '%SST(LONGSTR 1 5)' \CHAR 5 \N 93ð)) are being journaled, the system implicitly begins jour-
naling both the before and the after images for the dura- FILE parameter. A copy of the data is used only when it
tion of the changes being made to files opened under is needed to perform the requested query functions.
this commitment definition.
*NO: The system does not use a copy of data from the
*NO: The open query file is not placed under commit- files, file members, and record formats specified on the
ment control. FILE parameter. If it is necessary to use a copy of the
data to perform the requested query functions, the query
*YES: The open query file is placed under commitment
file is not opened and an error message is sent.
control.
*OPTIMIZE: The system uses a sort routine to order the
OPNSCOPE
output from the files, file members, and record formats
Specifies the extent of influence (scope) of the open
specified on the FILE parameter. A sort routine is used
operation.
only if the KEYFLD parameter is specified, and if using a
*ACTGRPDFN: The scope of the open operation is sort routine would improve query performance without
determined by the activation group of the program that conflicting with other OPNQRYF options.
called the OPNQRYF command processing program. If
A sort will improve the performance of a query that
the activation group is the default activation group, the
returns most or all of the records in the file or files speci-
scope is the call level of the system program performing
fied on the FILE parameter.
the open operation. If the activation group is a non-
default activation group, the scope is that activation Using a sort can increase the time required for the
group. OPNQRYF command to process. This occurs because
the sort is performed and all records to be returned
*ACTGRP: The scope of the open data path (ODP) is
through the query are processed while the OPNQRYF
the activation group. Only those shared opens from the
command is active. However, because the records are
same activation group can share this ODP. This ODP is
already processed, the reading of the records (by using
not reclaimed until the activation group is deactivated, or
either a program or the CPYFRMQRYF command) is
until the Close File (CLOF) command closes the file.
very fast. Therefore, the overall time to process the
*JOB: The scope of the open operation is the job in query is reduced.
which the open operation occurs.
Specifying the KEYFLD parameter for the OPNQRYF
DUPKEYCHK command does not ensure that the query will use an
Specifies whether duplicate key feedback is returned on index if ALWCPYDTA(*OPTIMIZE) is specified. If a sort
input/output (I/O) operations. Duplicate key feedback routine is used, the file is not opened with indexed
should be requested only for files that are processed by access. If the program reading the records from the
COBOL programs since this is the only high-level lan- OPNQRYF command requires indexed access (random
guage (HLL) that utilizes the feedback. Duplicate key processing rather than sequential processing),
feedback should only be requested when it is used by ALWCPYDTA(*YES) or ALWCPYDTA(*NO) should be
the COBOL application since providing it can cause a specified.
performance degradation. More information on duplicate When a sort is used, the query file's position is not
key feedback is in the DB2 for AS/400 Database Pro- changed when a ROLLBACK command is issued.
gramming book. Therefore, when a query is opened that has parameters,
*NO: Duplicate key feedback is not returned on I/O ROLLBACK commands that follow do not reset the
operations. queried file's position to where it was at the start of the
unit of recovery.
*YES: Duplicate key feedback is returned on I/O oper-
ations. Note: Do not specify ALWCPYDTA(*OPTIMIZE) if you
require that a ROLLBACK command reposition
ALWCPYDTA the query file, or if you require that the queried
Specifies whether the system is allowed to copy data file be opened with indexed access.
from the files, file members, and record formats specified
on the FILE parameter. If so, the system is allowed to The following items are required before a sort is valid for
open the query file to the copy. The system tries to the OPNQRYF command:
avoid using a copy of the data because a copy does not ALWCPYDTA(*OPTIMIZE) must be specified.
reflect changes made to the database after the informa-
tion is copied. However, certain requests (such as when The OPTION parameter, if specified, must be *INP.
key fields contained in multiple based-on files for a join A value other than *FILE or *NONE must be speci-
are specified) require that the data be copied before the fied on the KEYFLD parameter.
specified query functions are performed.
The UNIQUEKEY parameter must not be specified,
*YES: The system may use a copy of data from the or must specify *NONE.
files, file members, and record formats specified on the
The SEQONLY parameter, if specified, must be
*YES.
If COMMIT(*YES) is specified, the level of record *NO: Allow the query optimizer to operate normally.
locking (LCKLVL parameter on the STRCMTCTL When determining how to implement a query, the opti-
command) must not be *ALL. mizer considers access paths until an internal timeout
value has been exceeded. If there are a large number
The DUPKEYCHK parameter must not be specified,
of access paths over the files being queried, the opti-
or must specify *NO.
mizer may time out before it has considered all the avail-
The total buffer length of all fields in the file speci- able access paths.
fied on the FORMAT parameter (or FILE parameter,
*YES: Force the query optimizer to ignore the internal
if the FORMAT parameter is not specified) must not
timeout value and consider all the available access
exceed 32700 bytes.
paths over all the files in the query.
The query optimizer determines whether a sort is used.
Note: If there are a large number of access paths over
This decision is based on the number of records
the files it may take a long time to optimize the
expected from the query and the options specified on
query.
the OPNQRYF statement. The following items influence
the optimizer's choice of a sort: SRTSEQ
Specifies the sort sequence to be used for sorting and
The OPTIMIZE parameter should specify *ALLIO or
grouping selections specified on the QRYSLT or
*MINWAIT. If *FIRSTIO is specified, the number of
GRPSLT parameters, joins specified on the JFLD
records specified should be close to or equal to the
parameter, ordering specified on the KEYFLD param-
number of result records expected from the query.
eter, grouping specified on the GRPFLD parameter,
The number of records in a file specified on the %MIN or %MAX built in functions, or unique key values
FILE parameter should contain a minimum of 200 specified on the UNIQUEKEY parameter.
records.
*JOB: The SRTSEQ value for the job is retrieved for
The query result should contain a minimum of 200 the job.
records.
*HEX: A sort sequence table is not used. The
OPTIMIZE hexadecimal values of the characters are used to deter-
Specifies the most efficient way the system can perform mine the sort sequence.
the selection and join processing necessary to satisfy *LANGIDUNQ: A unique-weight sort table is used.
the other parameter specifications on the OPNQRYF
*LANGIDSHR: A shared-weight sort table is used.
command.
The name of the sort sequence table can be qualified by
If the KEYFLD or GRPFLD parameters require that an
one of the following library values:
access path be built (when no existing access path is
shared), the access path is built completely, regardless *LIBL: All libraries in the job's library list are
of the OPTIMIZE entry. Optimization primarily affects searched until the first match is found.
system operation when selection processing is per-
*CURLIB: The current library for the job is
formed.
searched. If no library is specified as the current
*ALLIO: The system attempts to reduce the total library for the job, the QGPL library is used.
input/output time required to process the whole query,
assuming that all query records are read from the file.
library-name: Specify the name of the library to be
searched.
Element 1: Time Reduction Options
table-name: Specify the name of the sort sequence
*FIRSTIO: The system attempts to reduce the
table to be used with this query.
input/output time required to open the query file and to
retrieve the first buffer of records from the file. LANGID
Specifies the language identifier to be used when
*MINWAIT: The system attempts to reduce the time
SRTSEQ(*LANGIDUNQ) or SRTSEQ(*LANGIDSHR) is
required to open the query file by minimizing delays
specified.
when records are read from the file.
*JOB: The LANGID value for the job is retrieved for the
Element 2: Number of Records to Retrieve
job.
number-of-records: Specify the number of query records
to use in the optimize operation. This value is ignored
language-ID: Specify the language identifier to be used
by the job.
when the value *MINWAIT is specified.
TYPE
OPTALLAP
Specifies the recursion level at which the Reclaim
Specifies whether the query optimizer should consider all
Resources (RCLRSC) command closes the file.
the access paths that exist over the files being queried
when determining how to implement the query. Note: This parameter is ignored unless the default
value is specified on the OPNSCOPE parameter
and the request is from the default activation *PERM: The file remains open until the Close File
group. (CLOF) command closes it, or until the routing step or
default activation group ends. The query file remains
*NORMAL: The RCLRSC command closes the file if
open even if the RCLRSC command is run.
the program call that ran the OPNQRYF command is
ended without closing the file.
This example shows a way to make the uppercase version of OPNQRYF FILE(partpf partpf)
field USRNAME available to the HLL program. This is done FORMAT(partjoin)
by defining a mapped field (MAPFLD parameter) for the JFLD((1/pnbr 2/pnbr \GE))
translated value of field USRNAME. The field has the same MAPFLD((pnm1 '1/pname') (pnm2 '2/pname')
field name as the field name in the open query file record (pnbr '1/pnbr'))
format being used. The translated version of the field is
This example illustrates how a file is joined to itself, as well
used for selection (QRYSLT parameter) and is used in the
as how to use the MAPFLD parameter to rename fields in
open query file record format.
the based-on files. A greater than or join is performed using
Example 4: Using the %SST Built-In Function field PNBR as both the join from-field and the join to-field.
OPNQRYF FILE((histlib/ordfile hist1)) The format of file PARTJOIN is assumed to contain fields
OPTION(\inp \upd \dlt) named PNBR, PNM1, and PNM2. The field name PNBR is
FORMAT(ordinfo orddtls) valid in the query output record format because that field is
QRYSLT('month=7') defined on the MAPFLD parameter. If the record format in
MAPFLD((year '%sst(orddate 1 2)' \zoned 2) file PARTJOIN contains a field named PNAME, an error
(month '%sst(orddate 3 2)' \zoned 2) occurs because the field exists in both files specified on the
(day '%sst(orddate 5 2)' \zoned 2)) FILE parameter, and is not the name of a field defined on the
MAPFLD parameter. The mapped field definitions are field
This command uses the %SST built-in function to create a
names, so the attributes of fields PNM1 and PNM2 match
substring of the year, month, and day parts of character field
the attributes of field PNAME, and the attributes of field
ORDDATE in file ORDFILE. The command also maps a
PNBR in the open query file records match field PNBR in file
character string to a zoned field, which is valid as long as the
PARTPF. Further, when a file is joined to itself, it is always
zoned field has the same length as the character string. If
necessary to specify a file number name for any field that is
the file ORDINFO has a record format, ORDDTLS, con-
defined in the based-on file.
taining at least the field's YEAR, MONTH, and DAY records,
these fields have input-only usage in the open query file Example 7: Renaming Fields in Based-On Files
record format because they are defined by using a built-in
function (%SST) and are mappings that mix character and The same query can also be specified as follows:
numeric (zoned decimal format) types. The file is opened for OPNQRYF FILE(partpf partpf)
input, update, and delete operations, but none of the field's FORMAT(partjoin)
YEAR, MONTH, and DAY records are updated using the QRYSLT('1/pnbr \GE 2/pnbr')
open query file open data path (ODP). The open query file MAPFLD((pnm1 '1/pname') (pnm2 '2/pname')
uses only records in the HIST1 member of file ORDFILE in (pnbr '1/pnbr'))
library HISTLIB, and the records retrieved through the file
have the same format as record format ORDDTLS in file Because more than one file is specified on the FILE param-
ORDINFO. Only records pertaining to the month of July are eter, and the default value is specified for the JDFTVAL and
processed through the open query file (QRYSLT parameter). JORDER parameters, the system takes the join specifica-
tions from the values specified on the QRYSLT parameter.
Example 5: Returning the First Record of Each Set
Example 8: Selecting Master Records With No Detail
OPNQRYF FILE((routelf \first locusr))
Records
QRYSLT('%sst(toloc 1 4) \eq "ROCH"')
KEYFLD(fromusr fromloc tousr toloc) OPNQRYF FILE(cusmas ordfil)
UNIQUEKEY(\all) FORMAT(cusmas)
JFLD((cusnbr ordfil/cusnbr))
This command uses the KEYFLD and UNIQUEKEY parame- JDFTVAL(\onlydft)
ters to return only the first record of each set of records in MAPFLD((cusnbr 'cusmas/cusnbr'))
record format LOCUSR in the first member of file ROUTELF
that have the same values for the fields FROMUSR, This command uses a join query to select only master
FROMLOC, TOUSR, and TOLOC. The query result is records that have no associated detail records. The master
further restricted by selecting only records that have the file (CUSMAS) is joined (equal join) to the detail file
value ROCH in the first four characters of field TOLOC. The (ORDFIL) by the customer number field that appears in both
records available through the open query file contain all of record formats. The customer number field name is the
the fields in record format LOCUSR of file ROUTELF. If the same in both record formats (CUSNBR). Because CUSNBR
file ROUTELF contains information about messages routed is the name of a field defined on the MAPFLD parameter,
by an application, this example identifies all unique sender everywhere the simple field name CUSNBR is used, the
and receiver pairs in which the receiving location name mapped field version of the CUSNBR field in file CUSMAS is
begins with ROCH. used (including the open query file record format, which
matches the customer master file record format). The
Example 6: Joining a File to Itself JDFTVAL parameter indicates that only records that are
produced by using default values are available through the
open query file. Every master record that has associated system to attempt to improve processing for the open query
detail records (with the same value of the customer number file to minimize the time needed to retrieve the first buffer of
field) is excluded, and every master record that has no asso- ten records. This combination of parameter values is a good
ciated detail records creates a result record. choice if the file is used with a high-level language interactive
inquiry program that shares the open query file open data
Example 9: Identifying Detail Records With No Associ- path (ODP) and shows ten records on each display screen.
ated Master Record The open data path (ODP) for the open query file is 'perma-
OPNQRYF FILE(ordfil cusmas) nent' (TYPE parameter), which means that it remains open
FORMAT(ordfil) either until the file is closed by using the Close File (CLOF)
JFLD((cusnbr cusmas/cusnbr)) command or until the routing step ends.
JDFTVAL(\onlydft)
MAPFLD((cusnbr 'ordfil/cusnbr')) Example 12: Tagging a Literal with a Specific CCSID
OPNQRYF FILE(itmmast)
This change of the previous example (using the same files)
QRYSLT('itmtype=pfield')
shows how to identify all detail records with no associated MAPFLD((pfield 'P' \CHAR 1 \N 93ð))
master record (in this case, all orders with an unregistered
customer number): This command selects from the first member of file
ITMMAST only the records that have a value of field
Example 10: Calculating Basic Statistics ITMTYPE equal to the letter 'P' in character set 930. The
OPNQRYF FILE(scores) mapped field is created so that the literal 'P' can be tagged
FORMAT(clsstats) with a specific CCSID.
GRPFLD(clsid)
GRPSLT('clsavg<7ð & clsmax-clsmin>3ð') If a literal is not tagged with a specific CCSID, it is assigned
MAPFLD((clscnt '%count') the CCSID of the job running the query. Because of this, if
(clsavg '%avg(usrscore)') an OPNQRYF statement is part of a CL program that is
(clsmin '%min(usrscore)') shared among systems with differing CCSIDs (in different
(clsmax '%max(usrscore)')) countries, perhaps), a query that uses a literal in the
selection specifications may not return the same results on
This command uses the grouping function to calculate basic
all systems, even though the data in the files is the same.
statistics for each group of records in file SCORES that have
This happens because the internal representation of the
the same value in the field CLSID. Assuming file CLSSTATS
literal may be different when the CL program is run in a job
has a record format containing field CLSID and all fields
with a different CCSID. This representation then may not
specified on the MAPFLD parameter, each record available
match the same records in the file. Note that the internal
through the open query file contains the value of the
representation of the data in the file does not change based
grouping field (CLSID) as well as the number of records
on the CCSID of the current job.
included in the group and the average, minimum, and
maximum values of field USRSCORE in the group. Tagging the literal with a specific CCSID avoids this problem.
Selection occurs after grouping, so that records are created A literal tagged with a specific CCSID keeps the same
for groups only when the average value of USRSCORE in internal representation on all systems. The CCSID that is
the group is less than 70 and the difference between the used to tag the literal should be the same as the CCSID
maximum and minimum scores in the group is greater than assigned to the field against which the literal is being com-
30. pared.
Example 11: Selecting Records With a Specific Value Example 13: Using a Nonjoin Query
OPNQRYF FILE(itmmast) OPNQRYF FILE((EMPLOYEE)) KEYFLD((NAME))
QRYSLT('itmcode=%range(32 5ð) & itmtype="P"') ALWCPYDTA(\OPTIMIZE)
ALWCPYDTA(\no)
OPTIMIZE(\firstio) This command returns all of the records in the EMPLOYEE
SEQONLY(\yes 1ð) file.
TYPE(\perm)
Example 14: Using a Join Query
This command selects from the first member of file
ITMMAST only the records that have a value of field OPNQRYF FILE((EMPLOYEE) (MANAGEMENT))
ITMCODE in the range from 32 through 50 and also have a FORMAT(EMPLOYEE) KEYFLD((NAME))
JFLD((1/EMPID 2/MEMPID)) ALWCPYDTA(\OPTIMIZE)
value of field ITMTYPE equal to the letter P. The
ALWCPYDTA parameter specifies that the open query file This command returns all of the records required by the join
must never use a copy of the records in file ITMMAST. The criteria.
OPTIMIZE and SEQONLY parameter values cause the
Additional Considerations same file and record format is specified more than once
in the list on the FILE parameter.
The file, library, and file member names used by the open For example, AMOUNT is valid if the field named
data path (ODP) are the same as the first file and file AMOUNT is defined on the MAPFLD parameter. It is
member names specified on the FILE parameter, unless an also valid if AMOUNT is not defined on the MAPFLD
override forces the use of a different file or file member parameter, as long as there is only one field named
name. The record format name of the open query file is the AMOUNT in any record format specified on the FILE
same as that specified on the FORMAT parameter. parameter.
The OPNQRYF command always opens a file with an open file-name/field-name
data path (ODP) that is shared, as if SHARE(*YES) is speci- Specify a field name that is qualified with the simple
fied for the file. If the file, library, or file member name speci- name of the file specified on the FILE parameter whose
fied in the HLL program differs from the name of the open record format contains the field, but only if the simple file
query file, an override command must be used to specify the name is unique among all file names specified on the
correct file, library, and member names to allow the high- FILE parameter. This form is not allowed if the same
level language program to share the open query file ODP. If simple file name is specified more than once in the list
the first, or the only, member queried has an attribute of specified for the FILE parameter, even if different library,
SHARE(*NO), SHARE(*YES) must be specified in an over- member, or record format names are used.
ride to enable an HLL program to share the query file ODP.
For example, WHS01/PARTNBR is valid if there is a
If the OPNQRYF is scoped to the job, any subsequent field named PARTNBR in the record format for file
OPNQRYF can share the ODP whether scoped to an acti- WHS01, and file name WHS01 is only specified once on
vation group or the job. If the OPNQRYF is scoped to an the FILE parameter.
activation group, any subsequent OPNQRYF can share the file-nbr/field-name
ODP if it is also scoped to the same activation group. Specify a simple field name that is qualified with the
number of the element in the FILE parameter list for the
The open query file ODP also has a LVLCHK attribute that
record format that contains the field. The file-nbr qual-
matches the first, or only, member used for the query.
ifier must be specified without leading zeros. This form
Shared opens of an open query file are level checked unless
is only required if the same simple file name is specified
the first queried member has an attribute of LVLCHK(*NO) or
more than once in the list specified on the FILE param-
LVLCHK(*NO) is specified either in the program that opens
eter.
the file or in an override which occurs before the shared
open. The level number for the open query file record format For example, 2/BALDUE is valid if the second file record
is the same as the record format identified on the FORMAT format in the list specified on the FILE parameter con-
parameter. tains a field named BALDUE.
expressions on the QRYSLT, GRPSLT, and MAPFLD param- Except for operators ¬ and *NOT, the operators for priorities
eters differ from normal CL expressions: 1 through 4 are numeric operators, which require numeric
operands. The operators for priority 5 are string operators,
The expression string must be enclosed in apostrophes
which require operands to be either character or DBCS
if it contains embedded blanks or special characters
strings. Priority 6 operators are called relational operators,
The following differences affect numeric and string
which require at least one operand that is a field name or a
literals:
numeric or string expression (not a constant). The operators
– Character string constants are quoted by using
for priorities 7 and 8, plus the ¬ and *NOT operators (priority
apostrophes or double quotes
1), are logical operators. The operands in a logical
– The leading and trailing zeros of a numeric constant
expression are relations (constructed by using a relational
are significant parts of its attributes
operator with appropriate operands) and other logical
– Floating-point constants (including the special
expressions.
values *INF and *NEGINF) are used in expressions
The following differences contrast CL variables with
The operands in a string expression, including string oper-
database fields:
ands for a built-in function, are a combination of character
– No prefixed ampersand (&) is used in database field
fields and DBCS fields and constants. If both operands of
names
such an expression are DBCS-only fields or constants, the
– Qualified field names are supported
final result from evaluation of the expression is a DBCS-only
– No 'logical' field type exists for database fields
field value. If the operands are a combination of DBCS or
– Many additional data types are supported for data-
character fields or constants, the result is a DBCS-open field
base fields
value. When DBCS fields are concatenated, the extraneous
The following CL operators are not supported on the
shift-in and shift-out characters between the fields are
OPNQRYF command:
removed.
– *BCAT or ∨>
– *TCAT or ∨< The result produced by a + or − sign prefixed operator has
The following additional operators are supported beyond the same attributes as the operand, unless the operand of a
CL support: − sign prefixed operator is a *BIN2, in which case the result
– // for remainder is a *BIN4. The result of an ** operator (exponentiation) is a
– ** for exponentiation double-precision floating-point number (*FLT8). For other
– *CT for 'contains' (character scan) numeric operators that require two operands, if either
– *XOR or && for 'logical exclusive or' operand is a floating-point number, the result is a double-
The following differences affect built-in function support: precision floating point number (*FLT8). If both operands are
– The %SWITCH built-in function is not supported fixed-point numbers, the system uses the information in the
– Many additional built-in functions are supported following table to determine the number of total and fractional
– Nested built-in functions and expressions for built-in digits required to produce a packed decimal (*DEC) result. If
function arguments (such as '%LOG(%SIN(x))') gen- both operands are zero-precision binary fields and/or integer
erally are allowed constants, the result is a *BIN4, unless the operator is a "/".
– To support expressions as built-in function argu- In that case, the result is the same as for a fixed-point result.
ments, any argument that is a signed numeric value If the total number of digits required exceeds 31, the number
or an expression (for example, '%MIN(3 (-2) x of fraction digits is reduced enough to enable calculation of
(y+4))') must be enclosed in parentheses the result with a total of 31 digits. If some fraction digits are
The following table shows the priority of all operators that are dropped and the attributes of the end result of the computa-
used for expressions on the QRYSLT, GRPSLT, or MAPFLD tion (the attributes specified on the MAPFLD parameter for
parameters. Only operators listed for priorities 1 through 5, the field) require greater precision than that of the interme-
excluding the *NOT and ¬ operators, are allowed in an diate result, a warning message is sent to indicate that some
expression specified on the MAPFLD parameter: precision was lost in evaluating the expression.
7 *AND, &
8 *OR, *XOR, ∨, &&
Both operands of a relational operator can be constants. 'BASEFLD *CT TESTFLD ∨∨ ''Z''' False
The fields, constants, or expressions specified as operands 'BASEFLD ∨∨ ''ABC'' *CT ''TAB''' True
on the left and right side of a relational operator must be of
the same type, either numeric or string. Any combination of Built-in Functions
character and DBCS field operands are allowed except that a
character field cannot be related to a DBCS-only field. The built-in functions listed below are supported for the
expression used to define a derived field on the MAPFLD
There are two types of DBCS constants: DBCS-only and parameter or a complex selection operand specified on the
DBCS-open. A DBCS-only constant has only DBCS data QRYSLT or GRPSLT parameters.
between its apostrophes. This data must be enclosed in
SO/SI characters. A DBCS-open constant has a mixture of A numeric argument is a numeric field, a numeric constant or
DBCS and alphameric data. An SO character (HEX 0E) indi- a numeric expression. A string argument is a character field,
cates the start of a group of DBCS characters and an SI a character string literal, or a string expression. Unless oth-
character (HEX 0F) follows the last double-byte character of erwise noted, all built-in functions allow expressions,
the group. including other built-in functions, to be used as arguments.
If a numeric or string expression appears as a complex For a field that appears in the record format identified by the
selection operand on the QRYSLT or GRPSLT parameters, FORMAT parameter, and that is also defined by an
attributes of the final result of the expression used for the expression on the MAPFLD parameter, the expression result
selection operand are changed to match the other relational is calculated by using the attributes described below. Then
operand. the resultant value is mapped to match the attributes of the
field.
It is not necessary for operands of a relational operator to
have identical attributes, but numeric operands cannot be %ABSVAL (numeric-argument)
mixed with character operands. If the operands do not have %ABSVAL accepts a numeric argument and returns
identical attributes, the system changes them to identical the absolute value of the argument. The returned
attributes (except for the *CT operator, where the character value has the same attributes as the argument,
string operands may be of different lengths), before per- unless the argument is a *BIN2, in which case the
forming the operation. This change uses packed decimal returned value is a *BIN4.
format if both operands are fixed-point numeric operands, or The following argument types are treated as
floating-point format if either operand is a floating-point numeric values: date duration, time duration, and
number. The changes for fixed-point numeric operands align timestamp duration. Arguments of these types can
their decimal points and pad them with zeros. Numeric type be specified either as fields or literal values. The
changes may truncate fractional digits if more than 31 total returned value is a packed decimal number (*DEC)
digits are required for fixed-point numbers, or may drop some with 8 digits and 0 precision (date duration), 6 digits
of the least significant digits if more than 15 total digits are and 0 precision (time duration), or 20 digits and 6
required for floating-point numbers. Character operands are precision (timestamp duration).
changed by padding the shorter operand with blanks.
The following argument types are treated as If the argument is date duration, time duration,
numeric values: date duration, time duration, and or timestamp duration, the returned value is a
timestamp duration. Arguments of these types can packed decimal number (*DEC) with 31 digits
be specified either as fields or literal values. The and 0 precision (date duration), 31 digits and 0
returned value is a double-precision floating-point precision (time duration), or 31 digits and 6 pre-
number (*FLT8). cision (timestamp duration).
including the sign or a decimal point. The result is eter, and is allowed as part of an arithmetic (addi-
tagged with the CCSID of the current job. For tion or subtraction) expression with a date or
example, %DIGITS (-1.5) returns the character timestamp field on the QRYSLT, GRPSLT, or
string 15. The numeric argument must not be a MAPFLD parameters.
floating point number.
%DURSEC (integer-argument)
%DURDAY (integer-argument) %DURSEC accepts an integer argument and
%DURDAY accepts an integer argument and returns a labeled duration of seconds. The integer
returns a labeled duration of days. The integer argument for this function can be a numeric
argument for this function can be a numeric expression, a field, or a literal.
expression, a field, or a literal.
This built-in function is allowed to stand by itself in
This built-in function is allowed to stand by itself in the mapped-field-definition on the MAPFLD param-
the mapped-field-definition of the MAPFLD param- eter, and is allowed as part of an arithmetic (addi-
eter, and is allowed as part of an arithmetic (addi- tion or subtraction) expression with a time or
tion or subtraction) expression with a date or timestamp field on the QRYSLT, GRPSLT, or
timestamp field on the QRYSLT, GRPSLT, or MAPFLD parameters.
MAPFLD parameters.
%DURYEAR (integer-argument)
%DURHOUR (integer-argument) %DURYEAR accepts an integer argument and
%DURHOUR accepts an integer argument and returns a labeled duration of years. The integer
returns a labeled duration of hours. The integer argument for this function can be a numeric
argument for this function can be a numeric expression, a field, or a literal.
expression, a field, or a literal.
This built-in function is allowed to stand by itself in
This built-in function is allowed to stand by itself in the mapped-field-definition value on the MAPFLD
the mapped-field-definition on the MAPFLD param- parameter, and is allowed as part of an arithmetic
eter, and is allowed as part of an arithmetic (addi- (addition or subtraction) expression with a date or
tion or subtraction) expression with a time or timestamp field on the QRYSLT, GRPSLT, or
timestamp field on the QRYSLT, GRPSLT, or MAPFLD parameters.
MAPFLD parameters. Example:
%DURMICSEC (integer-argument) OPNQRYF
%DURMICSEC accepts an integer argument and FILE((library/file))
returns a labeled duration of microseconds. The QRYSLT('startfld > %CURDATE + oneyear \AND
integer argument for this function can be a numeric endfld < %CURDATE + %DURYEAR(2)')
MAPFLD((oneyear '%DURYEAR(1)'))
expression, a field, or a literal.
%EXP (numeric-argument)
This built-in function is allowed to stand by itself in
%EXP accepts a numeric argument and returns a
the mapped-field-definition on the MAPFLD param-
value that is the base of the natural logarithm (e)
eter, and is allowed as part of an arithmetic (addi-
raised to a power specified by the argument. %EXP
tion or subtraction) expression with a timestamp
and %LN are inverse operations.
field on the QRYSLT, GRPSLT, or MAPFLD param-
eters. The following argument types are treated as
numeric values: date duration, time duration, and
%DURMINUTE (integer-argument)
timestamp duration. Arguments of these types may
%DURMINUTE accepts an integer argument and
be specified either as fields or literal values. The
returns a labeled duration of minutes. The integer
returned value is a double-precision floating-point
argument for this function can be a numeric
number (*FLT8).
expression, a field, or a literal.
%HASH (expression-argument)
This built-in function is allowed to stand by itself in
%HASH accepts a valid expression and returns a
the mapped-field-definition on the MAPFLD param-
4-byte binary number (*BIN4) with 10 total decimal
eter, and is allowed as part of an arithmetic (addi-
digits and no fraction digits. The returned value will
tion or subtraction) expression with a time or
be the partition number of the record selected.
timestamp field on the QRYSLT, GRPSLT, or
MAPFLD parameters. A valid expression cannot include aggregate func-
tions such as %COUNT, %AVG, %MIN, %MAX,
%DURMONTH (integer-argument)
%SUM, and %STDDEV as operands to %HASH.
%DURMONTH accepts an integer argument and
returns a labeled duration of months. The integer Use the %HASH function to determine what the par-
argument for this function can be a numeric titions would be if the partitioning key was com-
expression, a field, or a literal. posed of EMPNO and LASTNAME. The following
example returns the partition number for every row
This built-in function is allowed to stand by itself in
in EMPLOYEE.
the mapped-field-definition on the MAPFLD param-
next string, and then continues to XOR each suc- %VALUES (allowed-value...)
cessive argument with the previous result. If an %VALUES is used to identify a list of allowed values
argument is encountered that is longer than the pre- for a field or expression. %VALUES must be speci-
vious result, the previous result is padded with fied as the right side of a relation whose operator is
blanks before the XOR operation. If any of the equal. The allowed-value arguments must be char-
arguments is variable-length, the maximum length is acter string or numeric literals, to match the type of
used as the length of the argument. The final result the field or expression specified as the left side of
is a string of type *HEX with the same length as the the relation. For example, to select only records
longest argument. where the second character of field CHARFLD has
a value that is one of the values 'A', 'E', 'I', 'O', or
%YEAR
'U', specify the following:
%YEAR accepts a date/time argument and returns
the year part of the value. The date/time argument '%SST(charfld 2 1) =
can be a date or timestamp field, a date duration or %VALUES(''A'' ''E'' ''I'' ''O'' ''U'')'
timestamp duration (field or literal), or a numeric %WLDCRD (''pattern-string'' ''wild-characters''])
field or literal. The returned value is of type *BIN4. %WLDCRD is used to specify a pattern that per-
A numeric field argument must be defined as forms a wildcard scan of the character or
packed decimal (*DEC) with 8 digits and 0 precision hexadecimal field or string expression (except for
for date duration or packed decimal (*DEC) with 20 expressions made up of a single character-string
digits and 6 precision for timestamp duration. A literal) that must be specified as the left side of the
numeric constant argument must have 8 digits fol- relation. %WLDCRD must be specified as the right
lowed by a decimal point, or 14 digits followed by a side of a relation whose operator is equal. The
decimal point and 6 digits. pattern-string argument must be a character-string,
DBCS, or graphic literal, to match the left side of the
Restricted Built-in Functions relation. The wild-characters argument is an
optional parameter that specifies what 'wildcard'
The following built-in function is supported only as the characters are used in the pattern-string.
second operand of the 'equal' or 'not-equal' relational opera-
tors specified on the QRYSLT or GRPSLT parameter. If specified for character data only (no DBCS data),
the wild-characters argument must be a character-
%NULL string literal of exactly two characters. The first
%NULL accepts no arguments. It is used to select character is the value that matches any single char-
or omit records based on whether or not a field in acter in the search string. The second character is
the record contains a null value. the value that matches a substring of any zero or
Example: more characters. The two characters must not be
OPNQRYF the same, but there is no requirement that either
FILE(library/file) character appear in the pattern-string. If the wild-
QRYSLT('charfld = %NULL') characters argument is omitted, the default is for an
This query would select all the records where underline ('_') to match any single character and an
'charfld' contains the null value. asterisk ('*') to match a substring of any zero or
more characters.
The following three built-in functions are supported only as If the wild-characters argument is specified for
the second operand of the 'equal' relational operator speci- DBCS data only (no character data), the argument
fied on the QRYSLT or GRPSLT parameter. must be a double-byte character-string literal of
%RANGE (low-value high-value) exactly two double-byte characters. The first
%RANGE is used to identify the lower and upper double-byte character is the value that will match
boundaries for the value of a field or expression. any one double-byte character in the search string.
%RANGE must be specified as the right side of a The second double-byte character is the value that
relation whose operator is equal. The low-value and will match a substring of any zero or more charac-
high-value argument must be field names, character ters. The two double-byte characters must not be
strings, or numeric literals, to match the type of field the same, but there is no requirement that either
or expression specified as left side of the relation. character appear in the pattern string. If the wild-
For example, to select only records where the characters argument is omitted, the default is for a
numeric field NBRFLD has a value ranging from 10 DBCS underline to match any one double-byte char-
through 20, specify: acter and a DBCS asterisk to match a substring of
'nbrfld = %RANGE(1ð 2ð)' any zero or more double-byte characters.
If the low-value argument is greater than the high- If the wild-characters argument is specified for both
value argument, the relation produces a logical character and DBCS data, in addition to the pre-
value of 'false'. vious rules, the argument must first contain a single-
byte character-string literal (two single-byte
characters), then a double-byte character string (two Note: The asterisks at the start and end of the
double-byte characters). pattern-string are required to allow the 'T'
and 'E' to appear somewhere other than the
In this case, the first character matches any single-
first and last positions in the field:
byte character in the character string, the second
character matches a substring of any number of To select only records where the character field
single-byte or double-byte characters. The first CHARFLD starts with the string 'ABC', followed by
double-byte character matches any double-byte one or more other characters and then followed by
character in the character string. The second the string 'XYZ' (but not necessarily at the end of
double-byte character matches a substring of any the field), specify the following:
number of single-byte or double-byte characters. 'charfld = %WLDCRD(''ABC_\XYZ\'')'
The following example selects only records where To select only records where the second character
the character field CHARFLD contains a 'T', followed of field CHARFLD is an asterisk ('*'), the last char-
by any two characters and an 'E', appearing any- acter is an underline ('_'), and the letter 'M' appears
where in the field. somewhere in between, specify the following:
'charfld = %WLDCRD(''\T__E\'')' 'charfld = %WLDCRD(''#\.M._'' ''#.'')'
55──OVRDBF──FILE(──overridden-file-name──)──┬───────────────────────────────────────────────────────┬───────────────────────────5
│ ┌─\FILE─────────────────────────────────┐ │
│ │ ┌─\LIBL/────────┐ │ │
└─TOFILE(──┴─┼───────────────┼──database-file-name─┴──)─┘
├─\CURLIB/──────┤
└─library-name/─┘
(P) ──┬───────────────────────────────────────────────────────────────────────────────┬───────────5
5──┬──────────────────────────┬───
└─MBR(──┬─\FIRST──────┬──)─┘ └─POSITION(──┬─\NONE───────────────────────────────────────────────────────┬──)─┘
├─\LAST───────┤ ├─\START──────────────────────────────────────────────────────┤
├─\ALL────────┤ ├─\END────────────────────────────────────────────────────────┤
└─member-name─┘ ├─\RRN──relative-record-number────────────────────────────────┤
└─┬─\KEYB──┬──number-of-fields──record-format-name──key-value─┘
├─\KEYBE─┤
├─\KEY───┤
├─\KEYAE─┤
└─\KEYA──┘
5──┬─────────────────────────────────────────────────────────────┬──────────────────────────────────────────────────────────────5
│ ┌──
───────────────────────────────────────┐ │
└─RCDFMTLCK(───6─(──record-format-name──┬─\SHRRD──┬──)─┴───
(1) ──)─┘
├─\SHRNUP─┤
├─\SHRUPD─┤
├─\EXCLRD─┤
└─\EXCL───┘
5──┬───────────────────────────────────────────────────────────┬──┬─────────────────────────────────────────────┬───────────────5
└─FRCRATIO(──┬─\NONE───────────────────────────────────┬──)─┘ │ ┌─\LIBL/────────┐ │
└─number-of-write-operations-before-force─┘ └─FMTSLR(──┼───────────────┼──program-name──)─┘
├─\CURLIB/──────┤
└─library-name/─┘
5──┬─────────────────────────────────────┬──┬────────────────────────────────────┬──┬────────────────────────────────┬──────────5
└─WAITFILE(──┬─\IMMED────────────┬──)─┘ └─WAITRCD(──┬─\IMMED────────────┬──)─┘ └─NBRRCDS(──number-of-records──)─┘
├─\CLS──────────────┤ ├─\NOMAX────────────┤
└─number-of-seconds─┘ └─number-of-seconds─┘
5──┬───────────────────────────────────┬──┬─────────────────┬──┬──────────────────────┬──┬──────────────────────┬───────────────5
└─EOFDLY(──┬─\NONE─────────────┬──)─┘ └─LVLCHK(──\NO──)─┘ └─EXPCHK(──┬─\YES─┬──)─┘ └─INHWRT(──┬─\YES─┬──)─┘
└─number-of-seconds─┘ └─\NO──┘ └─\NO──┘
5──┬──────────────────────┬──┬──────────────────────────────┬──┬─────────────────────┬──┬──────────────────────────────┬────────5
│ ┌─\NO──┐ │ │ ┌─\ACTGRPDFN─┐ │ └─SHARE(──┬─\NO──┬──)─┘ └─OPNSCOPE(──┬─\ACTGRPDFN─┬──)─┘
└─SECURE(──┴─\YES─┴──)─┘ └─OVRSCOPE(──┼─\CALLLVL───┼──)─┘ └─\YES─┘ └─\JOB───────┘
└─\JOB───────┘
5──┬────────────────────────────────────────┬──┬────────────────────────────┬──────────────────────────────────────────────────5%
└─SEQONLY(──┬─\NO───────────────────┬──)─┘ └─DSTDTA(──┬─\BUFFERED──┬──)─┘
├─\YES──────────────────┤ ├─\PROTECTED─┤
└─┬───────────────────┬─┘ └─\CURRENT───┘
└─number-of-records─┘
Notes:
P All parameters preceding this point can be specified in positional form.
1 A maximum of 32 repetitions
Parameters that are not specified do not affect parameters *LAST: The last member of the specified physical file is
specified in the file description, in the program, or in other used.
previously issued file override commands.
*ALL: All members in the file are processed sequen-
Note: The override cannot be used for all commands. A list tially. All members are opened with the same override
of the commands that cannot be overridden, along parameters as the first member. While overrides issued
with more information on overriding files is in the prior to the open operation of the first member are pro-
Data Management book. cessed, overrides or delete overrides issued following
the open operation of the first member are not pro-
Note: To see the parameter and value descriptions for this
cessed. EOFDLY, FMTSLR, INHWRT, or the POSI-
command, refer to the online help text. For more
TION parameter cannot be specified if MBR(*ALL) has
information about printing the help text, refer to
been specified on a previously issued OVRDBF
“Printing CL Command Descriptions” in Chapter 1.
command that is still in effect for this file. An escape
message is sent if any of the mutually exclusive parame-
Required Parameter ters are specified.
FILE member-name: Specify the member name that over-
Specifies the name of the file being used by the program rides (at file open time) the member name specified in
to which this override command is applied. If the using program, or in other called OVRDBF com-
TOFILE(*FILE) is specified, a display device file must be mands. If the member name is not specified, and a
specified. Otherwise, any device file or database file TOFILE parameter other than *FILE has been specified,
can be specified. the first member in the file is used.
POSITION
Optional Parameters Specifies the starting position for retrieving records from
the database file. The first record to get can be at the
TOFILE beginning (*START) or at the end (*END) of the file, the
Specifies the qualified name of the database file that is nth record in the file (*RRN), or the record indicated by a
used instead of the file specified in the FILE parameter key field value and one of the key-search values (*KEY,
or, if *FILE is specified, specifies that certain attributes *KEYA, *KEYAE, *KEYB, or *KEYBE). This parameter
are overridden by parameters specified in this command. overrides the value specified in the program, or in other
The parameters specified on this OVRDBF command called OVRDBF commands.
override the same parameters specified in the database
file, in the program, or in other previously issued Note: This parameter cannot be specified if MBR(*ALL)
OVRDBF commands. was specified in a previously issued OVRDBF
command that is still in effect for this file.
*FILE: The database file named in the FILE parameter
has some of its parameters overridden by values speci- *NONE: No special positioning is required. The first I/O
fied in this command. operation indicates the record that is retrieved.
The name of the database file can be qualified by one of *START: The starting position is the first record in the
the following library values: file. If a read-previous is specified in the program, an
end-of-file condition occurs.
*LIBL: All libraries in the job's library list are
*END: The starting position is the last record in the file.
searched until the first match is found.
When the next record is retrieved, an end-of-file condi-
*CURLIB: The current library for the job is tion is reached. If a read previous is requested, the last
searched. If no library is specified as the current record of the file is retrieved.
library for the job, the QGPL library is used.
Element 1: Relative Record Number
library-name: Specify the name of the library to be
*RRN relative-record-number: Specify the number of the
searched.
relative record (its position from the beginning of the
database-file-name: Specify the name of the database file), preceded by the value *RRN, that is retrieved first.
file that is used instead of the file specified in the FILE For example, POSITION(*RRN 480) specifies that record
parameter. number 480 is retrieved next. If a read-previous is
requested, the 479th record in the file is retrieved.
MBR
Specifies the members used within the database file. Element 2: Key-Search Values
This parameter is not valid for DDM files that reference The first record that is retrieved is identified by the speci-
remote systems other than the System/38 or the AS/400 fied key-operation, number-of-fields, record-format-name,
system. and key-value. If a record that matches these values
*FIRST: The first member in the database file is used. does not exist, an error message is sent.
Specify one of the following key-search types:
*KEYB (key-before): A record that precedes the record If a key is specified that contains more than one field,
identified by the remaining search values (number-of- the key must be coded to match the definition of the key
fields, record-format-name, and key-value) is the first in the file. If the definition is for a key other than a char-
record retrieved. acter or signed decimal key, the key must be coded in
hexadecimal form.
*KEYBE (key-before or equal): The record identified by
the search values is the first record retrieved. If no For example, suppose the key definition has the fol-
record matches those values, the record is selected that lowing key fields:
matches the largest previous value.
Character field (6A)
*KEY (key-equal): The record identified by the search
Packed numeric field (5P 2)
values is the first record retrieved. If a read-previous is
specified in the program, the preceding record is Signed numeric field (2S 0)
retrieved.
A character string the length of the entire key (6+3+2 in
*KEYAE (key-after or equal): The record identified by this example) can be specified on the POSITION param-
the search values is the first record retrieved. If no eter. POSITION(*KEY 3 YOURFMT
records matches those values, the record is selected X'E6D9C5D5C3C812345FF9F9') specifies that the
with the next highest value. system searches for the record in format YOURFMT, a
*KEYA (key-after): A record that follows the record key containing three fields is used in the search, and the
identified by the remaining search values (number-of- record contains the hexadecimal value
fields, record-format-name, and key-value) is the first E6D9C5D5C3C812345FF9F9. The hexadecimal value
record retrieved. corresponds to the following desired key values:
Specify the remaining search values as follows: Hexadecimal value E6D9C5D5C3C8 corresponds to
the character field key value WRENCH.
Element 3: Number of Fields
number-of-fields: Specify the number of key fields to Hexadecimal value 12345F corresponds to the
use in the search. The number of fields specified in this packed numeric field value +123.45.
parameter does not have to be the same as the actual Hexadecimal value F9F9 corresponds to the signed
number of fields in each key for the file. For example, if numeric field value 99.
POSITION(*KEY 1 FMT1 A) is specified, the first record
in the file format FMT1 that has a first key field value of The Distributed Data Management book has more infor-
mation on the effects of using the POSITION parameter
A is retrieved. If a number of fields of zero are speci-
with DDM files.
fied, the search is based on all key fields. If zero is
used, the key value contains the maximum key size. RCDFMTLCK
Element 4: Name of Record Format Specifies the lock state of the named record format while
it is used by the program. The lock state indicates how
record-format-name: Specify the name of the record the data associated with each format is locked. The fol-
format in the database file that contains the key value
lowing chart shows the lock states that are specified for
specified. If no record format name is specified (*N), all
each record format and the operations allowed to other
record formats are searched for the first record that
programs when the lock is in effect:
matches the other search values.
Lock Definition Other Program Operations
Element 5: Key Value State
key-value: Specify the first record retrieved. This value *SHRRD Shared read Read and update allowed
is specified as a quoted character string for character or *SHRNUP Shared read, no Read allowed, update not allowed
positive zoned decimal formats, or is specified in update
hexadecimal form at (x'value'). You can specify up to *SHRUPD Shared update Read and update allowed
2000 characters in the character string. *EXCLRD Exclusive allow read Read allowed, update not allowed
For example, POSITION(*KEY 1 FMT2 X'123F') speci- *EXCL Exclusive no read Neither read nor update allowed
fies that the system searches for a record from the
record format FMT2, that a single key field is used in the An explanation of each lock state is in the CL Program-
search (even though the key value may have more key ming book.
fields), and that the record contains the hexadecimal
For each record format, specify the record format name
value 123F (the hexadecimal equivalent of packed
followed by one lock state value. This parameter over-
decimal value 123).
rides the record format locks specified in the program, in
POSITION(*KEYB 0 *N X'123F') specifies that a record other called OVRDBF commands, and the default locks
of any format is retrieved next (its key value must established when the member was created. If the lock
precede the record identified by key value X'123F'). state specified for the file in an Allocate Object
(ALCOBJ) command is more restrictive than the lock
state specified in this parameter, this parameter is cated when the file is opened. If those resources are
ignored. Therefore, this parameter can only impose a not allocated within the specified wait time, an error
more restrictive lock state on a record format than that message is sent to the program.
specified for the file.
This parameter overrides the wait time specified in the
FRCRATIO database file, in the program, or in other previously
Specifies the number of insert, delete, or update oper- issued OVRDBF commands. More information on this
ations that can occur on records before they are forced parameter is in Appendix A, “Expanded Parameter
into auxiliary (permanent) storage. More information on Descriptions.”
this parameter is in Appendix A, “Expanded Parameter *IMMED: The program does not wait; when the file is
Descriptions.” More information on journal management opened, an immediate allocation of the file resources is
is in the Backup and Recovery book. required.
This parameter overrides the force-write ratio specified in *CLS: The job default wait time is used as the wait time
the database file, in the program, or in other previously for the file resources being allocated.
issued OVRDBF commands.
number-of-seconds: Specify the number of seconds that
*NONE: There is no force write ratio; the system deter- the program waits for the file resources to be allocated.
mines when the records are written to auxiliary storage. Valid values range from 1 through 32767 seconds.
number-of-write-operations-before-force: Specify the WAITRCD
number of operations. If a physical file associated with
Specifies the number of seconds that a program waits
this database file is journaled, specify a larger force-write
for a record to be updated or deleted, or for a record
ratio.
read in the commitment control environment with
FMTSLR LCKLVL(*ALL) specified. More information on record
Specifies the qualified name of a record format selection locking is in the DB2 for AS/400 Database Programming
program that is called when a logical file member con- book. If the record is not allocated in the specified wait
tains more than one logical record format. The user- time, an error message is sent to the program.
written selector program is called when a record is Note: This parameter overrides the record wait time
inserted into the database file and a record format name specified in the database file, specified in the
is not specified in the high-level language program. program, or in other previously issued OVRDBF
More information about the use of format selector pro- commands. The minimum delay for DDM files is
grams is in the DB2 for AS/400 Database Programming 60 seconds. This value may need to be longer
book. This parameter overrides the value specified in than the delay specified for local database files.
the database file and in other previously issued
*IMMED: The program does not wait; when a record is
OVRDBF commands.
locked, an immediate allocation of the record is required.
A program specified as the format selector program
*NOMAX: There is no disconnect limit.
cannot be created with USRPRF(*OWNER) specified in
the Create CL Program (CRTCLPGM) command. number-of-seconds: Specify the number of seconds that
the program waits for the record lock. Valid values
Note: This parameter cannot be specified if MBR(*ALL)
range from 1 through 32767 seconds.
was specified in a previously issued OVRDBF
command that is still in effect for this file. NBRRCDS
The name of the program can be qualified by one of the Specifies the number of records moved as a unit from
following library values: auxiliary storage to main storage. (The amount of data
actually moved is equal to the number of records multi-
*LIBL: All libraries in the job's library list are plied by the physical record length, not the logical record
searched until the first match is found. length.) Valid values range from 1 through 32767
*CURLIB: The current library for the job is records. The NBRRCDS parameter is valid for sequen-
searched. If no library is specified as the current tial or random processing and is specified only when the
library for the job, the QGPL library is used. data records are physically located in auxiliary storage in
the sequence in which they are processed. This param-
library-name: Specify the name of the library to be eter overrides the number of records value specified in
searched.
the program, or in other previously issued OVRDBF
program-name: Specify the name of a record format commands.
selection program called when a logical file member con-
EOFDLY
tains more than one logical record format.
Specifies the number of seconds to delay when the end-
WAITFILE of-file is reached before trying to retrieve additional
Specifies the number of seconds that the program waits records. This delay allows other jobs to add records to
for the file resources and session resources to be allo- the file, and have the new records processed without
having to restart the job. When the delay time ends, the
job is made active, and the database determines *NO: The level identifiers are not checked when the file
whether new records were added. If no new records is opened.
were added, the job waits for another time delay without
EXPCHK
informing the application program. When a number of
Specifies whether the expiration date of the named
seconds is specified, no end-of-file condition occurs on
member is checked. This date check is valid only on a
the given database file until an End Job (ENDJOB)
physical file member. This parameter overrides the
command or forced end of data (FEOD) occurs.
value specified in the program, or in other called
Note: This parameter cannot be specified if MBR(*ALL) OVRDBF commands.
was specified on a previously issued OVRDBF
*YES: The expiration date of the physical file member is
command that is still in effect for this file.
checked. If the current date is later than the expiration
There are several ways to end a job that is waiting for date, an error message is sent to the job, where it is
records due to an EOFDLY. They are: monitored. An escape message is sent to the program.
Write a record to the specified file which is recog- *NO: The expiration date is not checked.
nized by the application program as a last record.
INHWRT
The application program may then do a force end of
Specifies whether the processed records are written,
data (FEOD) to start the end-of-file processing or
deleted, or changed in the database file. This parameter
close the file.
tests a program without storing the processed records
End the job using the controlled value (ENDJOB back in the database. This parameter overrides the
OPTION(*CNTRLD)) with a delay time greater than INHWRT parameter in other previously issued OVRDBF
the time specified on the EOFDLY time. The commands.
DELAY parameter time specified must allow for the
Note: This parameter cannot be specified if MBR(*ALL)
EOFDLY time to run out, plus time to process any
was specified on a previously issued OVRDBF
new records that may have been added to the file,
command that is still in effect for this file.
and any end-of-file processing that is done in the
user's application. The end-of-file is set by data- *YES: Processed records are prevented from being
base, and a normal end-of-file condition occurs after written into the database; they are written only to an
new records are retrieved. output device.
End the job immediately (ENDJOB *NO: All new and changed processed records are
OPTION(*IMMED)). written into the database, unless the program is in debug
mode with UPDPROD(*NO) specified, and the file is in a
If the job is interactive, start a system request and
production library. In that case, an escape message is
end the previous request.
sent to the program.
*NONE: Normal end-of-file processing is done.
SECURE
number-of-seconds: Specify the number of seconds that Specifies whether this file is safe from the effects of pre-
the program waits between each attempt to get a record viously called file override commands. If SECURE is not
when an end-of-file condition occurs. No end-of-file con- specified, processing occurs as if SECURE(*NO) is
dition is signaled until end of data is forced, or the job is specified.
ended with the *CNTRLD option. Valid values range
*NO: This file is not protected from the effects of other
from 1 through 99999 seconds.
file overrides; its values can be overridden by the effects
LVLCHK of previously called file override commands.
Specifies whether the record format level identifiers in
*YES: This file is protected from the effects of any file
the program are checked against those in the device file
override commands previously called.
when the file is opened. If so, the record format identi-
fiers in the program must match those in the device file. OVRSCOPE
Because the same record format name can exist in more Specifies the extent of influence (scope) of the override.
than one file, each record format is given an internal
*ACTGRPDFN: The scope of the override is determined
system identifier when it is created.
by the activation group of the program that calls this
Note: This parameter overrides the value specified in command. When the activation group is the default acti-
the database file, in the program, or in other pre- vation group, the scope equals the call level of the
viously issued OVRDBF commands issued in this calling program. When the activation group is not the
or the following call level. Level checking cannot default activation group, the scope equals the activation
be done unless the program contains the record group of the calling program.
format identifiers. This command cannot over-
*CALLLVL: The scope of the override is determined by
ride level checking from *NO to *YES.
the current call level. All open operations done at a call
level that is the same as or higher than the current call
level are influenced by this override.
*JOB: The scope of the override is the job in which the output files, sequential-only processing is valid for phys-
override occurs. ical file members and for logical file members that are
based on one physical file member only.
SHARE
Specifies whether the open data path (ODP) for the If SEQONLY(*YES) is specified, and any of the following
database file member is shared with other programs in conditions are true, the SEQONLY parameter is ignored
the routing step. When an ODP is shared, the programs and a message is issued.
accessing the file share facilities such as the file status
The program opened the member for output only
and the buffer.
and SEQONLY(*YES) is specified with the default
More information on shared database files is in the DB2 number of records, and the member opened is
for AS/400 Database Programming book. either a logical member, a unique keyed physical
member, or other access paths are built over the
*NO: The ODP created by the program with this attri-
physical member.
bute is not shared with other programs in the routing
step. Every time a program opens the file with this attri- The program opened the member for other than
bute, a new ODP to the file is created and activated. input or output.
Note: This includes several opens in the same The member opened by the program for output is
program. based on many other members.
*YES: The ODP created with this attribute is shared The record length plus the feedback area sum
with each program in the routing step that also specifies exceeded 32,767 bytes.
SHARE(*YES) when it opens the file.
Note: Unpredictable results occur when this parameter
Note: When SHARE(*YES) is specified and control is is used for alternate index files for DDM on a
passed to a program, a read operation in that system other than an AS/400 system.
program retrieves the next input record. A write
*NO: The database file is not restricted to sequential-
operation produces the next output record.
only processing.
OPNSCOPE
*YES: The database file uses sequential-only pro-
Specifies the extent of influence (scope) of the open
cessing. A default value for the number of records
operation.
transferred as a group is determined by the system
*ACTGRPDFN: The scope of the open operation is based on how the file is used, the type of access path
determined by the activation group of the program that involved, and the file's record length:
called the OVRDBF command processing program. If
the activation group is the default activation group, the The default is approximately the number of records
scope is the call level of the caller. If the activation that fit in an internal buffer of 4K for:
group is a non-default activation group, the scope is the – All database files opened for input only
activation group of the caller.
– Physical files opened for output that are only
*JOB: The scope of the open operation is the job in processed in either arrival sequence or in non-
which the open operation occurs. unique keyed sequence and that have no
logical file members based on them
SEQONLY
Specifies, for database files whose records are pro- The default is 1 record for:
cessed in sequential order only, whether sequential-only – All logical files opened for output only
processing is used on the file. This parameter also
specifies the number of records transferred as a group – Physical files opened for output only that either
to or from the database, if sequential-only processing is have unique keyed sequence access paths or
have at least one dependent logical file with a
used. If a number is not specified, a default number is
keyed sequence access path that does not
determined by the system. This parameter is used to
share the access path of the keyed physical file
improve the performance of programs that process data-
member
base files in a sequential manner. This parameter over-
rides the value specified in the program or in other number-of-records: Specify *YES followed by a value
previously issued OVRDBF commands. (ranging from 1 through 32767) for the number of
For files opened for input only in a program, the speci- records transferred between the database and the
fied number of records is transferred as a group from the internal buffer. The user must ensure that the buffer
database to an internal data management buffer. size specified is always available to the program in the
storage pool in which the program is running. The file
For files opened for output only in a program, a group of
uses sequential-only processing.
records is transferred to the database whenever the
internal data management buffer receives the specified While records are in the internal data management
number of processed records from the program. For buffer, other jobs can make changes to the same
records in the database, and the program performing OVRDBF FILE(ORDERSIN) SHARE(\YES)
sequential-only input processing does not see the
updates. To ensure that no other updating is done to This command overrides the share specification for the file
records while they are in the buffer, the Allocate Object ORDERSIN. Because of this override, any subsequent
(ALCOBJ) command can be used in the program to opens of this file within the routing step share the ODP for
specify either an *EXCLRD or an *EXCL lock on the file. the file.
If a program performs sequential-only output processing Example 3: Overriding a File, Member and Lock State
and does not handle output errors (such as duplicate
OVRDBF FILE(INPUT) TOFILE(PAYROLL) MBR(MBR1)
keys and conversion mapping errors) that may occur
RCDFMTLCK((EMPDATA \EXCL))
when the records in the buffer are written to the data-
base, records in the buffer after the first record in error This command overrides the file, the member, and the lock
are not written. state of the record format EMPDATA. The override will
If the file is opened for output and the value specified in cause the following to occur when the file INPUT is opened:
this parameter is not the same as the force write ratio The file PAYROLL will be processed instead of the file
specified for the file, the value used by the system is the INPUT.
smaller of the two; a message stating which value is
changed is sent to the user. The member MBR1 will be processed instead of the pre-
viously specified member.
When processing SEQONLY(*YES) for writing records
into a database file, feedback information for each The lock *EXCL will be placed on record format
record (such as relative record number) is not always EMPDATA instead of the existing lock. (*EXCL prevents
changed. If such feedback information is important, another program from using the record format while the
specify SEQONLY(*NO) or SEQONLY(*YES 1). override is in effect.)
55──OVRDKTF──FILE(──overridden-file-name──)──┬──────────────────────────────────────────────────────────────┬───────────────────5
│ ┌─\FILE────────────────────────────────────────┐ │
│ │ ┌─\LIBL/────────┐ │ │
└─TOFILE(──┴─┼───────────────┼──diskette-device-file-name─┴──)─┘
├─\CURLIB/──────┤
└─library-name/─┘
(P) ──┬───────────────────────────────────────┬──┬────────────────────────────┬───────────────────────5
5──┬──────────────────────┬───
└─DEV(──device-name──)─┘ └─VOL(──┬─\NONE────────────────────┬──)─┘ └─LABEL(──data-file-label──)─┘
│ ┌──
───────────────────┐ │
└──6─volume-identifier─┴───
(1) ─┘
5──┬──────────────────────────┬──┬───────────────────────┬──┬────────────────────────────────┬──────────────────────────────────5
└─EXCHTYPE(──┬─\STD───┬──)─┘ └─CODE(──┬─\EBCDIC─┬──)─┘ └─CRTDATE(──┬─\NONE─────────┬──)─┘
├─\BASIC─┤ └─\ASCII──┘ └─creation-date─┘
├─\H─────┤
└─\I─────┘
5──┬──────────────────────────────────┬──┬─────────────────────┬──┬────────────────────────────────────────────────┬────────────5
└─EXPDATE(──┬─\NONE───────────┬──)─┘ └─SPOOL(──┬─\NO──┬──)─┘ │ ┌─\LIBL/────────┐ │
├─\PERM───────────┤ └─\YES─┘ └─OUTQ(──┼───────────────┼──output-queue-name──)─┘
└─expiration-date─┘ ├─\CURLIB/──────┤
└─library-name/─┘
5──┬──────────────────────────────────┬──┬────────────────────────────┬──┬────────────────────┬──┬────────────────────┬─────────5
└─MAXRCDS(──┬─\NOMAX──────────┬──)─┘ └─SCHEDULE(──┬─\JOBEND──┬──)─┘ └─HOLD(──┬─\NO──┬──)─┘ └─SAVE(──┬─\NO──┬──)─┘
└─maximum-records─┘ ├─\FILEEND─┤ └─\YES─┘ └─\YES─┘
└─\IMMED───┘
5──┬─────────────────────────────────┬──┬───────────────────────────┬──┬──────────────────────┬─────────────────────────────────5
└─OUTPTY(──┬─\JOB────────────┬──)─┘ └─USRDTA(──┬─\BLANK────┬──)─┘ └─IGCDTA(──┬─\NO──┬──)─┘
└─output-priority─┘ └─user-data─┘ └─\YES─┘
5──┬─────────────────────────────────────┬──┬──────────────────────┬──┬──────────────────────────────┬──────────────────────────5
└─WAITFILE(──┬─\IMMED────────────┬──)─┘ │ ┌─\NO──┐ │ │ ┌─\ACTGRPDFN─┐ │
├─\CLS──────────────┤ └─SECURE(──┴─\YES─┴──)─┘ └─OVRSCOPE(──┼─\CALLLVL───┼──)─┘
└─number-of-seconds─┘ └─\JOB───────┘
5──┬─────────────────────┬──┬──────────────────────────────┬───────────────────────────────────────────────────────────────────5%
└─SHARE(──┬─\NO──┬──)─┘ └─OPNSCOPE(──┬─\ACTGRPDFN─┬──)─┘
└─\YES─┘ └─\JOB───────┘
Notes:
P All parameters preceding this point can be specified in positional form.
1 A maximum of 50 repetitions
Purpose are not specified do not affect parameters specified in the file
description, in the program, or in other called file override
The Override with Diskette File (OVRDKTF) command is commands.
used to (1) override (replace) the file named in the program,
(2) override certain parameters of a file that is used by the More information on overriding files is in the Data Manage-
program, or (3) override the file named in the program and ment book, the Application Display Programming book, and
override certain parameters of the file processed. the Printer Device Programming book.
Note: To see the parameter and value descriptions for this
Parameters overridden by this command are specified in the
command, refer to the online help text. For more
file description, in the program, or in other called file override
information about printing the help text, refer to
commands. If a file named in the program is overridden, the
“Printing CL Command Descriptions” in Chapter 1.
name of that file is specified in the FILE parameter and the
name of the overriding file (the file processed) is specified in
the TOFILE parameter. The OVRDKTF command also spec- Required Parameter
ifies parameters to override values contained in the file
description of the overriding file. If the file named in the FILE
program is not replaced but certain parameters of the file are Specifies the name of the file being used by the program
overridden, the name of the file is specified in the FILE to which this override command is applied. If
parameter and *FILE is specified in the TOFILE parameter. TOFILE(*FILE) is specified, a display device file must be
The parameters overridden are then specified by the other specified. Otherwise, any device file or database file
parameters of the OVRDKTF command. Parameters that can be specified.
Optional Parameters *NONE: The diskette volume identifiers are not speci-
fied for this file in this command. They can be specified
TOFILE later before the device file is opened, either in a Over-
Specifies the qualified name of the diskette file that is ride with Diskette File (OVRDKTF) command or a
used instead of the file specified in the FILE parameter Change Diskette File (CHGDKTF) command, or in the
or, if *FILE is specified, specifies that certain attributes high-level language program. Otherwise, no volume
are overridden by parameters specified in this command. identifier checking is done.
The parameters specified in this OVRDKTF command
volume-identifier: Specify the identifiers of one or more
override the same parameters specified in the diskette
volumes in the order in which they are put on the device
device file in the program, or in other called OVRDKTF
and used. Each volume identifier contains a maximum
commands.
of 6 alphanumeric characters. A blank is used as a sep-
*FILE: The diskette device file named in the FILE arator character when listing multiple identifiers.
parameter has some of its parameters overridden by
values specified in this command. LABEL
Specifies the data file label of the data file on diskette
The name of the diskette file can be qualified by one of that is used with this diskette device file. For input files
the following library values: (diskette input to system), this label specifies the identi-
*LIBL: All libraries in the job's library list are fier of the file that exists on the diskette. For output files
searched until the first match is found. (system output to diskette), the label specifies the identi-
fier of the file that is created on the diskette. More infor-
*CURLIB: The current library for the job is mation on this parameter is in Appendix A, “Expanded
searched. If no library is specified as the current Parameter Descriptions.”
library for the job, the QGPL library is used.
This parameter overrides the label specified in the
library-name: Specify the name of the library to be diskette device file, in the program, or in other called
searched. OVRDKTF commands.
diskette-device-file-name: Specify the name of the data-file-label: Specify up to 8 characters for the identi-
diskette device file that is used instead of the overridden fier of the data file used with this diskette device file.
file.
EXCHTYPE
DEV Specifies, for diskette output files only, the exchange
Specifies the name of the diskette device used with this type used by the device file when the system is writing
diskette device file to perform input/output data oper- diskette data. More information on this parameter is in
ations. The device name of the IBM-supplied diskette Appendix A, “Expanded Parameter Descriptions.”
device description is QDKT. This parameter is ignored if
This parameter overrides the value specified in the
SPOOL(*YES) is specified for the file when it is opened.
device file, in the program, or in other called OVRDKTF
This parameter overrides the value specified in the commands.
device file, in the program, or in other called OVRDKTF
*STD: The basic exchange format is used for a type 1
commands.
or a type 2 diskette. The H exchange type is used for a
device-name: Specify the name of the device that is type 2D diskette.
used with this diskette device file. The device name
*BASIC: The basic exchange type is used.
must already exist on the system as a device description
before this device file is created. *H: The H exchange type is used.
*NO: The spooled file data is not saved on the output SECURE
queue after it has been produced. Specifies whether this file is safe from the effects of pre-
viously called file override commands. If SECURE is not
*YES: The spooled file data is saved on the output
specified, processing occurs as if SECURE(*NO) is
queue until the file is deleted.
specified.
OUTPTY *NO: This file is not protected from the effects of other
Specifies the output priority for spooled output files that file overrides; its values can be overridden by the effects
are produced by this job. The highest priority is 1 and of previously called file override commands.
the lowest priority is 9. More information on this param-
eter is in Appendix A, “Expanded Parameter *YES: This file is protected from the effects of any file
Descriptions.” override commands previously called.
*JOB: The output priority associated with the job that OVRSCOPE
created the spooled file is used. Specifies the extent of influence (scope) of the override.
output-priority: Specify the output priority. Valid values *ACTGRPDFN: The scope of the override is determined
range from 1 (high priority) through 9 (low priority). by the activation group of the program that calls this
command. When the activation group is the default acti-
USRDTA
vation group, the scope equals the call level of the
Specifies, for spooled output only, the user-specified
calling program. When the activation group is not the
data that identifies the file.
default activation group, the scope equals the activation
*BLANK: Ten blanks are used as the user data. group of the calling program.
user-data: Specify up to 10 characters of text. *CALLLVL: The scope of the override is determined by
the current call level. All open operations done at a call
IGCDTA
level that is the same as or higher than the current call
Specifies whether the file processes double-byte char-
level are influenced by this override.
acter set (DBCS) data.
*JOB: The scope of the override is the job in which the
*NO: The file does not process DBCS data.
override occurs.
*YES: The file processes DBCS data.
SHARE
WAITFILE Specifies whether the open data path (ODP) for the
Specifies the number of seconds that the program waits diskette file is shared with other programs in the routing
for the file resources and session resources to be allo- step. When an ODP is shared, the programs accessing
cated when the file is opened, or for the device or the file share facilities such as the file status and the
session resources to be allocated when an acquire oper- buffer.
ation is performed to the file. If those resources are not
More information on shared database files is in the DB2
allocated within the specified wait time, an error
for AS/400 Database Programming book.
message is sent to the program. More information on
This parameter also overrides the value specified in group is a non-default activation group, the scope is the
other called OVRDKTF commands. activation group of the caller.
*NO: The ODP created by the program with this attri- *JOB: The scope of the open operation is the job in
bute is not shared with other programs in the routing which the open operation occurs.
step. Every time a program opens the file with this attri-
bute, a new ODP to the file is created and activated.
Examples
*YES: The ODP created with this attribute is shared
with each program in the routing step that also specifies Example 1: Changing Spooling Specifications
SHARE(*YES) when it opens the file. OVRDKTF FILE(OUT) VOL(DPT7ð6) LABEL(STATUSR)
Note: When SHARE(*YES) is specified and control is SPOOL(\YES)
passed to a program, a read operation in that
This command changes the spooling specification for the
program retrieves the next input record. A write
output file named OUT. When a program produces output
operation produces the next output record.
data for the OUT file, the data is spooled for processing by a
OPNSCOPE spooling writer. The writer processes the data by writing it in
Specifies the extent of influence (scope) of the open a data file called STATUSR that is on a diskette whose
operation. volume identifier is DPT706.
*ACTGRPDFN: The scope of the open operation is Example 2: Specifying DBCS Processing
determined by the activation group of the program that
called the OVRDKTF command processing program. If OVRDKTF FILE(IGCLIB/IGCDCT) IGCDTA(\YES)
the activation group is the default activation group, the
This command overrides the diskette file IGCDCT, which is
scope is the call level of the caller. If the activation
stored in the library IGCLIB, so that the file contains double-
byte character set data.
55──OVRDSPF──FILE(──overridden-file-name──)──┬─────────────────────────────────────────────────────────────┬────────────────────5
│ ┌─\FILE───────────────────────────────────────┐ │
│ │ ┌─\LIBL/────────┐ │ │
└─TOFILE(──┴─┼───────────────┼──display-device-file-name─┴──)─┘
├─\CURLIB/──────┤
└─library-name/─┘
(P) ──┬─────────────────────────────────────────────────┬──┬───────────────────────┬───────5
5──┬─────────────────────────────────┬───
| └─DEV(──┬─\REQUESTER─────────┬──)─┘ └─CHRID(──┬─\DEVD────────────────────────────┬──)─┘ └─DECFMT(──┬─\FILE─┬──)─┘
| │ ┌──
─────────────┐ │ ├─\SYSVAL──────────────────────────┤ └─\JOB──┘
6 (1)
└───device-name─┴────┘ ├─\JOBCCSID────────────────────────┤
└─graphic-character-set──code-page─┘
5──┬──────────────────────┬──┬─────────────────────────┬──┬─────────────────────────────────────┬───────────────────────────────5
└─IGCDTA(──┬─\NO──┬──)─┘ └─IGCEXNCHR(──┬─\YES─┬──)─┘ └─WAITFILE(──┬─\IMMED────────────┬──)─┘
└─\YES─┘ └─\NO──┘ ├─\CLS──────────────┤
└─number-of-seconds─┘
5──┬────────────────────────────────────┬──┬─────────────────┬──┬──────────────────────┬──┬──────────────────────────────┬──────5
└─WAITRCD(──┬─\NOMAX────────────┬──)─┘ └─LVLCHK(──\NO──)─┘ │ ┌─\NO──┐ │ │ ┌─\ACTGRPDFN─┐ │
├─\IMMED────────────┤ └─SECURE(──┴─\YES─┴──)─┘ └─OVRSCOPE(──┼─\CALLLVL───┼──)─┘
└─number-of-seconds─┘ └─\JOB───────┘
5──┬──────────────────────────────────────────────────┬──┬─────────────────────┬──┬──────────────────────────────┬─────────────5%
└─DTAQ(──┬─\NONE──────────────────────────────┬──)─┘ └─SHARE(──┬─\NO──┬──)─┘ └─OPNSCOPE(──┬─\ACTGRPDFN─┬──)─┘
│ ┌─\LIBL/────────┐ │ └─\YES─┘ └─\JOB───────┘
└─┼───────────────┼──data-queue-name─┘
├─\CURLIB/──────┤
└─library-name/─┘
Notes:
1 A maximum of 50 repetitions
*LIBL: All libraries in the job's library list are *JOBCCSID: The character data is changed from the
searched until the first match is found. device CHRID to the CCSID (coded character set identi-
fier) of the job on display file input, and from the CCSID
*CURLIB: The current library for the job is
of the job to the device CHRID on display file output.
searched. If no library is specified as the current
library for the job, the QGPL library is used. Note: This value is not allowed if the file was created
on a system at an earlier release level than
library-name: Specify the name of the library to be
V2R3M0.
searched.
Element 1: Character Set
display-device-file-name: Specify the name of the
display device file used instead of the overridden file. graphic-character-set: Specify the graphic character set
values that match the attributes of the display device.
DEV Valid values range from 1 through 32767.
Specifies the names of one or more display devices
Element 2: Code Page
used with this display device file to pass data records
between the users of the display devices and their jobs. code-page: Specify the code page set values that
The device name specified in the display device file sup- match the attributes of the display device. Valid values
plied by IBM is *REQUESTER. range from 1 through 32767.
This parameter overrides the device names specified in | DECFMT
the device file, in the program, or in other called | Specifies which decimal format value is used when
OVRDSPF commands. | editing numeric fields with the EDTCDE DDS keyword.
*REQUESTER: The device from which the program is | The decimal format value determines the use of commas
called is assigned to the file when the file is opened. | and periods for the decimal position and three digit posi-
| tional separators on edited fields.
device-name: Specify the names of one or more display
devices used with this device file to pass data records | *FILE: Use the decimal format value stored with the file
between the users of the devices and the system. Each | when the file was created.
device name must already be known on the system by a | *JOB: Use the decimal format value from the DECFMT
device description before this device file is created. | job attribute when the file is opened.
*REQUESTER can be specified as one of the names.
Up to 50 names can be specified in this command, but IGCDTA
the total number cannot exceed the number specified on Specifies, for program-described original files, whether
the MAXDEV parameter. the file processes double-byte character set (DBCS)
data. For externally described printer files, this param-
CHRID eter specifies DBCS attributes of the file.
Specifies the character identifier (graphic character set
*NO: The file does not process DBCS data.
and code page) that a work station display device sup-
ports. When a display file that was created with the *YES: The file processes DBCS data.
CHRID DDS keyword is used with the device, the
IGCEXNCHR
system converts data sent to and received from the
Specifies whether the system processes double-byte
device to ensure that the correct characters are shown
character set (DBCS) extension characters.
and that the correct hexadecimal byte values are
returned to the application program. More information *YES: The system processes DBCS extension charac-
about display file CHRID processing and the translation ters.
tables that are used to convert data sent to and received
*NO: The system does not process DBCS extension
from the display are in the Application Display Program-
characters; it displays extension characters as the unde-
ming book. fined character.
*DEVD: The CHRID value specified in the device
WAITFILE
description of the work station on which the application
Specifies the number of seconds that the program waits
is running is used. If no CHRID value is specified, the
for the file resources and session resources to be allo-
QCHRID system value (for the system on which the
cated when the file is opened, or for the device or
application is running) is used. No translation is neces-
session resources to be allocated when an acquire oper-
sary because the file has the same character identifier
ation is performed to the file. If those resources are not
as the work station. For a list of valid values, see the
allocated within the specified wait time, an error
CHRID parameter of the Create Device Description
message is sent to the program. More information on
Display (CRTDEVDSP) command description.
this parameter is in Appendix A, “Expanded Parameter
*SYSVAL: The system determines the graphic char- Descriptions.”
acter set and code page values for the command param-
eters from the QCHRID system values.
number-of-seconds: Specify the number of seconds that *NONE: A data queue does not receive an entry from
the program waits for the completion of the read-from- the system.
invited-device operation. Valid values range from 1 The name of the data queue can be qualified by one of
through 32767. the following library values:
*LIBL: All libraries in the job's library list are *YES: The ODP created with this attribute is shared
searched until the first match is found. with each program in the routing step that also specifies
SHARE(*YES) when it opens the file.
*CURLIB: The current library for the job is
searched. If no library is specified as the current Note: When SHARE(*YES) is specified and control is
library for the job, the QGPL library is used. passed to a program, a read operation in that
program retrieves the next input record. A write
library-name: Specify the name of the library to be
operation produces the next output record.
searched.
OPNSCOPE
data-queue-name: Specify the name of the data queue
Specifies the extent of influence (scope) of the open
that is to receive an entry from the system when the
operation.
data-available event is signaled.
*ACTGRPDFN: The scope of the open operation is
SHARE
determined by the activation group of the program that
Specifies whether the open data path (ODP) for the
called the OVRDSPF command processing program. If
display file is shared with other programs in the routing
the activation group is the default activation group, the
step. When an ODP is shared, the programs accessing
scope is the call level of the caller. If the activation
the file share facilities such as the file status and the
group is a non-default activation group, the scope is the
buffer.
activation group of the caller.
More information on shared database files is in the DB2
*JOB: The scope of the open operation is the job in
for AS/400 Database Programming book. which the open operation occurs.
This parameter overrides the value specified in the
device file, in the program, or in other called OVRDSPF
commands.
Example
OVRDSPF FILE(DISPLAY75) WAITFILE(3ð)
*NO: The ODP created by the program with this attri-
bute is not shared with other programs in the routing This command overrides the file wait time value specified in
step. Every time a program opens the file with this attri- the DISPLAY75 device file description, in the program, or in
bute, a new ODP to the file is created and activated. other called OVRDSPF commands. The program in which
this command occurs waits up to 30 seconds (if necessary)
to allocate the required file resources to the file named
DISPLAY75.
55──OVRICFDEVE──PGMDEV(──program-device-name──)──┬──────────────────────────────────────────┬───────────────────────────────────5
└─RMTLOCNAME(──┬─\REQUESTER───────────┬──)─┘
└─remote-location-name─┘
(P) ──┬──────────────────────────┬──┬─────────────────────────────────────────┬──────────────────5
5──┬───────────────────────────┬───
│ ┌─\ALL─────┐ │ └─DEV(──┬─\LOC────────┬──)─┘ └─LCLLOCNAME(──┬─\LOC────────────────┬──)─┘
└─CMNTYPE(──┼─\APPC────┼──)─┘ └─device-name─┘ ├─\NETATR─────────────┤
├─\ASYNC───┤ └─local-location-name─┘
├─\BSCEL───┤
├─\FINANCE─┤
├─\INTRA───┤
├─\RETAIL──┤
└─\SNUF────┘
5──┬─────────────────────────┬──┬─────────────────────────────────────┬──┬─────────────────────────┬────────────────────────────5
└─MODE(──┬─\NETATR───┬──)─┘ └─RMTNETID(──┬─\LOC──────────────┬──)─┘ └─FMTSLT(──┬─\PGM────┬──)─┘
├─BLANK─────┤ ├─\NETATR───────────┤ ├─\RECID──┤
└─mode-name─┘ ├─\NONE─────────────┤ └─\RMTFMT─┘
└─remote-network-ID─┘
5──┬───────────────────────────────┬──┬─────────────────────┬──┬───────────────────────┬──┬───────────────────────────────┬─────5
└─APPID(──┬─\DEVD──────────┬──)─┘ └─BATCH(──┬─\NO──┬──)─┘ └─HOST(──┬─\DEVD───┬──)─┘ └─ENDSSNHOST(──┬─\RSHUTD───┬──)─┘
├─\USER──────────┤ └─\YES─┘ ├─\CICS───┤ └─\TERMSELF─┘
└─application-ID─┘ ├─\IMS────┤
└─\IMSRTR─┘
5──┬────────────────────────────┬──┬───────────────────────┬──┬────────────────────────┬──┬──────────────────────┬──────────────5
│ ┌─\DEVD──┐ │ └─INZSELF(──┬─\NO──┬──)─┘ └─HDRPROC(──┬─\SYS──┬──)─┘ └─MSGPTC(──┬─\YES─┬──)─┘
└─SPCHOSTAPP(──┼─\NONE──┼──)─┘ └─\YES─┘ └─\USER─┘ └─\NO──┘
└─\FLASH─┘
5──┬─────────────────────────────────────────┬──┬──────────────────────────┬────────────────────────────────────────────────────5
└─EMLDEV(──┬─\NONE───────────────────┬──)─┘ └─CNVTYPE(──┬─\SYS────┬──)─┘
│ ┌─\UNFORMAT─┐ │ ├─\USER───┤
└─┬─3278─┬──┼───────────┼─┘ └─\SRCPGM─┘
├─3284─┤ ├─\FIELD────┤
├─3286─┤ ├─\NOFIELD──┤
├─3287─┤ └─\EXTFIELD─┘
├─3288─┤
└─3289─┘
5──┬─────────────────────────────────────────────────────┬──┬───────────────────────────────┬───────────────────────────────────5
└─BLOCK(──┬─\DEVD────────────────────────────────┬──)─┘ └─RCDLEN(──┬─\DEVD─────────┬──)─┘
├─\NONE────────────────────────────────┤ └─record-length─┘
├─\ITB─────────────────────────────────┤
├─\IRS─────────────────────────────────┤
├─\NOSEP───────────────────────────────┤
├─\USER────────────────────────────────┤
│ ┌─X'1E'──────────────────────┐ │
└─\SEP──┼────────────────────────────┼─┘
└─record-separator-character─┘
5──┬──────────────────────────────┬──┬───────────────────────┬──┬───────────────────────┬──┬──────────────────────┬─────────────5
└─BLKLEN(──┬─\DEVD────────┬──)─┘ └─TRNSPY(──┬─\DEVD─┬──)─┘ └─DTACPR(──┬─\DEVD─┬──)─┘ └─TRUNC(──┬─\DEVD─┬──)─┘
└─block-length─┘ ├─\NO───┤ ├─\NO───┤ ├─\NO───┤
└─\YES──┘ └─\YES──┘ └─\YES──┘
5──┬─────────────────────────────┬──┬──────────────────────────┬──┬─────────────────────────┬──┬───────────────────────┬────────5
└─OVRFLWDTA(──┬─\DISCARD─┬──)─┘ └─GRPSEP(──┬─\DEVD────┬──)─┘ └─RMTBSCEL(──┬─\DEVD─┬──)─┘ └─INLCNN(──┬─\CTLD─┬──)─┘
└─\RETAIN──┘ ├─\EOT─────┤ ├─\NO───┤ ├─\DIAL─┤
├─\DEV374ð─┤ └─\YES──┘ └─\ANS──┘
└─\OFCSYS──┘
5──┬──────────────────────┬──┬──────────────────────────────┬──────────────────────────────────────────────────────────────────5%
│ ┌─\NO──┐ │ │ ┌─\ACTGRPDFN─┐ │
└─SECURE(──┴─\YES─┴──)─┘ └─OVRSCOPE(──┼─\CALLLVL───┼──)─┘
└─\JOB───────┘
Note:
P All parameters preceding this point can be specified in positional form.
*SNUF: The SNA upline facility (SNUF) parameters location, and remote network ID, an escape message is
appear in the prompt. sent when the program device entry is acquired.
DEV RMTNETID
Specifies the communications device used in the remote Specifies the remote network ID used with the remote
location. This parameter should be specified only for location. This parameter applies to the APPC commu-
APPC, INTRA, and SNUF communications types. If the nications type only and is ignored for all other commu-
Add Intersystem Communications Function Program nications types. If the ADDICFDEVE command is not
Device Entry (ADDICFDEVE) command is not run for run for the specified program device and this parameter
the specified program device and this parameter is not is not overridden, RMTNETID(*LOC) is used.
overridden, DEV(*LOC) is used.
*LOC: The remote network identifier (ID) associated
*LOC: The device associated with the remote location with the remote location is used. If several remote
is used. If several devices are associated with the network IDs are associated with the remote location, the
remote location, the system determines which device is system determines which remote network ID is used.
used.
*NETATR: The RMTNETID value specified in the
device-name: Specify the name of a communications system network attributes is used.
device associated with the remote location. If the device
*NONE: No remote network identifier (ID) is used.
name is not valid for the remote location, a message is
sent when the program device entry is acquired. More remote-network-ID: Specify a remote network ID for the
information on device names is in the APPC Program- APPC communications device.
ming book. FMTSLT
LCLLOCNAME Specifies the record format selection used for input oper-
Specifies the local location name. ations. If the ADDICFDEVE command is not run for the
specified program device and this parameter is not over-
Note: This parameter applies to the APPC communica-
ridden, FMTSLT(*PGM) is used.
tions type only and is ignored for all other com-
munications types. If the ADDICFDEVE *PGM: The program determines which record formats
command is not run for the specified program are selected. If an input (read) operation with a record
device or is not overridden, this parameter format name is specified, that format is selected. If an
defaults to *LOC. input operation without a record format is specified, the
default format (the first record format in the file) is
*LOC: The device associated with the remote location
selected. This also means that if there are any record
is used. If several devices are associated with the
identification (RECID) parameters specified in the data
remote location, the system determines which device is
description specifications (DDS) for the file, or if any
used.
remote formats are received, they are not taken into
*NETATR: The LCLLOCNAME value specified in the consideration when the record is selected.
system network attributes is used.
*RECID: The record identification (RECID) keywords
local-location-name: Specify the name of the user's specified in the DDS for the file are used to do record
location. If the local location name is not valid for the selection. If there are no RECID keywords in the file, an
remote location or remote location and device, an error message is sent, the acquire operation of the
escape message is sent when the program device entry program device ends, and the device is not acquired.
is acquired.
*RMTFMT: The remote format names received from the
MODE sending system are used to do record selection. If the
Specifies the mode name used. This parameter applies device is not an APPC or intrasystem device and
only to the APPC communications type and is ignored *RMTFMT is specified, a run time error occurs at the
for all other communications types. If the ADDICFDEVE time the program device entry is acquired.
command is not run for the specified program device
APPID
and this parameter is not overridden, MODE(*NETATR)
Specifies (in characters) the VTAM identifier of the Cus-
is used.
tomer Information Control System for Virtual Storage
*NETATR: The mode name specified in the network (CICS/VS) or Information Management System/Virtual
attributes is used. Storage (IMS/VS) host subsystem sent with the sign-on
message. This parameter applies to the SNUF commu-
*BLANK: The mode name consisting of 8 blank charac-
nications type only and is ignored for all other devices.
ters is used.
If the ADDICFDEVE command is not run for the speci-
mode-name: Specify a mode name for the APPC com- fied program device and this parameter is not over-
munications device. If the specified mode is not valid for ridden, APPID(*DEVD) is used.
any combination of remote location, device, local
*DEVD: The application identifier specified in the device
description is sent with the sign-on message.
3284: The data stream is for a 3284 Printer. No blocking/deblocking: The record format
described in the DDS is the format for both the
3286: The data stream is for a 3286 Printer.
record and the block.
3287: The data stream is for a 3287 Printer.
User blocking and deblocking: Give the BSC con-
3288: The data stream is for a 3288 Printer. trols needed to describe the record format of the
3289: The data stream is for a 3289 Printer. system.
Element 2: Format of Data Stream System blocking with record separator characters:
Specify the record separator character used by the
*UNFORMAT: An unformatted 3270 data stream is sent
system to determine record boundaries in the block.
or received. The user application program must trans-
late the data stream into a display or printer image. System blocking of fixed-length records: The
system uses fixed-length records, and blocks and
*FIELD: A formatted 3270 data stream is sent or
deblocks records accordingly.
received. The formatted 3270 data stream contains a
display or printer image followed by field definitions. The If a parameter value other than *NONE or *USER is
field definitions indicate the location and characteristics specified, records are blocked as required by the system
of each field. for output and are deblocked on input.
*NOFIELD: A formatted 3270 data stream that has no Element 1: Blocking Option
field definitions but contains a display or printer image is
*DEVD: The block option in the device description is
sent or received.
used.
Note: If *FIELD or *NOFIELD is specified,
*NONE: Blocking or deblocking is not done by the
BATCH(*NO) must also be specified.
system.
*EXTFIELD: A formatted 3270 data stream contains
*ITB: The records are blocked or deblocked, based on
extended field attribute information. The extended field
the location of an Intermediate Text Block (ITB) control
attribute information is in the field definitions which follow
character. For input files, a record is delimited by
the display image. The field definitions indicate the
locating the next intermediate text block character. An
location and characteristics of each field. This value can
end-of-text or end-of-transmission block character is
only be specified if 3278 is also specified for the type of
used as an intermediate text block character to delimit a
device on the EMLDEV parameter.
block. For output files, an ITB character is added after
CNVTYPE the record. If it is the last character of the block, the ITB
Specifies the conversation type for which the application is replaced by an end-of-text or end-of-transmission
program is designed. This parameter is valid only for block character.
the APPC communications type and is ignored for all *IRS: The records are blocked or deblocked based on
other communications types. If the ADDICFDEVE the location of an Interrecord Separator (IRS) character.
command is not run for the specified program device For input files, a record is delimited by locating the next
and this parameter is not overridden, CNVTYPE(*SYS) IRS character. For output files, an IRS character is
is used. added after the record.
More information on the APPC communications type is *NOSEP: No record separator character is contained in
in the APPC Programming book. the block that is sent to or received from the device.
*SYS: The advanced program-to-program communica- The system blocks and deblocks the records using a
tions (APPC) mapped conversation support is used. fixed-length record, as specified in the DDS format spec-
ifications.
*USER: The advanced program-to-program communica-
tions (APPC) basic conversation support is used. *USER: The program provides all the control characters
(including record separator characters, binary synchro-
*SRCPGM: The target program accepts the conversa-
nous communications (BSC) framing characters, and
tion type specified by the source program.
transparency characters) necessary to send records.
BLOCK More information about the device and binary synchro-
Specifies whether the system or the user controls the nous communications equivalence link (BSCEL) support
combination of records into blocks when they are sent. characteristics is in the BSC Equivalence Link Program-
This parameter is for the BSCEL communications type ming book.
only and is ignored for all other communications types. *SEP: Records are blocked or deblocked, based on the
If the ADDICFDEVE command is not run for the speci- location of a user-specified record separator character.
fied program device and this parameter is not over- For input files, a record is delimited by locating the next
ridden, BLOCK(*DEVD) is used. record separator character. For output files, a record
With this parameter, specify one of the following condi- separator character is added after the record.
tions of record blocking: Element 2: Record Separator
X'1E': The record separator X'1E' is used. block-length: Specify the maximum block length (in
bytes) of records sent. The value must be at least the
record-separator-character: Specify a unique 1-byte
size of the largest record sent. Valid values range from
record separator character. The record separator char-
1 through 32767 for SNA upline facility (SNUF). For
acter may be specified as 2 hexadecimal characters, as
binary synchronous communications equivalence link
in BLOCK(*SEP X'FD'), or as a single character, as in
(BSCEL) communications, the maximum block length is
BLOCK(*SEP @). If a record separator character is not
8192.
specified, the record separator character X'1E' is used.
The following is a list of BSC control characters that TRNSPY
should not be used as record separator characters: Specifies whether text is sent in transparent text mode.
Transparent text mode sends all 256 extended binary-
EBCDIC ASCII BSC Control coded decimal interchange code (EBCDIC) character
codes; use this feature when sending packed or binary
X'01' X'01' SOH (start-of-header)
data fields. This parameter is for the BSCEL commu-
X'02' X'02' STX (start-of-text) nications type only and is ignored for all other commu-
X'03' X'03' ETX (end-of-text) nications types. If the ADDICFDEVE command is not
X'10' X'10' DLE (data-link escape) run for the specified program device and this parameter
is not overridden, TRNSPY(*DEVD) is used.
X'1D' X'1D' IGS (interchange group separator)
*DEVD: The text transparency option specified in the
X'1F' X'1F' ITB (intermediate text block)
device description is used.
X'26' X'17' ETB (end-of-transmission block)
*NO: Text transparency is not used.
X'2D' X'05' ENQ (enquiry)
X'32' X'16' SYN (synchronization)
*YES: Text transparency is used, which sends all 256
EBCDIC character codes. *YES is valid only when
X'37' X'04' EOT (end-of-transmission)
BLOCK(*NONE), BLOCK(*NOSEP), or BLOCK(*USER)
X'3D' X'15' NAK (negative acknowledgment) is specified.
Note: Transparency of received data is determined by
RCDLEN the data stream; therefore, this parameter is not
Specifies the maximum record length (in bytes) for data relevant for received data. If TRNSPY(*YES) is
sent and received. This parameter applies to the SNUF specified with BLOCK(*USER), BSCEL ignores
and the BSCEL communications types only and is the transparency indicator during write oper-
ignored for all other communications types. If the ations. Correct controls must be given with the
ADDICFDEVE command is not run for the specified data to get transparent transmission of data. For
program device and this parameter is not overridden, example, first specify the DLE and STX control
RCDLEN(*DEVD) is used. characters; the system gives the remaining
*DEVD: The record length specified in the device control characters for transparent transmission of
description is used. If a record is longer than the speci- data.
fied record length, a run time error occurs at the time the
DTACPR
record is sent or received.
Specifies whether data compression is performed.
record-length: Specify the maximum record length (in
Note: This parameter is for the BSCEL communications
bytes) to use with this device file. The value must be at
type only and is ignored for all other communica-
least the size of the largest record sent. If a record is
tions types. If the ADDICFDEVE command is
longer than the specified record length, a run time error
not run for the specified program device and this
occurs when the record is sent or received. Valid values
parameter is not overridden, DTACPR(*DEVD) is
range from 1 through 32767 bytes for SNUF commu-
used.
nications. For BSCEL communications, the maximum
record length is 8192 bytes. *DEVD: The data compression option specified in the
device description is used.
BLKLEN
Specifies the maximum block length (in bytes) for data *NO: No data compression or decompression occurs.
sent. This parameter applies to the BSCEL and the *YES: Data is compressed for output and decom-
SNUF communications types and is ignored for all other pressed for input. DTACPR(*YES) cannot be specified if
communications types. If the ADDICFDEVE command TRNSPY(*YES) is specified.
is not run for the specified program device and this
parameter is not overridden, this parameter defaults to TRUNC
*DEVD. Specifies whether trailing blanks are removed from any
output records. TRUNC(*YES) cannot be specified if
*DEVD: The block length specified in the device BLOCK(*NOSEP) or BLOCK(*ITB) is specified. If
description is used. TRUNC(*YES) is specified when DTACPR(*YES) or
BLOCK(*USER) is specified, truncation is ignored. This
OVRFLWDTA SECURE
Specifies whether overflow data is discarded or retained. Specifies whether this file is safe from the effects of pre-
*DISCARD: Overflow data is not kept. viously called file override commands. If SECURE is not
specified, processing occurs as if SECURE(*NO) is
*RETAIN: Overflow data is kept. specified.
GRPSEP *NO: This file is not protected from the effects of other
Specifies a separator for groups of data (for example, file overrides; its values can be overridden by the effects
data sets and documents). This parameter is for the of previously called file override commands.
BSCEL communications type only and is ignored for all
*YES: This file is protected from the effects of any file
other communications types. If the ADDICFDEVE
override commands previously called.
command is not run for the specified program device
and this parameter is not overridden, GRPSEP(*DEVD) OVRSCOPE
is used. Specifies the extent of influence (scope) of the override.
*DEVD: The group separator option specified in the *ACTGRPDFN: The scope of the override is determined
device description is used. by the activation group of the program that calls this
command. When the activation group is the default acti-
*EOT: The end-of-transmission (EOT) BSC control
vation group, the scope equals the call level of the
character is used as a data group separator.
calling program. When the activation group is not the
*DEV3740: A null record (STXETX) is used as a data default activation group, the scope equals the activation
group separator. group of the calling program.
*OFCSYS: A block sent with the end-of-text (ETX) BSC *CALLLVL: The scope of the override is determined by
control character is used as a data group separator. the current call level. All open operations done at a call
level that is the same as or higher than the current call
RMTBSCEL
level are influenced by this override.
Specifies whether the type of BSCEL session is with a
BSCEL system. This parameter applies to the BSCEL *JOB: The scope of the override is the job in which the
communications type only and is ignored for all other override occurs.
communications types. If the ADDICFDEVE command
is not run for the specified program device and this
parameter is not overridden, RMTBSCEL(*DEVD) is
Examples
used. Example 1: Overriding the Device Entry with the Record
*DEVD: The RMTBSCEL option specified in the device Format Selection Attributes
description is used. OVRICFDEVE PGMDEV(BSCEL2) RMTLOCNAME(BSCNYC)
*NO: A RMTBSCEL attribute of *NO indicates that the FMTSLT(\RECID)
remote system cannot recognize BSCEL commands or
This command overrides the program device named BSCEL2
messages. In most cases, *NO is used when communi-
with a corresponding remote location named BSCNYC for
cating with remote systems such as a 3741 Data Entry
any ICF file associated with the job. The program device is
Station, an Office System 6, a 5230 Data Collection
overridden with the attributes of FMTSLT(*RECID).
System, or a System/38.
*YES: The remote system recognizes the BSCEL trans- Example 2: Overriding the Device Entry with the Record
action starting commands, transaction ending com- Format Selection and the Conversation Type Attributes
mands, and online messages. In most cases, *YES OVRICFDEVE PGMDEV(APPC1) RMTLOCNAME(\REQUESTER)
indicates that the remote system is another AS/400 FMTSLT(\RMTFMT) CNVTYPE(\SYS)
system, System/38, System/36, or a System/34 with
BSCEL support. This command overrides the program device entry named
APPC1 with a remote location name of *REQUESTER. The
program device entry is overridden with the Example 4: Specifying the Communications Device
FMTSLT(*RMTFMT) and CNVTYPE(*SYS) attributes. OVRICFDEVE PGMDEV(APPC) RMTLOCNAME(APPCMPLS)
DEV(MPLSLINE2)
Example 3: Overriding an Entry for Associated ICF Files
OVRICFDEVE PGMDEV(JOE) RMTLOCNAME(LUðMPLS) This command overrides the program device entry named
APPC with a remote location named APPCMPLS using
This command overrides the program device entry named device MPLSLINE2.
JOE with a remote location named LU0MPLS for any ICF file
associated with the job.
55──OVRICFF──FILE(──overridden-file-name──)──┬──────────────────────────────────────────────┬───────────────────────────────────5
│ ┌─\FILE────────────────────────┐ │
│ │ ┌─\LIBL/────────┐ │ │
└─TOFILE(──┴─┼───────────────┼──file-name─┴──)─┘
├─\CURLIB/──────┤
└─library-name/─┘
(P) ──┬──────────────────────────────────┬──────────────────────────────────────────5
5──┬────────────────────────────────────────┬───
└─ACQPGMDEV(──┬─\NONE───────────────┬──)─┘ └─MAXRCDLEN(──┬─\CALC─────────┬──)─┘
└─program-device-name─┘ └─record-length─┘
5──┬─────────────────────────────────────┬──┬────────────────────────────────────┬──┬─────────────────┬─────────────────────────5
└─WAITFILE(──┬─\IMMED────────────┬──)─┘ └─WAITRCD(──┬─\NOMAX────────────┬──)─┘ └─LVLCHK(──\NO──)─┘
├─\CLS──────────────┤ ├─\IMMED────────────┤
└─number-of-seconds─┘ └─number-of-seconds─┘
5──┬──────────────────────┬──┬──────────────────────────────┬──┬──────────────────────────────────────────────────┬─────────────5
│ ┌─\NO──┐ │ │ ┌─\ACTGRPDFN─┐ │ └─DTAQ(──┬─\NONE──────────────────────────────┬──)─┘
└─SECURE(──┴─\YES─┴──)─┘ └─OVRSCOPE(──┼─\CALLLVL───┼──)─┘ │ ┌─\LIBL/────────┐ │
└─\JOB───────┘ └─┼───────────────┼──data-queue-name─┘
├─\CURLIB/──────┤
└─library-name/─┘
5──┬─────────────────────┬──┬──────────────────────────────┬───────────────────────────────────────────────────────────────────5%
└─SHARE(──┬─\NO──┬──)─┘ └─OPNSCOPE(──┬─\ACTGRPDFN─┬──)─┘
└─\YES─┘ └─\JOB───────┘
Note:
P All parameters preceding this point can be specified in positional form.
library-name: Specify the name of the library to be *CLS: The job default wait time is used as the wait time
searched. for the file resources being allocated.
file-name: Specify the qualified name of the physical file number-of-seconds: Specify the number of seconds that
or device file that receives the copied records. If no the program waits for the file resources to be allocated
library qualifier is specified, *LIBL is used to locate the to the ICF file when the file is opened, or the wait time
file. However, if CRTFILE(*YES) is specified and the for the device allocated when an acquire operation is
specified file cannot be found, the file name must be performed to the file. Valid values range from 1 through
qualified with a library name. When the physical to-file 32767 seconds.
is created, it is placed in the specified library.
WAITRCD
ACQPGMDEV Specifies the number of seconds the program waits for
Specifies which program device is acquired to the file the completion of a read-from-invited-device operation to
when the file is opened. This parameter overrides the a multiple device file in a high-level language program.
value in the ICF file, in the program, or in the other Refer to the appropriate high-level language reference
OVRICFF commands run later. manual to determine when a file is treated as a multiple
device file. The program performing the read operation
*NONE: The file is opened without any devices
waits for input from all invited devices currently
acquired. All devices used with this file must be explic-
accessing the file. If a record is not returned from an
itly acquired before input/output is directed to them.
invited device in the specified amount of time, a notify
program-device-name: Specify the name of the program message is sent to the program. This parameter has no
device that is acquired when the file is opened. The effect on an input operation directed to a specific device.
name should be specified on the Add Intersystem Com-
Note: This parameter is also used to specify the time
munications Function Program Device Entry
(seconds) that a CL program waits to complete a
(ADDICFDEVE) command or the Override Intersystem
WAIT command. If a record is not returned from
Communications Function Program Device Entry
any of the devices that should return a record, an
(OVRICFDEVE) command as a program-device-name
escape message is sent to the CL program.
before the file is opened.
More information on the WAITRCD parameter is
MAXRCDLEN in the Receive File (RCVF), Send File (SNDF),
Specifies the maximum record length used when the file Send/Receive File (SNDRCVF), and WAIT (Wait)
is opened. This parameter overrides the value in the command descriptions.
ICF file, in the program, or in the other OVRICFF com- This parameter overrides the wait record value specified
mands run later. in the device file, in the program, or in other override
*CALC: The value calculated in the file is used when commands started later.
the file is opened. *NOMAX: There is no limit on the time the system waits
record-length: Specify the maximum record length (in for the completion of the operation.
bytes) used when the file is opened. Valid values range *IMMED: The program does not wait for the read-from-
from 1 through 32767. invited-device operation for the completion of the file. A
WAITFILE record must be available from an invited program device
Specifies the number of seconds that the program waits when the read-from-invited-program-device operation is
for the file resources and session resources to be allo- performed. If a record is not already available when the
read-from-invited-program-device operation is performed,
cated when the file is opened, or for the device or
session resources to be allocated when an acquire oper- a notify message is sent to the program.
ation is performed to the file. If those resources are not number-of-seconds: Specify the number of seconds that
allocated within the specified wait time, an error the program waits for the completion of the read-from-
message is sent to the program. More information on invited-device operation. Valid values range from 1
this parameter is in Appendix A, “Expanded Parameter through 32767.
Descriptions.”
LVLCHK
Note: An immediate allocation of the device by the Specifies whether the record format level identifiers in
device resource is required when an acquire the program are checked against those in the device file
operation is performed to the file. when the file is opened. If so, the record format identi-
This parameter overrides the wait time specified in the fiers in the program must match those in the device file.
device file, in the program, or in other OVRICFF com- Because the same record format name can exist in more
mands run later. than one file, each record format is given an internal
system identifier when it is created.
*IMMED: The program does not wait; when the file is
opened, an immediate allocation of the file resources is Note: This parameter overrides the value specified in
required. the device file, in the program, or in other over-
ride commands run later. Level checking cannot
be done unless the program contains the record *CURLIB: The current library for the job is
format identifiers. This command cannot over- searched. If no library is specified as the current
ride level checking from *NO to *YES. library for the job, the QGPL library is used.
*NO: The level identifiers of the record formats are not library-name: Specify the name of the library to be
checked when the file is opened. searched.
*LIBL: All libraries in the job's library list are This command overrides the file named ICFHIST to the ICF
searched until the first match is found. file named ICFCURT in library PRSNNL.
┌─\LIBL/────────┐
(P) ───────────────────────5
55──OVRMSGF──MSGF(──overridden-message-file-name──)──TOMSGF(──┼───────────────┼──message-file-name──)────
├─\CURLIB/──────┤
└─library-name/─┘
5──┬──────────────────────┬────────────────────────────────────────────────────────────────────────────────────────────────────5%
│ ┌─\NO──┐ │
└─SECURE(──┴─\YES─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
55──OVRPRTF──FILE(──┬─\PRTF──────────────┬──)──┬─────────────────────────────────────────────────────────────┬──────────────────5
└─file-override-name─┘ │ ┌─\FILE───────────────────────────────────────┐ │
│ │ ┌─\LIBL/────────┐ │ │
└─TOFILE(──┴─┼───────────────┼──printer-device-file-name─┴──)─┘
├─\CURLIB/──────┤
└─library-name/─┘
(P) ──┬─────────────────────────────┬─────────────────────────────────────────────────────────────5
5──┬──────────────────────────┬───
└─DEV(──┬─\SYSVAL─────┬──)─┘ └─DEVTYPE(──┬─\SCS───────┬──)─┘
├─\JOB────────┤ ├─\IPDS──────┤
└─device-name─┘ ├─\USERASCII─┤
├─\AFPDS─────┤
├─\AFPDSLINE─┤
└─\LINE──────┘
5──┬────────────────────────────────────────────────────────┬──┬──────────────────┬──┬───────────────────┬──────────────────────5
└─PAGESIZE(──page-length──┬─────────────────────────┬──)─┘ └─LPI(──┬─3───┬──)─┘ └─CPI(──┬─5────┬──)─┘
│ ┌─\ROWCOL─┐ │ ├─4───┤ ├─1ð───┤
└─page-width──┼─────────┼─┘ ├─6───┤ ├─12───┤
└─\UOM────┘ ├─7.5─┤ ├─13.3─┤
├─8───┤ ├─15───┤
├─9───┤ ├─16.7─┤
└─12──┘ ├─18───┤
└─2ð───┘
5──┬──────────────────────────────────────────────────────┬──┬─────────────────────────────────────────────────────┬────────────5
└─FRONTMGN(──┬─\DEVD──────────────────────────────┬──)─┘ └─BACKMGN(──┬─\FRONTMGN──────────────────────────┬──)─┘
└─┬─ð───────────┬──┬─ð─────────────┬─┘ ├─\DEVD──────────────────────────────┤
└─offset-down─┘ └─offset-across─┘ └─┬─ð───────────┬──┬─ð─────────────┬─┘
└─offset-down─┘ └─offset-across─┘
5──┬──────────────────────────────────┬──┬────────────────────┬──┬─────────────────────────────────────────────────────┬────────5
└─OVRFLW(──overflow-line-number──)─┘ └─FOLD(──┬─\YES─┬──)─┘ │ ┌─' '─────────────────────┐ │
└─\NO──┘ └─RPLUNPRT(──┬─\YES──┼─────────────────────────┼─┬──)─┘
│ └─'replacement-character'─┘ │
└─\NO───────────────────────────────┘
5──┬─────────────────────┬──┬──────────────────────────────┬──┬───────────────────────────┬─────────────────────────────────────5
└─ALIGN(──┬─\NO──┬──)─┘ └─DRAWER──┬─\E1───────────┬──)─┘ └─OUTBIN──┬─\DEVD──────┬──)─┘
└─\YES─┘ ├─\FORMDF───────┤ └─output-bin─┘
└─source-drawer─┘
5──┬──────────────────────────────────────────┬──┬────────────────────────────┬──┬─────────────────────────────┬────────────────5
└─FONT(──┬─\CPI───────────────────────┬──)─┘ └─FORMFEED(──┬─\DEVD────┬──)─┘ └─PRTQLTY(──┬─\STD───────┬──)─┘
├─\DEVD──────────────────────┤ ├─\AUTOCUT─┤ ├─\DRAFT─────┤
│ ┌─\NONE──────┐ │ ├─\CONT────┤ ├─\DEVD──────┤
└─identifier──┼────────────┼─┘ ├─\CONT2───┤ ├─\NLQ───────┤
└─point-size─┘ └─\CUT─────┘ └─\FASTDRAFT─┘
5──┬───────────────────────────┬──┬───────────────────────────────────────────────┬──┬────────────────────────────┬─────────────5
(1) ┘ └─FIDELITY──┬─\CONTENT──┬──)─┘
└─CTLCHAR(──┬─\NONE────┬──)─┘ └─CHLVAL(──┬─\NORMAL─────────────────────┬──)───
├─\FCFC────┤ └─channel-number──line-number─┘ └─\ABSOLUTE─┘
└─\MACHINE─┘
5──┬─────────────────────────────────────────────────┬──┬───────────────────────┬───────────────────────────────────────────────5
| └─CHRID(──┬─\DEVD────────────────────────────┬──)─┘ └─DECFMT(──┬─\FILE─┬──)─┘
| ├─\SYSVAL──────────────────────────┤ └─\JOB──┘
├─\JOBCCSID────────────────────────┤
└─graphic-character-set──code-page─┘
5──┬───────────────────────────────────────────────────────────────────────────────────────────────────┬────────────────────────5
└─FNTCHRSET(──┬─\FONT──────────────────────────────────────────────────────────────────────────┬──)─┘
| │ ┌─\LIBL/────────┐ ┌─\LIBL/────────┐ ┌─\NONE──────┐ │
| └─┼─\CURLIB/──────┼──character-set──┼─\CURLIB/──────┼──code-page──┴─point-size─┴─┘
└─library-name/─┘ └─library-name/─┘
5──┬────────────────────────────────────────────────────────────────────┬───────────────────────────────────────────────────────5
└─CDEFNT(──┬─\FNTCHRSET─────────────────────────────────────────┬──)─┘
| │ ┌─\LIBL/────────┐ ┌─\NONE──────┐ │
| └─┼─\CURLIB/──────┼──coded-font-name──┴─point-size─┴─┘
└─library-name/─┘
5──┬─────────────────────────────────────────────────────────┬──┬─────────────────────────────────────────────────────────┬─────5
│ ┌─\NONE───────────────────────────────────┐ │ │ ┌─\NONE───────────────────────────────────┐ │
│ │ ┌─\LIBL/────────┐ │ │ └─FORMDF(──┼─\DEVD───────────────────────────────────┼──)─┘
└─PAGDFN(──┴─┼───────────────┼──page-definition-name─┴──)─┘ │ ┌─\LIBL/────────┐ │
├─\CURLIB/──────┤ └─┼───────────────┼──form-definition-name─┘
└─library-name/─┘ ├─\CURLIB/──────┤
└─library-name/─┘
5──┬──────────────────────────────────────────┬──┬─────────────────────────┬──┬───────────────────────┬─────────────────────────5
│ ┌─\NONE──────────────────┐ │ │ ┌─\NO──┐ │ └─PAGRTT(──┬─\AUTO─┬──)─┘
│ │ ┌──
─────────────────┐ │ │ └─TBLREFCHR(──┴─\YES─┴──)─┘ ├─\DEVD─┤
6 (3) ─┴──)─┘
└─AFPCHARS(──┴───coded-font-name─┴─── ├─\COR──┤
├─ð─────┤
├─9ð────┤
├─18ð───┤
└─27ð───┘
5──┬────────────────────┬──┬───────────────────────┬──┬──────────────────────────────┬──┬──────────────────────┬────────────────5
└─MULTIUP(──┬─1─┬──)─┘ └─REDUCE(──┬─\TEXT─┬──)─┘ └─PRTTXT(──┬─\JOB─────────┬──)─┘ └─JUSTIFY(──┬─ð───┬──)─┘
├─2─┤ └─\NONE─┘ ├─\BLANK───────┤ ├─5ð──┤
├─3─┤ └─'print-text'─┘ └─1ðð─┘
└─4─┘
5──┬─────────────────────────┬──┬────────────────────┬──────────────────────────────────────────────────────────────────────────5
└─DUPLEX(──┬─\NO─────┬──)─┘ └─UOM(──┬─\INCH─┬──)─┘
├─\YES────┤ └─\CM───┘
├─\TUMBLE─┤
└─\FORMDF─┘
5──┬──────────────────────────────────────────────────────────────────────────────────────┬─────────────────────────────────────5
│ ┌─\NONE──────────────────────────────────────────────────────────────┐ │
│ │ ┌─\LIBL/────────┐ │ │
└─FRONTOVL(──┴─┼───────────────┼──overlay──┬────────────────────────────────────┬─┴──)─┘
├─\CURLIB/──────┤ │ ┌─ð───────────┐ ┌─ð─────────────┐ │
└─library-name/─┘ └─┴─offset-down─┴──┼───────────────┼─┘
└─offset-across─┘
5──┬─────────────────────────────────────────────────────────────────────────────────────┬──┬──────────────────────┬────────────5
│ ┌─\FRONTOVL──────────────────────────────────────────────────────────┐ │ └─DFRWRT(──┬─\YES─┬──)─┘
└─BACKOVL(──┼─\NONE──────────────────────────────────────────────────────────────┼──)─┘ └─\NO──┘
│ ┌─\LIBL/────────┐ │
└─┼───────────────┼──overlay──┬────────────────────────────────────┬─┘
├─\CURLIB/──────┤ │ ┌─ð───────────┐ ┌─ð─────────────┐ │
└─library-name/─┘ └─┴─offset-down─┴──┼───────────────┼─┘
└─offset-across─┘
5──┬─────────────────────┬──┬────────────────────────────────────────────────────┬──┬─────────────────────────────┬─────────────5
└─SPOOL(──┬─\YES─┬──)─┘ └─OUTQ(──┬─\DEV─────────────────────────────────┬──)─┘ └─FORMTYPE(──┬─\STD──────┬──)─┘
└─\NO──┘ ├─\JOB─────────────────────────────────┤ └─form-type─┘
│ ┌─\LIBL/────────┐ │
└─┼───────────────┼──output-queue-name─┘
├─\CURLIB/──────┤
└─library-name/─┘
5──┬────────────────────────────────┬──┬───────────────────────────────────────────────────┬────────────────────────────────────5
(2) ┘ └─PAGERANGE(──┬─\ENDPAGE──────┬──┬─────────────┬──)─┘
└─COPIES(──number-of-copies──)───
└─starting-page─┘ ├─\END────────┤
└─ending-page─┘
5──┬──────────────────────────────────┬──┬────────────────────────────────────────┬──┬────────────────────────────┬─────────────5
└─MAXRCDS(──┬─\NOMAX──────────┬──)─┘ └─FILESEP(──number-of-file-separators──)─┘ └─SCHEDULE(──┬─\JOBEND──┬──)─┘
└─maximum-records─┘ ├─\FILEEND─┤
└─\IMMED───┘
5──┬────────────────────┬──┬────────────────────┬──┬─────────────────────────────────┬──┬───────────────────────────┬───────────5
└─HOLD(──┬─\NO──┬──)─┘ └─SAVE(──┬─\NO──┬──)─┘ └─OUTPTY(──┬─\JOB────────────┬──)─┘ └─USRDTA(──┬─\SOURCE───┬──)─┘
└─\YES─┘ └─\YES─┘ └─output-priority─┘ └─user-data─┘
5──┬──────────────────────────────┬──┬──────────────────────────────────┬──┬──────────────────────────────────────┬─────────────5
└─SPLFOWN(──┬─\CURUSRPRF─┬── )─┘ └─USRDFNOPT(──┬─\NONE─────────┬──)─┘ └─USRDFNDTA(──┬─\NONE─────────────┬──)─┘
├─\JOB───────┤ │ ┌──
────────┐ │ └─user-defined-data─┘
├─\CURGRPPRF─┤ └──6─option─┴───
(3) ─┘
└─\JOBGRPPRF─┘
5──┬────────────────────────────────────────────────────────────────┬──┬─────────────────────────────────────┬──────────────────5
└─USRDFNOBJ(──┬─\NONE───────────────────────────────────────┬──)─┘ └─SPLFNAME(──┬─\FILE─────────────┬──)─┘
│ ┌─\LIBL/────────┐ │ └─spooled-file-name─┘
└─┼───────────────┼──object-name──┬─\DTAARA─┬─┘
├─\CURLIB/──────┤ ├─\DTAQ───┤
└─library-name/─┘ ├─\FILE───┤
├─\PSFCFG─┤
├─\USRIDX─┤
├─\USRQ───┤
└─\USRSPC─┘
5──┬─────────────────────────────────────┬──┬─────────────────┬──┬──────────────────────┬──┬──────────────────────────────┬─────5
└─WAITFILE(──┬─\IMMED────────────┬──)─┘ └─LVLCHK(──\NO──)─┘ │ ┌─\NO──┐ │ │ ┌─\ACTGRPDFN─┐ │
├─\CLS──────────────┤ └─SECURE(──┴─\YES─┴──)─┘ └─OVRSCOPE(──┼─\CALLLVL───┼──)─┘
└─number-of-seconds─┘ └─\JOB───────┘
5──┬─────────────────────┬──┬──────────────────────────────┬──┬──────────────────────┬──┬─────────────────────────┬─────────────5
└─SHARE(──┬─\NO──┬──)─┘ └─OPNSCOPE(──┬─\ACTGRPDFN─┬──)─┘ └─IGCDTA(──┬─\NO──┬──)─┘ └─IGCEXNCHR(──┬─\YES─┬──)─┘
└─\YES─┘ └─\JOB───────┘ └─\YES─┘ └─\NO──┘
5──┬─────────────────────────┬──┬────────────────────────────┬──┬─────────────────────────┬─────────────────────────────────────5
└─IGCCHRRTT(──┬─\NO──┬──)─┘ └─IGCCPI(──┬─\CPI───────┬──)─┘ └─IGCSOSI(──┬─\YES───┬──)─┘
└─\YES─┘ ├─\CONDENSED─┤ ├─\NO────┤
├─5──────────┤ └─\RIGHT─┘
├─6──────────┤
└─1ð─────────┘
5──┬───────────────────────────────────────────────────────────────────┬───────────────────────────────────────────────────────5%
└─IGCCDEFNT(──┬─\SYSVAL────────────────────────────────────────┬──)─┘
| │ ┌─\LIBL/────┐ ┌─\NONE──────┐ │
| └─┼─\CURLIB/──┼──coded-font-name──┴─point-size─┴─┘
└─lib-name/─┘
Notes:
1 A maximum of 12 channels with corresponding line numbers are allowed.
3 A maximum of 4 repetitions.
When using the 5553 and 5583 DBCS-capable printers, This parameter overrides the form size values specified
DEVTYPE(*SCS) must be specified. in the printer file, in the program, or in other called
OVRPRTF commands.
*IPDS: An intelligent printer data stream* (IPDS*) is
created. This parameter can be specified when using an Element 1: Page Length Value
IPDS printer. page-length: Specify the page length that is used by
this printer file. Although a value ranging from 1 through
If *IPDS is specified and the spooled printer file is
255 can be specified as the page length, the value spec-
directed to a printer other than an IPDS printer, the
ified must not exceed the actual length of the forms
IPDS printer file is converted to an SCS printer file.
used.
More information is in the Printer Device Program-
ming book. More information about the page lengths that are valid
for each printer type is in Appendix B, “Font, Character
*USERASCII: An ASCII data stream is placed on a Identifier, and Other Values Supported for Different
spooled output queue. The user is responsible for Printers.”
placing the entire hexadecimal data stream in the buffer,
Element 2: Page Width Value
since the AS/400 system does not change or validate
the values that are passed. This value cannot be speci- page-width: Specify the page width used by this printer
fied with SPOOL(*NO). file. The value specified must not exceed the actual
width of the forms used.
*AFPDS: An advanced function print data stream
(AFPDS) is created. Some systems refer to this data More information about page width is in Appendix B,
stream as MODCA-P. “Font, Character Identifier, and Other Values Supported
for Different Printers.”
*AFPDSLINE: Mixed data (line data and AFPDS data)
is created. This value can be specified when using the Element 3: Method of Measure
3812 IPDS, 3816 IPDS, 3820, 3825, 3827, 3828, 3829,
*ROWCOL: Page length and page width are measured
3831, 3835, 3900, 3912, 3916, 3930, 3935, 4028, 4224,
as numbers of rows and columns.
4230, 4234, 6404, 6408, or 6412 IPDS* printer. The
printer must be configured with AFP(*YES). *UOM: Page length and page width are measured in
the units specified on the UOM parameter.
*LINE: Line data is created. This value can be speci-
fied when using the 3812 IPDS, 3816 IPDS, 3820, 3825, LPI
3827, 3828, 3829, 3831, 3835, 3900, 3912, 3916, 3930, Specifies the line spacing setting on the printer, in lines
3925, 4028, 4224, 4230, 4234, 6406, 6408, or 6412 per inch, used by this printer file.
IPDS printers. The printer must be configured with
The line spacing on the 5256 printer must be set manu-
AFP(*YES).
ally. When the lines per inch (LPI) value on this param-
eter changes (from the value on the previous printer file),
an inquiry message is sent to the message queue asso-
ciated with the printer that requests a change to the LPI in Appendix B, “Font, Character Identifier, and Other
value. Values Supported for Different Printers.”
The line spacing on the 4214, 4224, 4230, 4234, 4245, This parameter overrides the value specified in the
and 5262 Printers is set by a print command. These printer file, in the program, or in other called OVRPRTF
also allow setting the lines per inch spacing on the commands.
control panel of the printer. The lines per inch value
5: Double-byte character density is 5 characters per
must not be set at the printer. If the LPI value is over-
inch.
ridden at the control panel, the system overrides the
value set with the LPI value of the next printer file 10: Character density is 10 characters per inch.
received. 12: Character density is 12 characters per inch.
More information about the lines per page and lines per 13.3: Character density is 13.3 characters per inch.
inch that are valid for each printer type is in Appendix B, This value is valid only for double-byte character set
“Font, Character Identifier, and Other Values Supported (DBCS) printers.
for Different Printers.”
15: Character density is 15 characters per inch.
This parameter overrides the overflow value specified in
the printer file, in the program, or in other called 16.7: Character density is 16.7 characters per inch.
OVRPRTF commands. 18: Character density is 18 characters per inch. This
3: The line spacing on the printer is 3 lines per inch. value is valid only on double-byte character set (DBCS)
This value is valid only for double-byte character set printers.
(DBCS) data. 20: Character density is 20 characters per inch. This
4: The line spacing on the printer is 4 lines per inch. value is valid only on double-byte character set (DBCS)
printers.
6: The line spacing on the printer is 6 lines per inch.
FRONTMGN
7.5: The line spacing on the printer is 7.5 lines per inch.
Specifies the offset, down and across, of the origin from
This value is valid only for double-byte character set
the edge on the front side of the paper. The offsets are
(DBCS) printers.
in the units of measure specified on the UOM parameter.
8: The line spacing on the printer is 8 lines per inch. If UOM(*CM) is specified, valid values range from 0
Note: When printing double-byte character set (DBCS) through 57.79, and if UOM(*INCH) is specified, valid
data for a file specified with LPI(8), use double values range from 0 through 22.57. This parameter can
spacing. Otherwise, the DBCS data does not only be used for printer files with DEVTYPE(*AFPDS)
print correctly. Alphanumeric data, however, specified.
prints correctly in single spacing when LPI(8) is *DEVD: The no-print border from the printer is used to
specified. place the text on the page when printing to a printer con-
9: The line spacing on the printer is 9 lines per inch. figured as AFP(*YES). A margin of 0 is used for IPDS*
printers without a no-print border, or which are config-
12: The line spacing on the printer is 12 lines per inch. ured as AFP(*NO).
CPI Element 1: Offset Down
Specifies the printer character density, in characters per
0: No offset of the origin occurs.
inch (CPI), used by this printer file.
offset-down: Specify the offset of the origin from the top
For the printers that support fonts, the value specified in of the page.
the font special value implies the CPI. If FONT(*CPI) is
specified, the font used is based on the CPI value. The Element 2: Offset Across
following diagram describes the default font ID for each 0: No offset of the origin occurs.
CPI value:
offset-across: Specify the offset of the origin from the
CPI FONT ID DEFAULT left side of the page.
5 245 BACKMGN
10 011 Specifies the offset, down and across, of the origin from
12 087 the edge on the back side of the paper. The offsets are
13.3 204 in the units of measure specified on the UOM parameter.
15 222 If UOM(*CM) is specified, valid values range from 0
16.7 400 through 57.79, and if UOM(*INCH) is specified, valid
18 252 values range from 0 through 22.57. This parameter can
20 281 only be used for printer files with DEVTYPE(*AFPDS)
specified.
More information about the characters per page and
characters per inch that are valid for each printer type is
*FRONTMGN: The offsets specified on the *YES: Records whose length exceeds the page width
FRONTMGN parameter are used. are folded on the following lines. Records whose length
exceeds the form width are folded on the following lines.
*DEVD: The no-print border from the printer is used to
place the text on the page when printing to a printer con- *NO: Records are not folded; if a record is longer than
figured as AFP(*YES). A margin of 0 is used for IPDS* the page width, only the part of the record that fits on
printers without a no-print border, or which are config- one line is printed.
ured as AFP(*NO).
RPLUNPRT
Element 1: Offset Down Specifies (1) whether unprintable characters are
0: No offset of the origin occurs. replaced and (2) which substitution character (if any) is
used. An unprintable character is a character the printer
offset-down: Specify the offset of the origin from the top is unable to print.
of the page.
Double-Byte Character Set Considerations:
Element 2: Offset Across
For double-byte character set (DBCS) data, an unprint-
0: No offset of the origin occurs.
able character is one that cannot be processed. When
offset-across: Specify the offset of the origin from the using DBCS-capable printers, consider the following:
left side of the page.
If IGCEXNCHR(*YES) is also specified, the system
OVRFLW replaces unprintable extension characters with
Specifies the line number on the current page at which DBCS underline characters. There may be some
overflow to a new page begins. Generally, after the cases in which the system is unable to replace an
specified line is printed, the printer overflows to the next unprintable character with a DBCS underline char-
page before printing continues. Margins specified for the acter. In this case, the undefined character is
printer file are ignored when determining overflow. More printed.
information is in the Printer Device Programming book.
If IGCEXNCHR(*NO) is also specified, the device
This parameter overrides the overflow value specified in
replaces all extension characters with the undefined
the printer file, in the program, or in other called
character. Choosing a blank as the replacement
OVRPRTF commands.
character for alphanumeric characters might
overflow-line-number: Specify the line number on the improve system performance.
current page at which overflow to a new page begins,
More information is in the Printer Device Programming
whether or not printing has occurred on that line. The
book.
value specified must not be greater than the page length
(PAGESIZE). Margins specified for the printer file are Element 1: Replace Character
ignored when determining overflow.
*YES: Unprintable characters are replaced. The
FOLD program is not notified when unprintable characters are
Specifies whether all positions in a record are printed detected. Note the DBCS considerations above.
when the record length exceeds the page width (speci- *NO: Unprintable characters are not replaced. When
fied by the PAGESIZE parameter). When folding is an unprintable character is detected, a message is sent
specified and a record exceeds the page width, any to the program.
portion of the record that cannot be printed on the first
line continues (is folded) on the next line or lines until Element 2: Replacement Character
the entire record has been printed. ' ': Specify, if *YES is also specified on this parameter,
that a blank is used as the substitution character when
The FOLD parameter is ignored under the following con-
an unprintable character is detected.
ditions:
'replacement-character': Specify, if *YES is also speci-
When DEVTYPE(*SCS) is not specified.
fied on this parameter, the replacement character that is
When printing through OfficeVision*.
used each time an unprintable character is detected.
When in the S/36 execution environment.
Any printable EBCDIC character can be specified. Valid
Double-Byte Character Set Considerations: values range from 40 through 99 and A1 through FE.
is specified on the STRPRTWTR command, then this *NONE: The point size is supplied by the system and is
parameter is used to determine whether an alignment determined by the specified font identifier.
message is sent by the system.
point-size: Specify a point size ranging from 0.1 through
This parameter is ignored when cut sheets are used 999.9.
(spooled and direct output). Page alignment can be
FORMFEED
done only for text-only files. Page alignment cannot be
Specifies the form feed attachment used by this printer
done for print jobs containing graphics or bar codes.
device file.
This parameter overrides the alignment value specified
*DEVD: The forms are fed into the printer in the manner
in the printer file, in the program, or in other called
specified in the device description.
OVRPRTF commands.
*CONT: Continuous forms are used by the printer. The
*NO: No page alignment is required.
tractor feed attachment must be on the device.
*YES: The page is aligned before the output is printed.
*CONT2: Continuous forms are used by the printer.
DRAWER The form is fed from the secondary tractor feed attach-
Specifies the source drawer used when single-cut sheets ment. The secondary tractor feed attachment must be
are fed into the printer (specified by on the printer device.
FORMFEED(*AUTOCUT)).
*CUT: Single-cut sheets are used by the printer. Each
*E1: The envelopes are fed from the envelope drawer sheet must be manually loaded. For cut sheets, the
on the sheet-feed paper handler. forms alignment message is not sent.
*FORMDF: The paper is fed from the source drawer *AUTOCUT: The sheet-feed attachment must be on the
specified in the form definition. If a form definition is not printer. Single-cut sheets are automatically fed into the
specified, then source drawer 1 is used. printer. The forms alignment message is not sent for cut
source-drawer: Specify the drawer from which the paper sheets.
is fed. Valid values range from 1 through 255. PRTQLTY
OUTBIN Specifies, for the 3812 SCS, 3816 SCS, 4214, 4224,
Specifies the destination of the output on printers 4230, 4234, and 5219 printers, the quality of print
capable of multiple output bins. produced.
*DEVD: The destination of the output is the device For the 5219 Printer, different print qualities are
default output bin. produced by varying the speed at which the print ribbon
advances. Quality mode (*STD or *NLQ) results in
output-bin: Specify the output bin for the destination of normal print ribbon advancement. In draft mode
the output. Valid values range from 1 through 65535. (*DRAFT), the ribbon advances at a rate of one-third the
FONT distance it advances in quality mode. The 5219 Printer
Specifies the font identifier and point size used with this has a conserve ribbon switch that overrides the value of
printer device file. If a font identifier or point size is not *DRAFT specified by this parameter.
specified, the system automatically sets them. For the 3812 SCS and 3816 SCS Printers, the automatic
More information about the valid font identifiers, the hardware selection of computer output reduction printing
display value, the characters per inch value implied with selected through soft switches on the printers occurs
each font style, a description of each font style, and only when *DRAFT is specified for PRTQLTY and
whether the font is supported on a particular printer is in PAGRTT is *DEVD. If PAGRTT(*COR) is specified, the
Appendix B, “Font, Character Identifier, and Other PRTQLTY parameter does not affect the printed output.
Values Supported for Different Printers.” For the 4224, 4230, and 4234 Printers, standard print
Note: Some fonts can be substituted by the printer. quality is produced by varying the density of the dot
Consult the various printer reference guides for matrix pattern used to create printable characters.
details. Standard mode (*STD) is the normal mode. Quality
mode (*NLQ) requires multiple passes by the printer to
*CPI: The identifier of the font with the specified pitch produce a line of data. Draft mode (*DRAFT) results in
(characters per inch (CPI)) is used. high-speed printing.
*DEVD: The font identifier and point size specified in For the 4214 printer, only draft (*DRAFT), quality
the device description are used. (*NLQ), and device default (*DEVD) modes are sup-
Element 1: Font Identifier ported. Other values are set to quality (*NLQ) mode.
identifier: Specify the numeric font identifier associated More information about the valid values for the 4214,
with this printer. 4224, 4230, 4234, and 5219 Printers is in Appendix B,
“Font, Character Identifier, and Other Values Supported
Element 2: Point Size
for Different Printers.”
Notes: CHLVAL
Specifies a list of channel numbers with their assigned
1. For the 4214 Printer, quality mode (*STD or *NLQ)
line numbers. Use this parameter only if
is only supported for 10 and 12 characters per inch.
CTLCHAR(*FCFC) has been specified.
If PRTQLTY(*STD or *NLQ) and 5, 15, or 16.7 char-
acters per inch is specified, the data is printed in Note: If one or more channel-number/line-number com-
draft mode. binations are changed, all other combinations
must be re-entered.
2. For the 4234 Printer, only a limited character set (62
characters) is supported when PRTQLTY(*DRAFT) *NORMAL: The default values for skipping to channel
is specified. A description of the character set sup- identifiers are used. The default values are found in the
ported with draft print quality is in the 4234 Printer following table.
Operator's Guide.
3. For the 4224 and 4230 printers, the fonts supported Code Action before Printing a Line
are not available for all three print qualities. The
OCR-A and OCR-B fonts are supported only with '' Space one line (blank code)
PRTQLTY(*NLQ). The Courier and Essay fonts are 0 Space two lines
available only with PRTQLTY(*NLQ) and - Space three lines
PRTQLTY(*STD). The Gothic font is available only
+ Suppress space
with PRTQLTY(*DRAFT) or
PRTQLTY(*FASTDRAFT). If there is a mismatch 1 Skip to line 1
between the print quality and the font selected, the 2-11 Space one line
font is changed to match the print quality.
12 Skip to overflow line (OVRFLW parameter)
4. Specify PAGRTT(*DEVD) and PRTQLTY(*DRAFT)
on this command to enable automatic rotation if the
data does not fit on the paper.
Figure 3. ANSI First-Character Forms-Control Codes
*STD: The output is printed with standard quality.
Element 1: Channel Number
*DRAFT: The output is printed with draft quality.
channel-number: Specify an American National
*DEVD: The print quality is set on the printer by the Standard channel number to be associated with a corre-
user, if it is not set within the data stream. sponding 'skip to' line number. Valid values for this
*NLQ: The output is printed with near letter quality. parameter range from 1 through 12, corresponding to
channels 1 through 12. The CHLVAL parameter associ-
*FASTDRAFT: The output is printed at a higher speed
ates the channel number with a page line number. For
and with lower quality than it would be if you specified
example, if you specify CHLVAL(2 20), channel identifier
*DRAFT. This value is only supported by the 4230
2 is allocated with line number 20; therefore, if you place
printer.
the forms-control 2 in the first position of a record, the
CTLCHAR printer skips to line 20 before printing the line.
Specifies whether the printer file supports input with print Note: If the printer stops and the next record processed
control characters. Any invalid control characters that has a channel value forms-control number that is
are found are ignored, and single spacing is assumed. the same value as the line number the printer is
*NONE: No print control characters are passed in the on, the printer advances to that value (line
data being printed. number) on the next page. However, if the
printer is positioned at the top of the page (line
*FCFC: The first character of every record contains an
number one) and the channel value forms-control
American National Standards Institute (ANSI) forms
value is associated with line number one, the
control character. If *FCFC is specified, the record
printer does not advance to a new a new page.
length must include one extra position for the first-
character forms-control code. This value is not valid for If no line number is specified for a channel identifier, and
externally described printer files. that channel identifier is encountered in the data, a
default of 'space one line' before printing is used. Each
*MACHINE: The first character of every record contains
channel number can be specified only once.
a machine code control character. If *MACHINE is
specified, the record length must include one extra posi- Element 2: Line Number
tion for the first character forms control code. This value line-number: Specify the line number assigned for the
is not valid for externally described printer files. channel number in the same list. Valid line numbers
If TBLREFCHR(*YES) is also specified, then the record range from 1 through 255. If no line number is assigned
length must include two extra positions for the control to a channel number, and that channel number is
character and the table reference character. encountered in the data, a default of 'space one line'
*CURLIB: The current library for the job is *CURLIB: The current library for the job is
searched. If no library is specified as the current searched. If no library is specified as the current
library for the job, the QGPL library is used. library for the job, the QGPL library is used.
library-name: Specify the name of the library to be library-name: Specify the name of the library to be
searched. searched.
coded-font-name: Specify the DBCS-coded font name form-definition-name: Specify the name of the form defi-
to use. nition that must exist in the library specified. Valid
values range from 1 to 8 characters.
| Element 2: Point Size
| *NONE: The point size is supplied by the system and is AFPCHARS
| determined by the specified font identifier. Specifies one or more AFP characters (coded fonts) to
be used with line data and a page definition.
| point-size: Specify a point size ranging from 0.1 through
| 999.9. *NONE: No AFP character (coded fonts) specified.
PAGDFN
coded-font-name: Specify up to four 4-byte names of
coded fonts to be specified with line data and a page
Specifies the qualified name of the page definition to be
definition. The 4-byte names would be concatenated to
used to format line data.
X0 to identify up to four coded fonts which are to be
*NONE: No page definition is specified. used when TBLREFCHR is being used within the data.
Because PSF/400 requires a page definition when *LINE
TBLREFCHR
or *AFPSDLINE is specified, an inline page definition is
Specifies whether table reference characters are present
built from the print file parameters and passed to
in the line data.
PSF/400 when *NONE is specified.
*NO: No table reference character is present in line
The name of the page definition can be qualified by one
data.
of the following library values:
*YES: Table reference characters are present in line
*LIBL: All libraries in the job's library list are data.
searched until the first match is found.
If forms control characters are used with the data, the
*CURLIB: The current library for the job is table reference character follows the forms control char-
searched. If no library is specified as the current acter but precedes the data bytes. If forms control char-
library for the job, the QGPL library is used. acters are not used, the table reference character is the
library-name: Specify the name of the library to be first byte of the data record. As with forms control char-
searched. acter, if table reference characters are used, every data
record must contain a TRC byte.
page-definition-name: Specify the name of the page
definition that must exist in the library specified. Valid PAGRTT
values range from 1 to 8 characters. Device type Specifies the degree of text rotation for the 3112, 3116,
*AFPDSLINE or *LINE must be specified when using a 3130, 3812, 3816, 4028, 3820, 3825, 3827, 3829, 3831,
page definition. 3835, 3900, 3916, 3930 and 3935 printers. This param-
eter allows the user to specify the degree of rotation of
FORMDF the text on the page with respect to the way the form is
Specifies the form definition to use when printing the file. loaded into the printer. See the note under the
A form definition is a resource object that defines the PAGESIZE parameter for directions on specifying page
characteristics of the form, including overlays, position of size when rotating the page.
page data on the form, and number of copies of pages
Specify *AUTO or *DEVD for this parameter and
and modifications to pages. The form definition is
PRTQLTY(*DRAFT) on this command to enable auto-
located inline with the file being printed, or in a library.
matic rotation if the data does not fit on the paper.
*NONE: No form definition is used.
*AUTO: Indicates that automatic rotation of output is
Because PSF/400 requires a form definition, an inline done to fit the printed data on the form. If rotation does
form definition is built from the print file parameters and not accomplish this, computer output reduction is per-
passed to PSF/400 when *NONE is specified. formed automatically (regardless of the print quality
*DEVD: The name of the form definition is specified in being used). This parameter is valid only for printers
the printer device description. supporting rotation.
The name of the form definition can be qualified by one *DEVD: The operating system sends a device default
of the following library values: rotation value to the printer. Page rotation is dependent
on your printer's specifications. See your printer or
*LIBL: All libraries in the job's library list are
searched until the first match is found.
printer emulation documentation to determine how page 3: Three pages of output are printed on 1 physical
rotation is affected. sheet of paper.
*COR: Computer output reduction is done. Computer 4: Four pages of output are printed on 1 physical sheet
output reduction allows printed output intended for a of paper.
13.2 inch wide by 11.0 inch long form to be printed on
REDUCE
an 11 inch wide by 8.5 inch long form.
Specifies whether or not to reduce the output when
For computer output reduction printing, the following doing multiple up printing.
operations are done for the 3112, 3116, 3130, 3812,
For examples and more details see the Printer Device
3816, 4028, 3820, 3825, 3827, 3829, 3831, 3835, 3900,
3916, 3930 and 3935 printers:
Programming book.
*TEXT: The text output is reduced when doing multiple
Automatic rotation to *COR is not done if the file
up printing.
contains graphics, bar codes, variable LPI, variable
font, variable page rotations, or variable drawer. *NONE: The output is not reduced when doing multiple
up printing.
The text is rotated 90 degrees clockwise from the 0
degree rotation position (lower left corner of the first PRTTXT
edge loaded into the printer). Specifies up to 30 characters of text to be printed at the
bottom of each page of output. More information on this
Note: For landscape paper on a 3835 printer, the
parameter is in Appendix A, “Expanded Parameter
rotation is counter-clockwise from the 0
Descriptions.”
degree rotation position (upper right corner
of the first edge loaded into the printer). *JOB: The value for the current job is used.
A top and left margin of 0.5 inches is added to the *BLANK: Text is not specified.
printed output. 'print-text': Specify the character string printed at the
The 12-pitch fonts are changed to a 15-pitch font bottom of each page. No more than 30 characters of
and 15-pitch fonts are changed to a 20-pitch font. text can be entered, enclosed in apostrophes.
All other font widths are changed to a 13.3-pitch
JUSTIFY
font, except for the 4028 printer where they are
Specifies the printing positions of the characters on a
changed to a 15-pitch font.
page so the right-hand margin of printing is regular.
Vertical spacing (specified by the LPI parameter) is Justification is done to the record length on the printer
70 percent of the normal spacing. file opened.
The page size is set to 8.5 inches wide by 11 Note: The JUSTIFY parameter is supported only on the
inches long. 3812 SCS, 3816 SCS, and 5219 Printers.
0: No rotation occurs. Printing starts at and is parallel 0: No justification occurs.
to the edge loaded into the printer. 50: Spaces are added to the blanks in the text so that
90: Rotation of the text is done 90 degrees clockwise the right margin is more closely aligned but not flush.
from the 0 degree writing position. 100: The text is expanded by spaces (added where the
180: Rotation of the text is done 180 degrees clockwise blanks already exist) until the right margin is flush.
from the 0 degree writing position.
DUPLEX
270: Rotation of the text is done 270 degrees clockwise Specifies whether output is printed on one side or two
from the 0 degree writing position. sides of the paper.
MULTIUP *NO: The output is printed on one side of the paper.
Specifies, for spooled output only, the number of pages *YES: The output is printed on both sides of the paper
printed on a single physical page. with the top of each printed page at the same end of the
Note: Overlays are not reduced when more than one paper.
page is printed on a side. *TUMBLE: The output is printed on both sides of the
For examples and more details see the Printer Device paper with the top of one printed page at the opposite
Programming book. end of the sheet from the top of the other printed page.
1: One page of output is printed on one physical sheet This is usually used for output that is bound at the top.
of paper. *FORMDF: The output is printed on both sides of the
2: Two pages of output are printed on 1 physical sheet paper if the duplex value is specified in the form defi-
of paper. nition. If a form definition is not specified, then the
output is printed on one side of the paper.
*CURLIB: The current library for the job is offset-across: Specify the offset across from the point of
searched. If no library is specified as the current origin at which to begin printing the overlay. If
library for the job, the QGPL library is used. UOM(*CM) is specified, valid values range from 0
through 57.79, and if UOM(*INCH) is specified, valid
library-name: Specify the name of the library to be values range from 0 through 22.57.
searched.
DFRWRT
overlay-name: Specify the name of the overlay. Specifies how much output is held in the system buffer
Element 2: Offset Down before being sent to the printer.
0: No offset down from the point of origin is used. Note: If this command is specified, the Display Over-
ride (DSPOVR) command will either display or
offset-down: Specify the offset down from the point of
print the override along with any others that are
origin at which to begin printing the overlay. If
specified on this command.
UOM(*CM) is specified, valid values range from 0
through 57.79, and if UOM(*INCH) is specified, valid *YES: The system controls the amount of output that is
values range from 0 through 22.57. held in the buffer before being sent to the printer.
Element 3: Offset Across If SPOOL(*YES) is specified along with
SCHEDULE(*IMMED), output is held in the buffer until a
0: No offset across from the point of origin is used.
page of output is available or until the system buffer is
offset-across: Specify the offset across from the point of full.
origin at which to begin printing the overlay. If
*NO: If SPOOL(*NO) is specified, output is not held in
UOM(*CM) is specified, valid values range from 0
the buffer. Output is sent to the printer immediately after
through 57.79, and if UOM(*INCH) is specified, valid
the program performs a write operation.
values range from 0 through 22.57.
If the spooled output schedule is not immediate, speci-
BACKOVL
fying DFRWRT(*NO) has no effect.
Specifies the object name and library name containing
both the overlay that is printed on the BACK side of the SPOOL
page and the offset, down and across, from the point of Specifies whether the output data for the printer file is
origin used when the overlay is printed. spooled. If SPOOL(*NO) is specified, the following
parameters in this command are ignored: OUTQ,
*FRONTOVL: The values that are specified on the
COPIES, MAXRCDS, FILESEP, SCHEDULE, HOLD,
FRONTOVL parameter are used.
SAVE, OUTPTY, and USRDTA.
*NONE: No overlay is used.
Note: If SPOOL(*NO) is the current value in the printer
Element 1: Overlay Name file, or if SPOOL(*NO) is specified in this or any
The name of the overlay can be qualified by one of the other OVRPRTF command that is in effect when
following library values: the file is opened, the following parameters that
apply to spooled files are ignored: OUTQ,
*LIBL: All libraries in the job's library list are COPIES, MAXRCDS, FILESEP, SCHEDULE,
searched until the first match is found. HOLD, SAVE, OUTPTY, USRDTA, and
SPLFNAME. This parameter overrides the spool
*FILEEND: The spooled file is made available to the QWTSETP) to a new user profile, the new user profile is
writer as soon as the file is closed in the program. the owner of the spooled file.
*IMMED: The spooled file is made available to the *JOB: The spooled file is owned by the original user
writer as soon as the file is opened in the program. profile of the job. If the job has switched to a new user
profile, the original user profile is still the owner of the
HOLD
spooled file.
Specifies, for spooled output only, whether the spooled
file is held. The spooled file can be released by using *CURGRPPRF: The spooled file is owned by the group
the Release Spooled File (RLSSPLF) command. profile of the current user profile. If the job has switched
profiles, the owner of the spooled file is the group profile
Note: This parameter overrides the hold value specified
of the new user profile that the job has switched to. If
in the printer file or in other called OVRPRTF
no group profile exists for the current user profile, owner-
commands.
ship of the spooled file is determined the same way as
*NO: The spooled printer file is not held by the output *CURUSRPRF.
queue. The spooled output is available to a writer based
*JOBGRPPRF: The spooled file is owned by the group
on the SCHEDULE parameter value.
profile of the original user profile of the job. If the job
*YES: The spooled file is held until released by the has switched to a new user profile, the group profile of
Release Spool File (RLSSPLF) command. the original user profile is still the owner of the spooled
file. If no group profile exists, ownership of the spooled
SAVE
file is determined the same way as *JOB.
Specifies, for spooled output only, whether the spooled
file is saved (left on the output queue) after the output USRDFNOPT
has been produced. This parameter overrides the save Specifies, for spooled output only, one or more user-
value specified in the printer file or in other called defined options to be used by user applications or user-
OVRPRTF commands. specified programs that process spooled files. A
maximum of four user-defined options can be specified.
*NO: The spooled file data is not saved on the output
This parameter overrides the user-defined options speci-
queue after it has been produced.
fied in the printer file or in other called OVRPRTF com-
*YES: The spooled file data is saved on the output mands.
queue until the file is deleted. After the file is produced,
*NONE: No user-defined options specified.
the number of copies (see COPIES parameter) is set to
1, and its status is changed from WTR to SAV. Refer to user-defined-option: Specify the user-defined option to
the Release Spooled File (RLSSPLF) command for infor- be used by user applications or user-specified programs
mation on how to produce the spooled file again. that process spooled files. All characters are accept-
able.
OUTPTY
Specifies the output priority for spooled output files that USRDFNDTA
are produced by this job. The highest priority is 1 and Specifies, for spooled output only, the user-defined data
the lowest priority is 9. More information on this param- to be used by user applications or user-specified pro-
eter is in Appendix A, “Expanded Parameter grams that process spooled files. This parameter over-
Descriptions.” rides the user-defined data specified in the printer file or
in other called OVRPRTF commands.
*JOB: The output priority associated with the job that
created the spooled file is used. *NONE: No user-defined data specified.
output-priority: Specify the output priority. Valid values user-defined-data: Specify the user-defined data to be
range from 1 (high priority) through 9 (low priority). used by user applications or user-specified programs
that process spooled files. All characters are accept-
USRDTA
able.
Specifies, for spooled output only, the user-specified
data that identifies the file. USRDFNOBJ
Specifies, for spooled output only, the qualified name
*SOURCE: If the spooled file was created by an appli-
and type of the user-defined object to be used by user
cation program, the name of the program is used. Oth-
applications or user-specified programs that process
erwise, blanks are used.
spooled files. This parameter overrides the user-defined
user-data: Specify up to 10 characters of text. object name specified in the printer file or in other called
OVRPRTF commands.
SPLFOWN
Specifies, for spooled output only, who the owner of the *NONE: No user-defined object specified.
spooled file is.
Element 1: Name of User-Defined Object
*CURUSRPRF: The spooled file is owned by the
The name of the user-defined object can be qualified by
current user profile. If the job has switched (See API
one of the following library values:
*LIBL: All libraries in the job's library list are time for the device allocated when an acquire operation
searched until the first match is found. is performed to the file. Valid values range from 1
through 32767 seconds.
*CURLIB: The current library for the job is
searched. If no library is specified as the current LVLCHK
library for the job, the QGPL library is used. Specifies whether the record format level identifiers in
library-name: Specify the name of the library to be the program are checked against those in the device file
searched. when the file is opened. If so, the record format identi-
fiers in the program must match those in the device file.
object-name: Specify the user-defined object to be used Because the same record format name can exist in more
by user applications or user-specified programs that than one file, each record format is given an internal
process spooled files. system identifier when it is created.
Element 2: Type of User-Defined Object Note: This parameter overrides the value specified in
object-type: The user object type can be one of the fol- the printer file, in the program, or in other called
lowing: OVRPRTF commands. Level checking cannot
be done unless the program contains the record
*DTAARA Data Area format identifiers. This command cannot over-
*DTAQ Data Queue ride level checking from *NO to *YES.
*FILE File *NO: The level identifiers are not checked when the file
is opened.
*PSFCFG PSF Configuration Object
SECURE
*USRIDX User Index
Specifies whether this file is safe from the effects of pre-
*USRQ User Queue viously called file override commands. If SECURE is not
*USRSPC User Space specified, processing occurs as if SECURE(*NO) is
specified.
SPLFNAME *NO: This file is not protected from the effects of other
Specifies, for spooled output only, the spooled file name. file overrides; its values can be overridden by the effects
of previously called file override commands.
*FILE: The name of the printer file is used for the
spooled file name. *YES: This file is protected from the effects of any file
override commands previously called.
spooled-file-name: Specify up to 10 characters for the
spooled file name. OVRSCOPE
Specifies the extent of influence (scope) of the override.
WAITFILE
Specifies the number of seconds that the program waits *ACTGRPDFN: The scope of the override is determined
for the file resources and session resources to be allo- by the activation group of the program that calls this
cated when the file is opened, or for the device or command. When the activation group is the default acti-
session resources to be allocated when an acquire oper- vation group, the scope equals the call level of the
ation is performed to the file. If those resources are not calling program. When the activation group is not the
allocated within the specified wait time, an error default activation group, the scope equals the activation
message is sent to the program. More information on group of the calling program.
this parameter is in Appendix A, “Expanded Parameter
*CALLLVL: The scope of the override is determined by
Descriptions.”
the current call level. All open operations done at a call
Note: An immediate allocation of the device by the level that is the same as or higher than the current call
device resource is required when an acquire level are influenced by this override.
operation is performed to the file.
*JOB: The scope of the override is the job in which the
This parameter overrides the wait time specified in the override occurs.
printer file, in the program, or in other called OVRPRTF
SHARE
commands.
Specifies whether the open data path (ODP) for the
*IMMED: The program does not wait; when the file is printer file is shared with other programs in the routing
opened, an immediate allocation of the file resources is step. When an ODP is shared, the programs accessing
required. the file share facilities such as the file status and the
*CLS: The job default wait time is used as the wait time buffer.
for the file resources being allocated. More information on shared database files is in the DB2
number-of-seconds: Specify the number of seconds that for AS/400 Database Programming book.
the program waits for the file resources to be allocated *NO: The ODP created by the program with this attri-
to the printer file when the file is opened, or the wait bute is not shared with other programs in the routing
step. Every time a program opens the file with this attri- IGCCPI
bute, a new ODP to the file is created and activated. Specifies the printer character density of double-byte
Note: This includes several opens in the same character set (DBCS) characters, in characters per inch
program. (CPI).
*YES: The ODP created with this attribute is shared Note: This parameter does not specify the printer char-
with each program in the routing step that also specifies acter density of alphanumeric characters. Alpha-
SHARE(*YES) when it opens the file. numeric characters are printed with the value
specified on the CPI parameter.
Note: When SHARE(*YES) is specified and control is
passed to a program, a read operation in that *CPI: DBCS character density is based on the values
program retrieves the next input record. A write specified for the CPI parameter. The system prints one
operation produces the next output record. double-byte character for every two alphanumeric char-
acters.
OPNSCOPE
Specifies the extent of influence (scope) of the open For CPI(10), DBCS characters print at 5 characters
operation. per inch.
*ACTGRPDFN: The scope of the open operation is For CPI(12), DBCS characters print at 6 characters
determined by the activation group of the program that per inch.
called the OVRPRTF command processing program. If For CPI(13.3), DBCS characters print at 6.7 charac-
the activation group is the default activation group, the ters per inch (same as IGCCPI(*CONDENSED)).
scope is the call level of the caller. If the activation
For CPI(15), DBCS characters print at 7.5 charac-
group is a non-default activation group, the scope is the
ters per inch.
activation group of the caller.
For CPI(18), DBCS characters print at 9 characters
*JOB: The scope of the open operation is the job in
per inch.
which the open operation occurs.
For CPI(20), DBCS characters print at 10 characters
IGCDTA per inch.
Specifies, for program-described original files, whether
the file processes double-byte character set (DBCS) *CONDENSED: Condensed printing is used in which
data. For externally described printer files, this param- the system prints 20 DBCS characters every 3 inches.
eter specifies DBCS attributes of the file. This value is valid only for the 5553 or 5583 Printers.
*YES: The system rotates double-byte characters 90 *SYSVAL: The DBCS-coded font specified in the
degrees counterclockwise when printing. The printer system value QIGCCDEFNT is used.
rotates each character individually. The name of the coded font name can be qualified by
one of the following library values:
*LIBL: All libraries in the job's library list are OVRPRTF FILE(PRINTOUT) TOFILE(PRINT3) SPOOL(\YES)
searched until the first match is found. COPIES(5) OUTQ(OUTPUT1)
*CURLIB: The current library for the job is This command overrides the file named PRINTOUT and
searched. If no library is specified as the current uses the printer file named PRINT3 to produce the spooled
library for the job, the QGPL library is used. output on the printer. The output from the program is sent to
library-name: Specify the name of the library to be the OUTPUT1 output queue. Five copies of the spooled file
searched. are printed on the printer specified on the Start Printer Writer
(STRPRTWTR) command.
coded-font-name: Specify the coded font name to use.
| Element 2: Point Size Example 2: Rotating Double-Byte Characters
| *NONE: The point size is supplied by the system and is OVRPRTF FILE(IGCLIB/IGCPRT) IGCDTA(\YES)
IGCCHRRTT(\YES)
| determined by the specified font identifier.
| point-size: Specify a point size ranging from 0.1 through This command overrides the IGCPRT printer file, which is
| 999.9. stored in the IGCLIB library. The override puts the
IGCALTTYP DDS keyword into effect to change character
output fields to DBCS fields, and rotates the double-byte
Examples characters when printing.
Example 1: Printing Output
(P) ───────────────────────────5
55──OVRSAVF──FILE(──overridden-file-name──)──┬───────────────────────────────────────────────────┬───
│ ┌─\FILE─────────────────────────────┐ │
│ │ ┌─\LIBL/────────┐ │ │
└─TOFILE(──┴─┼───────────────┼──save-file-name─┴──)─┘
├─\CURLIB/──────┤
└─library-name/─┘
5──┬──────────────────────┬──┬────────────────────────────────────────────────┬──┬─────────────────────────────────────┬────────5
└─EXTEND(──┬─\NO──┬──)─┘ └─POSITION(──┬─\START───────────────────────┬──)─┘ └─WAITFILE(──┬─\IMMED────────────┬──)─┘
└─\YES─┘ └─\RRN──relative-record-number─┘ ├─\CLS──────────────┤
└─number-of-seconds─┘
5──┬──────────────────────┬──┬──────────────────────────────┬──┬─────────────────────┬──┬──────────────────────────────┬───────5%
│ ┌─\NO──┐ │ │ ┌─\ACTGRPDFN─┐ │ └─SHARE(──┬─\NO──┬──)─┘ └─OPNSCOPE(──┬─\ACTGRPDFN─┬──)─┘
└─SECURE(──┴─\YES─┴──)─┘ └─OVRSCOPE(──┼─\CALLLVL───┼──)─┘ └─\YES─┘ └─\JOB───────┘
└─\JOB───────┘
Note:
P All parameters preceding this point can be specified in positional form.
*YES: This file is protected from the effects of any file This command overrides the file named ONLINE so that the
override commands previously called. first record gotten after the file is opened for input is relative
record number 100. The file is also safe from overrides (in
previous program calls).
55──OVRTAPF──FILE(──overridden-file-name──)──┬──────────────────────────────────────────────────────────┬───────────────────────5
│ ┌─\FILE────────────────────────────────────┐ │
│ │ ┌─\LIBL/────────┐ │ │
└─TOFILE(──┴─┼───────────────┼──tape-device-file-name─┴──)─┘
├─\CURLIB/──────┤
└─library-name/─┘
5──┬─────────────────────────────┬─── (P) ──┬───────────────────────────────────────┬────────────────────────────────────────────────5
│ ┌──
─────────────┐ │ └─VOL(──┬─\NONE────────────────────┬──)─┘
└─DEV(───6─device-name─┴───
(1) ──)─┘ │ ┌──
───────────────────┐ │
└──6─volume-identifier─┴───
(2) ─┘
5──┬──────────────────────────────────────────┬──┬─────────────────────────────────┬──┬─────────────────────────────────┬───────5
└─REELS(──┬─\SL──┬──┬─────────────────┬──)─┘ └─SEQNBR(──┬─\END────────────┬──)─┘ └─LABEL(──data-file-identifier──)─┘
├─\NL──┤ └─number-of-reels─┘ ├─\NEXT───────────┤
├─\NS──┤ └─sequence-number─┘
├─\BLP─┤
└─\LTM─┘
5──┬───────────────────────────────┬──┬──────────────────────────────┬──┬───────────────────────────────────┬───────────────────5
└─RCDLEN(──┬─\CALC─────────┬──)─┘ └─BLKLEN(──┬─\CALC────────┬──)─┘ └─BUFOFSET(───(3) ─┬─\BLKDSC───────┬──)─┘
└─record-length─┘ └─block-length─┘ └─buffer-offset─┘
5──┬───────────────────────────┬──┬────────────────────────────────────┬──┬────────────────────────────┬────────────────────────5
(4) ─┬─\F───┬──)─┘ └─EXTEND(──┬─\NO────────────────┬──)─┘ └─DENSITY(──┬─\DEVTYPE──┬──)─┘
└─RCDBLKFMT(───
├─\FB──┤ │ ┌─\NOCHECK─┐ │ ├─16ðð──────┤
├─\V───┤ └─\YES──┼──────────┼─┘ ├─32ðð──────┤
├─\VB──┤ └─\CHECK───┘ ├─625ð──────┤
├─\D───┤ ├─\FMT348ð──┤
├─\DB──┤ ├─\FMT349ðE─┤
├─\VS──┤ ├─\FMT357ð──┤
├─\VBS─┤ ├─\FMT357ðE─┤
└─\U───┘ ├─\FMT359ð──┤
├─\QIC12ð───┤
├─\QIC525───┤
├─\QIC1ððð──┤
├─\QIC2GB───┤
├─\QIC3ð4ð──┤
├─\QIC5ð1ð──┤
├─\FMT2GB───┤
├─\FMT5GB───┤
└─\FMT7GB───┘
5──┬────────────────────────┬──┬───────────────────────┬──┬────────────────────────────────┬────────────────────────────────────5
└─COMPACT(──┬─\DEVD─┬──)─┘ └─CODE(──┬─\EBCDIC─┬──)─┘ └─CRTDATE(──┬─\NONE─────────┬──)─┘
└─\NO───┘ └─\ASCII──┘ └─creation-date─┘
5──┬──────────────────────────────────┬──┬─────────────────────────┬────────────────────────────────────────────────────────────5
└─EXPDATE(──┬─\NONE───────────┬──)─┘ └─ENDOPT(──┬─\REWIND─┬──)─┘
├─\PERM───────────┤ ├─\LEAVE──┤
└─expiration-date─┘ └─\UNLOAD─┘
5──┬───────────────────────────────────────────────────────────────┬──┬──────────────────────┬──────────────────────────────────5
└─USRLBLPGM(──┬─\NONE──────────────────────────────────────┬──)─┘ └─IGCDTA(──┬─\NO──┬──)─┘
│ ┌─\LIBL/────────┐ │ └─\YES─┘
└─┼───────────────┼──user-label-program-name─┘
├─\CURLIB/──────┤
└─library-name/─┘
5──┬─────────────────────────────────────┬──┬──────────────────────┬──┬──────────────────────────────┬──────────────────────────5
└─WAITFILE(──┬─\IMMED────────────┬──)─┘ │ ┌─\NO──┐ │ │ ┌─\ACTGRPDFN─┐ │
├─\CLS──────────────┤ └─SECURE(──┴─\YES─┴──)─┘ └─OVRSCOPE(──┼─\CALLLVL───┼──)─┘
└─number-of-seconds─┘ └─\JOB───────┘
5──┬─────────────────────┬──┬──────────────────────────────┬───────────────────────────────────────────────────────────────────5%
└─SHARE(──┬─\NO──┬──)─┘ └─OPNSCOPE(──┬─\ACTGRPDFN─┬──)─┘
└─\YES─┘ └─\JOB───────┘
Notes:
1 A maximum of 4 repetitions
2 A maximum of 50 repetitions
3 The value *BLKDSC is valid only for a file with record block format *D or *DB.
4 The values *F, *FB, *VS, *VBS, and *U are valid for both EBCDIC and ASCII codes; *V and *VB are valid only for EBCDIC;
VOL
Required Parameter Specifies one or more volume identifiers used by the file.
The volumes must be installed in the same order as the
FILE identifiers are specified here (and as they are specified
Specifies the name of the file being used by the program on the DEV parameter). If the file is opened for read
to which this override command is applied. If backward, then the volume identifiers in the list are pro-
TOFILE(*FILE) is specified, a display device file must be cessed from last to first (while the devices in the device
specified. Otherwise, any device file or database file list are used in first-to-last order). If a list of volume
can be specified. identifiers is provided for the file, operator messages
indicate the name of the required volume. More infor-
Optional Parameters mation on this parameter is in Appendix A, “Expanded
Parameter Descriptions.”
TOFILE
This parameter overrides the volume identifiers specified
Specifies the qualified name of the tape device file that
in the tape device file.
is used instead of the file specified in the FILE param-
eter, or if *FILE is specified, specifies that certain attri- *NONE: No tape volume identifiers are specified for this
butes are overridden by parameters specified in this file. They can be supplied before the device file is
command. The parameters specified on this OVRTAPF opened, either in a CHGTAPF or OVRTAPF command
command override the other values specified in the tape or in the high-level language program. If volume identi-
device file or in the program. fiers are not specified before the device file is opened,
volume checking is not performed beyond verifying that
*FILE: The tape device file named in the FILE param-
the correct label type volume is on the device, and
eter has some of its parameters overridden by values
volume names are not provided in operator messages.
specified in this command.
The maximum number of reels processed for an *NL,
The name of the tape device file can be qualified by one *NS, *BLP, or *LTM input file when VOL(*NONE) is
of the following library values: specified is determined by the REELS(number-of-reels)
parameter value.
*LIBL: All libraries in the job's library list are
searched until the first match is found.
volume-identifier: Specify the identifiers of one or more *SL: The volumes have standard labels. If a list of
volumes in the order in which they are placed on the volume identifiers is specified (with the VOL parameter),
device. Each volume identifier contains a maximum of 6 the system checks that the correct tape volumes are on
alphanumeric characters. Use a blank as a separator the device in the specified sequence.
character when listing multiple identifiers. Up to 50
If no volume identifier list is given and the file is
volume identifiers can be specified. These identifiers are
opened for output, any standard-label volumes may
used in messages sent to the operator during pro-
be installed on the device.
cessing. The maximum number of reels processed for
an *NL, *NS, *BLP, or *LTM input file is determined by If no volume identifier list is given and the file is
the number of volume identifiers in the list. opened for input, the first volume may have any
volume identifier, but if the file is continued, the
Note: If the VOL parameter value used for the file
system requires the correct continuation volumes to
specifies a list of identifiers rather than
be processed (verified by checking the data file
VOL(*NONE), the number-of-reels part of the
labels). For an input file, the end-of-file message is
REELS parameter is ignored regardless of where
sent to the program being used when the labels on
it is specified. A description of how the param-
the last volume processed indicate that it is the last
eter values for the file are determined when over-
volume for the data file.
rides are used, the high-level language interface,
and the device file when the file is opened is in *NL: The volumes are not labeled. On a nonlabeled
the Data Management book. To ensure that the volume, tape marks are used to indicate the end of each
number-of-reels part of the REELS parameter is data file and the end of the volume. For an input file,
used (rather than a VOL identifier list) to control the end-of-file message is sent to the program when the
the volumes processed by the tape device file, number of volumes specified in the volume list have
specify VOL(*NONE) in the same command in been processed, or, if no list of volume identifiers is pro-
which the REELS parameter is specified. vided, when the number of reels specified in the REELS
parameter are processed.
REELS
Specifies the type of labeling used on the tape reels and *NS: The volumes have nonstandard labels. Each
the maximum number of reels processed if both a list of volume must start with some kind of label information,
volume identifiers is not specified (VOL parameter) and optionally preceded by a tape marker and always fol-
this device file is used with either *NL, *NS, *LTM, or lowed by a tape marker. This nonstandard label infor-
*BLP input files. When the number of reels is specified mation is ignored. The system spaces forward to a point
as the second element of this parameter, the volume beyond the tape marker that follows the nonstandard
identifiers on the volumes are ignored if labeled tapes labels and positions the tape at the file's data. Each reel
are being processed; instead, the order in which the must have a tape marker at the end of the file's data.
reels are installed on the device must be checked by the Information beyond this ending tape marker is ignored.
operator. Only a single data file can exist on a nonstandard tape.
Standard-label volumes cannot be processed by using
The number-of-reels value is not a limiting value for
the *NS label processing.
standard-label or output files. For a standard-label input
file, the data file labels limit the number of volumes pro- For an input file, the end-of-file message is sent to the
cessed by indicating end-of-file. For an output file, the program using the file when the number of volumes
number-of-reels value is ignored; the system requests specified in the volume list have been processed, or, if
that additional volumes be kept on the device until the no list of volume identifiers is provided, when the
file is closed. number of reels specified in the REELS parameter are
processed.
The system checks the first record following the load
point on the tape to see (1) whether it has exactly 80 *BLP: Standard-label processing is bypassed. Each
bytes for EBCDIC or at least 80 bytes for ASCII and (2) reel must have standard labels. Although each reel is
whether the first 4 bytes contain the values VOL and 1. checked for a standard volume label and each file must
If so, the reel contains a standard-label tape. *SL and have at least one standard header label (HDR1) and one
*BLP files require standard-label tape volumes. *NL, standard trailer label (EOV1 or EOF1), most other label
*NS, and *LTM tape files cannot process standard-label information (such as the data file record length or block
volumes. length) is ignored. The sequence number of each file on
the volume is determined only by the number of tape
Note: The values *SL, *NL, and *LTM can be specified
markers between it and the start of tape (in contrast to
if the device file is used for either reading or
*SL processing in which the file sequence number stored
writing on tapes. The values *NS and *BLP are
in the header and trailer labels of each file are used to
valid only if the device file is used to read tapes.
locate a data file).
This parameter overrides the values specified in the
Most of the information in the data file trailer label is
device file, in the program, or in other called OVRTAPF
ignored, but if an end-of-file (EOF) trailer label is found,
commands.
the end-of-file message is sent to the program using the sequence-number: Specify the sequence number of the
tape file. If no end-of-file trailer label is encountered by file. Valid values range from 1 through 16777215.
the time the specified number of volumes or reels have
LABEL
been processed (volume identifier list and REELS
Specifies the data file identifier of the data file processed
parameter), the end-of-file message is immediately sent
by this tape device file. An identifier is defined only for
to the program using the tape file. Bypass label pro-
standard-label tapes and is stored in the header label
cessing can be used when the user does not know the
immediately before the data file.
name of the file used or when some file label information
is incorrect. If a data file identifier is specified for any type of label
processing other than *SL, it is ignored.
*LTM: The volumes have no labels but do have a single
leading tape marker before the first data file. An identifier is required for a standard label output file,
REELS(*LTM) is processed the same as REELS(*NL) but is optional for an input file because the sequence
except that when SEQNBR(1) is specified for an output number uniquely identifies the data file to process.
file to create the first data file on the tape, a leading tape
For an input file or output file with EXTEND(*YES) speci-
marker is written at the start of the tape before the first
fied, this parameter specifies the identifier of the data file
data block.
on the tape. The specified identifier must match the one
number-of-reels: Specify the maximum number of reels in the labels of the data file that the SEQNBR parameter
to be processed for an *NL, *LTM, *NS, or *BLP input specifies; otherwise, an error message is sent to the
tape operation when a list of volume identifiers is not program using this device file. For output files with
specified (VOL parameter). If the next reel is not on the EXTEND(*NO) specified, this parameter specifies the
device when the end of the currently-processing tape is identifier of the data file to be created on the tape. More
reached, a message is sent to the operator requesting information on this parameter is in Appendix A,
that the next tape be installed on the next tape device. “Expanded Parameter Descriptions.”
The number-of-reels value is ignored for a standard-label
This parameter overrides the data file identifier specified
(*SL) file or for any output file.
in the device file, in the program, or in other called
SEQNBR OVRTAPF commands.
Specifies the sequence number of the data file on the data-file-identifier: Specify the identifier (17 alphanu-
tape being processed. meric characters maximum) of the data file used with
this tape device file. If this identifier is for a tape written
When standard-label tapes are used, the four-
in the basic exchange format, and is used on a system
position file sequence number is read from the first
other than an AS/400 system, up to eight characters or a
header label of the data file.
qualified identifier having no more than eight characters
When bypass label processing is used or when per qualifier must be used.
standard-label tapes are not used, the system
counts the tape markers from the start of the tape to RCDLEN
locate the correct sequence number data file to be Specifies, in bytes, the length of the records contained in
processed. the data file processed with this device file. The system
always uses the record length and block length specified
When multiple-file, multiple-volume tapes are pro-
in the data file labels for any standard-label input file or
cessed using REELS(*SL), the file sequence
output file with EXTEND(*YES) specified (if a second
numbers continue consecutively through the
header label (HDR2) is found on the tape and *BLP
volumes; thus, each new data file has a sequence
label processing has not been specified).
number one greater than the previous file, regard-
less of its volume location. This parameter overrides the value specified in the
device file, in the program, or in other called OVRTAPF
*END: The file is written on the end of the tape. This commands.
value is used only for files that are written to tape.
*CALC: No record length is specified for the data file
An error message is shown on the display when a tape being processed. If *CALC is specified, the system will
device file is used to read from a tape and the *END attempt to calculate an appropriate record length when
special value is specified in the tape device file. the file is opened. RCDLEN(*CALC) can be used for
*NEXT: The next file in the sequence is processed. nonlabeled tapes or when there is no HDR2 label if a
This value is used for files read from tape. If the tape is BLKLEN value other than *CALC is specified for the file
currently in a position that is prior to the first file, the first and RCDBLKFMT does not specify spanned or blocked
file on the tape is processed. records. In this case, the system calculates an appro-
priate record length from the block length, record block
An error message is shown on the display when a tape
format, and buffer offset (for an ASCII file) specified for
file is used to write to a tape and the *NEXT special
the file. In any other case, the actual record length must
value is specified in the tape file.
be specified by a CHGTAPF command or OVRTAPF
command, or in the high-level language program that RCDLEN value other than *CALC is specified for the file
opens the device file. and RCDBLKFMT does not specify spanned or blocked
records. In this case, the system calculates an appro-
record-length: Specify a value ranging from 1 through
priate block length from the record length, record block
32767 bytes that indicates the length of each record in
format, and buffer offset (for an ASCII file) specified for
the data file. The minimum and maximum record length
the file. In any other case, the actual block length must
allowed for a file is dependent on the record block
be specified by a CHGTAPF command or OVRTAPF
format, block length, buffer offset (for an ASCII file), and
command, or in the high-level language program that
recording code. The EBCDIC Record Length Values
opens the device file.
and ASCII Record Length Values tables (at the end of
this parameter description) show the minimum and block-length: Specify a value, not exceeding 524288
maximum record length values allowed for each record bytes, that specifies the maximum length of each block
block format, assuming the block length value is large in the data file to be processed. The minimum block
enough to support the maximum record length. The fol- length that can be successfully processed is determined
lowing EBCDIC Record Length Values and ASCII by the tape device hardware and AS/400 system
Record Length Values tables show the minimum and machine support functions.
maximum record length values allowed for each record
The maximum block length is always 524288 bytes
block format, assuming the block length value is large
for an input file, but is limited to 9999 bytes if block
enough to support the maximum record length.
descriptors must be created for an ASCII output file.
The following table shows the minimum and
EBCDIC RCDLEN Ranges
maximum block length values allowed for an output
file:
RCDFBLKFMT FILETYPE(*DATA) FILETYPE(*SRC)
*F *FB *U 18 – 32767 30 – 32767
*V *VB 1 – 32759 13 – 32767 Minimum Maximum
CODE BUFOFSET BLKLEN BLKLEN
*VS *VBS 1 – 32759 13 – 32767
*EBCDIC Ignored 18 524288
*ASCII 0 18 524288
Figure 4. EBCDIC Record Length Vlaues (RCDLEN Parameter)
*ASCII *BLKDSC 18 9999
(OVRTAPF) command, or by the file labels for an input The Required RCDLEN/BLKLEN/BUFOFSET Relation
file that contains any information (such as a block table, at the end of this parameter description, shows the
descriptor) ahead of the first record in each block. If the required relationship between the record length, block
user does not specify a buffer offset value when a tape length, and buffer offset (for ASCII) file parameters for
file is created, it is not necessary to specify an offset an output file or an input file where the file parameters
value when the file is read. are not determined from a second file header label
(HDR2).
The only buffer offset values allowed for an output file
are zero and *BLKDSC. An existing standard-label data Note: When BUFOFSET(*BLKDSC) is specified for the
file with a buffer offset value in the HDR2 label can be file, a value of 4 should be used for the
extended only if the buffer offset value is either 0 or 4. BUFOFSET part of any BLKLEN calculations,
A buffer offset value of 0 in the HDR2 label adds data unless existing file labels on the tape specify a
blocks with no buffer offset. BUFOFSET(*BLKDSC) different value.
must be specified to extend an existing tape data file
This parameter overrides the value specified in the
that contains an offset value of 4 in the HDR2 label.
device file, in the program, or in other called OVRTAPF
This parameter overrides the value specified in the commands.
device file, in the program, or in other called OVRTAPF
*F: Fixed-length, unblocked, unspanned records in
commands.
either EBCDIC or ASCII code are processed. The
*BLKDSC: Creates 4-byte block descriptors in any tape system may change this record block format to *FB,
file created by using this device file. Any input file read based on other file parameters.
by using this device file should assume 4 bytes of buffer
*FB: Fixed-length, blocked, unspanned records in either
offset information preceding the first record in each data
EBCDIC or ASCII code are processed. The system may
block. This value is valid only for a record block format
change this record block format to *F, based on other
*D or *DB file. The contents of the buffer offset informa-
file parameters.
tion of each output data block when
BUFOFSET(*BLKDSC) is specified is the actual length *V: Variable-length, unblocked, unspanned records in
of the data block, expressed in zoned decimal format. EBCDIC type V format are processed. The system may
change this record block format to *VB, *D, or *DB,
buffer-offset: Specify a value ranging from 0 through 99 based on other file parameters.
bytes that specifies the length of the buffer offset infor-
mation that precedes the first record in each data block. *VB: Variable-length, blocked, unspanned records in
EBCDIC type V format are processed. The system may
RCDBLKFMT change this record block format to *DB, based on the
Specifies the type and blocking attribute of records in the volume code.
tape data file being processed.
*D: Variable-length, unblocked, unspanned records in
Record block format *V and *VB records can be pro- ASCII type D format are processed. The system may
cessed only for an EBCDIC file; *D and *DB records can change this record block format to *DB, *V, or *VB,
be processed only for an ASCII file. If a standard-label based on other file parameters.
tape (label type *SL or *BLP) is being processed and an
inconsistent record block format is specified for the *DB: Variable-length, blocked, unspanned records in
volume code, the correct record type is assumed (V or ASCII type D format are processed. The system may
D) for the volume code and a warning message is sent change this record block format to *VB, based on the
to the program that opens the file. If the record type and volume code.
code are inconsistent for a nonlabeled volume (label *VS: Variable-length, unblocked, spanned records in
type *NL, *LTM, or *NS), an error message is sent and either EBCDIC or ASCII code are processed. The
the file is not opened, because there are no labels to system may change this record block format to *VBS,
verify the correct volume code. based on other file parameters. Note that the represen-
If a valid record length, block length, and buffer offset tation of spanned records on the tape is different for
value (for an ASCII file) are specified for fixed-length EBCDIC and ASCII files, but the system selects the
records but the block attribute is incorrect, the correct correct format based on the file code.
block attribute is assumed (changing record block format *VBS: Variable-length, blocked, spanned records in
*F to *FB or record block format *FB to *F), and a either EBCDIC or ASCII code are processed. Note that
warning message is sent to the program that opens the the representation of spanned records on the tape differs
file. for EBCDIC and ASCII files, but the system selects the
If a block length is specified that is longer than required correct format based on the file code.
to process a maximum length record, then record block *U: Undefined format records in either EBCDIC or
format *V, *D, or *VS is changed to *VB, *DB, or *VBS ASCII code are processed. RCDBLKFMT(*U) records
and a warning message is sent to the program that are processed as variable-length records, and each
opens the file. record written or read is in a separate tape block. This
format can be useful for processing tape files that do not *NO: Records are not added to the end of the specified
have the formatting requirements of any other record data file. If there is already a data file with the specified
block format. or ASCII code. RCDBLKFMT(*U) records SEQNBR on the tape, a new data file is created by over-
are processed as variable length records, where each writing the existing data file and any files that follow it.
record written or read is in a separate tape block. This Records are not added to the end of the specified data
format is useful for processing tape device files that do
*YES: New records are added to the end of the speci-
not meet the formatting requirements of any other record
fied data file on tape when this device file is used.
block format.
Element 2: Checking Active Files
The following Required RCDLEN/BLKLEN/BUFOFSET
Relation table shows the required relationship between If EXTEND(*YES) is specified, the following values
the record length, block length, and buffer offset (for check to see whether the file already exists:
ASCII) file parameters for an output file or an input file *NOCHECK: The file is extended without being checked
where the file parameters are not determined from a to see whether the file is active.
second file header label (HDR2).
*CHECK: Before the file is extended, the file is checked
Note: When BUFOFSET(*BLKDSC) is specified for the to see whether it is active.
file, a value of 4 should be used for the
BUFOFSET part of any BLKLEN calculations, DENSITY
unless existing file labels on the tape specify a Specifies the density of the data that is written on the
different value. tape volume when this device file is created. This
parameter is used only for tape files being written to
tape; it is ignored for tape files being read from the tape
(in the case of files being read from tape, the density on
CODE RCDBLKFMT BLKLEN1
the tape is used).
*EBCDIC *F *U = RCDLEN
*ASCII *F *U = RCDLEN + BUFOFSET
The density of a standard-label volume is specified on
the INZTAP command, which initializes tapes as
*EBCDIC *FB = RCDLEN * n standard-label volumes by writing volume labels on
*ASCII *FB = (RCDLEN * n) + BUFOFSET
them. If the density specified on this parameter is dif-
(where n is the number of records ferent than the density of a standard-labeled tape, the
in a maximum-length block) tape must be reinitialized to the specified density.
*EBCDIC *V = RCDLEN * 8
*DEVTYPE: The density is based on the kind of tape
*ASCII *D = RCDLEN * 4 + BUFOFSET
device being used.
*EBCDIC *VB >= RCDLEN + 8
*ASCII *DB >= RCDLEN + 4 + BUFOFSET 1600: The data density on the tape volume is 1,600 bits
per inch, which is used for 1/2 inch reel tapes.
*EBCDIC *VS *VBS >= 18
*ASCII *BS *VBS >= 6 + BUFOFSET (18 minimum) 3200: The data density on the tape volume is 3,200 bits
1 Block length (BLKLEN) is a function of record length per inch, which is used for 1/2 inch reel tapes.
(RCDLEN) and buffer offset (BUFOFSET). 6250: The data density on the tape volume is 6,250 bits
per inch, which is used for 1/2 inch reel tapes.
*FMT3480: The format of this tape is FMT3480. The
Figure 7. Required RCDLEN/BLKLEN/BUFOFSET Relation data density on this tape volume is formatted to support
a 3480 device. This density is used for 1/2 inch car-
EXTEND tridge tapes.
Specifies, for output operations to tape, whether new
records are added to the end of a data file currently on *FMT3490E: The format of this tape is FMT3490E. The
the tape. The specific data file is identified by the data density on this tape volume is formatted to support
SEQNBR parameter and, for a standard-label file, the a 3490E device. This density is used for 1/2 inch car-
LABEL parameter. If the data file is extended, it tridge tapes.
becomes the last file on the tape volume; data files that *FMT3570: The format of this tape is FMT3570. The
follow it are overwritten as the specified file is extended. data format is written on the tape volume with a 3570
Note: This parameter is not valid for 1/4-inch cartridge device.
tape devices. *FMT3570E: The format of this tape is FMT3570E. The
This parameter overrides the extend value specified in data format is written on the tape volume with a 3570E
the device file, in the program, or in other called device.
OVRTAPF commands. *FMT3590: The format of this tape is FMT3590. The
Element 1: Adding Records to Data File data format is written on the tape volume with a 3590
device. This density is used for 1/2 inch cartridge tapes.
*QIC120: The format of this tape is QIC120, which is any type of label processing other than standard-
used for 1/4 inch cartridge tapes that can hold 120 label (*SL), it is ignored. If the creation date
megabytes of data. written on the tape containing the data file does
*QIC525: The format of this tape is QIC525, which is not match the date specified in this device file
used for 1/4 inch cartridge tapes that can hold 525 description, an inquiry message is sent to the
megabytes of data. operator.
*QIC1000: The format of this tape is QIC1000, which is This parameter overrides the value specified in the
used for 1/4 inch cartridge tapes that can hold 1200 program, device file, or in other called OVRTAPF com-
megabytes of data. mands.
*QIC2GB: The format of this tape is QIC2GB, which is *NONE: The creation date is not specified. It is not
used for 1/4 inch cartridge tapes that can hold 2.5 checked unless it is supplied before the device file is
gigabytes of data. opened, either in a OVRTAPF command or CHGTAPF
command, or in the high-level language program.
*QIC3040: The format of this tape is QIC3040, which is
used for 1/4 inch minicartridge tapes that can hold up to
creation-date: Specify the creation date of the data file
used by this device file. The date must be specified in
840 megabytes of data.
the format defined by the job attributes DATFMT and, if
*QIC5010: The format of this tape is QIC5010, which is separators are used, DATSEP.
used for 1/4 inch cartridge tapes that can hold 13.5
gigabytes of data. EXPDATE
Specifies, for tape output data files only, and only when
*FMT2GB: The format of this tape is FMT2GB, which is standard-labeled tapes are used, the expiration date of
used for 8 millimeter cartridge tapes that can hold 2 the data file used by this device file. If a date is speci-
gigabytes of data. fied, the data file is protected and cannot be overwritten
*FMT5GB: The format of this tape is FMT5GB, which is until after the specified expiration date. The files cannot
used for 8 millimeter cartridge tapes that can hold 5 be overwritten until after the expiration date.
gigabytes of data. Note: The data file expiration date is stored in file
*FMT7GB: The format of this tape is FMT7GB, which is labels on the tape. If an expiration date is speci-
used for 8 millimeter cartridge tapes that can hold 7 fied for any type of label processing other than
gigabytes of data. *SL, it is ignored.
*REWIND: The tape is automatically rewound, but not Note: An immediate allocation of the device by the
unloaded, after the operation has ended. device resource is required when an acquire
operation is performed to the file.
*LEAVE: The tape does not rewind or unload after the
operation ends. It remains at the current position on the This parameter overrides the wait time specified in the
tape drive. program or in the device file.
This option is used to reduce the time required to posi- *IMMED: The program does not wait; when the file is
tion the tape if the next tape file that opens to this device opened, an immediate allocation of the file resources is
uses a data file that is on this volume. required.
Note: Even if ENDOPT(*LEAVE) is specified, the next *CLS: The job default wait time is used as the wait time
tape file opened to this reel is positioned at the for the file resources being allocated.
beginning of some data file on the volume (or at
number-of-seconds: Specify the number of seconds that
the end of a data file, for either read backward or
the program waits for the file resources to be allocated
for output that extends an existing data file on
to the tape file when the file is opened, or the wait time
the volume). A tape file is always positioned at
for the device allocated when an acquire operation is
the start or end of a data file when it is opened.
performed to the file. Valid values range from 1 through
*UNLOAD: The tape is automatically rewound and 32767 seconds.
unloaded after the operation ends.
SECURE
USRLBLPGM Specifies whether this file is safe from the effects of pre-
Specifies the qualified name of the user program that viously called file override commands. If SECURE is not
processes user tape labels. On an output file, the user specified, processing occurs as if SECURE(*NO) is
label program will pass the user labels that are written to specified.
tape. On an input file, the user labels are passed to the
*NO: This file is not protected from the effects of other
user label program.
file overrides; its values can be overridden by the effects
*NONE: There is no user label program for this device of previously called file override commands.
file.
*YES: This file is protected from the effects of any file
The name of the user label program can be qualified by override commands previously called.
one of the following library values:
OVRSCOPE
*LIBL: All libraries in the job's library list are Specifies the extent of influence (scope) of the override.
searched until the first match is found.
*ACTGRPDFN: The scope of the override is determined
*CURLIB: The current library for the job is by the activation group of the program that calls this
searched. If no library is specified as the current command. When the activation group is the default acti-
library for the job, the QGPL library is used. vation group, the scope equals the call level of the
calling program. When the activation group is not the
library-name: Specify the name of the library to be
default activation group, the scope equals the activation
searched.
group of the calling program.
user-label-program-name: Specify the name of the user *CALLLVL: The scope of the override is determined by
program that processes the user tape labels. If no
the current call level. All open operations done at a call
library qualifier is given, *LIBL is used to find the file.
level that is the same as or higher than the current call
IGCDTA level are influenced by this override.
Specifies whether the file processes double-byte char- *JOB: The scope of the override is the job in which the
acter set (DBCS) data. override occurs.
*NO: The file does not process DBCS data.
SHARE
*YES: The file processes DBCS data. Specifies whether the open data path (ODP) for the tape
file is shared with other programs in the routing step.
WAITFILE
When an ODP is shared, the programs accessing the
Specifies the number of seconds that the program waits
file share facilities such as the file status and the buffer.
for the file resources and session resources to be allo-
cated when the file is opened, or for the device or More information on shared database files is in the DB2
session resources to be allocated when an acquire oper- for AS/400 Database Programming book.
ation is performed to the file. If those resources are not *NO: The ODP created by the program with this attri-
allocated within the specified wait time, an error bute is not shared with other programs in the routing
message is sent to the program. More information on step. Every time a program opens the file with this attri-
this parameter is in Appendix A, “Expanded Parameter bute, a new ODP to the file is created and activated.
Descriptions.”
This is the first command in a program source file for a This is the first command in a program source file for a
program that contains two parameters, &X and &Y, that have program that specifies two parameters in positional form,
values passed to them from the calling program. &PARM1 and &PARM2. When this program is called, the
calling program passes, through the CALL or TFRCTL
Example 3: Program Containing Two Parameters in command, the values to be assumed for &PARM1 and
Positional Form &PARM2.
PGM (&PARM1 &PARM2)
PING Command
PING Command
For the description of the PING command, see the VFYTCPCNN (Verify TCP/IP Connection) command description.
(P) ────────────────────────────────────────────────────────────────5%
55──POSDBF──OPNID(──opnid-name──)──POSITION(──┬─\START─┬──)────
└─\END───┘
Note:
P All parameters preceding this point can be specified in positional form.
POSITION Example
Specifies the starting or ending position of the database POSDBF OPNID(XXX) POSITION(\START)
file.
This command sets the record position of the database file
*START: The position of the database file is set to the
that is opened with OPNID(XXX) to the starting position of
start position of the member currently open. After the
the database file member that is currently open.
start position is set, a read next operation gets the first
(P) ─────────────────────────────────────5%
55──PRTADPOBJ──USRPRF(──┬─\ALL───────────────────────┬──)──┬──────────────────────────┬───
├─user-profile-name──────────┤ │ ┌─\NO──┐ │
└─generic\-user-profile-name─┘ └─CHGRPTONLY(──┴─\YES─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose Note: To see the parameter and value descriptions for this
command, refer to the online help text. For more
The Print Adopting Objects (PRTADPOBJ) command allows information about printing the help text, refer to
you to print a report of the objects that adopt the special and “Printing CL Command Descriptions” in Chapter 1.
private authorities of the specified user profile. This is a way
to check for security exposures associated with program
adoption. Required Parameter
USRPRF
This command prints two reports for a user profile. The first
Specifies the name of the user profile whose adopted
report (Full Report) contains all of the objects that adopt the
object information will be printed.
authorities of the user profile. The second report (Changed
Report) contains the objects that now adopt the authorities of *ALL: The adopted information is printed for all user
the user profile that did not adopt the authorities of the user profiles.
profile when the PRTADPOBJ command was previously run user-profile-name: Specify the name of the user profile
for the user profile. If the PRTADPOBJ command was not to print the adopted information for.
previously run for the user profile, there will be no 'Changed
Report'. If the command has been previously run for the generic*-user-name: Specify the generic name of the
user profile but no additional objects adopt the authorities of user profile to print the adopted information for. A
the user profile, then the 'Changed Report' is printed but generic name is a character string of one or more char-
there are no objects listed. acters followed by an asterisk (*).
┌─\LIBL/────────┐
(P) ─┬──────────────────────────┬──┬──────────────────────────────────┬────5
55──PRTAFPDTA──FILE(──┼───────────────┼──file-name──)────
├─\CURLIB/──────┤ │ ┌─\FIRST──────┐ │ │ ┌─\JOB────────────────┐ │
└─library-name/─┘ └─MBR(──┴─member-name─┴──)─┘ └─DEV(──┼─\SYSVAL─────────────┼──)─┘
└─printer-device-name─┘
5──┬─────────────────────────────────────────────────────────┬──┬─────────────────────────────────────┬─────────────────────────5
│ ┌─\DEVD───────────────────────────────────┐ │ │ ┌─1────────────────┐ │
(1) ──)─┘
└─FORMDF(──┼─\INLINE─────────────────────────────────┼──)─┘ └─COPIES(──┴─number-of-copies─┴───
│ ┌─\LIBL/────────┐ │
└─┼───────────────┼──form-definition-name─┘
├─\CURLIB/──────┤
└─library-name/─┘
5──┬───────────────────────────────────────┬──┬─────────────────────────────────────┬──┬─────────────────────────────┬─────────5%
│ ┌─1────────────────────┐ │ │ ┌─\END───────────────┐ │ │ ┌─\ABSOLUTE─┐ │
└─STRPAGE(──┴─starting-page-number─┴──)─┘ └─ENDPAGE(──┴─ending-page-number─┴──)─┘ └─FIDELITY(──┴─\CONTENT──┴──)─┘
Notes:
P All parameters preceding this point can be specified in positional form.
*CURLIB: The current library for the job is *END: Printing concludes at the end of the file.
searched. If no library is specified as the current
ending-page-number: Specify the page number on
library for the job, the QGPL library is used.
which printing ends.
library-name: Specify the name of the library to be
FIDELITY
searched.
Specifies the degree of exactness required when printing
form-definition-name: Specify the name of the form defi- the file.
nition that must exist in the library named. A valid name
*ABSOLUTE: The job is printed only if the file can be
has up to 8 characters.
printed exactly as specified by the data stream and
COPIES external controls.
Specifies, for spooled files, the number of copies being *CONTENT: Prints the file using all available exception
printed. handling.
1: One copy of the output is printed.
number-of-copies: Specify the number of copies that are Examples
printed.
Example 1: Printing Specific Pages
STRPAGE
PRTAFPDTA FILE(MYLIB/MYFILE)
Specifies the page on which printing starts. This param- STRPAGE(2) ENDPAGE(6)
eter is used for partial printing of a file.
1: Printing starts with page 1. If the start page is not This command prints the first member in file MYFILE in
specified, 1 is assumed. library MYLIB starting with page 2 and ending on page 6.
starting-page-number: Specify the page number on Example 2: Printing Using All Available Exception Han-
which printing starts. dling
ENDPAGE PRTAFPDTA FILE(MYLIB/MYFILE)
Specifies the page on which printing ends. This param- FORMDF(F1ð1ð1) FIDELITY(\CONTENT)
eter is used for partial printing of a file ending at a speci-
fied page number. If both start page and end page are This command prints the first member in file MYFILE in
specified, the end page must be greater than or equal to library MYLIB using a form definition of F10101 and all avail-
the start page. Specifying an end page beyond the end able exception handling.
of the actual file does not create an error condition.
┌──
─────────────────────────────────┐
│ ┌─\LIBL/────────┐ │
6 (1) ──)──┬───────────────────────────────────────────────────────┬───
55──PRTCMDUSG──CMD(────┼───────────────┼──command-name─┴─── (P) ───5%
└─library-name/─┘ │ ┌─\USRLIBL/─────┐ ┌─\ALL──────────────────┐ │
└─PGM(──┼───────────────┼──┼─program-name──────────┼──)─┘
├─\CURLIB/──────┤ └─generic\-program-name─┘
├─\ALLUSR/──────┤
└─library-name/─┘
Notes:
1 A maximum of 50 repetitions
Purpose libraries for which the user has some (any) authority are
included in the report. This parameter also can specify
The Print Command Usage (PRTCMDUSG) command that all (*ALL) programs in the specified library or
creates a cross-referenced list of a specified group of CL libraries (*USRLIBL/*ALLUSR, for example) are
commands that are used in a specified group of CL pro- searched.
grams. The report shows, program by program, which of the
The name of the program can be qualified by one of the
specified commands are used in each program. The report
following library values:
can be used to identify which programs need to be recom-
piled because of changes that have been made to the *USRLIBL: Only the libraries in the user portion of
command definition objects of commands specified on the the job's library list are searched.
PRTCMDUSG command. Note that this command can take
*CURLIB: The current library for the job is
a long time to run and can make a lot of printed output.
searched. If no library is specified as the current
Note: To see the parameter and value descriptions for this library for the job, the QGPL library is used.
command, refer to the online help text. For more
*ALLUSR: All user libraries are searched. All
information about printing the help text, refer to
libraries with names that do not begin with the letter
“Printing CL Command Descriptions” in Chapter 1.
Q are searched except for the following:
#CGULIB #DFULIB #RPGLIB #SEULIB
Required Parameter #COBLIB #DSULIB #SDALIB
CMD Although the following Qxxx libraries are provided
Specifies the qualified names of up to 50 CL commands by IBM, they typically contain user data that
for which specified programs are searched and printed in changes frequently. Therefore, these libraries are
a command usage report. The system searches the considered user libraries and are also searched:
specified programs for every occurrence of each library- | QDSNX QPFRDATA QUSRBRM QUSRSYS
name/command-name character string you specify. | QGPL QRCL QUSRIJS QUSRVxRxMx
The name of the command can be qualified by one of | QGPL38 QS36F QUSRINFSKR
| QMQMDATA QUSER38 QUSRNOTES
the following library values:
| QMQMPROC QUSRADSM QUSRRDARS
*LIBL: All libraries in the job's library list are Note: A different library name, of the form
searched until the first match is found. QUSRVxRxMx, can be created by the user
library-name: Specify the name of the library to be for each release that IBM supports. VxRxMx
searched. is the version, release, and modification level
of the library.
command-name: Specify the names of the commands
for which specified programs are searched.
library-name: Specify the name of the library to be
searched.
Optional Parameter
*ALL: All CL programs in the specified library (or all
PGM
libraries identified in the library qualifier) for which the
Specifies the qualified name of the program or the
user has some authority are searched.
generic name of several programs that are searched for
the specified commands. Only the programs and program-name: Specify the name of the program being
searched for the specified command.
generic*-program-name: Specify the name of the objects can be printed only if *ALL or *ALLUSR library
program or the generic name of several programs in the values can be specified for the name. For more infor-
specified library qualifier that are searched for the speci- mation on the use of generic names, refer to “Generic
fied commands. A generic name is a character string of Object Names” in Chapter 2.
one or more characters followed by an asterisk (*); for
example, ABC*. The asterisk substitutes for any valid
characters. A generic name specifies all objects with
Example
names that begin with the generic prefix for which the PRTCMDUSG CMD(CPYF) PGM(PAYROLL/\ALL)
user has authority. If an asterisk is not included with the
generic (prefix) name, the system assumes it to be the This commands searches all CL programs in the library
complete object name. If the complete object name is PAYROLL for the Copy File (CPYF) commands and prints
specified, and multiple libraries are searched, multiple the names of both the commands and the program.
(P) ─────────────────────────────────────────────────────────────────────────────────5%
55──PRTCMNSEC──┬──────────────────────────┬───
│ ┌─\NO──┐ │
└─CHGRPTONLY(──┴─\YES─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
The spooled output file containing the *DEVD, *CTLD and *YES: Only the changed report is printed.
*LIND objects contains two reports. The first report (Full
Report) contains all of the communications objects and prints Example
the security attributes of each object. The second report
PRTCMNSEC
(Changed Report) contains the communications objects that
have changed since the PRTCMNSEC command was last Both the full and change report will be generated for the
run. If the PRTCMNSEC command was not previously run, communication security information.
(P) ─┬──────────────────────────┬───────────────────────5
55──PRTCMNTRC──CFGOBJ(──────configuration-name──)──CFGTYPE(──┬─\LIN─┬──)────
├─\NWI─┤ │ ┌─\PRINT───┐ │
└─\NWS─┘ └─OUTPUT(──┴─\OUTFILE─┴──)─┘
5──┬───────────────────────────────────────────┬──┬───────────────────────────────────────────┬──┬───────────────────────┬──────5
│ ┌─\LIBL/────────┐ │ │ ┌─\FIRST──────┐ ┌─\REPLACE─┐ │ │ ┌─\EBCDIC─┐ │
└─OUTFILE(──┼───────────────┼──file-name──)─┘ └─OUTMBR(──┼─────────────┼──┴─\ADD─────┴──)─┘ └─CODE(──┼─\ASCII──┼──)─┘
├─\CURLIB/──────┤ └─member-name─┘ └─\CALC───┘
└─library-name/─┘
5──┬──────────────────────────────┬──┬────────────────────────────────────┬──┬────────────────────────┬─────────────────────────5
│ ┌─\ALL──────┐ │ │ ┌─\ALL────────────┐ │ │ ┌─\NO──┐ │
(1) ┘ └─SLTCTLD(──┴─controller-name─┴──)───
└─SLTLIND(──┴─line-name─┴──)─── (2) ┘ └─FMTSNA(──┴─\YES─┴──)───
(3) ┘
5──┬─────────────────────────┬──┬────────────────────────────┬──┬───────────────────────────┬──┬──────────────────────────┬─────5
| │ ┌─\NO──┐ │ │ ┌─\LINTYPE─┐ │ │ ┌─\NO──┐ │ │ ┌─\NO──┐ │
| (4, 3) ┘ └─FMTTCP(──┼─\YES─────┼──)───
└─FMTRR(──┴─\YES─┴──)───── (3) ┘ └─FMTUI(──┴─\YES─┴──)───────
(3, 5, 6) ┘ └─FMTMAC(──┴─\YES─┴──)─────
(3, 5) ┘
| └─\NO──────┘
5──┬──────────────────────────┬──┬──────────────────────────┬──┬──────────────────────────┬──┬────────────────────────┬─────────5
│ ┌─\NO──┐ │ │ ┌─\NO──┐ │ │ ┌─\YES─┐ │ │ ┌─\NO──┐ │
(3, 7) ┘ └─FMTCCD(──┴─\YES─┴──)─────
└─FMTETH(──┴─\YES─┴──)───── (3, 8) ┘ └─FMTBCD(──┴─\NO──┴──)─────
(3, 5) ┘ └─EXCLMI(──┴─\YES─┴──)───
(3) ┘
5──┬──────────────────────────┬──┬─────────────────────────────────────────────────────┬──┬───────────────────────────┬─────────5
| │ ┌─\NO──┐ │ │ ┌─\ALL─────────┐ ┌─\ALL─────────┐ │ │ ┌─\YES─┐ │
| (3, 9) ┘ └─TCPIPADR(──┴─IP-address-1─┴──┴─IP-address-2─┴──)────
└─FMTLMI(──┴─\YES─┴──)───── (10) ┘ └─FMTLCP(──┴─\NO──┴──)──────
(3, 11) ┘
5──┬───────────────────────────┬───────────────────────────────────────────────────────────────────────────────────────────────5%
| │ ┌─\YES─┐ │
| (3, 11) ┘
└─FMTNCP(──┴─\NO──┴──)──────
Notes:
P All parameters preceding this point can be specified in positional form.
2 This option is valid only for the following controllers: ASYNC, X.25, ISDN data link control (IDLC), synchronous data link
4 This option is valid only for LANs, SDLC, IDLC, ISDN, and X.25.
*YES: Only Integrated Services Digital Network (ISDN) IP-address-2: Specify the address of the system for
signaling data is formatted. which communications between this system and the
systems specified on the IP address 1 element are
FMTBCD printed.
Specifies whether broadcast data and data received con-
taining destination MAC addresses is formatted. | FMTLCP
| Specifies whether Link Control Protocol (LCP) data is
*YES: Broadcast data is formatted.
| included in the formatted communications trace.
*NO: Broadcast data is not formatted.
| Note: If FMTLCP, FMTNCP, and FMTTCP are all
EXCLMI | specified *NO when formatting data for a Point-
Specifies whether to exclude local management interface | to-Point Protocol (PPP) line, then asynchronous
(LMI) data from the formatted output. | and unrecognized data will be placed in the
| spooled file. If all are specified *YES (or
*NO: LMI data is not excluded from the formatted
| *LINTYPE for FMTTCP), then all PPP line trace
output.
| data is formatted and placed in the spooled file.
*YES: LMI data is excluded from the formatted output.
| *YES: LCP data is formatted.
FMTLMI | *NO: LCP data is not formatted.
| Specifies whether LMI data is formatted.
| FMTNCP
*NO: LMI data is not formatted.
| Specifies whether Network Control Protocol (NCP) data
*YES: LMI data is formatted. | is included in the formatted communications trace.
Note: You cannot specify *YES on both the EXCLMI | *YES: NCP data is formatted.
and FMTLMI parameters.
| *NO: NCP data is not formatted.
TCPIPADR
Specifies an internet address pair for which TCP/IP data Example
is formatted. Any values that are valid for IP address 1
are also valid for IP address 2. PRTCMNTRC CFGOBJ(\QESLINE) CFGTYPE(\LIN)
The internet address is specified in the form This command prints communications trace data for line
nnn.nnn.nnn.nnn, where nnn is a decimal number description QESLINE.
(P) ────────────────────────────────────────────────────────────────────────────5%
55──PRTDEVADR──CTLD(──controller-description──)────
Note:
P All parameters preceding this point can be specified in positional form.
(P) ──┬─────────────────────────────┬───
55──PRTDOC──┬────────────────────────────┬──┬──────────────────────────┬─── (K) ─────────────────5
│ ┌─\PRV──────────┐ │ │ ┌─\PRV────────┐ │ │ ┌─\NO──────┐ │
└─DOC(──┼─\ALL──────────┼──)─┘ └─FLR(──┴─folder-name─┴──)─┘ (1) ─┼─\YES─────┼──)─┘
└─OPTIONS(───
└─document-name─┘ ├─\PRTFILE─┤
└─\OUTFILE─┘
5──┬─────────────────────────────────────────────────────────────────────────────┬──────────────────────────────────────────────5
│ ┌─QSYSPRT─────────────────────────────────────┐ │
│ │ ┌─\LIBL/────────┐ │ │
├─PRTFILE(──┴─┼───────────────┼──printer-device-file-name─┴──)────────────────┤
│ ├─\CURLIB/──────┤ │
│ └─library-name/─┘ │
│ ┌─\PRV──────────────────────────────────┐ │
│ │ ┌─\LIBL/────────┐ │ │
└─OUTFILE(──┴─┼───────────────┼──database-file-name─┴──)──┤ OUTFILE Details ├─┘
├─\CURLIB/──────┤
└─library-name/─┘
5──┬──────────────────────────────────────────────────┬──┬─────────────────────────┬────────────────────────────────────────────5
│ ┌─\SAME──┐ │ │ ┌─\SAME──┐ │
(2) ─┼─\──────┼──)──┬────────────────────┬─┘ └─MRGTYPE(──┼─\QRY───┼──)─┘
└─OUTPUT(───
└─\PRINT─┘ └─┤ OUTPUT Details ├─┘ ├─\DOC───┤
├─\FILE──┤
└─\BLANK─┘
5──┬───────────────────────────────────────────────────────────────────────────────────┬──┬──────────────────────────┬──────────5
│ ┌─\SAME────────────────────────────────────┐ │ │ ┌─\SAME─┐ │
│ │ ┌─\LIBL/────────┐ │ │ └─MLTLINRPT(──┼─\YES──┼──)─┘
(3)
├─QRYDFN(────┴─┼───────────────┼──query-definition-name─┴──)────────────────────────┤ └─\NO───┘
│ └─library-name/─┘ │
│ ┌─\SAME─────────┐ ┌─\SAME───────┐ │
(4) ─┴─document-name─┴──)──DTAFLR(──┴─folder-name─┴──)──────────────────────┤
├─DTADOC(───
│ ┌─\SAME────────────────────────┐ │
│ │ ┌─\LIBL/────────┐ │ ┌─\SAME────────────┐ │
(5)
└─DTAFILE(────┴─┼───────────────┼──file-name─┴──)──DTAMBR(──┼─\FILE────────────┼──)─┘
├─\CURLIB/──────┤ ├─\FIRST───────────┤
└─library-name/─┘ ├─\LAST────────────┤
└─data-member-name─┘
5──┬─────────────────────────┬──┬─────────────────────────┬──┬─────────────────────────┬──┬───────────────────────────┬─────────5
│ ┌─\SAME─┐ │ │ ┌─\SAME─┐ │ │ ┌─\SAME─┐ │ │ ┌─\SAME─┐ │
└─ADJLINES(──┼─\YES──┼──)─┘ └─ADJPAGES(──┼─\YES──┼──)─┘ └─ALWWIDOW(──┼─\YES──┼──)─┘ └─RENUMBER(─── (6) ─┼─\YES──┼──)─┘
└─\NO───┘ └─\NO───┘ └─\NO───┘ └─\NO───┘
5──┬──────────────────────────┬──┬────────────────────────┬──┬───────────────────────────┬──┬───────────────────────┬───────────5
│ ┌─\SAME─┐ │ └─SYMBOLS(──┬─\SAME─┬──)─┘ │ ┌─\SAME─┐ │ │ ┌─\SAME─┐ │
└─PRTCHGSYM(──┼─\YES──┼──)─┘ └─value─┘ └─DRAFTSPACE(──┼─\YES──┼──)─┘ └─LINNBR(──┼─\YES──┼──)─┘
└─\NO───┘ └─\NO───┘ └─\NO───┘
5──┬────────────────────────┬──┬───────────────────────────┬──┬─────────────────────────────────────────┬───────────────────────5
│ ┌─\SAME─┐ │ │ ┌─\SAME─┐ │ │ ┌─\SAME────────────────────┐ │
└─RESOLVE(──┼─\YES──┼──)─┘ └─LEFTSPACES(──┴─value─┴──)─┘ └─CHRID(──┼─\BLANK───────────────────┼──)─┘
└─\NO───┘ └─character-set──code-page─┘
5──┬──────────────────────────┬──┬───────────────────────────────┬──┬─────────────────────────────┬──┬─────────────────────┬────5
│ ┌─\SAME─┐ │ │ ┌─\SAME─────────┐ │ │ ┌─\SAME───────┐ │ │ ┌─\SAME─┐ │
└─SAVOUTPUT(──┼─\YES──┼──)─┘ └─SAVDOC(──┼─\BLANK────────┼──)─┘ └─SAVFLR(──┼─\BLANK──────┼──)─┘ └─JOBQ(──┼─\YES──┼──)─┘
└─\NO───┘ └─document-name─┘ └─folder-name─┘ └─\NO───┘
5──┬───────────────────────────────────────────────────────┬──┬───────────────────────┬──┬───────────────────────┬──────────────5
│ ┌─\SAME───────────────────────────────────┐ │ │ ┌─\SAME─┐ │ │ ┌─\SAME─┐ │
│ │ ┌─\LIBL/────────┐ │ │ └─SNDMSG(──┼─\YES──┼──)─┘ └─CNLERR(──┼─\YES──┼──)─┘
└─JOBD(──┴─┼───────────────┼──job-description-name─┴──)─┘ └─\NO───┘ └─\NO───┘
└─library-name/─┘
5──┬─┬────────────────────────────────────────────────────────────┬───────────┬──┬──────────────────────────┬───────────────────5
│ │ ┌─\PAGERANGE──┐ ┌─\PAGERANGE──┐ │ │ │ ┌─\SAME─┐ │
│ └─STRPAGE(──┼─\SAME───────┼──)──ENDPAGE(──┼─\SAME───────┼──)─┘ │ └─LBLACROSS(──┴─value─┴──)─┘
│ ├─\FIRST──────┤ ├─\FIRST──────┤ │
│ ├─\LAST───────┤ ├─\LAST───────┤ │
│ └─page-number─┘ ├─\STRPAGE────┤ │
│ └─page-number─┘ │
└───┬──────────────────────────────────────────────────────────────────┬───┘
│ ┌─\SAME──────────────────────────────────────┐ │
│ │ ┌──
────────────────────────────────────────┐ │ │
└─PAGERANGE(──┴──6─(──┬─\FIRST──────┬──┬─\FIRST──────┬──)─┴─┴───
(7) ──)─┘
├─\LAST───────┤ ├─\LAST───────┤
└─page-number─┘ ├─\STRPAGE────┤
└─page-number─┘
5──┬─────────────────────────┬──┬──────────────────────────┬──┬────────────────────────┬──┬───────────────────────────┬────────5%
│ ┌─\SAME─┐ │ │ ┌─\SAME─┐ │ │ ┌─\SAME─┐ │ │ ┌─\SAME─┐ │
└─LBLWIDTH(──┴─value─┴──)─┘ └─SHEETFEED(──┼─\YES──┼──)─┘ └─LBLDOWN(──┴─value─┴──)─┘ └─SHFLEFTMAR(──┼─\YES──┼──)─┘
└─\NO───┘ └─\NO───┘
OUTFILE Details:
┌─\FIRST──────┐ ┌─\REPLACE─┐ ┌─\PRV───┐ ┌─\PRV───┐ ┌─\PRV─┐
├──OUTMBR(──┼─────────────┼──┼──────────┼──)──CURSTS(──┼────────┼──)──NEWSTS(──┼────────┼──)──OUTDTATYP(──┼──────┼──)───────────5
├─\PRV────────┤ └─\ADD─────┘ ├─\NOCHK─┤ ├─\NOCHG─┤ ├─\ALL─┤
└─member-name─┘ └─value──┘ └─value──┘ └─\IDP─┘
┌─\NO──┐
5──DLTDOC(──┼──────┼──)─────────────────────────────────────────────────────────────────────────────────────────────────────────┤
└─\YES─┘
OUTPUT Details:
┌─\SAME────────┐ ┌─\SAME────────────────────────────────────┐ ┌─\SAME───────────┐
├──DEV(──┼──────────────┼──)──OUTQ(──┼──────────────────────────────────────────┼──)──SPLFILE(──┼─────────────────┼──)──────────5
├─\USRPRF──────┤ ├─\DEV─────────────────────────────────────┤ ├─\FILE───────────┤
├─\SYSVAL──────┤ ├─\FILE────────────────────────────────────┤ ├─\DOC────────────┤
├─\WRKSTN──────┤ ├─\WRKSTN──────────────────────────────────┤ └─spool-file-name─┘
└─printer-name─┘ │ ┌─\LIBL/────────┐ │
└─┼───────────────┼──┬───────────────────┬─┘
└─library-name/─┘ └─output-queue-name─┘
┌─\SAME─────┐ ┌─\SAME─┐ ┌─\SAME───┐ ┌─\SAME─┐
5──FORMTYPE(──┼───────────┼──)──COVERPAGE(──┼───────┼──)──PRTQLTY(──┼─────────┼──)──COPIES(──┼───────┼──)───────────────────────5
├─\STD──────┤ ├─\YES──┤ ├─\LETTER─┤ └─value─┘
└─form-type─┘ └─\NO───┘ ├─\TEXT───┤
└─\DRAFT──┘
┌─\SAME───┐ ┌─\SAME─┐ ┌─\SAME─┐ ┌─\PRV─┐
5──DUPLEX(──┼─────────┼──)──AUTOBIND(──┼───────┼──)──HOLD(──┼───────┼──)──PRTERRLOG(──┼──────┼──)───────────────────────────────5
├─\TUMBLE─┤ ├─\YES──┤ ├─\YES──┤ ├─\YES─┤
├─\YES────┤ └─\NO───┘ └─\NO───┘ └─\NO──┘
└─\NO─────┘
┌─\SAME───────────┐ ┌─\SAME─┐
5──ERRFORM(──┼─────────────────┼──)──LARGEPRINT(──┼───────┼──)──────────────────────────────────────────────────────────────────┤
├─\STD────────────┤ ├─\YES──┤
└─error-form-name─┘ └─\NO───┘
Notes:
P All parameters preceding this point can be specified in positional form.
7 A maximum of 7 repetitions
Purpose Note: To see the parameter and value descriptions for this
command, refer to the online help text. For more
The Print Document (PRTDOC) command permits the user information about printing the help text, refer to
to print a document using the word processing function of “Printing CL Command Descriptions” in Chapter 1.
OfficeVision
This command also permits the user to override all print Optional Parameters
option values that are currently stored with a document.
DOC
When a document is created, a set of default print options is
Specifies the name of the document to print.
associated with that document. If the user wants to override
one or more of the parameters in this print command, the *PRV: The name used in the previous session is used.
user must select OPTIONS(*YES) so that the print options *ALL: All documents to which the user is authorized are
appear on the display. When the print options appear, any printed to a database file. This is valid only when the
of the print parameters can be changed. The user can over- output is directed to an OUTFILE.
ride one or all of the print option parameters with this
command. More information on printing documents is in the document-name: Specify the name of the document that
Using OfficeVision/400 Word Processing book. is printed.
QSYSPRT: The document is printed using the system Element 1: Member to Receive Output
printer. This value overrides the printer name specified *FIRST: The first member in the file receives the output.
in the print options associated with the document. If OUTMBR(*FIRST) is specified and the member does
The name of the printer device file can be qualified by not exist, the system creates a member with the name of
one of the following library values: the file specified on the OUTFILE parameter.
*PRV: The name used in the previous session is used.
*LIBL: All libraries in the job's library list are
searched until the first match is found. member-name: Specify the file member that receives
the output. If OUTMBR(member-name) is specified and
*CURLIB: The current library for the job is
the member does not exist, the system creates it.
searched. If no library is specified as the current
library for the job, the QGPL library is used. Element 2: Operation to Perform on Member
library-name: Specify the name of the library to be *REPLACE: The system clears the existing member
searched. and adds the new records.
printer-device-file-name: Specify the name of the printer *ADD: The system adds the new records to the end of
file to use for this PRTDOC request. This value over- the existing records.
rides the printer file name specified in the print options
CURSTS
associated with the document.
Specifies the value the document Interchange Document
OUTFILE Profile (IDP) status field must have before the document
Specifies the qualified name of the database file where may be printed to the database file. This field is 20
the displayed information is stored. If the specified file
characters long and is valid only if OUTFILE output is *PRINT: The output is printed with the job's spooled
requested. output.
Note: If the name of the document is specified in lower- DEV
case letters, the AS/400 system automatically Specifies the name of the selected printer.
shifts the name to uppercase letters. If the docu-
*SAME: The name of the printer specified in the docu-
ment name is to remain in lowercase letters, the
ment print options does not change.
name must be enclosed in apostrophes.
*USRPRF: The printer ID indicated in the user profile is
*PRV: The name used in the previous session is used.
used to print the document.
*NOCHK: The status field is not checked before printing
*SYSVAL: The value specified in the system value
this document to a database file.
QPRTDEV is used.
value: Specify the value to which the status field must
*WRKSTN: The printer assigned to the user's work
be equal before the document is printed to the database.
station is used to print the document.
NEWSTS
printer-name: Specify the name of the printer to use to
Specifies the value to which the document IDP status
print the document.
field value is set after the document has been printed to
the database file. If a NEWSTS value is specified, the OUTQ
user must have at least *CHANGE authorization to the Specifies the qualified name of the output queue.
document. This field is 20 characters long and is valid
*SAME: The output queue value specified in the docu-
only if OUTFILE output is requested.
ment print options does not change.
*PRV: The name used in the previous session is used.
*DEV: The output queue specified on the PRTDEV
*NOCHG: The status field is not changed after printing parameter is used.
this document to a database file.
*FILE: The output queue and output queue library
value: Specify the value to which the status field is set values are based on:
after the document is printed to a database file.
1. If the PRTFILE parameter is specified, the values
OUTDTATYP from the specified printer device are used.
Specifies whether the entire document, or just the IDP
2. If the PRTFILE parameter is not specified, the
information, is printed to the database file. This is valid
values from the printer file prompt on the document
only if OUTFILE output is requested.
print options are used.
*PRV: The name used in the previous session is used.
*WRKSTN: The output queue assigned to the user's
*ALL: The entire document is printed to a database file. work station is used.
*IDP: Only the IDP information is printed to a database The name of the output queue can be qualified by one
file. of the following library values:
DLTDOC *LIBL: All libraries in the job's library list are
Specifies whether a document is deleted after it has searched until the first match is found.
been printed to the database file. This is valid only if
*CURLIB: The current library for the job is
OUTFILE output is selected.
searched. If no library is specified as the current
Note: The user must be the owner of the document or library for the job, the QGPL library is used.
have *ALL authority to delete it.
library-name: Specify the name of the library to be
*NO: The document is not deleted after being printed to searched.
the database file.
output-queue-name: Specify the name of the output
*YES: The document is deleted after being printed to
queue to use to hold the output until it is ready to print.
the database file.
SPLFILE
OUTPUT
Specifies the name of the output file in which spooled
Specifies whether the output from the command is
files are kept.
shown at the requesting workstation or printed with the
job's spooled output. More information on this param- *SAME: The name of the output file specified in the
eter is in Appendix A, “Expanded Parameter document print options does not change.
Descriptions.” *FILE: The name chosen for the output file is the name
*SAME: The output device specified in the document for the printer file being used.
print options does not change. *DOC: The document name is used for the spool file
*: The document is shown on the display. name. However, if the document name is longer than
*STD: The standard form type is used. The output is *NO: The document is printed on one side of the paper.
printed on the form type specified in the printer file for
AUTOBIND
the printer selected. The printer file contains the infor-
Specifies whether the left and right margins of the even
mation controlling how the document is printed on a par-
pages will line up with the left and right margins of the
ticular printer.
odd pages when both sides of the paper are being
form-type: Specify the type of form to use. Valid values printed.
range from 1 through 10 alphanumeric characters.
*SAME: The automatic binding value specified in the
Note: Lowercase, blanks, or special characters must be document print options does not change.
enclosed in apostrophes. For example, a host
*YES: The document is adjusted for binding.
system form type is entered as FORMTYPE(' ').
The value is returned by the host system in a *NO: The document is not adjusted for binding.
forms mount message.
HOLD
COVERPAGE Specifies whether a print job is put on hold. Documents
Specifies whether a cover page is printed. The cover are held on the output queue and can be released to
page includes such reference items as: print or deleted. This parameter allows printing of
several documents together by putting them on the
Document name output queue before releasing them to print.
Folder name
*SAME: The hold value specified in the document print
Document description
options does not change.
Subject
Reference, and *YES: The print job is held.
Authors' names
*NO: The print job is not held.
*SAME: The cover page value specified in the docu-
PRTERRLOG
ment print options does not change.
Specifies whether a document error log is included as
*YES: The cover page is printed. part of the information printed with the document.
*NO: The cover page is not printed. *PRV: The value used in the previous (last) PRTDOC
request for this user is used.
PRTQLTY
Specifies the print quality used to print the document. *YES: The error log is printed with the document.
*SAME: The print quality value specified in the docu- *NO: The error log is not printed with the document.
ment print options does not change.
ERRFORM
*LETTER: The letter quality (highest quality) is used. Specifies the type of form on which to print the error log.
*TEXT: The text quality setting is used. *SAME: The error form value specified in the document
print options does not change.
*DRAFT: The draft quality (lowest quality) setting is
used. *STD: The standard form type is used. The output is
printed on the form type specified in the printer file for
COPIES
the selected printer. The printer file contains the infor-
Specifies the number of copies to print. This parameter
mation controlling how the document is printed on a par-
only applies to spooled files.
ticular printer.
*SAME: The number of copies specified in the docu- error-form-name: Specify the name of the form on which
ment print options does not change.
to print the error log.
value: Specify a value ranging from 1 through 99 indi-
cating the number of copies to print.
*DOC: The data stored in a document is merged. *CURLIB: The current library for the job is
searched. If no library is specified as the current
*FILE: The data stored in a file is merged.
library for the job, the QGPL library is used.
*BLANK: No data is merged. library-name: Specify the name of the library to be
QRYDFN searched.
Specifies the name of the query that defines the data to
file-name: Specify the name of the file that contains the
be merged. This parameter is valid only when
data to merge.
MRGTYPE(*QRY)is selected.
DTAMBR
*SAME: The query name specified in the document
Specifies the name of the member that contains the data
print options does not change.
to merge. This parameter is valid only when
The name of the query can be qualified by one of the MRGTYPE(*FILE) is selected.
following library values:
*SAME: The member name specified in the document
*LIBL: All libraries in the job's library list are print options does not change.
searched until the first match is found.
*FILE: The member with the same name as the
*CURLIB: The current library for the job is member name is used.
searched. If no library is specified as the current
*FIRST: The first member is used.
library for the job, the QGPL library is used.
*LAST: The last member is used.
library-name: Specify the name of the library to be
searched. data-member-name: Specify the name of the member
that contains the data to merge.
query-definition-name: Specify the query name used to
move the merged data. MLTLINRPT
Specifies whether a multiple line report is created. In
DTADOC this report, data field instructions are merged to create
Specifies the name of the document that contains the records with several lines of output.
data being merged. This parameter is valid only when
*SAME: The multiple-line-report option specified in the
MRGTYPE(*DOC) is selected.
document print options is used.
*SAME: The document name specified in the document
*YES: A multiple line report is created.
print options does not change.
*NO: A multiple line report is not created.
document-name: Specify the name of the document by
selecting a value ranging from 1 to 12 alphanumeric ADJLINES
characters. If more than 8 characters are used, the Specifies whether the line endings in a printed document
ninth character must be a period (.) followed by a 1 to 3 are adjusted. The line endings are adjusted according
character extension. to the specifications on the Line Spacing/Justification
options display. This parameter is useful when printing
DTAFLR
a document that has been merged, has instructions, has
Specifies the name of the folder that contains the docu-
display attributes that do not print spaces, or that uses a
ment to merge. This parameter is valid only if
proportionally spaced font.
MRGTYPE(*DOC) is selected.
*SAME: The line ending adjustment specified in the value: Specify up to 5 change symbol characters to
document print options does not change. appear in the left margin of the document.
*YES: The line endings are adjusted. DRAFTSPACE
*NO: The line endings are not adjusted. This special Specifies whether the spacing value in the document
value is used when text is to be printed out in the same can be adjusted. For example, if 3 (triple) is entered on
way that it was typed. the Line Spacing prompt, the double spacing value is 6,
and 5 blank lines are printed between each line in the
ADJPAGES text of the document. Nevertheless, the document is still
Specifies whether the page endings in a printed docu- paginated using the value specified in the Line Spacing
ment are adjusted. The page ending adjustment is prompt. Therefore, depending on the amount of text
specified on the first typing line and last typing line being printed on a page, one page may print over onto a
prompts on the Page Layout/Paper Options display. second page.
*SAME: The page ending adjustment specified in the *SAME: The draft space value specified in the docu-
document print options does not change. ment print options does not change.
*YES: The page endings are adjusted. *YES: The space value in the document is doubled.
*NO: The page endings are not adjusted. *NO: The space value in the document is not doubled.
ALWWIDOW LINNBR
Specifies whether the document's page endings are Specifies whether line numbers are printed in the docu-
determined by the exact number of lines per page speci- ment. The line numbers begin with 1 on the first page of
fied on the Page Layout/Paper Options display. the document. Line numbers are not printed in headers
*SAME: The allow widow lines value specified in the or footers.
document print options does not change. *SAME: The line numbers value specified in the docu-
*YES: The page endings are determined by the exact ment print options does not change.
number of lines per page. *YES: The line numbers are printed in the document.
*NO: The page endings are not determined by the *NO: The line numbers are not printed in the document.
exact number of lines per page.
RESOLVE
RENUMBER Specifies whether the instructions placed in the docu-
Specifies whether the pages are renumbered when the ment are processed. For example, the Date (.date)
document is printed. instruction is resolved to the actual date, which, in this
*SAME: The renumber system page numbers value example, is 04/03/62.
specified in the document print options does not change. *SAME: The resolve value specified in the document
*YES: The page numbers are renumbered when the print options does not change.
document is printed. *YES: The instructions placed in the document are
*NO: The page numbers are not renumbered when the resolved.
document is printed. *NO: The instructions placed in the document are not
resolved. For example, the Date instruction (.date)
PRTCHGSYM
prints as *date.
Specifies whether change symbols are printed in the left
margin of the document. Change symbols are used to LEFTSPACES
indicate all lines have been revised. Specifies whether the left margin of the document is
*SAME: The print-change-symbol value specified in the increased.
document print options does not change. *SAME: The left-spaces value specified in the docu-
*YES: The change symbols are printed in the left ment print options does not change.
margin of the document. value: Specify a value, ranging from 0 through 99, for
*NO: The change symbols are not printed in the left the number of spaces to add to the left margin in the
margin of the document. printed document.
SYMBOLS CHRID
Specifies whether 5 different kinds of change symbols Specifies the character identifier (graphic character set
appear in the left margin of the document. and code page) for the file. This parameter allows
printing of text that is in different character identifier
*SAME: The change symbol value specified in the doc-
(graphic character set and code page) coding. The
ument print options does not change.
value specified on this parameter is used to instruct the
printer device to interpret the hexadecimal byte string to
print the same characters that were intended when the *SAME: The place on the job queue that is specified in
text was created. More information about the character the document print options does not change.
identifier is in the Printer Device Programming book. A
*YES: The printing of the document is placed in the job
list of valid CHRID values and applicable printers is in
queue.
the "CHRID Values and Applicable Printers (CHRID
parameter)" table in Appendix B, “Font, Character Identi- *NO: The printing of the document is not placed in the
fier, and Other Values Supported for Different Printers.” job queue.
Note: If the STRPAGE(page-number) value specified is *STRPAGE: The end page value is the same as the
larger than the ENDPAGE(page-number) value start page value. Only one page is printed.
specified, the entire document is printed.
page-number: Specify the page on which to stop
*SAME: The start page specified in the document print printing. Valid values range from 0.01 through 9999.99.
options does not change.
LBLACROSS
Note: If STRPAGE(*SAME) is specified and additional Specifies the number of labels to print across the page.
page ranges exist in the document print options,
*SAME: The label-across-the-page value specified in
an error message is sent and the document is
the document print options does not change.
not printed.
*FIRST: Printing is started on the first page of the docu-
value: Specify a value, ranging from 1 through 99, that
indicates the number of labels to print across the page.
ment.
*LAST: Printing is started on the last page of the docu- LBLWIDTH
ment. Specifies how wide to make the label. The width of a
label is the number of characters from the left edge of
page-number: Specify the page on which to begin the first label to the left edge of the next label, including
printing. Valid values range from 0.01 through 9999.99.
the blank spaces between the labels. If the width speci-
ENDPAGE fied is larger than the margins specified for the docu-
Specifies the page on which printing ends. ment, the margins are used as the width.
*PAGERANGE: The pages specified on the *SAME: The label width value specified in the docu-
PAGERANGE parameter are printed. ment print options does not change.
*SAME: The end page value specified in the document value: Specify a value, ranging from 2 through 198, that
print options does not change. indicates the label width.
*NO: The left margin is not shifted when text exceeds Example 3: Printing Document Error Log
the right margin. Any text exceeding the right margin is PRTDOC DOC(MYDOC) FLR(MYFLR) OPTIONS(\NO)
truncated. PRTERRLOG(\YES)
(P) ─┬───────────────────────────────────────┬──┬───────────────────────────────────┬───
55──PRTDSKINF──RPTTYPE(──┬─\LIB─┬──)──── (3) ────5
├─\FLR─┤ │ ┌─\ALL─────────────────┐ │ │ ┌─\ALL─────────────────┐ │
├─\OWN─┤ (1) ──)──┤ └─OBJ(──┼─\NONE────────────────┼──)─┘
├─LIB(──┼─library-name─────────┼───
├─\OBJ─┤ │ └─generic-library-name─┘ │ ├─object-name──────────┤
└─\SYS─┘ │ ┌─\ALL────────────────┐ │ └─generic\-object-name─┘
├─OWNER(──┼─owner-name──────────┼──)──── (2) ┤
│ └─generic\-owner-name─┘ │
│ ┌─\ALL─────────────────┐ │
├─FLR(──┼─folder-name──────────┼──)────(3) ─┤
│ └─generic\-folder-name─┘ │
│ ┌─\ALL───────────────────┐ │
└─DOC(──┼─document-name──────────┼──)───┘ (3)
└─generic\-document-name─┘
5──┬───────────────────────────────────┬──┬───────────────────────┬──┬────────────────────────────┬────────────────────────────5%
│ ┌─\ALL─────────────┐ │ │ ┌─ð────┐ │ │ ┌─\SIZE───┐ │
│ │ ┌──
─────────┐ │ (6, 7) ──)─┘
│ └─MINSIZE(──┴─size─┴──)─┘ └─SORT(──┼─\OWNER──┼─────
6 (4, 5)
└─OBJTYPE(──┴───objtype─┴──────┴──)─┘ ├─\LSTCHG─┤
├─\LSTUSE─┤
└─\NAME───┘
Notes:
P All parameters preceding this point can be specified in positional form.
4 A maximum of 60 repititions
5 A list of the valid OS/400 object types for this command is in Appendix A.
6 This parameter is not valid if *OWN is specified on the RPTTYPE parameter, unless the OBJ parameter is used with a value
of generic names, refer to “Generic Object Names” in printed on all the specified object types within the library
Chapter 2. or controlled by the owner. If an object name is speci-
fied, information on all object types within that name,
OWNER
within the library, or controlled by the owner is printed. If
Specifies the names of the owners (user profiles) to print
a library or owner is not specified, the report has infor-
information about.
mation on all object types on the system. If an object
*ALL: The report contains information on all user pro- name is specified, information only on object types with
files on the system. that name is printed.
owner-name: Specify the user profile. object-type: Specify a library or owner, then the object
type information is the object type specified within the
generic*-owner-name: Specify the generic user profile.
library or controlled by the owner. If an object is speci-
FLR fied, the report has information on the objects with the
Specifies the names of the folders to print information specified object type within the library or controlled by
about. the owner.
*ALL: The report has information on all user folders on MINSIZE
the system. Specifies the size of the smallest piece of information to
folder-name: Specify the folder name. include. For example, if a library report is requested
without objects, then this size would be the size of the
generic*-folder-name: Specify the generic folder name. smallest library to include. If objects within the library
DOC are requested, then this would be the size of the
Specifies the names of the documents to print informa- smallest object within the library to include.
tion about. 0: All objects are included regardless of size.
*ALL: The report contains information on all documents size: Specify size in thousands of bytes.
in the specified folder.
SORT
document-name: Specify the document by the given Specifies the order in which the information should be
name within the specified folder.
sorted.
generic*-document-name: Specify the documents speci- *SIZE: Information is sorted from large to small.
fied by the generic qualification.
*OWNER: The information is sorted in alphabetical
OBJ order by owner name.
Specifies the names of the objects to print information
*LSTCHG: The information is sorted by last-change
about.
date with the oldest information first.
*ALL: If you specify a library or owner, then the object
*LSTUSE: The information is sorted by last-use date
information is all objects within the library or those con-
with the oldest information first.
trolled by the owner
*NAME: Information is sorted in alphabetical order
*NONE: No library or owner is specified.
according to the report type.
object-name: Specify a library or owner, then the object
information is the object specified by the given name
within the library or controlled by the owner. Example
generic*-object-name: Specify a library or owner, then PRTDSKINF RPTTYPE(\LIB) LIB(\ALL) OBJ(\ALL)
the object information are the objects that meet the SORT(\SIZE)
specified generic qualification within the library or con-
This command prints a library report from database file
trolled by the owner.
QAEZDISK in library QUSRSYS in member QCURRENT,
OBJTYPE containing information about all libraries, objects, and object
Specifies the object types to print information about. types in the libraries. The information is sorted by size and
sent to the printer file QPEZDISK.
*ALL: If you specify a library or owner, information is
(P) ──┬───────────────────────────────────────────┬────────────────────────────────────5
55──PRTERRLOG──┬─────────────────────────┬───
│ ┌─\ALL──────┐ │ │ ┌─\ALL───────────────────────┐ │
└─TYPE(──┼─\ALLSUM───┼──)─┘ │ │ ┌──
─────────────────────┐ │ │
├─\ANZLOG───┤ ├─DEV(─── 6
(1) ─┴───logical-device-name─┴─── (2) ─┴──)─┤
├─\MCH──────┤ │ ┌──
───────────────┐ │
├─\DEV──────┤ └─RSRCNAME(─── 6─resource-name─┴───
(1) ── (2) ──)──────┘
├─\ERRLOGID─┤
└─\VOLSTAT──┘
5──┬─────────────────────────────────────────────┬──┬─────────────────────────┬─────────────────────────────────────────────────5
│ ┌──
──────────────────────┐ │ │ ┌─\CHAR─┐ │
└─ERRLOGID(─── 6─error-log-identifier─┴───
(3) ── (2) ──)─┘ └─PRTFMT(───
(4) ─┴─\HEX──┴──)─┘
5──┬──────────────────────────────────────────────────────────────────────────────────────┬──┬──────────────────────────┬───────5
│ ┌─\AVAIL─────┐ ┌─\CURRENT───┐ │ │ (7) ┐
┌─\PRINT─── │
(5, 6) ─┴─start-time─┴──┴─start-date─┴──)──┬──────────────────────────────────┬─┘ └─OUTPUT(──┴─\OUTFILE─┴──)─┘
└─PERIOD(─────
│ ┌─\AVAIL───┐ ┌─\CURRENT─┐ │
└─(──┴─end-time─┴──┼──────────┼──)─┘
└─end-date─┘
5──┬─────────────────────────────────────────────┬──┬───────────────────────────────────────────┬───────────────────────────────5
│ ┌─\LIBL/────────┐ │ │ ┌─\FIRST──────┐ ┌─\REPLACE─┐ │
(8) ─┼───────────────┼──file-name──)─┘ └─OUTMBR(──┴─member-name─┴──┼──────────┼──)─┘
└─OUTFILE(───
├─\CURLIB/──────┤ └─\ADD─────┘
└─library-name/─┘
5──┬────────────────────────────┬──┬───────────────────────────┬──┬───────────────────────────────────┬─────────────────────────5
(9) ─volume-type──)─┘ └─MODEL(───
└─VOLTYPE(─── (9) ─model-number──)─┘ │ ┌─\ALL───────────────┐ │
│ │ ┌──
─────────────┐ │ │
(9) 6 (2)
└─VOL(────┴───volume-name─┴────┴──)─┘
5──┬────────────────────────────┬──┬───────────────────────────────┬──┬───────────────────────────┬─────────────────────────────5
│ ┌─\KEEP───┐ │ │ ┌─\LIFETIME─┐ │ │ ┌─\ALL───┐ │
(9) ─┴─\DLT────
└─VOLSTAT(─── (10) ┴──)─┘ └─VOLSTATTYP(──┴─\SESSION──┴──)─┘ └─SELECT(────
(11) ─┼─\PRC───┼──)─┘
├─\MEDIA─┤
├─\LWS───┤
├─\CMN───┤
├─\PWR───┤
├─\LPP───┤
└─\LIC───┘
5──┬────────────────────────────┬──────────────────────────────────────────────────────────────────────────────────────────────5%
│ ┌─\DATETIME─┐ │
(12) ─┼─\TIME─────┼──)─┘
└─SORT(────
├─\DEVADR───┤
├─\ERRTYPE──┤
└─\RSRCNAME─┘
Notes:
1 DEV and RSRCNAME are valid only if TYPE(*DEV) is specified.
2 A maximum of 10 repetitions
5 PERIOD contains 2 lists of 2 elements each. *N must be specified for any element that goes before the value specified.
9 VOLTYPE, MODEL, VOL, VOLSTAT, and VOLSTATTYP are valid only if TYPE(*VOLSTAT) is specified.
TYPE PRTFMT
Specifies the type of error log data from the machine Specifies that the indicated report prints any
error log to print in the spooled printer file. hexadecimal data in character format. This parameter
cannot be specified if TYPE(*VOLSTAT) is specified or if
*ALL: All the error codes in the machine's error log are the OUTFILE parameter is specified.
printed. In addition, the error codes for each subsystem
(for example, direct access storage devices or printers) *CHAR: The report is formatted so that hexadecimal
are printed in summary form. data prints as character data.
*ALLSUM: All the data in the error log is printed in *HEX: The report is formatted so that hexadecimal data
summary form. is printed in hexadecimal format.
*ANZLOG: A one-line summary is created for each Note: Specifying PRTFMT(*HEX) can cause spooling
entry in the error log. or printing of large amounts of data. This can
impact overall system performance.
*MCH: Only the error data produced by machine checks
is printed. PERIOD
Specifies the period of time for which the error log data
*DEV: Only the error data produced by the devices
is printed. This parameter is specified as two sets of
specified on the DEV or RSRCNAME parameters are
two values each.
printed.
Element 1: Start Time
*ERRLOGID: Only the error data with the specified
error log record is printed. If this value is specified, the *AVAIL: The error data that is available for the speci-
ERRLOGID parameter must also be specified. It is fied starting date is printed.
ignored for other request types. start-time: Specify the start time on the specified start
*VOLSTAT: If this value is specified and if date for which the error data is printed. The time is
OUTPUT(*PRINT) is specified, the tape or diskette specified in 24-hour format with or without a time sepa-
volume 'lifetime' statistical data records are printed. If rator as follows:
this value is specified and if OUTPUT(*OUTFILE) is
With a time separator, specify a string of 5 or 8
specified, 'session' volume statistical data records are
digits, where the time separator for the job sepa-
printed.
rates the hours, minutes, and seconds. If you issue
DEV this command from the command line, the string
Specifies the device names for which the user wants the must be enclosed in apostrophes. If a time sepa-
error log data printed. rator other than the separator specified for your job
is used, this command fails.
Note: This parameter is valid only if TYPE(*DEV) is
specified. This parameter cannot be specified if Without a time separator, specify a string of 4 or 6
the RSRCNAME parameter is specified. digits (hhmm or hhmmss) where hh = hours, mm =
minutes, and ss = seconds. Valid values for hh
*ALL: The error log data is printed for all device names.
range from 00 through 23. Valid values for mm and
ss range from 00 through 59.
Element 2: Start Date new records are added. If the member does not exist
and a member name is not specified, the system creates
*CURRENT: The error data that is available for the
a member with the name of the output file specified on
current day and between the specified start and end
the OUTFILE parameter. If an output file member name
times (if specified) is printed.
is specified, but the member does not exist, the system
start-date: Specify the starting date. The date must be creates it.
specified in the job date format.
Element 1: Member to Receive Output
Element 3: End Time
*FIRST: The first member in the file receives the output.
*AVAIL: The error data that is available for the speci- If OUTMBR(*FIRST) is specified and the member does
fied end date is printed. not exist, the system creates a member with the name of
end-time: Specify the ending time for the specified the file specified on the OUTFILE parameter.
ending date that determines the error data that is member-name: Specify the file member that receives
printed. the output. If OUTMBR(member-name) is specified and
Element 4: End Date the member does not exist, the system creates it.
*CURRENT: The error data that is available for the Element 2: Operation to Perform on Member
current day and between the specified start and end *REPLACE: The system clears the existing member
times (if specified) is printed. and adds the new records.
end-date: Specify the end date for which error data is *ADD: The system adds the new records to the end of
printed. The date must be specified in job date format. the existing records.
OUTPUT VOLTYPE
Specifies whether the output from the command is Specifies the volume type of the specified volume identi-
printed with the job's spooled output or directed to a fier. Valid values are 4-digit device type numbers for
database file. More information on this parameter is in cartridge tape, reel tape, or diskette. This parameter
Appendix A, “Expanded Parameter Descriptions.” returns information about all the volumes that use the
*PRINT: The output is printed with the job's spooled same technology as the tape device type that was speci-
output. fied. For example, if 6380 is the specified value for this
parameter, information about all 1/4 inch tape cartridges
*OUTFILE: The output is directed to the database file
on the system is returned.
specified on the OUTFILE parameter.
MODEL
OUTFILE
Specifies the model number of the specified model type.
Specifies the database file to which the report is
This parameter is required if the device type is 9331 and
directed. If the output file already exists, the system
TYPE(*VOLSTAT) is specified.
attempts to use it. Records replace or are added to
existing data in the file member. If the output file does VOL
not exist, the system creates a database file in the spec- Specifies one or more volume identifiers used by the file.
ified library. A member is created for the file with the More information on this parameter is in Appendix A,
name specified in the OUTMBR parameter. “Expanded Parameter Descriptions.”
The name of the file can be qualified by one of the fol- *ALL: Volume statistics are processed for all volumes.
lowing library values:
volume-name: Specify the name of the volume for
*LIBL: All libraries in the job's library list are which statistics are processed. A maximum of 10
searched until the first match is found. volume names can be specified.
Note: If OUTPUT(*OUTFILE) is specified, *DLT cannot *DEVADR: The entries are sorted by the address of the
be specified. device. The summary entries are divided into three
levels: those for which the first two digits of the address
VOLSTATTYP
are the same, those for which the first four digits of the
Specifies the type of volume statistics printed or directed
address are the same, and those for which the first eight
to an output file. This parameter is valid only if
digits of the address are the same.
TYPE(*VOLSTAT) is specified.
*ERRTYPE: The entries are sorted by the severity of
*LIFETIME: Lifetime statistics are printed. Lifetime sta-
the type of error. The more severe error types report at
tistics cannot be placed in an output file.
the top of the list. The summary entries are divided into
*SESSION: Session statistics are directed to the output two levels: those that have a common error type, and
file specified on the OUTFILE parameter. Session sta- those that have a common error type and system refer-
tistics cannot be printed. ence code.
(1) ─┬─\DMP────┬──)────
55──PRTINTDTA──TYPE(─── (P) ─┬────────────────────────────────┬───────────────────────────────────────────────────5
├─\INTCFG─┤ │ ┌─\NONE───────────┐ │
└─\NOTES──┘ └─DMPID(──┴─dump-identifier─┴──)─┘
5──┬────────────────────────────────────────────────────────────────────────────────────┬──────────────────────────────────────5%
│ ┌─\AVAIL─────┐ ┌─\CURRENT───┐ │
(2) ─┴─start-time─┴──┴─start-date─┴──)──┬──────────────────────────────────┬─┘
└─PERIOD(───
│ ┌─\AVAIL───┐ ┌─\CURRENT─┐ │
└─(──┴─end-time─┴──┼──────────┼──)─┘
└─end-date─┘
Notes:
1 If *DMP is specified, the DMPID parameter must be specified.
2 PERIOD contains two lists of two elements each. PERIOD values must be coded in this order, using *N for those not being
specified: (start-time start-date) (end-time end-date). PERIOD is valid only if TYPE(*NOTES) is specified.
Purpose DMPID
Specifies, for internal dump operations only, the dump
The Print Internal Data (PRTINTDTA) command is used pri- identifier associated with the machine internal data that
marily for problem analysis. It writes the machine internal is printed. This parameter must be specified only if
data to a spooled printer file. The data is used to service the TYPE(*DMP) is specified; otherwise, it is ignored. The
system. The names of files produced by this and other com- dump identifier is sent in one of three ways:
mands is in the Programming Reference Summary book.
In a message to the job that issued the
Restrictions: DMPJOBINT command that dumped the internal
data
1. This command is shipped with public *EXCLUDE
In a damage message
authority and the QPGMR, QSYSOPR, QSRV, and
In a device error message or machine function
QSRVBAS user profiles have private authorities to use
check message. The message containing the dump
the command.
identifier may also be sent to the system history log.
2. This command is intended for use by service represen-
tatives only. *NONE: No dump identifier is specified.
Note: To see the parameter and value descriptions for this dump-identifier: Specify the dump identifier of the dump
command, refer to the online help text. For more output that is printed. The identifier specified must
information about printing the help text, refer to contain eight characters.
“Printing CL Command Descriptions” in Chapter 1. PERIOD
Specifies the period of time for which the notes portion
Required Parameters of the machine internal data is printed. This parameter
is valid only if TYPE(*NOTES) is specified; otherwise, it
TYPE is ignored. The following values can be coded in this
Specifies the type of data to be printed. parameter, which contains two sets of two values each.
*DMP: The data to be printed was dumped by a previ- Refer to the syntax diagram for the location of each
ously issued Dump Job Internal (DMPJOBINT) value specified. If this parameter is not specified, all the
command or by the machine when it processes a device available notes for the current date are printed.
error or object damage. The dump identifier of the data Element 1: Starting Time
must be specified on the DMPID parameter.
*AVAIL: The notes that are available from the starting
*INTCFG: The machine internal configuration and date to the ending date (or for the current day only) are
resource information is printed. printed.
*NOTES: The notes portion of the machine internal start-time: Specify the starting time for the specified
data, for the period specified by the PERIOD parameter, starting date for which the user wants the notes printed.
is printed. The time is specified in 24-hour format with or without a
time separator as follows:
Optional Parameters With a time separator, specify a string of 5 or 8
digits, where the time separator for the job sepa-
rates the hours, minutes, and seconds. If you issue *AVAIL: The notes that are available from the starting
this command from the command line, the string date to the ending date (or for the current day only) are
must be enclosed in apostrophes. If a time sepa- printed.
rator other than the separator specified for your job
end-time: Specify the ending time for the specified
is used, this command fails.
ending date that determines the notes that is printed.
Without a time separator, specify a string of 4 or 6
Element 4: Ending Date
digits (hhmm or hhmmss) where hh = hours, mm =
minutes, and ss = seconds. Valid values for hh *CURRENT: The notes that are available for the current
range from 00 through 23. Valid values for mm and day and between the specified starting and ending times
ss range from 00 through 59. (if specified) are printed.
55──PRTIPSCFG──────────────────────────────────────────────────────────────────────────────────────────────────────────────────5%
(P) ─────────────────────────────────────────────────────5%
55──PRTJOBDAUT──LIB(──┬─\LIBL────────┬──)──┬──────────────────────────┬───
├─\USRLIBL─────┤ │ ┌─\NO──┐ │
├─\CURLIB──────┤ └─CHGRPTONLY(──┴─\YES─┴──)─┘
├─\ALL─────────┤
├─\ALLUSR──────┤
└─library-name─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose LIB
Specifies the name of the library to search for job
The Print Job Description Authority (PRTJOBDAUT) descriptions with public authority that is not *EXCLUDE
command allows you to print a report of the job descriptions and a user name is specified.
in a library that do not have public authority of *EXCLUDE,
and a user name is specified in the job description. This is a *LIBL: All libraries in the job's library list are
way to check for job descriptions that every user on the searched until the first match is found.
system is authorized to use that allow the user to run as *CURLIB: The current library for the job is
another user profile. searched. If no library is specified as the current
library for the job, the QGPL library is used.
This command will print two reports for a library. The first
report (Full Report) will contain all of the job descriptions that *USRLIBL: Only the libraries in the user portion of
do not have public authority of *EXCLUDE and have a user the job's library list are searched.
name specified. The second report (Changed Report) will *ALL: All libraries in the system, including QSYS,
contain the job descriptions that now do not have public are searched.
authority of *EXCLUDE or have a user name specified that
*ALLUSR: All user libraries are searched.
either did have public authority of *EXCLUDE, did not have a
user name specified, or did not exist when the library-name: Specify the name of the library to be
PRTJOBDAUT command was previously run for the library. searched.
If the PRTJOBDAUT command was not previously run for
the library, there will be no 'Changed Report'. If the
command has been previously run for the library but no addi- Optional Parameter
tional job descriptions do not have public authority of CHGRPTONLY
*EXCLUDE and a user name specified, then the 'Changed Specifies whether just the changed report should be
Report' will be printed but there will be no job descriptions printed.
listed. Changes to user profile special authorities will not
cause a 'Changed Report' to be generated. *NO: The full and changed reports will be printed.
*YES: Only the changed report will be printed.
Restriction: You must have *ALLOBJ special authority to
use this command.
Example
Note: To see the parameter and value descriptions for this
command, refer to the online help text. For more PRTJOBDAUT LIB(QGPL)
information about printing the help text, refer to
This command will generate the full and changed report for
“Printing CL Command Descriptions” in Chapter 1.
the job descriptions in the library QGPL.
Required Parameter
(P) ──LIB(──┬─\LIBL────────┬──)─────────────────────────5
55──PRTPUBAUT──OBJTYPE(────object-type────)──┬──────────────────────────┬───
│ ┌─\NO──┐ │ ├─\USRLIBL─────┤
└─CHGRPTONLY(──┴─\YES─┴──)─┘ ├─\CURLIB──────┤
├─\ALL─────────┤
├─\ALLUSR──────┤
└─library-name─┘
5──┬──────────────────────┬──┬──────────────────────┬──┬──────────────────────┬──┬───────────────────────┬──────────────────────5
│ ┌─\NO──┐ │ │ ┌─\NO──┐ │ │ ┌─\NO──┐ │ │ ┌─\NO──┐ │
└─FILAUT(──┴─\YES─┴──)─┘ └─CMDAUT(──┴─\YES─┴──)─┘ └─PGMAUT(──┴─\YES─┴──)─┘ └─JOBDAUT(──┴─\YES─┴──)─┘
5──┬──────────────────────┬────────────────────────────────────────────────────────────────────────────────────────────────────5%
└─FLR(──folder-name──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
This command will print two reports. The first report (Full *LIBL: All libraries in the job's library list are
Report) will contain all of the specified objects that do not searched until the first match is found.
have public authority of *EXCLUDE. The second report
*CURLIB: The current library for the job is
(Changed Report) will contain the objects that now do not
searched. If no library is specified as the current
have public authority of *EXCLUDE that did have public
library for the job, the QGPL library is used.
authority of *EXCLUDE or did not exist when the
PRTPUBAUT command was previously run. If the *USRLIBL: Only the libraries in the user portion of
PRTPUBAUT command was not previously run for the speci- the job's library list are searched.
fied objects and library or folder, there will be no 'Changed *ALL: All libraries in the system, including QSYS,
Report'. If the command has been previously run, but no are searched.
additional objects do not have public authority of *EXCLUDE,
*ALLUSR: All user libraries are searched.
then the 'Changed Report' will be printed but there will be no
objects listed. library-name: Specify the name of the library to be
searched.
Restrictions: You must have *ALLOBJ special authority to
use this command. This is a required parameter for all object types except
*AUTL, *CFGL, *CNNL, *COSD, *CTLD, *DEVD, *DOC,
Note: To see the parameter and value descriptions for this
*FLR, *LIB, *LIND, *MODD, *NWID, *NWSD, and
command, refer to the online help text. For more
*USRPRF.
information about printing the help text, refer to
“Printing CL Command Descriptions” in Chapter 1. FILAUT
Specifies whether the Print Publicly Authorized Objects
(PRTPUBAUT) command will be run for *FILE objects
Required Parameter for each of the libraries that do not have public authority
OBJTYPE of *EXCLUDE. This parameter is only used when the
Specifies the type of object to search for. For a com- OBJTYPE is *LIB.
plete list of object types, position the cursor on the field *NO: The PRTPUBAUT command will not be run for
for the Object type prompt (OBJTYPE parameter), and *FILE objects for each of the libraries that does not have
press F4. public authority of *EXCLUDE.
object-type: The name of the object type to search for.
*YES: The PRTPUBAUT command will be run for The command will create the full and changed reports for the
*PGM objects for each of the libraries that does not have file objects in the library QSYS.
public authority of *EXCLUDE.
(P) ──┬───────────────────────┬─────────────────────────5
55──PRTPVTAUT──OBJTYPE(────object-type────)──┬──────────────────────────┬───
│ ┌─\NO──┐ │ └─LIB(──library-name──)─┘
└─CHGRPTONLY(──┴─\YES─┴──)─┘
5──┬──────────────────────────┬──┬──────────────────────┬──┬───────────────────────┬───────────────────────────────────────────5%
│ ┌─\OBJECT─┐ │ └─FLR(──folder-name──)─┘ │ ┌─\NO──┐ │
└─AUTTYPE(──┼─\FIELD──┼──)─┘ └─AUTLOBJ(──┴─\YES─┴──)─┘
└─\ALL────┘
Note:
P All parameters preceding this point can be specified in positional form.
Restriction: You must have *ALLOBJ special authority to *FIELD: For each data base file that has field level
use this command. authorities, a field level authority report is generated.
Note: To see the parameter and value descriptions for this This value is only valid if *FILE is specified for the
command, refer to the online help text. For more Object type prompt (OBJTYPE parameter).
information about printing the help text, refer to *ALL: For each data base file that has field level
“Printing CL Command Descriptions” in Chapter 1. authorities, a field level authority report is generated.
Also, the object level authority reports for all the files in vides a list of all the objects that are secured by a spe-
the specified library are generated. cific authorization list. This parameter is only used if the
object type is *AUTL. It is ignored for all other object
This value is only valid if *FILE is specified for the
types.
Object type prompt (OBJTYPE parameter).
*NO: The DSPAUTLOBJ command will not be run for
FLR
each of the authorization lists on the system.
Specifies the name of the folder to search for documents
to be included in the private authority report. *YES: The DSPAUTLOBJ command will be run for
each of the authorization lists on the system. The output
This is a required parameter if *DOC is specified for the for the command will be sent to the same output queue
Object type prompt (OBJTYPE parameter). as the authorization list report.
(P) ────────────────────────────────────────────────────5%
55──PRTQAUT──┬───────────────────────────┬──┬──────────────────────────┬───
│ ┌─\ALL─────────┐ │ │ ┌─\NO──┐ │
└─LIB(──┼─\LIBL────────┼──)─┘ └─CHGRPTONLY(──┴─\YES─┴──)─┘
├─\USRLIBL─────┤
├─\CURLIB──────┤
├─\ALLUSR──────┤
└─library-name─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose LIB
Specifies the name of the library to search for output
The Print Queue Authority (PRTQAUT) command allows you queue and job queue objects to report.
to print a report of the output queue and job queue authority
information for the objects in the specified library. This *ALL: All libraries in the system, including QSYS,
command provides a way to check the authority attributes of are searched.
the output queue and job queue objects on the system. *LIBL: All libraries in the job's library list are
searched until the first match is found.
This command prints two reports for a library. The first
report (Full Report) contains all of the output queues and job *USRLIBL: Only the libraries in the user portion of
queues in the specified library. The second report (Changed the job's library list are searched.
Report) contains the output queues and job queues that have *CURLIB: The current library for the job is
been created or had the authority attributes changed since searched. If no library is specified as the current
the PRTQAUT command was last run for the library. If the library for the job, the QGPL library is used.
PRTQAUT command was not previously run for the library,
*ALLUSR: All user libraries are searched.
there will be no 'Changed Report'. If the command has been
previously run for the library but no additional queue informa- library-name: Specify the name of the library to be
tion is available then the 'Changed Report' is printed but searched.
there are no queues listed.
CHGRPTONLY
Restriction: You must have *ALLOBJ special authority to Specifies whether just the changed report should be
use this command. printed.
Note: To see the parameter and value descriptions for this *NO: The full and changed reports are printed.
command, refer to the online help text. For more *YES: Only the changed report is printed.
information about printing the help text, refer to
“Printing CL Command Descriptions” in Chapter 1.
Example
PRTQAUT LIB(QUSRSYS)
Optional Parameters
This command generates the full and changed reports for the
output queues and job queues in the library QUSRSYS.
(P) ─────────────────────────────────────────────────────5%
55──PRTSBSDAUT──LIB(──┬─\LIBL────────┬──)──┬──────────────────────────┬───
├─\USRLIBL─────┤ │ ┌─\NO──┐ │
├─\CURLIB──────┤ └─CHGRPTONLY(──┴─\YES─┴──)─┘
├─\ALL─────────┤
├─\ALLUSR──────┤
└─library-name─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose LIB
Specifies the name of the library to search for sub-
The Print Subsystem Description Authority (PRTSBSDAUT) system descriptions contain a subsystem entry with a
command allows you to print a report of the subsystem default user profile specified.
descriptions in a library that contain a default user in a sub-
system entry. This command provides a way to check for *LIBL: All libraries in the job's library list are
subsystem descriptions that allow work to be performed on searched until the first match is found.
your system while running under a default user profile. *CURLIB: The current library for the job is
searched. If no library is specified as the current
This command prints two reports for a library. The first library for the job, the QGPL library is used.
report (Full Report) contains all of the subsytem descriptions
that contain a default user in a subsystem entry. The second *USRLIBL: Only the libraries in the user portion of
report (Changed Report) contains the subsystem descriptions the job's library list are searched.
that have been changed to contain a subsystem entry with a *ALL: All libraries in the system, including QSYS,
default user since the PRTSBSDAUT command was last run are searched.
for the library. If the PRTSBSDAUT command was not previ-
*ALLUSR: All user libraries are searched.
ously run for the library, there will be no 'Changed Report'. If
the command has been previously run for the library but no library-name: Specify the name of the library to be
additional subsystem descriptions contain subsystem entries searched.
with a default user, then the 'Changed Report' is printed but
there are no subsystem descriptions listed. Changes to user
profile special authorities do not cause a 'Changed Report' to Optional Parameter
be generated. CHGRPTONLY
Specifies whether just the changed report should be
Restriction: You must have *ALLOBJ special authority to
printed.
use this command.
*NO: The full and changed reports will be printed.
Note: To see the parameter and value descriptions for this
command, refer to the online help text. For more *YES: Only the changed report will be printed.
information about printing the help text, refer to
“Printing CL Command Descriptions” in Chapter 1.
Example
PRTSBSDAUT LIB(QSYS)
Required Parameter
The full and changed report for all subsystem descriptions in
library QSYS will be created.
┌─\LIBL/────────┐
(P) ────────────────────────────────────────5%
55──PRTSQLINF──OBJ(──┼───────────────┼──object-name──)──┬──────────────────────────┬───
├─\CURLIB/──────┤ │ ┌─\PGM────┐ │
└─library-name/─┘ └─OBJTYPE(──┼─\SQLPKG─┼──)─┘
└─\SRVPGM─┘
Note:
P All parameters preceding this point can be specified in positional form.
(P) ─┬─────────────────────┬────────────────────────────────────────────────────────5%
55──PRTSWL──LANGID(──language-identifier──)────
│ ┌─\IBM──┐ │
└─TYPE(──┴─\USER─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
55──PRTSYSSECA─────────────────────────────────────────────────────────────────────────────────────────────────────────────────5%
Purpose Restrictions:
The Print System Security Attributes (PRTSYSSECA) You must have *ALLOBJ special authority to use this
command prints a report of security-related system values command.
and network attributes to a spooled file. The report includes
the system value or network attribute name, the current
value, and the recommended value.
(P) ──────────────────────────────────────────────────────5%
55──PRTTRGPGM──LIB(──┬─\LIBL────────┬──)──┬──────────────────────────┬───
├─\USRLIBL─────┤ │ ┌─\NO──┐ │
├─\CURLIB──────┤ └─CHGRPTONLY(──┴─\YES─┴──)─┘
├─\ALL─────────┤
├─\ALLUSR──────┤
└─library-name─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose LIB
Specifies the name of the library to search for files that
The Print Trigger Program (PRTTRGPGM) command lists have trigger programs.
the programs which have been defined as a trigger program
for the physical files in the specified library. *LIBL: All libraries in the job's library list are
searched until the first match is found.
This command prints two reports for a library. The first *CURLIB: The current library for the job is
report (Full Report) contains all of the trigger programs asso- searched. If no library is specified as the current
ciated with files in the specified library. The second report library for the job, the QGPL library is used.
(Changed Report) contains the trigger programs that now
appear in the specified library and were not in the library *USRLIBL: Only the libraries in the user portion of
when the PRTTRGPGM command was previously run for the the job's library list are searched.
library. If the PRTTRGPGM command was not previously *ALL: All libraries in the system, including QSYS,
run for the library, there will be no 'Changed Report'. If the are searched.
command has been previously run for the library but no addi-
*ALLUSR: All user libraries are searched.
tional trigger programs are in the specified library, the
'Changed Report' is printed but there are no objects listed. library-name: Specify the name of the library to be
Changing the trigger time, trigger event or trigger update searched.
condition for a trigger program will not cause a 'Changed
Report' to be generated.
Optional Parameter
A program is not listed in the 'Changed Report' when the
CHGRPTONLY
program itself is changed. Therefore, you should periodically
Specifies whether just the changed report should be
review the entire list of objects that adopt to understand their
printed.
current function.
*NO: The full and changed reports are printed.
Restriction: You must have *ALLOBJ special authority to
*YES: Only the changed report is printed.
use this command.
Note: To see the parameter and value descriptions for this
command, refer to the online help text. For more Example
information about printing the help text, refer to PRTTRGPGM LIB(\ALL)
“Printing CL Command Descriptions” in Chapter 1.
This command searches all files in all libraries and produces
the full and changed trigger program reports.
Required Parameter
(P) ──────────────────────────────────────────────────────────5%
55──PRTUSROBJ──LIB(──library-name──)──┬──────────────────────────┬───
│ ┌─\NO──┐ │
└─CHGRPTONLY(──┴─\YES─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
(P)─┬────────────────────────┬──┬───────────────────────────┬──┬────────────────────────────────────┬──────────────5
55──PRTUSRPRF───
│ ┌─\ALL─────┐ │ │ ┌─\SPCAUT───┐ │ │ ┌─\ALL───────────────┐ │
└─TYPE(──┼─\AUTINFO─┼──)─┘ └─SELECT(──┼─\USRCLS───┼──)─┘ │ │ ┌──
─────────────┐ │ │
├─\ENVINFO─┤ └─\MISMATCH─┘ 6 (1) ─┴──)─┘
└─SPCAUT(──┴──┬─\ALLOBJ───┬┴───
└─\PWDINFO─┘ ├─\AUDIT────┤
├─\JOBCTL───┤
├─\IOSYSCFG─┤
├─\SAVSYS───┤
├─\SECADM───┤
├─\SERVICE──┤
├─\SPLCTL───┤
└─\NONE─────┘
5──┬──────────────────────────────────┬────────────────────────────────────────────────────────────────────────────────────────5%
│ ┌─\ALL─────────────┐ │
│ │ ┌──
───────────┐ │ │
6 (2)
└─USRCLS(──┴──┬─\USER───┬┴────┴──)─┘
├─\SYSOPR─┤
├─\PGMR───┤
├─\SECADM─┤
└─\SECOFR─┘
Notes:
P All parameters preceding this point can be specified in positional form.
1 A maximum of 9 repetitions
2 A maximum of 5 repetitions
Purpose SELECT
Specifies what criteria is used to select the user profiles
The Print User Profile (PRTUSRPRF) command allows you to include in the report.
to print a report containing information for the user profiles on
*SPCAUT: User profiles are selected for the report
the system. Three different reports can be printed. One
based on special authorities.
contains authority type information, one contains environment
type information, and one contains password type informa- *USRCLS: User profiles are selected for the report
tion. based on user class.
*MISMATCH: User profiles are selected for the report
Restriction: You must have *ALLOBJ special authority to
based on their special authorities not being the default
use this command.
values assigned to their user class.
Note: To see the parameter and value descriptions for this
Note: The defaulted special authorities for user classes
command, refer to the online help text. For more
were changed in Version 3, Release 7, Modifica-
information about printing the help text, refer to
tion 0. Therefore, when running this report for
“Printing CL Command Descriptions” in Chapter 1.
profiles created prior to V3R7M0, you may notice
a larger than expected number of profiles that do
Optional Parameters not match the default values.
TYPE SPCAUT
Specifies the type of information that can be printed for If *SPCAUT was specified for the SELECT parameter, it
the user profiles selected. specifies which special authorities should be used to
select users. User profiles with any of the special
*ALL: All of the reports are printed for the user profiles
authorities specified for this parameter are included in
selected.
the report. A maximum of 9 special authorities can be
*AUTINFO: A report containing the authority type infor- specified.
mation for the user profiles selected is printed.
*ALL: All user profiles are included in the report.
*ENVINFO: A report containing the environment type
*ALLOBJ: User profiles with *ALLOBJ special authority
information for the user profiles selected is printed.
are included in the report.
*PWDINFO: A report containing the password type
*AUDIT: User profiles with *AUDIT special authority are
information for the user profiles selected is printed.
included in the report.
*JOBCTL: User profiles with *JOBCTL special authority included in the report. A maximum of 5 user classes
are included in the report. can be specified.
*IOSYSCFG: User profiles with *IOSYSCFG special *ALL: All user profiles are included in the report.
authority are included in the report.
*USER: User profiles with *USER user class are
*SAVSYS: User profiles with *SAVSYS special authority included in the report.
are included in the report.
*SYSOPR: User profiles with *SYSOPR user class are
*SECADM: User profiles with *SECADM special included in the report.
authority are included in the report.
*PGMR: User profiles with *PGMR user class are
*SERVICE: User profiles with *SERVICE special included in the report.
authority are included in the report.
*SECADM: User profiles with *SECADM user class are
*SPLCTL: User profiles with *SPLCTL special authority included in the report.
are included in the report.
*SECOFR: User profiles with *SECOFR user class are
*NONE: User profiles with no special authorities are included in the report.
included in the report.
USRCLS Example
If *USRCLS was specified for the Select by prompt PRTUSRPRF TYPE(\ALL) SELECT(\SPCAUT)
(SELECT parameter), it specifies that user classes SPCAUT(\ALLOBJ \SECADM)
should be used to select users. User profiles with a
user class that is specified for this parameter are This command creates all three reports for user profiles that
have either *ALLOBJ or *SECADM special authority.
(P) ──┬──────────────────────────────────────┬──────────5
55──PWRDWNSYS──┬─────────────────────────┬──┬───────────────────────────┬───
│ ┌─\CNTRLD─┐ │ │ ┌─36ðð───────┐ │ │ ┌─\NO─────────────────┐ │
└─OPTION(──┴─\IMMED──┴──)─┘ └─DELAY(──┼─\NOLIMIT───┼──)─┘ │ │ ┌─\IPLA─┐ │ │
└─delay-time─┘ └─RESTART(──┴───\YES────┼─\SYS──┼─┴──)─┘
└─\FULL─┘
5──┬────────────────────────┬──┬─────────────────────────────────────────┬──┬───────────────────────────────┬──────────────────5%
| │ ┌─\PANEL─┐ │ │ ┌─\DFT─────────────────┐ │ │ ┌─\CONTINUE──┐ │
| └─IPLSRC(──┼─A──────┼──)─┘ │ │ ┌──
───────────────┐ │ │ └─TIMOUTOPT(──┼─\MSD───────┼──)─┘
| ├─B──────┤ 6 (1)
└─ENDSBSOPT(──┴───┬─\NOJOBLOG─┬─┴────┴──)─┘ └─\SYSREFCDE─┘
| └─D──────┘ ├─\CHGPTY───┤
| └─\CHGTSL───┘
Notes:
P All parameters preceding this point can be specified in positional form.
| 1 A maximum of 3 repetitions
| *CHGTSL: The timeslice of jobs that are ending is controlled end is allowed one hour (3600 seconds) for com-
| changed to a lower value. The remaining active jobs on pletion before any remaining jobs are ended. This method of
| the system may have better performance when issuing the PWRDWNSYS command could be used to allow
| *CHGTSL is specified. However, jobs that are ending other higher priority jobs on job queue QBATCH (including
| may take longer to finish. This option is ignored if the those that are on the queue as a result of the Transfer Job
| system is ending controlled. But if the DELAY time limit (TFRJOB) command) to be completed before the
| expires, this option will take affect immediately. PWRDWNSYS command is run. There must be an active
subsystem for which the QBATCH job queue is a source of
| TIMOUTOPT work.
| Specifies the option to take when the system does not
| end within the time limit specified by the Example 3: Specifying a Controlled End With No Time
| QPWRDWNLMT system value. If this time limit is Limit
| exceeded, the subsequent IPL will be abnormal regard-
PWRDWNSYS OPTION(\CNTRLD) RESTART(\YES)
| less of the value specified for this parameter.
| *CONTINUE: The system will ignore the timeout condi- This command causes the system to perform a controlled
| tion and continue powering the system down. If end with no time limit. When all jobs in the system have
| RESTART(*YES) is specified, the system will restart completed, the system prepares for ending and starts an IPL.
| automatically. A minimum of information will be avail-
| able for service to debug the system. After PWRDWNSYS OPTION(*CNTRLD) is entered, and
before the delay time ends, this command can be overridden
| *MSD: The system will issue a main store dump which by entering PWRDWNSYS OPTION(*IMMED). In this case,
| can be used by service to debug the system. If the the values specified or defaulted for the RESTART param-
| main store dump manager is configured correctly, the eter on the second command also override the values speci-
| system will restart after the dump is finished. See the fied or defaulted for the first command.
| AS/400 Licensed Internal Code Diagnostic Aids –
| Volume 1, LY44-5900 book, for more information on Example 4: Changing the IPL Source After Immediate
| main store dump manager. End
| *SYSREFCDE: The system will display system reference PWRDWNSYS OPTION(\IMMED) RESTART(\YES) IPLSRC(A)
| code B900 3F10 and the system will stop. This will
| allow service to debug the system. This command causes the system to end immediately and
change the IPL source to A. When the system restarts, it
IPLs on the A source.
Examples Example 5: Allowing the operating system to determine
Example 1: Performing An Immediate End the restart point
This command causes the system to perform an immediate This command causes the IPL to restart at the point deter-
end without allowing any active jobs to perform cleanup rou- mined by the operating system.
tines. Once the system completes its end functions, it starts
| Example 6: Changing the time out option.
the power-down sequence.
| PWRDWNSYS OPTION(\IMMED) TIMOUTOPT(\MSD)
Example 2: Specifying a Controlled End
| This command causes the system to end immediately. If the
SBMJOB JOB(LASTJOB) JOBD(QBATCH) JOBPTY(9)
| QPWRDWNLMT system value is exceeded, the system will
JOBQ(QBATCH) RQSDTA('PWRDWNSYS \CNTRLD 36ðð')
| dump the main storage. If the main store dump manager is
This command submits a low priority batch job that, when | configured correctly, the system will restart. Otherwise, the
run, causes the system to perform a controlled end. The | B900 3F10 system reference code will be displayed and the
| system will halt.
(P) ──┬────────────────────────────────────────────────────────┬──────────5
55──QRYDOCLIB──┬──────────────────────────────────────┬───
│ ┌─\CURRENT──────────────┐ │ │ ┌─\NONE─────────────────────────────────┐ │
└─USRID(──┴─user-ID──user-address─┴──)─┘ │ │ ┌─\LIBL/────────┐ │ │
└─OUTFILE(──┴─┼───────────────┼──database-file-name─┴──)─┘
├─\CURLIB/──────┤
└─library-name/─┘
5──┬───────────────────────────────────────────┬──┬────────────────────────────────────────┬────────────────────────────────────5
│ ┌─\FIRST──────┐ ┌─\REPLACE─┐ │ │ ┌─\DFT────────────────┐ │
└─OUTMBR(──┴─member-name─┴──┼──────────┼──)─┘ └─OUTDTATYP(──┼─\ALL────────────────┼──)─┘
└─\ADD─────┘ │ ┌──
──────────────┐ │
└──6─┬─\DOCD────┬─┴───
(1) ─┘
├─\DOCCLS──┤
├─\SUBJECT─┤
├─\EXPDATE─┤
├─\FILDATE─┤
├─\CHGDATE─┤
├─\USEDATE─┤
├─\CRTDATE─┤
├─\ACTDATE─┤
├─\CMPDATE─┤
├─\DOCDATE─┤
├─\AUTHOR──┤
├─\KWD─────┤
├─\CPYLST──┤
├─\REF─────┤
├─\STATUS──┤
├─\PROJECT─┤
├─\FILCAB──┤
├─\IDXDATE─┤
├─\REVDATE─┤
└─\IDP─────┘
5──┬──────────────────────────────────┬──┬─────────────────────────────┬──┬────────────────────────────┬────────────────────────5
│ ┌─\DFT───────────────┐ │ │ ┌─\BLANK────────┐ │ │ ┌─\NOMAX─────┐ │
└─DOCL(──┼─\NONE──────────────┼──)─┘ └─TEXT(──┴─'description'─┴──)─┘ └─TIMLMT(──┴─time-limit─┴──)─┘
└─document-list-name─┘
5──┬─────────────────────────────────┬──┬─────────────────────────────────┬──┬────────────────────────────┬─────────────────────5
│ ┌─\NOMAX──────────┐ │ │ ┌─\ALL───────────────┐ │ │ ┌─\NO──┐ │
└─SELLMT(──┴─selection-limit─┴──)─┘ └─FLR(──┼─\NONE──────────────┼──)─┘ └─SCHSUBFLR(──┴─\YES─┴───(3) ──)─┘
│ ┌──
─────────────┐ │
└──6─folder-name─┴───
(2) ─┘
5──┬──────────────────────────────────────────────────────────────────────────────────────────────────────┬─────────────────────5
│ ┌─\NONE────────────────────────────────────────────────────────────────────────────────┐ │
│ │ ┌──
──────────────────────────────────────────────────────────────────────┐ │ │
│ │ │ ┌─\AND─┐ │ │ │
6 (4) (5) (6) (7) (8)
└─QRYDFN(──┴─\IF(────(──┬─\DOCD────┬─────┬─\EQ─┬─────┬─\YES──────────┬─────┼──────┼─────)─┴─────)─┴──)─┘
├─\DOCCLS──┤ ├─\GT─┤ ├─\NO───────────┤ └─\OR──┘
├─\SUBJECT─┤ ├─\LT─┤ └─compare-value─┘
├─\DOCDATE─┤ ├─\NE─┤
├─\EXPDATE─┤ ├─\GE─┤
├─\FILDATE─┤ ├─\NL─┤
├─\CRTDATE─┤ ├─\LE─┤
├─\ACTDATE─┤ ├─\NG─┤
├─\CMPDATE─┤ ├─\CT─┤
├─\CHGDATE─┤ └─\BG─┘
├─\USEDATE─┤
├─\AUTHOR──┤
├─\KWD─────┤
├─\CPYLST──┤
├─\ALWRPL──┤
├─\OWNER───┤
├─\PROJECT─┤
├─\REF─────┤
├─\STATUS──┤
├─\DOCTYPE─┤
├─\IDXDATE─┤
├─\REVDATE─┤
└─\ASP─────┘
5──┬───────────────────────────────────────────────────────────────────────────────────────────────────┬────────────────────────5
│ ┌─\NONE─────────────────────────────────────────────────────────────────────────────┐ │
│ │ ┌──
────────────────────────────────────────────────────────────────┐ │ │
6
└─QRYTXT(──┴─\IF──(────'phrase'──┬──────────────────────────────────────────────────┬─┴──── (12) ──)─┴──)─┘
│ ┌─\ALL───┐ │
(9) ──┬───────────────────────────────┬─┘
└─┴─\EXACT─┴───
│ ┌─\NO──┐ ┌─\OR─────┐ │
(10) ──┼─────────┼────
└─┴─\YES─┴──── (11) ─┘
├─\AND────┤
└─\ANDNOT─┘
5──┬────────────────────────────────────────┬──┬─────────────────────────────────────────────────────────┬──────────────────────5
│ ┌─\JOB────────────────┐ │ │ ┌─\NONE────────────────────────────────────┐ │
└─TXTLANGID(──┴─language-identifier─┴──)─┘ │ │ ┌──
──────────────────────────────────┐ │ │
│ │ │ ┌─\ASCEND──┐ │ │ │
6 (13)
└─ORDER(──┴───(──┬─\DOCD────┬──┼──────────┼──)─┴─────┴──)─┘
├─\DOCCLS──┤ └─\DESCEND─┘
├─\SUBJECT─┤
├─\EXPDATE─┤
├─\FILDATE─┤
├─\CRTDATE─┤
├─\ACTDATE─┤
├─\CMPDATE─┤
├─\CHGDATE─┤
├─\USEDATE─┤
├─\DOCDATE─┤
├─\DOCTYPE─┤
├─\IDXDATE─┤
├─\REVDATE─┤
├─\KWD─────┤
├─\AUTHOR──┤
├─\CPYLST──┤
├─\OWNER───┤
├─\REF─────┤
├─\STATUS──┤
├─\PROJECT─┤
└─\ASP─────┘
5──┬────────────────────────────────────────────────────┬──────────────────────────────────────────────────────────────────────5%
│ ┌─\SYSVAL──────────────────────────┐ │
└─CMDCHRID(──┼─\DEVD────────────────────────────┼──)─┘
└─graphic-character-set──code-page─┘
Notes:
P All parameters preceding this point can be specified in positional form.
1 A maximum of 20 repetitions
3 If SCHSUBFLR(*YES) is specified, FLR(*ALL) and FLR(*NONE) are not valid and only one user-specified folder name can
be specified.
4 Profile parameter.
5 Relational operator.
6 Compare value.
8 A maximum of 49 repetitions
12 A maximum of 30 repetitions
13 A maximum of 5 repetitions
Record Code Description *IDP: The interchange document profile is written to the
155 Document class output file.
160 File cabinet reference
165 Subject DOCL
170 Keyword Specifies the name of the document list. A document
175 Reference list is an object that contains a pointer to each document
180 Status in the document library that the current user is author-
185 Project ized to request. This list is a copy of the library at the
190 Last indexed date time the search was run. As documents are deleted
195 Last content revision date from or added to the library, the document list is not
200 Last used date updated. The document library list name is specified
500 Interchange document profile data with the name of the user requesting the search. Users
can use identical document names. For example, Tom
*DOCD: The document description record is written to could name his list SALES and so could Mary. The
the output file. system knows the lists as TOM_SALES and
*DOCCLS: The document class record is written to the MARY_SALES.
output file. *DFT: A system-created name is used as the default
*SUBJECT: The subject records are written to the document list name. The default list is the same as the
output file. user ID entered in the USRID parameter (TOM_TOM or
MARY_MARY).
*EXPDATE: The expiration date record is written to the
output file. *NONE: No document list is created.
*FILDATE: The file date record is written to the output document-list-name: Specify the name of the document
file. list. Up to 8 characters can be used.
*DOCDATE: The document date record is written to the *NOMAX: No time limit for the search is set. All quali-
output file. fied documents are searched.
*AUTHOR: The author records are written to the output time-limit: Specify the maximum time limit (in minutes)
file. that the search runs. Up to 4 digits, ranging from 1
through 9999, can be specified for the number of
*KWD: The keyword records are written to the output minutes. A two-hour limit is specified as TIMLMT(120).
file. If the search has not been completed when the time limit
*CPYLST: The copy list records are written to the is reached, the search ends with an informational
output file. message followed by a completion message. The
output file, and if specified the document list, will contain
*REF: The reference record is written to the output file.
the documents found within the specified time limit.
*STATUS: The status record is written to the output file.
SELLMT
*PROJECT: The project record is written to the output Specifies the number of documents to select in the
file. search.
*FILCAB: The file cabinet reference record is written to *NOMAX: No document limit for the search is set. All
the output file. qualified documents are selected.
*IDXDATE: The last indexed date record is written to selection-limit: Specify the maximum number of docu-
the output file. OfficeVision text search services must be ments to select. A value ranging from 1 through 32767
installed if this value is specified. can be specified. If there are more query requests than
*REVDATE: The date of the last revision to the docu- the set limit, the document list and the output file contain
ment content is written to the output file. the information about the selected documents up to this
limit. If there is at least one more document that meets
To specify the conditions under which documents are *NL Not less than
selected, a set of values is specified for each condition. *LE Less than or equal
*NG Not greater than
Each set contains four values.
*CT Contains
1. The name of the document profile parameter to be *BG Begins
compared
The *CT operator performs a context search. It asks the
2. One of the relational operator values system to determine whether the character string speci-
3. The comparison value fied by this value is contained anywhere in the profile.
For example, a query request of (*IF ((*SUBJECT *CT
4. One of the logical operators, *AND or *OR 'Sales'))) would find a match for subjects that were:
Values 1 and 3 are compared for the relationship speci- '1985 Car Sales', 'Sales Awards', 'Salesperson Training
fied by value 2. Courses', 'Book of Sales Do's and Don'ts'.
Each QRYDFN relational set must be enclosed in paren- The *BG operator performs a search that compares the
theses. A maximum of 49 sets (conditions) can be specified value with the start of the profile parameter.
specified. The profile parameter is truncated or extended as neces-
sary to match the length of the specified value. It asks
Element 1: Profile Parameters the system to determine whether the character string
profile-parameter: Specify a value representing the specified by the value is contained at the start of the
profile parameters to be compared. profile parameter. For example, a query request of (*IF
((*SUBJECT *BG 'Sales'))) would find a match for sub-
jects of: 'Sales Awards', 'Salesperson Training Courses', system changes both the specified comparison value
and 'Sales by Phone'. and the original parameter value to upper case before
making a comparison. If the original document had
Some operators are excluded from being used with
been filed with a subject equal to 'Salesperson Training
some profile parameters. If the excluded operators are
Courses', any of the following would be a match:
specified in restricted profile parameters, the request is
rejected with a diagnostic message followed by an (\IF ((SUBJECT \EQ 'salesperson training
escape message. Two cases are invalid: courses')))
(\IF ((SUBJECT \EQ 'Salesperson Training
The *ALWRPL (allow document replacement) is a Courses')))
YES/NO value. The *EQ operator is the only oper- (\IF ((SUBJECT \EQ 'SALESPERSON TRAINING
ator allowed to have *ALWRPL. COURSES')))
(\IF ((SUBJECT \CT 'PERSON')))
The *CT and *BG operators are not allowed with the
(\IF ((SUBJECT \CT 'person')))
*ASP value or date values such as *CRTDATE and (\IF ((SUBJECT \BG 'SALES')))
*EXPDATE. (\IF ((SUBJECT \BG 'sales')))
Element 3: Compare Values Element 4: Logical Operator
compare-value: Specify the value to compare with the *AND: The profile parameter value relational groups on
contents of the specified profile parameter. The param- both sides of the *AND value must be satisfied before a
eter value is specified in apostrophes if it contains document is selected.
blanks or special characters.
*OR: If the parameter value relational group on either
The *ALWRPL field has two special values: *YES and side of the *OR value is satisfied, the document is
*NO. When these are specified with the *ALWRPL field, selected.
they are changed to internal values for the indicator.
The logical operators are used to group conditions. The
When specified for the text field, *YES and *NO retain
first AND operator encountered signifies that a condition
their original values.
group starts with the condition immediately preceding the
The *OWNER field is an 8-character user ID followed by AND operator. Subsequent conditions with the AND
its address. Trailing blanks cannot be omitted from the operator are added to the condition group. The first con-
user ID. For example, if the user ID is JMDOE and the dition encountered that contains the OR operator (when
address is SYSTEM1, the query request would be (*IF no more matrix entries exist) ends the condition group.
((*OWNER *EQ 'JMDOE SYSTEM1'))). If the user ID
For example:
is JIMSMITH, the query request would be (IF ((*OWNER
*EQ 'JIMSMITHSYSTEM1'))). QRYDFN(\IF
((COND1 \OR)
Dates must be specified in the system date format. (COND2 \AND) <----|
The allowable length for the search fields is limited by (COND3 \AND) |--Group 1
the Document Interchange Architecture (DIA) search (COND4 \AND) <----|
database. When the length of the value is greater than (COND5 \OR)
(COND6 \OR)
the maximum, the value is truncated to the allowed
(COND7 \AND) <----|
length. The maximum lengths are:
(COND8 \AND) |--Group 2
Value Maximum Length (COND9))) <----|
*DOCD 44 characters The previous example could be expressed:
*DOCCLS 16 characters (cond1) | (cond2 & cond3 & cond4 & cond5)
*SUBJECT 60 characters | cond6 | (cond7 & cond8 & cond9)
*AUTHOR 20 characters
*KWD 60 characters Because the AND operator is used to group conditions,
*CPYLST 60 characters the following logical expression cannot be used by the
*OWNER 16 characters QRYDFN parameter.
*REF 60 characters (cond1 | cond2) & (cond3 | cond4)
*STATUS 20 characters
*PROJECT 10 characters QRYDFN Examples
QRYDFN(\IF ((\ACTDATE \GE '6/1/89' \AND)
For all operators except *CT and *BG, if a value that is
(\AUTHOR \EQ 'JOHN HARKER' \OR)
shorter than the profile parameter value is specified, it is (\ACTDATE \GE '6/1/89' \AND)
padded on the right with blanks to match the length of (\PROJECT \EQ 'MGMT')))
the profile parameter.
All documents that have an action date later than or
The case (upper, lower, or mixed) of the letter charac- equal to 6/1/89 with author John Harker or project
ters used to enter the original parameter value or the MGMT are selected. This request is made up of two
case of the comparison value does not matter. The condition groups (AND sets). The first group requires
that the documents selected 1) must have an action date To specify the conditions under which documents are
of 6/1/89 or later and 2) must have John Harker as the selected, a set of values is specified for each condition.
author. The second group requires that the documents Each set contains four values:
selected 1) must have an action date of 6/1/89 or later
1. A phrase, which the system compares to entries in
and 2) must be part of project MGMT. If either of these
the text search index
condition groups is true, the document is selected.
QRYDFN (\IF ((\AUTHOR \EQ 'SUSAN MICKLE' \OR) 2. One of the type of phrase matching values
(\PROJECT \EQ 'BASEBALL' \AND) 3. One of the allow synonyms values
(\CMPDATE \GE '6/1/89')))
4. One of the logical operators
All documents that with the author of Susan Mickle or
that have a project of BASEBALL with a completion date A maximum of 30 sets of values can be specified. Each
on or after 6/1/89 are selected. set must be enclosed in parentheses.
FLR('RECORDS/SPORTS/BASEBALL/NATIONAL') Element 1: Phrase
QRYDFN(\IF ((\DOCD \CT 'giants' \AND) 'phrase': Specify a phrase of one or more words, which
(\FILDATE \GE '1/1/84' \AND)
the system compares to entries in the text search index.
(\FILDATE \LE '1ð/1/86')))
A maximum of 50 characters can be specified. When
If the word 'giants' is contained somewhere in the docu- specifying phrases:
ment description profile parameter, and if the document
file date is between 1/1/84 and 10/1/86, the document is an asterisk (*) can be used to mask a whole word
selected. within a phrase. For example, when searching for
documents containing references to various annual
The NATIONAL folder is contained in the BASEBALL reports, the following phrase can be specified:
folder, which is in the SPORTS folder, which is con-
annual \ report
tained in the RECORDS folder.
QRYDFN(\IF ((\EXPDATE \LE '1/1/86'))) The search results will include documents con-
taining such phrases as annual budget report,
All documents accessible by the user doing the search annual progress report, and annual sales report.
where the expiration date is less than or equal to 1/1/86, The search results will also include documents con-
are selected. taining the phrase 'annual report' without a word in
QRYDFN(\IF ((\AUTHOR \EQ 'ANDERSON' \AND) between.
(\DOCCLS \EQ 'account 431-2' \AND)
When using a word mask, a word must be specified
(EXPDATE \LE '1/1/86')))
before and after the asterisk. A word mask at the
All documents accessible by the user doing the search, beginning or end of a phrase is ignored.
when all three conditions on the author, document class,
an asterisk (*) can be used to mask part of a word
and expiration date profile parameters are met, are
within a phrase. The mask can be used at the
selected.
beginning, middle, or end of a word. For example,
QRYDFN(\IF ((\KWD \EQ 'alphabet soup' \OR) when searching for documents containing refer-
(\KWD \CT Campbells \OR) ences to word processing, the following phrase can
(\KWD \BG 'good for you'))) be specified:
All documents accessible by the user doing the search, word process\
when any one of the three keyword tests is satisfied, are
The search results will include documents con-
selected.
taining such phrases as word processing, word
QRYTXT processor, and word processed.
Specifies the text search values used to select docu- a question mark (?) can be used to mask one or
ments. The values specified on this parameter are used more characters in a word. For example, when
to search the text search index. If values other than searching for documents containing references to
*NONE are specified on both the QRYDFN parameter the various spellings of Johnson, the following
and the QRYTXT parameter, only documents that match phrase can be specified:
both sets of values are selected.
j?hns?n
*NONE: No text search values are used to select the
documents. The search results will include documents con-
taining such phrases as Johnson, Johnsen, and
*IF: Text search values are used in the document Jahnson.
search.
Note: When *IF is specified, ordering is not allowed. Element 2: Type of Phrase
*NONE must be specified on the ORDER param-
eter.
*ALL: The phrase must be contained within one sen- *CRTDATE: The returned documents are ordered by
tence, but the words do not have to be in the specified the create date profile parameter.
order.
*ACTDATE: The returned documents are ordered by
*EXACT: The phrase must be contained within one the action due date profile parameter.
sentence and the words must be in the specified order.
*CMPDATE: The returned documents are ordered by
Element 3: Synonyms the completion date profile parameter.
*NO: No synonyms are used when searching for docu- *CHGDATE: The returned documents are ordered by
ments. the last document change date.
*YES: Synonyms for each word in the phrase, if avail- *USEDATE: The returned documents are ordered by
able, are used to compare entries in the text index. the last used date.
Note: Using synonyms may affect the performance of *DOCDATE: The returned documents are ordered by
the request by causing more words to be the document date profile parameter.
searched for and by possibly causing more docu-
*DOCTYPE: The returned documents are ordered by
ments to be selected.
the document type profile parameter. Valid values range
Element 4: Logical Operator from 2 through 65535.
*OR: If the phrase on either side of the *OR value is *IDXDATE: The returned documents are ordered by the
found, the document is selected. last indexed date profile parameter. Text search ser-
*AND: If the phrases on both sides of the *AND value vices must be installed if this value is specified.
are found, the document is selected. *REVDATE: The returned documents are ordered by
*ANDNOT: If the phrase following the *ANDNOT value the last content revision date.
is not found, the document is selected. *KWD: The returned documents are ordered by the
keyword profile parameter.
TXTLANGID
Specifies the language identifier of the document for *AUTHOR: The returned documents are ordered by the
which the user is searching. This parameter is not author profile parameter.
allowed if the QRYTXT parameter is not specified. *CPYLST: The returned documents are ordered by the
*JOB: The language identifier specified for the job in copy list profile parameter.
which this command is entered is used. *OWNER: The returned documents are ordered by the
language-identifier: Specify the language identifier. owner profile parameter.
*NONE: No order is applied to the selected documents. *DESCEND: The returned documents are ordered in
the descending collating sequence.
*DOCD: The returned documents are ordered by the
document name profile parameter. CMDCHRID
Specifies the character identifier (graphic character set
*DOCCLS: The returned documents are ordered by the
and code page) for data being specified as parameter
document class profile parameter.
values on this command. This character identifier
*SUBJECT: The returned documents are ordered by (CHRID) is related to the display device used to specify
the subject profile parameter. the command. More information about CHRID pro-
*EXPDATE: The returned documents are ordered by cessing is in the Application Display Programming book.
the expiration date profile parameter. Note: The CMDCHRID parameter applies to the fol-
*FILDATE: The returned documents are ordered by the lowing parameters and means that the data is
file date profile parameter. translated to the code page and character set
(P) ──┬────────────────────────┬───────────────────5
55──QRYDST──┬──────────────────────────────────────┬──┬──────────────────────┬───
│ ┌─\CURRENT──────────────┐ │ │ ┌─\IN──┐ │ │ ┌─\NO──┐ │
└─USRID(──┼─\ALLAUT───────────────┼──)─┘ └─OPTION(──┴─\OUT─┴──)─┘ (1) ─┴─\YES─┴──)─┘
└─DLTSTS(───
└─user-ID──user-address─┘
5──┬────────────────────────────────────────────────────────┬──┬───────────────────────────────────────────┬────────────────────5
│ ┌─\NONE─────────────────────────────────┐ │ │ ┌─\FIRST──────┐ ┌─\REPLACE─┐ │
│ │ ┌─\LIBL/────────┐ │ │ └─OUTMBR(──┴─member-name─┴──┼──────────┼──)─┘
└─OUTFILE(──┴─┼───────────────┼──database-file-name─┴──)─┘ └─\ADD─────┘
├─\CURLIB/──────┤
└─library-name/─┘
5──┬───────────────────────────┬──┬──────────────────────────────────────────────────────┬─────────────────────────────────────5%
│ ┌─\ALL──────┐ │ │ ┌─\SYSVAL──────────────────────────┐ │
(2) ─┼─\DEVD────────────────────────────┼──)─┘
└─STATUS(──┼─\NEW──────┼──)─┘ └─CMDCHRID(───
├─\OLD──────┤ └─graphic-character-set──code-page─┘
├─\OPENED───┤
├─\UNOPENED─┤
├─\LOCAL────┤
├─\REMOTE───┤
├─\FILEPND──┤
├─\DELETED──┤
└─\DAMAGED──┘
Notes:
P All parameters preceding this point can be specified in positional form.
1 DLTSTS does not apply to incoming distributions. When OPTION(*IN) is specified, the DLTSTS parameter is ignored.
Purpose Note: To see the parameter and value descriptions for this
command, refer to the online help text. For more
The Query Distribution (QRYDST) command allows a information about printing the help text, refer to
request for distribution information for the user or on behalf “Printing CL Command Descriptions” in Chapter 1.
of another user.
Note: The formats of the output files must be OSLIN or Element 2: User Address
OSLOUT. These formats are defined in the physical user-address: Specify the user address of the user for
files QAOSILIN or QAOSILOT, respectively. These whom the distribution information is returned.
files are located in library QSYS. Users can specify
the Create Duplicate Object (CRTDUPOBJ) OPTION
command to create duplicates of these files for their Specifies the type of distribution information that is
libraries. If the user's library does not contain the returned.
files, the files are created when the command is run. *IN: Information about incoming distributions is returned.
If an output file is specified in the OUTFILE parameter,
one incoming distribution information record per distribu- database-file-name: Specify the qualified name of the
tion is written to the output file. database file that receives the output of the display.
*OUT: Information about outgoing distributions is OUTMBR
returned. If an output file is specified, N outgoing distri- Specifies the name of the database file member to which
bution information records per distribution are written to the output is directed. If a member already exists, the
the output file. N is the number of original receivers of system uses the second element of this parameter to
the distribution or the number of receivers that have dis- determine whether the member is cleared before the
tribution errors. new records are added. If the member does not exist
and a member name is not specified, the system creates
DLTSTS
a member with the name of the output file specified on
Specifies whether the status being kept for outgoing dis-
the OUTFILE parameter. If an output file member name
tributions is deleted from the system. This can be error
is specified, but the member does not exist, the system
or confirmation of delivery status.
creates it.
*NO: The distribution status is not deleted from the
Element 1: Member to Receive Output
system. The information is kept by the system and can
be returned by a request using the QRYDST command. *FIRST: The first member in the file receives the output.
If OUTMBR(*FIRST) is specified and the member does
*YES: The distribution status is deleted if all receivers
not exist, the system creates a member with the name of
are at returned status or completed confirmation of
the file specified on the OUTFILE parameter.
delivery status.
Note: Other products use this status information. Care
member-name: Specify the file member that receives
the output. If OUTMBR(member-name) is specified and
should be taken not to delete information used
the member does not exist, the system creates it.
by other products to track their distributions.
Element 2: Operation to Perform on Member
Status is deleted by the system if all receivers have
returned status or the status is returned to another *REPLACE: The system clears the existing member
product (such as the OfficeVision) for this user. and adds the new records.
OUTFILE *ADD: The system adds the new records to the end of
Specifies the qualified name of the database file to the existing records.
which the output of the command is directed. If the file
STATUS
does not exist, this command creates a database file in
Specifies the mail entry status of the distribution for
the specified library.
which the user is requesting information. This parameter
For incoming distributions, the system uses QAOSILIN in is valid only if *IN is specified on the OPTION parameter
QSYS with the format name of OSLIN as a model. and an output file is specified on the OUTFILE param-
eter.
For outgoing distributions, the system uses QAOSILOT
in QSYS with the format name of OSLOUT as a model. *ALL: Distribution information is returned regardless of
the distribution's mail entry status.
The authority for users with no specific authority to the
output file is *EXCLUDE. More information on defining *NEW: Distribution information is returned only for distri-
the format of database files (output file) is in the Office butions with a mail entry status of NEW.
Services Concepts and Programmer’s Guide book. *OLD: Distribution information is returned only for distri-
*NONE: The output is not directed to a database file. If butions with a mail entry status of OLD. A mail entry
*NONE is specified, the output from this command is a status of OLD indicates that the distribution has been
completion message containing the number of distribu- queried once but has not been processed.
tions on the DIA Distribution Recipient Index (*DRX) for
*OPENED: Distribution information is returned only for
the specified category and user.
distributions with a mail entry status of OPENED.
The name of the database file can be qualified by one of
*UNOPENED: Distribution information is returned for
the following library values:
distributions with a mail entry status of OLD or NEW.
*LIBL: All libraries in the job's library list are *LOCAL: Distribution information is returned only for
searched until the first match is found. distributions with a mail entry status of LOCAL. A mail
*CURLIB: The current library for the job is entry status of LOCAL indicates that the distribution has
searched. If no library is specified as the current been filed on the local system.
library for the job, the QGPL library is used. *REMOTE: Distribution information is returned only for
library-name: Specify the name of the library to be distributions with a mail entry status of REMOTE. A mail
searched. entry status of REMOTE indicates that the distribution
has been filed on a remote system.
*FILEPND: Distribution information is returned only for *SYSVAL: The system determines the graphic char-
distributions with a mail entry status of FILEPND. A mail acter set and code page values for the command param-
entry status of FILEPND indicates that the distribution is eters from the QCHRID system values.
being filed on a local or remote system but the filing has
*DEVD: The system determines the graphic character
not been completed.
set and code page values for the command parameter
*DELETED: Distribution information is returned only for from the display device description where the command
distributions with a mail entry status of DELETED. A is entered. This option is valid only when specified from
mail entry status of DELETED indicates that the docu- an interactive job. If this value is specified in an interac-
ment referred to by the distribution has been deleted. tive CL program or a batch job, an error message is
sent.
*DAMAGED: Distribution information is returned only for
distributions with a mail entry status of DAMAGED. A Element 1: Character Set
mail entry status of DAMAGED indicates that the docu-
graphic-character-set: Specify the graphic character set
ment referred to by the distribution is damaged.
values used to create the command parameter.
CMDCHRID Element 2: Code Page
Specifies the character identifier (graphic character set
and code page) for data being specified as parameter
code-page: Specify the code page. Valid values range
from 1 through 9999.
values on this command. This character identifier
(CHRID) is related to the display device used to specify
the command. More information about CHRID pro- Example
cessing is in the Application Display Programming book.
QRYDST USER(\CURRENT) OPTION(\IN)
Note: This value translates the USRID parameter to the OUTFILE(\CURLIB/MYFILE) OUTMBR(\FIRST \ADD)
character set and code page set of '930 500'.
The SNA Distribution Services book contains the This command requests information about incoming distribu-
character set and code page table for '930 500'. tions for the current user of this command. The output is
directed to the database file MYFILE in the user's current
library and is added to the first member in that file.
(P) ─┬────────────────────────────────────────────────────────────┬─────────────5
55──QRYPRBSTS──PRBID(──┬─problem-identifier─┬──)────
└─\PMR───────────────┘ │ ┌─\NETATR────────────┐ ┌─\NETATR────────────┐ │
└─ORIGIN(──┴─network-identifier─┴──┼────────────────────┼──)─┘
└─control-point-name─┘
5──┬───────────────────────────────────┬──┬──────────────────────────────────────────────┬──────────────────────────────────────5
│ ┌─service-identifier─┐ │ │ ┌─\IBMSRV───────────────────┐ │
(1) ────────────────┼──)─┘
└─SRVID(──┴────────────────────┴──)─┘ └─RMTCPNAME(──┼─\SELECT───
└─remote-control-point-name─┘
5──┬───────────────────────────────────────────────┬──┬──────────────────────────┬─────────────────────────────────────────────5%
│ ┌─\NETATR───────────────────┐ │ │ ┌─\YES─┐ │
(2) ─┴─remote-network-identifier─┴──)─┘ └─AUTOPRBCRT(──┴─\NO──┴──)─┘
└─RMTNETID(───
Notes:
P All parameters preceding this point can be specified in positional form.
RMTNETID
Optional Parameters Specifies the remote name of the service provider's
ORIGIN network.
Specifies the node of the system from which the problem *NETATR: The service provider is in the local network.
log entry originated. This parameter is used with the
remote-network-identifier: Specify the network name of
PRBID parameter to uniquely identify the problem.
the service provider to whom the request is sent.
Element 1: Network Identifier
AUTOPRBCRT
*NETATR: The LCLNETID value specified in the Specifies whether a problem should automatically be
system network attributes is used. created, if a problem does not exist on the system. This
network-identifier: Specify a network identifier. will be useful if the only thing the customer has is a
PMR number.
Element 2: Control Point Name
*YES: Create a problem.
*NO: Do not create a Problem.
55──QRYTIEF────────────────────────────────────────────────────────────────────────────────────────────────────────────────────5%
| For the description of the QSH command, see the STRQSH (Start QSH) command description.
55──RCLACTGRP──ACTGRP(──┬─\ELIGIBLE─────────────┬──)──┬───────────────────────────┬────────────────────────────────────────────5%
└─activation-group-name─┘ │ ┌─\NORMAL───┐ │
└─OPTION(──┴─\ABNORMAL─┴──)─┘
Purpose tion on how the system performs the rollback operation under
commitment control.
The Reclaim Activation Group (RCLACTGRP) command
Note: To see the parameter and value descriptions for this
frees the resources associated with a specified activation
command, refer to the online help text. For more
group. This command can reclaim a specific activation group
information about printing the help text, refer to
or all eligible activation groups.
“Printing CL Command Descriptions” in Chapter 1.
An activation group is eligible to be reclaimed if it meets the
following criteria: Required Parameter
The activation group is not the default activation group.
ACTGRP
The default activation group cannot be reclaimed. Specifies the activation group to be reclaimed.
The activation group is not active. *ELIGIBLE: All eligible activation groups within the job
An activation group cannot be reclaimed if there are pro- are deleted.
grams or procedures running within the activation group. activation-group-name: Specify the activation group to
The activation group is not one of the debug activation be reclaimed. The activation group can only be
groups. reclaimed if it has no active calls. If active calls exist, a
message is displayed informing the user that the request
When the job is in debug mode, the activation groups in failed. If the activation group is not found, a message is
use do not appear as active on the Call Stack or Display displayed informing the user that the request failed
Activation Group displays. When the job is no longer in because the activation group was not found.
debug mode, the activation groups used can be
reclaimed.
Optional Parameter
The activation group is not a shared activation group.
A shared activation group cannot be reclaimed because OPTION
is may be in use by another job. Specifies whether to commit or roll back pending
changes for an activation group level commitment defi-
When an activation group is reclaimed, all resources within nition, and whether a normal or abnormal close notifica-
the scope of the activation group are reclaimed. Resources tion is sent to the attached host system when mixed,
within the scope of the activation group include static storage communications, BSC, and ICF files are closed. This
for programs in the activation group, open files, user inter- parameter is ignored for all other files and objects within
face manager (UIM) application resources, Common Pro- the scope of the activation group.
gramming Interface (CPI) Communications conversations, *NORMAL: The changes pending for an activation
hierarchical file systems (HFS) resources, open FM sessions, group level commitment definition are committed (if there
and pending changes for the commitment definition. are no errors when closing files using the commitment
definition), and a normal close notification is sent to the
A close option can be specified on this command, and is
attached host system when mixed, communications,
used when closing mixed, communications, binary synchro-
BSC, and ICF files are closed.
nous (BSC), and ICF files. If an activation group level com-
mitment definition has been started for the activation group, *ABNORMAL: The changes pending for an activation
and it has pending committable changes, the close option group level commitment definition are rolled back and an
also indicates whether the system implicitly commits or rolls abnormal close notification is sent to the attached host
back the pending changes before ending the commitment system when mixed, communications, BSC, and ICF
definition. When specifying a close option of *NORMAL, and files are closed.
there are no errors when closing files using the activation
group level commitment definition, a commit is performed. Example
Otherwise, a rollback is performed. See the Backup and
Recovery and the Backup and Recovery books for informa- RCLACTGRP ACTGRP(MYGROUP)
55──RCLDDMCNV──────────────────────────────────────────────────────────────────────────────────────────────────────────────────5%
(P) ─┬─────────────────────────────────────┬───────────────────────────────5
55──RCLDLO──DLO(──┬─\FLR─────────────────────────┬──)────
├─\SYSOBJNAM───────────────────┤ │ ┌─\NONE───────┐ │
├─\INT─────────────────────────┤ ├─FLR(──┴─folder-name─┴──)────────────┤
| ├─\DOCDTL──────────────────────┤ (1) ─system-object-name──)─┘
└─SYSOBJNAM(───
├─\ALL─────────────────────────┤
└─document-library-object-name─┘
5──┬────────────────────────────┬──┬─────────────────────────┬──┬────────────────────────────────────────────────────────┬──────5
│ ┌─\NONE───┐ │ │ ┌─\ANY───────┐ │ │ ┌─\NONE─────────────────────────────────┐ │
└─SYSOBJATR(──┼─\INTDOC─┼──)─┘ └─ASP(──┴─ASP-number─┴──)─┘ │ │ ┌─\LIBL/────────┐ │ │
└─\DST────┘ └─OUTFILE(──┴─┼───────────────┼──database-file-name─┴──)─┘
├─\CURLIB/──────┤
└─library-name/─┘
5──┬───────────────────────────────────────────┬───────────────────────────────────────────────────────────────────────────────5%
│ ┌─\FIRST──────┐ ┌─\REPLACE─┐ │
└─OUTMBR(──┴─member-name─┴──┼──────────┼──)─┘
└─\ADD─────┘
Notes:
P All parameters preceding this point can be specified in positional form.
| *DOCDTL: Internal document library system objects eter only if *ALL or *DOCDTL is specified on the DLO
| and document details are to be reclaimed. parameter.
| DLO(*DOCDTL) synchronizes the relationships between
*ANY: The objects to be reclaimed reside in any ASP.
| all document library objects and their document details
When *ALL is specified on the DLO parameter, all docu-
| and will fix inconsistencies between them.
ment library objects on the system are reclaimed.
| Note: The RCLDLO DLO(*DOCDTL) command can be
ASP-ID: Only document library objects that reside in the
| a long-running function, performing a subset of
specified ASP are to be reclaimed. All document library
| the RCLDLO DLO(*ALL) processing necessary to
objects in other ASPs are ignored. Valid values range
| guarantee consistency between internal system
from 1 through 16 and must designate an existing ASP
| objects, document details, and DLOs.
that contains document library objects. ASP 1 is the
*ALL: All documents and folders (as specified on the system ASP.
ASP parameter) are reclaimed in addition to
Note: Unfiled distribution documents are classified as
DLO(*DOCDTL) processing.
document library objects in the system ASP.
Note: The RCLDLO DLO(*ALL) command can be a
OUTFILE
long-running function, depending on the number
Specifies the name of the database file to which special
of documents and folders on the system. If the
output is directed. If the output file does not exist, this
RCLDLO command can be issued at the user's
command creates a database file in the specified library.
discretion, the user may wish to avoid the opera-
If the file is created by this function, the descriptive text
tion until the time required can be scheduled.
is "OUTFILE created by RCLDLO" and the authority for
document-library-object-name: Specify the name of the users without specific authority to the file is *EXCLUDE.
folder or document to reclaim. A value other than *NONE can be specified on this
parameter only if *ALL or *DOCDTL is specified on the
DLO parameter.
Optional Parameters The output directed to this file includes the names of any
FLR documents that are physically damaged (and therefore
Specifies the name of the folder that contains the docu- unusable) or documents or folders that were missing
ment. from the system (and for which the document details
have been removed). This file is intended to provide the
Note: A folder name is entered in this parameter only if
user with a record of what was lost (such as a user
*FLR, or a folder or document name is entered in
ASP) when recovering from hardware failure.
the DLO parameter.
*NONE: No output is directed to a database file.
*NONE: The folder or document is not within a folder.
The name of the database file can be qualified by one of
folder-name: Specify the name of the folder that con-
the following library values:
tains the document or folder to reclaim, or the name of
the folder to reclaim along with all documents and *LIBL: All libraries in the job's library list are
folders within it. searched until the first match is found.
SYSOBJNAM *CURLIB: The current library for the job is
Specifies the system object name. This parameter is searched. If no library is specified as the current
valid only when DLO(*SYSOBJNAM) or library for the job, the QGPL library is used.
DOCL(*SYSOBJNAM) is specified. A full ten characters library-name: Specify the name of the library to be
must be specified. searched.
SYSOBJATR database-file-name: Specify the qualified name of the
Specifies the attributes of the object to reclaim. A value database file that is to receive the output. This file can
other than *NONE can be entered in this parameter only be reused when other RCLDLO commands are issued.
if *SYSOBJNAM is entered in the DLO parameter. Output is added to the file as specified on the OUTMBR
*NONE: The object to reclaim is a filed document or parameter. The IBM-supplied database file,
folder. QSYS/QARCLDLO, cannot be specified.
*INTDOC: The object to reclaim is an internal docu- OUTMBR
ment. Specifies the name of the database file member to which
*DST: The object to reclaim is a distribution document. the output is directed. If a member already exists, the
system uses the second element of this parameter to
ASP determine whether the member is cleared before the
Specifies the identifier (ID) of the auxiliary storage pool new records are added. If the member does not exist
(ASP) of the document library object to be reclaimed. A and a member name is not specified, the system creates
value other than *ANY can be specified on this param- a member with the name of the output file specified on
the OUTFILE parameter. If an output file member name This command reclaims internal document library system
is specified, but the member does not exist, the system objects.
creates it.
Example 7: Reclaiming Document Library System
Element 1: Member to Receive Output Objects and Document Details
*FIRST: The first member in the file receives the output. RCLDLO DLO(\DOCDTL)
If OUTMBR(*FIRST) is specified and the member does
not exist, the system creates a member with the name of This command reclaims internal document library system
the file specified on the OUTFILE parameter. If the objects and document details for all folders and documents.
member exists, the system adds records to the end of
the member or clears the member and then adds the Example 8: Reclaiming Document Library System
records. Objects and All Documents and Folders
member-name: Specify the file member that receives RCLDLO DLO(\ALL)
the output. If OUTMBR(member-name) is specified and
This command reclaims internal document library system
the member does not exist, the system creates it.
objects and all documents and folders and synchronizes their
Element 2: Operation to Perform on Member document details.
*REPLACE: The system clears the existing member
| Example 9: Reclaiming Document Library System
and adds the new records.
| Objects and All Documents and Folders in an ASP
*ADD: The system adds the new records to the end of
| RCLDLO DLO(\ALL) ASP(2)
the existing records.
| This command reclaims internal document library system
Examples | objects and all documents and folders residing in ASP 2 and
| synchronizes their document details.
Example 1: Reclaiming a Folder
RCLDLO DLO(FLR1) Additional Considerations
This command reclaims folder FLR1. When RCLDLO DLO(*ALL) or DLO(*DOCDTL) is run, the fol-
lowing items indicate what happens for folders and docu-
Example 2: Reclaiming a Document Within a Folder
ments whose document details are updated.
RCLDLO DLO(A) FLR(FLR2)
Objects that have lost folder path information are associ-
This command reclaims folder or document A in folder FLR2. ated with a system reclaim folder. An informational
message is sent to QSYSOPR message queue for each
Example 3: Reclaiming a Folder and All Documents and object reclaimed in this manner. System reclaim folders,
Folders Within It recognized by the name 'QRCLnnnn.DOC' or
RCLDLO DLO(\FLR) FLR(FLR3) 'QRCLnnnn.FLR,' should be deleted from the system
after moving the objects within them to an appropriate
This command reclaims folder FLR3 and all folders and doc- user folder. It may also be necessary to use the Edit
uments directly or indirectly contained within it. Document Library Object Authority (EDTDLOAUT)
command to grant specific authority to the reclaimed
Example 4: Reclaiming an Internal Document
objects again.
RCLDLO DLO(\SYSOBJNAM) SYSOBJNAM(AMBT133ð8ð)
Note: System reclaim folders are created in the ASP of
SYSOBJATR(\INTDOC)
the object or objects they are to contain.
This command reclaims the internal document specified by A log of the actions taken by the RCLDLO DLO(*ALL) or
the system object name AMBT133080. DLO(*DOCDTL) command is sent to the joblog and a
listing of status messages is sent to the QHST system
Example 5: Reclaiming a Distribution Document
log. Additional information about the objects shown in
RCLDLO DLO(\SYSOBJNAM) SYSOBJNAM(AMBT133ð82) the log can be displayed by the Display Object
SYSOBJATR(\DST) Description (DSPOBJD) command.
If the OUTFILE option is used on RCLDLO DLO(*ALL)
This command reclaims the distribution document specified or DLO(*DOCDTL), records for every document or folder
by the system object name AMBT133082. which was physically damaged (permanently unusable)
or destroyed are placed into the specified file. This pro-
Example 6: Reclaiming Document Library System
vides the system administrator with a list that can be
Objects
used to determine which documents and folders need to
RCLDLO DLO(\INT) be restored from backup media.
(P) ──────────────────────────────────────────────────────────────────────────────────────────5%
55──RCLLIB──LIB(──library-name──)────
Note:
P All parameters preceding this point can be specified in positional form.
(P) ──┬──────────────────────────────────┬────────────5
55──RCLOPT──MLB(──┬─\ALL──────────────────┬──)──┬─────────────────────────┬───
└─optical-media-library─┘ │ ┌─\SYNC───┐ │ │ ┌─\ALL──────────────┐ │
└─OPTION(──┼─\UPDATE─┼──)─┘ (1) ─┴─volume-identifier─┴──)─┘
└─VOL(───
└─\RESET──┘
5──┬─────────────────────┬─────────────────────────────────────────────────────────────────────────────────────────────────────5%
│ ┌─\YES─┐ │
(1) ─┴─\NO──┴──)─┘
└─DIR(───
Notes:
1 This parameter is valid only when OPTION(*UPDATE) is specified.
OPTION This command re-creates both the optical volume index and
Specifies which type of reclaim operation is performed. the optical directory index for the optical volume VOL01 in
the optical media library OPT01.
*SYNC: The optical volume index is synchronized with
(P) ──┬───────────────────────────┬─────────────────────────────────────────────────────────5%
55──RCLRSC──┬──────────────────────┬───
│ ┌─\───────┐ │ │ ┌─\NORMAL───┐ │
└─LVL(──┴─\CALLER─┴──)─┘ └─OPTION(──┴─\ABNORMAL─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
The resources that can be reclaimed are those within the Unpredictable results may also occur if the RCLRSC
scope of the program activation. Only programs or proce- command is issued from a command line with the
dures in the default activation group are affected. If a LVL(*CALLER) parameter.
program or procedure is no longer active and has run in the Note: To see the parameter and value descriptions for this
default activation group, the resources are reclaimed. No command, refer to the online help text. For more
other activation groups are affected. information about printing the help text, refer to
“Printing CL Command Descriptions” in Chapter 1.
When a program ends abnormally, this command can be
used to reclaim resources with the close option
*ABNORMAL. This close option is used when closing mixed, Optional Parameters
communications, binary synchronous (BSC), and intersys-
tems communications function (ICF) files. LVL
Specifies the reference level at which resources are
The storage and other resources used by the opened files freed.
can then be used by other programs running on the system. *: The reference level is the program or procedure that
contains this RCLRSC command. The resources are
The RCLRSC command is not needed to reclaim the
reclaimed for programs or procedures that have finished
resources of all CL programs that end (return) normally, for
running and returned control to this program.
RPG programs that have the last record (LR) indicator set
on, or for COBOL programs. This is true because, on a *CALLER: The reference level is the program or proce-
normal return for all these types, the storage is freed and the dure that called the program or procedure containing this
files are closed automatically. RCLRSC command. This value allows controlling pro-
grams or procedures written in a high-level language to
However, the RCLRSC command should not be used if it call a CL program to reclaim resources to the level of
might be processed while any COBOL program is still active the controlling program or procedure. The effect is the
in the application; instead, the COBOL CANCEL statement same as if the command were issued from the control-
should be used to reclaim the resources. That is, instead of ling program or procedure.
using the RCLRSC command following a COBOL program
Note: Using the *CALLER value can cause unexpected
that might end abnormally, the user should, in the COBOL
results when running the RCLRSC command
program, use a CANCEL statement that can be processed
from a command line or from within a program
when an abnormal condition occurs in that program.
that works with open files.
The RCLRSC command does not close files that were OPTION
opened with the Open Database File (OPNDBF) or the Open Specifies whether a normal or abnormal close notifica-
Query File (OPNQRYF) commands specifying tion is sent to the attached host system when mixed,
TYPE(*PERM). communications, BSC, and ICF files are closed. This
parameter is ignored for all other files and objects.
*NORMAL: The attached host system is given a normal In this example, PROGA is a controlling program that is
close notification when mixed, communications, BSC, written in another high-level language. The RCLRSC
and ICF files are closed. command cannot be issued from the high-level language
program so PROGD, a CL program, is called to issue the
*ABNORMAL: The attached host system is given an
command. When the RCLRSC command is issued in
abnormal close notification when mixed, communica-
PROGD, the static storage used by PROGB and PROGC is
tions, BSC, and ICF files are closed. Use this when the
freed; files that were left open are closed.
controlling program detects error conditions that should
be communicated to the host systems (the error condi-
Example 2
tion need not be file-related).
PROGA ┌───────5PROGB
┌────────────┐ │ ┌────────────┐
Examples │ . │ │ │ . │
│ . │ │ │ . │
│CALL PROGB──┼─┘ │CALL PROGC──┼──┐
Example 1 │ . %────────┼────┐ │ . %────────┼──┼─┐
PROGA │RCLRSC │ └─────┤RETURN │ │ │
└────────────┘ └────────────┘ │ │
│ │
│ │
CALL PROGB PROGC%──────────┘ │
RCLRSC ┌─────────┐ │
│ . │ │
│ . │ │
│RETURN───┼───────┘
CALL PROGC └─────────┘
RCLRSC
In this example, PROGA is a controlling program. When the
RCLRSC command is issued, the static storage used by
PROGB and PROGC is freed; files that were left open are
closed.
In this example, PROGA is a controlling program in an appli-
cation. PROGA calls other programs, which return control to Example 3
PROGA when they have finished running. Because control
is returned to the next sequential instruction, the RCLRSC PROGA PROGC
┌──────────────┐ ┌─────────────┐
command is issued following each CALL command to free │ . │ │ . │
the static storage that was used by the called program, and │ . │ │ . │
to close the files that were left open. │ CALL PROGB │ │ CALL PROGB │
│ │ │ │
│ TFRCTL PROGC │ │ RCLRSC │
Example 2 └──────────────┘ └─────────────┘
PROGA ┌──────PROGD
┌───────────┐ │ ┌─────────────────────┐
In this example, PROGA calls PROGB and, after returning
│ . │ │ │ RCLRSC LVL(\CALLER) │ from PROGB, PROGA transfers to program PROGC.
│ . │ │ ┌─┤ RETURN │ Because PROGB has already been called, static storage
│CALL PROGB │ │ │ └─────────────────────┘
│ . │ │ │
exists, and the call to PROGB from PROGC does not cause
│ . │ │ │ any new allocation for static storage; PROGC cannot reclaim
│CALL PROGC │ │ │ the static storage used by PROGB. If PROGB opened files
│ . │ │ │ when it was called by PROGA, these files would remain
│ . │ │ │
│CALL PROGD─┼─┘ │ open; if PROGB opened files when it was called by PROGC,
│ . %───────┼────┘ these files are closed.
└───────────┘
Example 3
Default Activation Group This example shows how ILE procedures and activation
┌────────────────────────────┐
│ PROGA │ groups are affected by the RCLRSC command.
│ ┌────────────┐ │
│ │ CALL PROGB ├──┐ │ In this example, PROGA is a program running in the default
│ │ . │ │ │ Activation Group AG1 activation group. PROGA calls program PROGB which runs
│ │ . │ │ │ ┌──────────────────────┐
│ │ RCLRSC │%─┼────┐ │ │ │ in the default activation group. PROGB calls ILE procedure
│ └────────────┘ │ │ │ │ │ PROCC which runs in the default activation group. PROCC
│ │ │ │ ┌─────┼─5 PROCD │ calls ILE procedure PROCD which causes activation group
│ │ │ │ │ │ ┌────────────┐ │
│ │ │ │ │ │ │ . │ │ AG1 to be created. PROCD returns to PROCC. PROCC
│ PROGB %────┘ │ │ │ │ │ . │ │ returns to PROGB. PROGB returns to PROGA, which then
│ ┌────────────┐ │ │ │ │ │ . │ │ calls the RCLRSC command.
│ │ CALL PROCC ├───┐ │ │ │ ┌──┼────┤ RETURN │ │
│ │ . │ │ │ │ │ │ │ └────────────┘ │
│ │ . │%──┼─┐ │ │ │ │ │ │ PROGA calls the RCLRSC command. Any resources in use
│ │ RETURN ├───┼─┼─┘ │ │ │ │ │ by PROGA are still open, since PROGA is still in use. Any
│ └────────────┘ │ │ │ │ │ │ │ resources by program PROGB or procedure PROCC are
│ │ │ │ │ │ └──────────────────────┘
│ │ │ │ │ │ reclaimed, since the program and procedure ran in the
│ │ │ │ │ │ default activation group and are no longer active. Any
│ PROCC %─────┘ │ │ │ │ resources opened by procedure PROCD are left alone, since
│ ┌────────────┐ │ │ │ │
│ │ CALL PROCD │ │ │ │ │ procedure PROCD ran in activation group AG1 and only the
│ │ . ├─────┼────┼──┘ │ default activation group is affected by the RCLRSC
│ │ . │%────┼────┼─────┘ command.
│ │ RETURN ├─────┘ │
│ └────────────┘ │
└────────────────────────────┘ Any other use of the RCLRSC command can result in files
remaining open and storage remaining allocated.
(P) ───────────────────────────────────────────────────────────────────5%
55──RCLSPLSTG──DAYS(──┬─\NONE───────────────────────┬──)────
└─days-to-keep-unused-storage─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose DAYS
Specifies that storage for spooled files that have not
The Reclaim Spool Storage (RCLSPLSTG) command been used for the number of days specified by the user
reclaims unused storage for spooled files that have not been is reclaimed.
used for more than the number of days specified by the user.
*NONE: All unused storage for spooled files is
Spooled files are stored with database file members on the
reclaimed. If there is no unused storage when subse-
system. When a spooled file is deleted, the member is
quent spooled files are created, then the system allo-
emptied but not deleted. Therefore, the member can be
cates storage for those spooled files. The allocation of
reused for the next spool file created. Reusing empty
storage for these spooled files may slow down the jobs
members improves the performance time when creating new
that are creating them. More information is in the Data
spooled files. The RCLSPLSTG command deletes unused
Management book.
and empty database members. This command uses syn-
chronous processing. More information about synchronous days-to-keep-unused-storage: Specify the number of
processing is in the Backup and Recovery book. days to keep unused storage for spooled files. Storage
that remains unused for more than the number of speci-
Restriction: This command is shipped with public fied days is reclaimed.
*EXCLUDE authority and the QPGMR, QSYSOPR, QSRV,
and QSRVBAS user profiles have private authorities to use
the command. Example
RCLSPLSTG DAYS(3ð)
Note: To see the parameter and value descriptions for this
command, refer to the online help text. For more This command reclaims all unused storage for spooled files
information about printing the help text, refer to that have remained unused for more than 30 days. When
“Printing CL Command Descriptions” in Chapter 1. storage has been unused for 1 second over 30 days it is
reclaimed because a date and time stamp is placed on the
Required Parameters storage area.
(P)─┬─────────────────────────┬──┬───────────────────────┬───────────────────────────────────────────────────────────5%
55──RCLSTG───
│ ┌─\ALL────┐ │ │ ┌─\NONE───┐ │
└─SELECT(──┴─\DBXREF─┴──)─┘ └─OMIT(──┴─\DBXREF─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
Note: The RCLSTG command can be a long-running func- *DBXREF: The database cross-reference table reclaim
tion, depending on the number and type of objects in function is performed.
the system, the amount of damage to them, the OMIT
amount of auxiliary storage configured to the system, Specifies the reclaim functions to be omitted from the
and the percentage of that storage in use. If data- reclaim operation.
base file objects are damaged, the keyed access
paths may need to be rebuilt; that operation takes a *NONE: No reclaim functions are omitted.
substantial amount of time. If the RCLSTG command *DBXREF: The database cross-reference table reclaim
can be run at the user's discretion, the user may want function is omitted.
to avoid the operation until the required time can be
scheduled.
Examples
Restrictions:
Example 1: Reclaim Storage of the Entire System
RCLSTG
Lost objects that are deleted are certain user objects and These directories are automatically created as needed
certain OS/400 system objects that are damaged and not by the RCLSTG command. An informational message is
usable. sent to the QSYSOPR message queue for each object
inserted in to one of these special reclaim storage direc-
The QRCL library, which is created (when needed) by the tories.
RCLSTG command, is a permanent library; but if it contains Note: For user-created objects remaining in QReclaim
no objects at the end of the operation because they were all directories after storage is reclaimed, the user
reclaimed, the library is deleted. must either move them to the appropriate direc-
tory, using the Move (MOV) command, or delete
The '/QReclaim' directories and
them, using the Remove Link (RVMLNK)
'/dev/QASPxx/QReclaimFS.udfs' user-defined file systems,
command. It may also be necessary to use the
which are created (when needed) by the RCLSTG command,
Change Authority (CHGAUT) command to grant
are permanent directories; but if they contain no objects at
specific authority to use the reclaimed objects
the end of the operation because there were no lost objects,
again.
the directories and UDFS are deleted.
In order to access the QReclaim directories that
Example 2: Reclaim Storage to Reclaim the Database are located in a user-defined file system, or to
Cross-reference Table
access the objects in one of the butes, checkout status, create auditing value (for directo-
/dev/QASPxx/QReclaimFS.udfs file systems, that ries), and file CCSID may no longer be available, even
user-defined file system must be mounted over a though the objects themselves can be reclaimed.
directory using the ADDMFS command.
User-created objects whose owners cannot be identified
Recovered user space (*USRSPC), user index are assigned to the system default owner user profile
(*USRIDX), and user queue (*USRQ) user domain (QDFTOWN). After storage is reclaimed, the Change
objects are deleted when neither QRCL nor the special Object Owner (CHGOBJOWN) command is used to
value *ALL are specified on the system value transfer each object back to its original owner or to a
QALWUSRDMN (allow user domain objects in libraries). new owner. As an object is transferred to an owner, a
If these recovered user objects are system domain message, stating that the object has been transferred
objects, they are moved to QRCL. and giving the name of the owner to whom it is trans-
ferred, is sent to the QSYSOPR message queue.
For lost objects that are placed in the QRCL library, if
more than one lost object has the same name and type, Damaged database files for which data still exists are
a unique name is assigned to each of those objects, rebuilt as field-level files. These field-level files are iden-
except the first one, and its original name is retained in tified in the QRCL library in their text descriptions.
the object's text description.
A log of the actions taken by the RCLSTG command
For lost objects that are placed in one of the QReclaim (such as objects deleted or renamed, and ownerships
directories, a unique name is given to them. Their ori- transferred) is sent to the QSYSOPR message queue
ginal name is lost. and to the QHST system log. The message CPF8260 is
For lost objects that are placed in the QRCL library, always sent to QHST. The logged objects in libraries
information such as save/restore history, programming are displayed by the Display Object Description
change status, and text descriptions, may no longer be (DSPOBJD) command for additional information about
retrievable, even though the objects themselves can be the damaged or repaired object. The logged objects in
reclaimed. directories are displayed by the Work with Object Links
(WRKLNK) command.
For lost objects that are placed in one of the QReclaim
directories, information such as personal computer attri-
55──RCLTMPSTG──┬───────────────────────────┬──┬──────────────────────────────┬─────────────────────────────────────────────────5%
│ ┌─\ALL─────────┐ │ │ ┌─7──────────────┐ │
└─LIB(──┼─\LIBL────────┼──)─┘ └─DAYS(──┼─\NONE──────────┼──)─┘
├─\CURLIB──────┤ └─number-of-days─┘
├─\USRLIBL─────┤
├─\ALLUSR──────┤
└─library-name─┘
Compressed Objects are objects that consume less *ALL: All libraries in the system, including QSYS, are
storage space than decompressed objects. When a searched.
compressed object is used or a compressed program is *LIBL: All libraries in the job's library list are searched
called, a decompressed version of the object automat- until the first match is found.
ically becomes available to the user.
*CURLIB: The current library for the job is searched. If
Decompressed Objects are objects that use the system no library is specified as the current library for the job,
storage space allocated to them and are in a final, the QGPL library is used.
ready-to-use state.
*USRLIBL: Only the libraries in the user portion of the
Temporarily Decompressed Objects are temporarily job's library list are searched.
decompressed copies of compressed objects. The
system allocates storage space for the decompressed *ALLUSR: All user libraries are searched. All libraries
objects, which is consumed by the temporary copies with names that do not begin with the letter Q are
until the system or the user determines that the tempo- searched except for the following:
rary storage space needs to be reclaimed. #CGULIB #DFULIB #RPGLIB #SEULIB
#COBLIB #DSULIB #SDALIB
Temporary storage is automatically reclaimed when:
Although the following Qxxx libraries are provided by
– The RCLTMPSTG command is run
IBM, they typically contain user data that changes fre-
– The next initial program load (IPL) is run quently. Therefore, these libraries are considered user
– The object is used often enough to cause the libraries and are also searched:
system to permanently decompress it | QDSNX QPFRDATA QUSRBRM QUSRSYS
| QGPL QRCL QUSRIJS QUSRVxRxMx
When an object is permanently decompressed, the com- | QGPL38 QS36F QUSRINFSKR
pressed version of the object is destroyed as well as any | QMQMDATA QUSER38 QUSRNOTES
temporary forms of the object; however, compressed | QMQMPROC QUSRADSM QUSRRDARS
versions remain intact as long as the objects are tempo-
rarily decompressed. Note: A different library name, of the form
QUSRVxRxMx, can be created by the user for
Restrictions: each release that IBM supports. VxRxMx is the
version, release, and modification level of the
1. This command is shipped with public *EXCLUDE
library.
authority and the QPGMR, QSYSOPR, QSRV, and
QSRVBAS user profiles have private authorities to use library-name: Specify the name of the library to be
the command. searched.
2. The user must have object management authority to the DAYS
object specified and execute authority to the library. Specifies the number of days an object has not been
Note: To see the parameter and value descriptions for this used or changed. If a temporarily decompressed object
command, refer to the online help text. For more has not been used or changed for more than the speci-
information about printing the help text, refer to fied number of days, it is reclaimed. If it has been used
“Printing CL Command Descriptions” in Chapter 1. or changed, it is left temporarily decompressed.
7: Objects that have not been used or changed for temporary space allocated for it is reclaimed. Valid
more than seven days are reclaimed. values range from 1 through 366.
*NONE: The storage space allocated for a temporarily
decompressed object is reclaimed regardless of the Example
number of days it has not been used or changed, unless
RCLTMPSTG LIB(QGPL)
the object is in use when this command is run.
number-of-days: Specify the number of days a tempo- This command reclaims the space consumed by all of the
rarily decompressed object can be unused before the temporarily decompressed copies of objects in library QGPL
that have not been used or changed in the last 7 days.
(P) ───────────────────────5
55──RCVDST──DSTID(──'distribution-ID'──)──┬────────────────────────────┬──┬──────────────────────────┬───
│ ┌─\NONE─────────┐ │ │ ┌─\NONE───────┐ │
└─DOC(──┴─document-name─┴──)─┘ └─FLR(──┴─folder-name─┴──)─┘
5──┬────────────────────────────────────────────────────────┬──┬───────────────────────────────────────────┬────────────────────5
│ ┌─\NONE─────────────────────────────────┐ │ │ ┌─\FIRST──────┐ ┌─\REPLACE─┐ │
│ │ ┌─\LIBL/────────┐ │ │ └─OUTMBR(──┴─member-name─┴──┼──────────┼──)─┘
└─OUTFILE(──┴─┼───────────────┼──database-file-name─┴──)─┘ └─\ADD─────┘
├─\CURLIB/──────┤
└─library-name/─┘
5──┬─────────────────────────────────────────┬──┬──────────────────────────────────────┬──┬──────────────────────┬──────────────5
│ ┌─\DFT─────────────────┐ │ │ ┌─\CURRENT──────────────┐ │ │ ┌─\YES─┐ │
└─OUTDTATYP(──┼─\ALL─────────────────┼──)─┘ └─USRID(──┴─user-ID──user-address─┴──)─┘ └─ACKRCV(──┴─\NO──┴──)─┘
│ ┌──
───────────────┐ │
└──6┬─\DSTINFO────┬┴───
(1) ─┘
├─\MSG────────┤
├─\DOCD───────┤
├─\DOCDATE────┤
├─\FILDATE────┤
├─\CRTDATE────┤
├─\REF────────┤
├─\CHGDATE────┤
├─\EXPDATE────┤
├─\ACTDATE────┤
├─\CMPDATE────┤
├─\SUBJECT────┤
├─\FILCAB─────┤
├─\STATUS─────┤
├─\AUTHOR─────┤
├─\DOCCLS─────┤
├─\KWD────────┤
├─\CPYLST─────┤
├─\AUTUSR─────┤
├─\DSTEXPDATE─┤
├─\RPYDATE────┤
├─\IDP────────┤
├─\DOC────────┤
└─\PROJECT────┘
5──┬─────────────────────────────────────────────┬──┬────────────────────┬──────────────────────────────────────────────────────5
│ ┌─\NONE─────────────────────┐ │ │ ┌─\NO──┐ │
└─DSTIDEXN(──┴─distribution-ID-extension─┴──)─┘ └─KEEP(──┴─\YES─┴──)─┘
5──┬──────────────────────────────────────────────────────┬────────────────────────────────────────────────────────────────────5%
│ ┌─\SYSVAL──────────────────────────┐ │
(2) ─┼─\DEVD────────────────────────────┼──)─┘
└─CMDCHRID(───
└─graphic-character-set──code-page─┘
Notes:
P All parameters preceding this point can be specified in positional form.
1 A maximum of 24 repetitions
received. If the identifier represents an outgoing distri- (output files) is in the Office Services Concepts and
bution, an error message is returned to the user. Programmer’s Guide book.
The distribution identifier consists of the sender's *NONE: The output is not directed to a database file.
address (padded on the right with blanks up to 8 charac-
The name of the database file can be qualified by one of
ters), the sender's user ID (padded on the right with
the following library values:
blanks up to 8 characters), and a 4-digit zoned
sequence number with leading zeros, for example, *LIBL: All libraries in the job's library list are
'NEWYORK␣SMITH␣␣␣ð2ð4' searched until the first match is found.
Record Code Description *KWD: The keyword records are written to the output
010 Distribution Description file.
020 Message Text
*CPYLST: The copy list records are written to the
105 Document Description
output file.
110 Creation Date
115 Expiration date *AUTUSR: The authorizing Userid and Address is
120 Document date written to the output file.
125 File date
130 Change date *DSTEXPDATE: The distribution expiration date and
135 Action due date time is written to the output file.
140 Completion date
*RPYDATE: The reply requested date and time is
145 Author
150 Copy list written to the output file.
155 Document class *IDP: The complete document record (base sub-profile,
160 File cabinet reference application subprofile, and any private sub-profiles) is
165 Subject
written to the output file.
170 Keyword
175 Reference *DOC: The document data records are written to the
180 Status output file.
185 Project
190 Authorizing Userid and Address *PROJECT: The project record is written to the output
195 Distribution expiration date and time file.
200 Reply requested date and time
500 Interchange document profile data USRID
800 Document Data Specifies the user ID and address of the user for whom
the distribution is received. The current user of this
*DSTINFO: The distribution description record is written command must have the authority to work on behalf of
to the output file. the specified user ID and address.
*MSG: The message text record is written to the output *CURRENT: The user profile that is currently running is
file. used.
*DOCD: The document description record is written to Element 1: User ID
the output file.
user-ID: Specify the user ID of the user for whom the
*DOCDATE: The document date record is written to the distribution is received.
output file.
Element 2: User Address
*FILDATE: The file date record is written to the output
user-address: Specify the user address of the user for
file.
whom the distribution is received.
*CRTDATE: The create date record is written to the
output file. ACKRCV
Specifies whether the acknowledgment for confirmation
*REF: The reference record is written to the output file. of delivery is sent back to the sender of the distribution.
*CHGDATE: The change date record is written to the *YES: The confirmation of delivery is sent back to the
output file. sender.
*EXPDATE: The expiration date record is written to the *NO: The confirmation of delivery is not sent back to
output file. the sender.
*ACTDATE: The action due date record is written to the
DSTIDEXN
output file.
Specifies the extension of the distribution identifier speci-
*CMPDATE: The completion date record is written to fied on the DSTID parameter. This extension uniquely
the output file. identifies duplicate distributions. This extension is a
*SUBJECT: The subject records are written to the 2-digit extension that ranges from 01 through 99. For
output file. example, if the distribution ID is NEWYORK SMITH
0204 and two copies of this distribution were sent to a
*FILCAB: The filing cabinet reference record is written user, then the user has 2 distributions with the same dis-
to the output file. tribution ID. To distinguish the two distributions, an
*STATUS: The status record is written to the output file. extension is added to each distribution ID and one
extension is NEWYORK SMITH 020401 and the other
*AUTHOR: The author records are written to the output
one is NEWYORK SMITH 020402. If there are no dupli-
file.
cates, the extension defaults to 01. These extensions
*DOCCLS: The document class record is written to the map one to one with the distribution ID specified on the
output file. DSTID parameter.
*NONE: There is no duplicate distribution. This is *DEVD: The system determines the graphic character
equivalent to an extension of 01. set and code page values for the command parameter
from the display device description where the command
distribution-ID-extension: Specify the extension associ-
is entered. This option is valid only when specified from
ated with the distribution. This is used to uniquely iden-
an interactive job. If this value is specified in an interac-
tify duplicate distribution IDs.
tive CL program or a batch job, an error message is
KEEP sent.
Specifies whether this distribution is either deleted from,
Element 1: Character Set
or kept in, the mail log.
graphic-character-set: Specify the graphic character set
*NO: When all the information requested has been
values used to create the command parameter.
written to the output file or document object name, the
distribution is removed from the user's incoming mail. Element 2: Code Page
*YES: When all the information requested has been code-page: Specify the code page. Valid values range
written to the output file or document object name, the from 1 through 9999.
distribution is not removed from the user's incoming mail.
The incoming distribution is available for another Examples
RCVDST request or for processing by another DIA inter-
face, such as OfficeVision. Example 1: Receiving Current User Distribution
CMDCHRID RCVDST DISTID('SYSTEM1 USERA ððð1')
Specifies the character identifier (graphic character set OUTFILE(MYLIB/MYFILE)
and code page) for data being specified as parameter OUTMBR(MYMBR \ADD) OUTDTATYP(\ALL) CMDCHRID(\DEVD)
values on this command. This character identifier
This command receives the current user distribution into
(CHRID) is related to the display device used to specify
output file MYFILE located in library MYLIB. The distribution
the command. More information about CHRID pro-
is added to member MYMBR. All output file information is
cessing is in the Application Display Programming book.
added to the output file MYFILE.
Note: This value translates the DSTID and USRID
parameters to the character set and code page Example 2: Receiving Distribution Sent to a User
of '930 500'. The SNA Distribution Services RCVDST DSTID('BAKER␣RCH38P␣ðð19') DSTINDEXN(ð1)
book contains the character set and code page OUTFILE(JOWLIB/DOCUMENTS) USRID(\CURRENT)
table for '930 500'.
This command receives a distribution that was sent to a
*SYSVAL: The system determines the graphic char-
user. It is copied into the first member in a database file
acter set and code page values for the command param-
called DOCUMENTS in a library called JOWLIB.
eters from the QCHRID system values.
55──RCVF──┬──────────────────────────┬──┬──────────────────────────────────────┬───(P) ──┬────────────────────┬────────────────────5%
│ ┌─\FILE───────┐ │ │ ┌─\FILE──────────────┐ │ │ ┌─\YES─┐ │
(1) ─┴─record-format-name─┴──)─┘
└─DEV(──┴─device-name─┴──)─┘ └─RCDFMT(─── └─WAIT(──┴─\NO──┴──)─┘
Notes:
1 A CL variable cannot be coded on this parameter.
Example 2 The CL program receives user data from several devices one
at a time by way of the device file named MSCREEN. The
DCLF FILE(SCREENX) RCDFMT(R1 R2)
program receives data from the device named in the variable
RCVF DEV(DISPLAY2) RCDFMT(R1) &DNAME using the record format MIN2, but it does not wait
for the data to come in. The same RCVF command is used
The CL program receives data from the user at the display to receive data from several devices; because the CL vari-
station named DISPLAY2. The data is received in the record able &DNAME is used, only the device name in the DEV
format named R1 in the device file named SCREENX. The parameter must be changed each time the command is run.
program waits for the user data before it continues pro- A WAIT command for each device must be issued later in
cessing. the program because the WAIT command actually receives
the data. Both the RCVF and the WAIT commands may be
Example 3 processed for each device (one at a time) to send data to the
DCLF FILE(INPUT) program. If a user response is delayed, the commands can
be processed as many times as necessary until the user
RCVF responds with the data or a End Receive (ENDRCV)
MONMSG CPFð864 EXEC(GOTO EOF) command cancels the request.
┌─\LIBL/────────┐ ┌─\LIBL/────────┐
55──RCVJRNE──JRN(──┼───────────────┼──journal-name──)──EXITPGM(──┼───────────────┼──program-name──)───────────────────────────────────────────────5
├─\CURLIB/──────┤ ├─\CURLIB/──────┤
└─library-name/─┘ └─library-name/─┘
5──┬───────────────────────────────────────────────────────────────────────────────────────┬──────────────────────────────────────────────────────5
│ ┌─\ALLFILE────────────────────────────────────────────────────────────────┐ │
│ │ ┌──
──────────────────────────────────────────────────────────────────┐ │ │
│ │ │ ┌─\LIBL/────────┐ ┌─\FIRST──────┐ │ │ │
6 (1) (2)
└─FILE(──┴───(──┼───────────────┼──┬─\ALL───────────────┬──┼─────────────┼──)─┴────┴──)─┘
├─\CURLIB/──────┤ └─physical-file-name─┘ ├─\ALL────────┤
└─library-name/─┘ └─member-name─┘
(P) ──────────────────────────────────5
5──┬────────────────────────────────────────────────────────────────────────────────────────────────────────┬───
│ ┌─\CURRENT───────────────────────────────────────────────────────────────────────────────┐ │
└─RCVRNG(──┼─\CURCHAIN──────────────────────────────────────────────────────────────────────────────┼──)─┘
│ ┌─\CURRENT────────────────────────────────┐ │
│ ┌─\LIBL/────────┐ │ ┌─\LIBL/────────┐ │ │
└─┼───────────────┼──start-journal-receiver──┴─┼───────────────┼──end-journal-receiver─┴─┘
├─\CURLIB/──────┤ ├─\CURLIB/──────┤
└─library-name/─┘ └─library-name/─┘
5──┬────────────────────────────────────────────────┬──┬──────────────────────────────────────────┬──┬───────────────────────┬────────────────────5
│ ┌─\FIRST───────────────────┐ │ │ (3) ──────────────┐
┌─\NONE──── │ │ ┌─\ALL──┐ │
├─FROMENT(──┴─starting-sequence-number─┴──)──────┤ ├─TOENT(──┼─\LAST──────────────────┼──)────┤ └─NBRENT(──┴─value─┴──)─┘
└─FROMTIME(──starting-date──┬───────────────┬──)─┘ │ └─ending-sequence-number─┘ │
└─starting-time─┘ └─TOTIME(──ending-date──┬─────────────┬──)─┘
└─ending-time─┘
5──┬────────────────────────────────────────────────────────┬──┬───────────────────────────────────┬──────────────────────────────────────────────5
│ ┌─\ALL───────────────────────────────────┐ │ │ ┌─\ALL──────────────┐ │
└─JRNCDE(──┼─\CTL───────────────────────────────────┼──)─┘ └─ENTTYP(──┼─\RCD──────────────┼──)─┘
│ ┌──
─────────────────────────────────┐ │ │ ┌──
────────────┐ │
│ │ ┌─\ALLSLT───────┐ │ │ └──6─entry-type─┴───
(6) ─┘
└──6─journal-code──┴─\IGNFILSLT────
(4) ┴─┴───
(5) ─┘
5──┬────────────────────────────────────────────────────────┬──┬───────────────────────────┬──┬───────────────────────────┬───────────────────────5
│ ┌─\ALL──────────────────────────────────────┐ │ │ ┌─\ALL─────────┐ │ │ ┌─\ALL──────┐ │
└─JOB(──┼─\─────────────────────────────────────────┼──)─┘ └─PGM(──┴─program-name─┴──)─┘ └─USRPRF(──┴─user-name─┴──)─┘
└─┬─────────────────────────────┬──job-name─┘
└─┬─────────────┬──user-name/─┘
└─job-number/─┘
5──┬───────────────────────────────────────────┬──┬───────────────────────┬──┬─────────────────────────────────────────────┬──────────────────────5
│ ┌─\ALL────────────────────┐ │ │ ┌─\ALL──┐ │ │ ┌─3ð────────────────────────┐ │
(7) ─┼─seconds───────────────────┼──)─┘
└─CMTCYCID(──┴─commit-cycle-identifier─┴──)─┘ └─DEPENT(──┴─\NONE─┴──)─┘ └─DELAY(────
(10)
└─\NEXTENT──────┬─\CLS────┬─┘
└─seconds─┘
5──┬────────────────────────┬──┬──────────────────────────────────────────────────────┬──┬───────────────────────────────┬───────────────────────5%
| │ ┌─\TYPE1─┐ │ │ ┌─\ENTFMT───────────────────────┐ │ │ ┌─\CONFIRMED─┐ │
| (8) ─┼─field-length──────────────────┼──)─┘ └─INCENT(────
└─ENTFMT(──┼─\TYPE2─┼──)─┘ └─NULLINDLEN(──── (9) ─┴─\ALL─────
(10) ──┴──)─┘
├─\TYPE3─┤ └─\VARLEN──maximum-field-length─┘
└─\TYPE4─┘
Notes:
1 If *ALL is specified instead of physical-file-name, the format must be library-name/*ALL.
3 TOENT(*NONE) is valid only if the RCVRNG parameter specifies a receiver that is currently attached when starting to
| 5 A maximum of 12 repetitions
6 A maximum of 50 repetitions.
7 This parameter is valid only when TOENT(*NONE) is specified, and the last receiver specified on the RCVRNG parameter
identifies the receiver that is currently attached when starting to receive journal entries.
8 The NULLINDLEN parameter can be specified only if ENTFMT(*TYPE3) or ENTFMT(*TYPE4) is specified.
parameter description. The format of the first parameter Char(1) Passed to the Exit Program
is detailed in the Backup and Recovery book.
N Additional journal entries are not currently
Note: The maximum length of the parameter specifica- available to be passed after this call of the
tion in the exit program is language dependent exit program, or the RCVJRNE command
(for example, for CL or RPG, the maximum will be ending after this call of the exit
length is 9999). For more information about limi- program.
tations refer to the corresponding programming
Y Additional journal entries are currently
language book.
available to be passed after this call of the
| A character variable of LEN(3) is passed in the second exit program.
exit program parameter. This parameter will be passed
Any information passed from the exit program to the
from the system to the exit program and can be passed
system in the second byte will be ignored.
from the exit program to the system. Its values are pre-
sented in the following lists: The second byte of the second exit program param-
eter is provided whether journal entries are being
Information in the first byte of the second parameter: passed as a single journal entry per call of the exit
Char(1) Passed to the Exit Program from the program, or as a block of journal entries per call.
System | Information in the third byte of the second param-
0 No journal entry is passed on this call of | eter:
the exit program. | Char(1) Passed to the Exit Program
1 A single journal entry is passed to the exit | '00'x One or more journal entries are being
program. | passed to the exit program and the object
2 A block of one or more journal entries is | names in the fixed length portion of each
passed to the exit program. | journal entry do not necessarily reflect the
| name of the object at the time the journal
3 No journal entry is passed on this call to
| entry was deposited into the journal.
the exit program, and no more entries can
be passed, because the journal receiver | Note: This value is returned only when
that was attached when the receive | receiving journal entries from a
journal entry operation started is no longer | journal receiver that was attached
attached. | to a journal prior to V4R2M0.
Note: The system ends the RCVJRNE | 0 No journal entries are currently being
command after calling the exit | passed, so the information normally
program once with a reason code | returned in this byte is not applicable.
of 3. | 1 One or more journal entries are being
| 4 No journal entry is passed on this call to | passed to the exit program and the object
| the exit program, and no more entries can | names in the fixed length portion of each
| be passed unless the local or remote | journal entry reflect the name of the object
| journal is activated. | at the time the journal entry was deposited
| into the journal.
| Note: This value can only be passed to
| the exit program when receiving | 2 One or more journal entries are being
| journal entries from the attached | passed to the exit program and the object
| receiver of a local or remote | names in the fixed length portion of each
| journal and the journal state for the | journal entry do not necessarily reflect the
| journal is currently *INACTIVE. | name of the object at the time the journal
| entry was deposited into the journal. The
Char(1) Passed to the System from the Exit
| object name in the fixed length portion of
Program
| the journal entry may be returned as a
8 Requests the command processing | previously known name for the object prior
program to start passing one or more | to the journal entry being deposited into
journal entries in a block. | the journal or be returned as *UNKNOWN.
9 Requests the RCVJRNE command to end. | Note: This value will only be returned
The exit program returns control to the | when receiving journal entries from
system. | a remote journal and the remote
Information in the second byte of the second param- | journal is currently being caught up
eter: | from its source journal. A remote
| journal is being caught up from its
| source journal when the
| *ALL: Journal entries in all physical files in the specified recent break in the chain through the receiver that is
| library (the library name must be specified) whose jour- attached when starting to receive journal entries.
| naled changes are currently in the journal receiver are
Element 1: Starting Journal Receiver
| converted for output. If *ALL is specified and the user
| does not have the required authority to all of the files, an The name of the journal receiver can be qualified by one
| error occurs, and the command ends. of the following library values:
physical-file-name: Specify the name of the physical *LIBL: All libraries in the job's library list are
database file for which a journal entry is received. searched until the first match is found.
Element 2: Member Name *CURLIB: The current library for the job is
searched. If no library is specified as the current
*FIRST: Entries for the first member in the file are
library for the job, the QGPL library is used.
received.
*ALL: Entries for currently existing members of the file
library-name: Specify the name of the library to be
searched.
are received.
member-name: Specify the name of the member for starting-journal-receiver: Specify the name of the first
which journal entries are received. journal receiver that contains the journal entries to be
received.
If *ALL is specified for the file-name value, this member
name is used for all applicable files in the library. For Element 2: Ending Journal Receiver
example, if library-name/*ALL *FIRST is specified on the *CURRENT: The journal receiver that is currently
FILE parameter, the journal entries of the first members attached when starting to receive journal entries is used.
of all applicable files in the specified library are received.
The name of the journal receiver can be qualified by one
| Note: If more than the maximum number of members of the following library values:
| is identified (32767 members if a list of files is
specified), an error occurs and no entries are *LIBL: All libraries in the job's library list are
received. This restriction is ignored if *ALLFILE searched until the first match is found.
is specified. *CURLIB: The current library for the job is
If the specified physical file does not exist on the searched. If no library is specified as the current
system, specify either *ALL or a specific file member library for the job, the QGPL library is used.
name. library-name: Specify the name of the library to be
searched.
RCVRNG
Specifies the starting (first) and ending (last) journal ending-journal-receiver: Specify the qualified name of
receivers used in the search for the journal entries that the last journal receiver that contains journal entries to
are received. The system starts the search with the be received. If the end of the receiver chain is reached
starting journal receiver (as specified by the first value) before a receiver with this name is found, an error
and proceeds through the receiver chain until the ending message is sent and no journal entries are received.
journal receiver (as specified by the last value) is pro-
Note: The maximum number of receivers in the range
cessed.
is 256. If more receivers than this maximum are
If dual receivers (receivers attached and detached in specified, an exception is signaled, and no
pairs) are used at any time, the system uses the first of journal entries are received.
the paired receivers when chaining through the
receivers. The Work with Journal Attributes (WRKJRNA) FROMENT
command can be used to display the order of the Specifies the first journal entry considered for reception.
receivers in the receiver chain. *FIRST: The first journal entry in the journal receiver
If a problem is found in the receiver chain (such as range specified is the first entry considered for reception.
damaged or not-found receivers) before the search oper- starting-sequence-number: Specify the sequence
ation begins, the system tries to use the second of the number of the first journal entry considered for reception.
dual receivers. If these receivers also are damaged or
not found, the operation ends. FROMTIME
Specifies the date and time of the first journal entry con-
*CURRENT: The journal receiver that is currently sidered for reception. The journal entry with the speci-
attached when starting to receive journal entries is used.
fied date and time or the next later journal entry is the
*CURCHAIN: The journal receiver chain that includes starting point for reception of journal entries.
the journal receiver that is currently attached when
Element 1: Starting Date
starting to receive journal entries is used. This receiver
chain does not cross a break in the chain. If there is a starting-date: Specify the date of the first journal entry
break in the chain, the receiver range is from the most considered for reception. The format of the date must
A job identifier is a special value or a qualified name *ALL: The journal entries relating to trigger programs
with up to three elements. For example: and referential constraints are received.
\ALL *NONE: The journal entries relating to trigger programs
\ and referential constraints are not received.
job-name
user-name/job-name DELAY
job-number/user-name/job-name Specifies the number of seconds that the command pro-
cessing program (CPP) waits for a new journal entry to
More information on this parameter is in Appendix A,
arrive if the last entry has already been received. After
“Expanded Parameter Descriptions.”
the last entry in the journal is received and passed to the
*ALL: The journal entries received are not limited to a exit program, the CPP tries to receive the next entry. If
specified job. no new journal entry exists, the exit program is passed a
*: The journal entries received are limited to those for value of 0 in the first byte of the second parameter.
the current job. Note: This parameter is valid only when
job-name: Specify the name of the job whose journal TOENT(*NONE) is specified, and the last
entries are considered for reception. receiver specified on the RCVRNG parameter
identifies the journal receiver that is currently
user-name: Specify the name of the user of the job attached when journal entries are starting to be
whose journal entries are considered for reception. received.
job-number: Specify the number of the job whose When the last entry on the journal has been passed to
journal entries are considered for reception. the exit program and no journal entries are currently
PGM available to be passed to the exit program, one of the
Specifies whether the journal entries received are limited following occurs:
to the those created for a specified program. If a number of seconds is specified for the first
*ALL: The journal entries received are not limited to element in the list, the exit program is immediately
those created by a specified program. called and a '0' is passed to the first byte of the
second exit parameter indicating that no additional
program-name: Specify the name of the program whose
journal entries are currently available. When the
journal entries are considered for reception. Only journal
exit program returns control to the command, the
entries for this program are considered for reception.
system delays for the specified number of seconds.
USRPRF When the delay time has expired, the system then
Specifies that the journal entries to be received are checks whether any additional journal entries are
limited to the journal entries for a specified user profile available to be passed to the exit program. Any
name. additional entries are passed to the exit program
*ALL: The journal entries received are not limited to sequentially, until there are no more available.
entries for a specified user profile. When there are no further journal entries available,
the exit program is called, and a '0' is passed as the
user-name: Specify the name of the user profile whose
first byte of the second exit program parameter, indi-
journal entries are considered for reception. Only journal
cating there are no more journal entries currently
entries for this user profile are considered for reception.
available. When the exit program returns control to
CMTCYCID the command, the system again delays for the spec-
Specifies that the journal entries are limited to the ified number of seconds.
journal entries that contain the specified commit cycle If there are no new journal entries to pass to the exit
identifier. program after the delay, the exit program is called,
*ALL: The journal entries received are not limited to a and a '0' is passed as the first byte of the second
specified commit cycle identifier. exit program parameter to indicate that no further
journal entries are available. The exit program then
commit-cycle-identifier: Specify the commit cycle identi-
can pass the value '9' for the first byte of the second
fier that limits the journal entries received. Only journal
parameter, indicating that this command is to end.
entries that contain the commit cycle ID are considered
for reception. If *NEXTENT is specified for the first element in the
list, then additional journal entries are passed to the
DEPENT exit program as they become available. When this
Specifies whether to receive the journal entries recording option is used, the second element in the list indi-
actions that occur as a result of a trigger program and cates the maximum number of seconds between
actions on records that are part of a referential con- calls to the exit program. If there are no additional
straint. journal entries to pass after the specified maximum
delay time, the exit program is called, and a '0' is
Table 26 (Page 2 of 2). *TYPE2 Journal Entry Format Table 27. NULLINDLEN(*ENTFMT) Journal Entry Format
for ENTFMT(*TYPE3)
Field Name Length From To
Field Name Length From To
Flag 1 107 107
Commit Cycle ID 10 108 117 Object Library 10 91 100
User Profile 10 118 127 Member Name 10 101 110
System Name 8 128 135 Count/RRN 10 111 120
Reserved 20 136 155 Flag 1 121 121
Entry-Specific Data N1 156 N + 155 Commit Cycle ID 10 122 131
User Profile 10 132 141
Note: System Name 8 142 149
1 Number of Null 5 150 154
The length of the entry-specific data field varies from
Value Indicators1
entry to entry. It is long enough to accommodate all
Null Value Indicators M 155 154+M
the entry-specific data in each received journal entry.
Length of Entry- 5 155+M 159+M
Specific Data2
Entry-Specific Data N 160+M 159+
*TYPE3: The journal entries received include the infor-
M+N
mation returned when ENTFMT(*TYPE2) is specified, Notes:
and the null value indicators. The format of the received
1 This field contains the number of null value indicators
entries depends on the value specified on the
(in decimal digits) in the received journal entry.
NULLINDLEN parameter. The tables in the
2 This field contains the length of the entry-specific data
NULLINDLEN parameter description show the three
(in decimal digits) in the received journal entry.
formats for *TYPE3.
*TYPE4: The journal entries received include the infor-
mation returned when ENTFMT(*TYPE3) is specified,
Table 28. NULLINDLEN(*ENTFMT) Journal Entry Format
the journal identifier, the physical file trigger indicator,
for ENTFMT(*TYPE4)
and the referential constraint indicator. The format of
the received entries depends on the value specified on Field Name Length From To
the NULLINDLEN parameter. The tables in the Entry Length 5 1 5
NULLINDLEN parameter description show the three Sequence Number 10 6 15
formats for *TYPE4. Journal Code 1 16 16
Journal Entry Type 2 17 18
NULLINDLEN Timestamp 26 19 44
Specifies the length, in bytes, used for the null value Job Name 10 45 54
indicators portion of the journal entry received by the User Name 10 55 64
user. This parameter is valid only if ENTFMT(*TYPE3) Job Number 6 65 70
Program Name 10 71 80
or ENTFMT(*TYPE4) is specified.
Object Name 10 81 90
*ENTFMT: All null value indicators are received for Object Library 10 91 100
each journal entry. The format for this value is shown in Member Name 10 101 110
the following tables. Count/RRN 10 111 120
Flag 1 121 121
Note: The number of null value indicators, as well as Commit Cycle ID 10 122 131
the length of the entry-specific data can vary User Profile 10 132 141
from entry to entry. In the following table, the System Name 8 142 149
number of null value indicators is designated by Journal Identifier 10 150 159
the variable 'M' and the length of the entry- Referential 1 160 160
Constraint
specific data is designated by the variable 'N'.
Trigger 1 161 161
Reserved 8 162 169
Table 27. NULLINDLEN(*ENTFMT) Journal Entry Format Number of Null 5 170 174
for ENTFMT(*TYPE3) Value Indicators1
Field Name Length From To Null Value Indicators M 175 174+M
Length of Entry- 5 175+M 179+M
Entry Length 5 1 5 Specific Data2
Sequence Number 10 6 15 Entry-Specific Data N 180+M 179+
Journal Code 1 16 16 M+N
Journal Entry Type 2 17 18 Notes:
Timestamp 26 19 44
1 This field contains the number of null value indicators
Job Name 10 45 54
User Name 10 55 64 (in decimal digits) in the received journal entry.
Job Number 6 65 70 2 This field contains the length of the entry-specific
Program Name 10 71 80 data (in decimal digits) in the received journal entry.
Object Name 10 81 90
Table 31 (Page 2 of 2). NULLINDLEN(*VARLEN field-length) Table 32. NULLINDLEN(*VARLEN field-length) Journal
Journal Entry Format for ENTFMT(*TYPE3) Entry Format for ENTFMT(*TYPE4)
Field Name Length From To Field Name Length From To
Count/RRN 10 111 120 Entry-Specific Data M3 177+ 176+
Flag 1 121 121 field M+ field
Commit Cycle ID 10 122 131 length length
User Profile 10 132 141 Notes:
System Name 8 142 149 1 This field contains the number of null value indicators
Number of Null Value 2 150 151
(in binary digits) in the received journal entry.
Indicators1
2 This field contains the length of the entry-specific
Null Value Indicators field 152 151+
length field data (in decimal digits) in the received journal entry.
length 3 The length of entry-specific data can vary from entry
Length of Entry -Spe- 5 152+ 156+ to entry and is designated by the variable M.
cific Data2 field field
length length
Entry-Specific Data M 157+ 156+ M+
field field | INCENT
length length | Specifies whether only the confirmed or both the con-
Notes: | firmed and unconfirmed, journal entries are converted for
1 This field contains the number of null value indicators (in | output. This parameter only applies when converting
binary digits) in the received journal entry. | journal entries for output from a remote journal.
2 This field contains the length of the entry-specific data (in | Confirmed entries are those journal entries which have
decimal digits) in the received journal entry. | been sent to this remote journal and the state of the
| Input/Output (I/O) to auxiliary storage for the same
| journal entries on the local journal is known.
Table 32. NULLINDLEN(*VARLEN field-length) Journal | Unconfirmed entries are those journal entries which have
Entry Format for ENTFMT(*TYPE4) | been sent to this remote journal, but the state of the
Field Name Length From To | Input/Output (I/O) to auxiliary storage for the same
| journal entries on the local journal is not known, or the
Entry Length 5 1 5
Sequence Number 10 6 15 | object name information for those journal entries is not
Journal Code 1 16 16 | yet known to the remote journal. Unconfirmed journal
Journal Entry Type 2 17 18 | entries can only exist within the attached receiver of a
Timestamp 26 19 44 | remote journal. This only applies if synchronous delivery
Job Name 10 45 54 | mode is being used for a particular remote journal.
User Name 10 55 64
Job Number 6 65 70 | *CONFIRMED: Only those journal entries which have
Program Name 10 71 80 | been confirmed are converted for output.
Object Name 10 81 90
| *ALL: All confirmed and unconfirmed journal entries are
Object Library 10 91 100
| converted for output.
Member Name 10 101 110
Count/RRN 10 111 120
Flag 1 121 121
Commit Cycle ID 10 122 131
Examples
User Profile 10 132 141
Example 1: Receiving Journal Entries
System Name 8 142 149
Journal Identifier 10 150 159 RCVJRNE JRN(APPLIB/JRN1) EXITPGM(MYLIB/RCVPGM)
Referential Con- 1 160 160 FILE(APPLIB/FILE3) TOENT(\LAST)
straint ENTFMT(\TYPE3) NULLINDLEN(\ENTFMT)
Trigger 1 161 161
Reserved 8 162 169 This command receives journal entries from the journal
Number of Null 2 170 171 receiver that is currently attached (when journal entries are
Value Indicators1 starting to be received) to the journal JRN1 in library APPLIB
Null Value Indicators field 172 171+
and passes them one at a time to program RCVPGM in
length field
library MYLIB. Only entries with file-level information for the
length
Length of Entry 5 172+ 176+ first member of file FILE3 in library APPLIB are received.
-Specific Data2 field field The format of each entry passed to the exit program is
length length shown in the "NULLINDLEN(*ENTFMT) Journal Entry Format
for ENTFMT(*TYPE3)" table shown within the NULLINDLEN
parameter description.
The RCVMSG command receives messages from a job You can specify the message being received by indicating
message queue (a message queue associated with a call the message type, the reference key of the message, or
stack entry or the external message queue (*EXT)), or from a both. The program receiving the message can also specify,
named message queue. The program can receive a on the RCVMSG command, whether a message is removed
message from a message queue associated with its own call from the message queue or left there as an old message. If
stack entry or from a message queue associated with the specified message queue is not allocated to the job in
another call stack entry. which this command is entered, or to any other job, the
message queue is implicitly allocated by this command for bound program name, which can be used to qualify the
the duration of the command's processing. procedure name.
*CURLIB: The current library for the job is used to another message available, blanks are returned in all CL
locate the message queue. If no library is specified variables.
as the current library for the job, the QGPL library is
When a message is received from a message queue
used.
associated with a call stack entry, *NEXT works only for
library-name: Specify the name of the library where one call stack entry. *NEXT cannot be used to receive
the message queue is located. messages for multiple call stack entries of the same
program.
message-queue-name: Specify the name of the
message queue from which a message is received. *PRV: The message previous to the message indicated
by the MSGKEY parameter is received.
MSGTYPE
Specifies the type of message received by this program. *RPY: A reply message is received. This program has
The message types *EXCP, and *RQS exists only on job sent an inquiry message to a message queue and
message queues and therefore can be received only expects a reply.
from a job message queue. For the coding relationships *RQS: A request message is received. The message
between the MSGTYPE and MSGKEY parameters, see specifies a request for a function. The receiving
Coding Relationships in the MSGKEY parameter program can then perform the function requested.
description.
MSGKEY
*ANY: Any type of message (except a sender's copy) is Specifies the message reference key of the message
received. To receive a sender's message, that is received.
MSGTYPE(*COPY) must be specified.
*NONE: No message reference key is specified.
*COPY: A copy of an inquiry message that was previ-
*TOP: The top of the message queue is used. *TOP
ously sent is received by this program. The message
can be used only when MSGTYPE(*NEXT) is specified.
queue specified for the PGMQ or MSGQ parameters
It causes the first message on the message queue to be
must be the same queue that was specified for the
received. For program message queues, this is the
RPYMSGQ parameter when the inquiry message was
message following the last request message that was
sent.
received, if any.
*COMP: A completion message is received. It indicates
the status of the work that this program requested of
&CL-variable-name: Specify the name of the control lan-
guage (CL) variable that contains the message reference
another program.
key of the message received by this program. This key
*DIAG: A diagnostic message is received. It provides is assigned by the system and cannot be shown. The
information about errors detected by another program in variable must be a character variable having a length of
the input sent by this program or errors that occurred 4 characters.
when the requested function was being processed by
Coding Relationships: The MSGTYPE and MSGKEY
the other program.
parameters can be used separately in the RCVMSG
*EXCP: An exception message is received. Exception command, or together.
messages (escape, notify, status) are received by the
program in last-in first-out (LIFO) order. The receiving If neither MSGTYPE nor MSGKEY is specified,
program can monitor for exception messages by using MSGTYPE(*ANY) is assumed and the first new
the MONMSG command. message in the queue is received; that is, the mes-
sages are received in FIFO (first-in, first-out) order.
Note: Non-exception messages are received in first-in
first-out (FIFO) order. If one of the message types specified on the
MSGTYPE parameter is *COMP, *DIAG, *INFO,
If an exception message is received from a message *INQ, *RPY, *COPY, or *RQS, a new message of
queue for a procedure, the related exception may not be the specified type is received in FIFO order. If the
handled at the time the RCVMSG command is run. The type is *EXCP, new messages are received in LIFO
RMV parameter can be used to specify whether the (last-in, first-out) order.
exception is to be handled by the RCVMSG command.
If only MSGKEY is specified with a CL variable
*FIRST: The first message currently on the specified name and the message queue contains a message
message queue is received. with the specified message reference key, that
*INFO: An information only message is received. message is received. If the MSGKEY specified is
for a sender's copy message, the reply to the
*INQ: An inquiry message is received.
message is received if it is available. If the reply is
*LAST: The last message currently on the specified not available, blanks will be returned in all CL vari-
message queue is received. ables. If a message is requested by key and the
*NEXT: The message that follows the one specified in message is not available, an escape message is
the MSGKEY parameter is received. If there is not sent to the requesting program.
If MSGTYPE(*COPY) and MSGKEY program ignores the WAIT parameter (Value for Wait is
(&CL-variable-name) are specified, the sender's 0).
copy of an inquiry message is received.
0: The program does not wait for the arrival of a
If both MSGTYPE and MSGKEY message. If a message of the specified type is not in
(&CL-variable-name) are specified and the message the queue when this command is processed, the speci-
queue has a message of that type, the message is fied CL variables are filled with blanks (or zeros, if they
received by the program. If the reference key is are decimal variables).
correct and the message type is not, then an error
*MAX: The program waits indefinitely for the arrival of
message is sent to the program.
the specified type of message.
If MSGTYPE(*NEXT) is specified, MSGKEY must
number-of-seconds: Specifies the number of seconds
be specified. The message following the message
that the program waits for the arrival of a specific type of
with the specified reference key is received. If
message.
MSGKEY(*TOP) is specified with
MSGTYPE(*NEXT), the first message on the RMV
message queue is received. For call message Specifies whether the message received by the program
queues, this is the first message following the last is removed from the message queue. For exception
request message received. messages for unhandled exceptions, also specifies
whether the exception is to be handled by the RCVMSG
If MSGTYPE(*PRV) is specified, MSGKEY must be
command. If MSGTYPE(*INQ) is specified, RMV(*NO)
specified. The message previous to the message
must also be specified so a reply to the inquiry message
with the specified reference key is recieved.
can be sent.
If MSGTYPE(*RPY) is specified with a MSGKEY value
*YES: The message is removed from the message
that refers to either a sender's copy or an inquiry
queue. If the message is an unhandled exception, the
message, any reply to the sender's copy or inquiry
exception is handled by running the RCVMSG
message is returned. If there is no reply to that sender's
command.
copy or inquiry message, blanks are returned. When the
MSGKEY value refers to an inquiry message, the WAIT *NO: The message is not removed from the message
parameter is ignored (this implies WAIT(0), which is the queue. It is left on the message queue as an old
default value for the WAIT parameter). message. If the message is an unhandled exception,
the exception is handled by running the RCVMSG
If MSGTYPE(*ANY) is specified with a KEYVAR variable
command.
and the first message type found is a reply message, the
KEYVAR variable returns the message reference key of Note: Old messages are messages that have been
the sender's copy message. Similarly, if received but not deleted. An old message can
MSGTYPE(*RPY) is specified with a KEYVAR variable, be received again in one of the following ways:
the message reference key of the sender's copy
1. The message reference key of the message
message is returned.
is specified for the MSGKEY parameter.
WAIT 2. A message type of *FIRST, *LAST, *NEXT,
Specifies the length of time (in seconds) that the or *PRV is specified for the MSGTYPE
program waits for a message of the specified type to parameter.
arrive in the message queue if it is not there when this
RCVMSG command is processed. If the message does *KEEPEXCP: If the message is an exception message
not arrive in the specified time, the CL variables named and the exception has not been handled, the exception
to receive message fields are filled with blanks. is left unhandled and the message is left on the
The program cannot wait for a message from a program message queue as a new message. It can be received
message queue unless it is receiving a reply. again by using the RCVMSG command to receive an
*EXCP message. If the message is not an exception
If a wait time is specified (not zero), the message queue
message, or if it is but the exception has already been
is implicitly allocated to the first user whose message is
handled, the message is left on the message queue as
received, and it is not released until the request has
an old message.
been handled by the program.
To handle an exception after the RCVMSG has been
If a message is sent to a message queue in the same
run, the command can be run a second time by speci-
job, and the message queue is in break delivery mode,
fying RMV(*YES) or RMV(*NO).
this parameter is ignored. (that implies WAIT(0), which
is the default value for the WAIT parameter). CCSID
Specifies the coded character set identifier (CCSID) that
If the value specified for MSGKEY refers to an inquiry
you want the message text returned in. This only
message, and MSGTYPE(*RPY) has been specified, the
applies to text returned in the MSG, SECLVL and
MSGDTA parameters. When replacement data is
returned in the MSGDTA parameter or substituted into used again after a message has been received
the text returned in the MSG or SECLVL parameters, and then removed (by specifying *YES on the
only the part of the replacement text that is defined as a RMV parameter).
character that can be converted (*CCHAR) is converted.
The variable must be a character variable having a
The rest of the replacement data is not converted. For
length of 4 characters.
more information about the *CCHAR field, see the
ADDMSGD command. Note: When using the message reference key
(obtained from the CL variable specified by the
*JOB: The received message is converted to the
KEYVAR parameter of the Send Program
CCSID of the job before being returned.
Message (SNDPGMMSG) command) to receive
*HEX: The received message is not converted before the reply to an inquiry message, note that the
being returned. message reference key refers to the sender's
copy. The sender's copy message is located on
coded-character-set-identifier: Specify the CCSID that
the reply message queue (which defaults to the
you want your message converted to before being
program message queue that sent the inquiry
returned. Valid values range from 1 through 65535. For
message), not the message queue to which the
a list of valid CCSID values, see the International Appli-
inquiry message was sent.
cation Development book. Only CCSID values that a job
can be changed to will be accepted. MSG
For more information on the message handler and its Specifies the name of the CL character variable, if any,
use of CCSIDs, see the National Language Support that contains the message text when the message is
book. received by the program. This includes the message
data fields that were substituted for substitution variables
Parameters for Received Message Fields in the text before the message was sent (replies and
immediate messages contain no message data fields).
All of the following parameters are used to specify the names This is a variable-length field, but most first-level
of the CL variables that receive the specified fields and attri- message text is less than 132 characters in length. This
butes of a message when the message is received by the parameter receives the reply from an *INQ message
program. If WAIT (number-of-seconds) is specified, and the sent by the same program that issued the RCVMSG
time-out occurs, the variables, which must already be command.
declared in the program, are filled with blanks. If the
message field returned is larger than the CL variable speci- MSGLEN
fied, the message field is truncated; if the message field is Specifies the name of the CL decimal variable, if any,
shorter, it is padded with blanks. If the program does not that contains the total length of the first-level message
need the value for a specific message parameter, no CL vari- text available to be received. The variable must be a
able is specified for it. If a parameter is not specified, the decimal variable having a length of 5 positions.
corresponding message value is not received in the program.
SECLVL
KEYVAR Specifies the name of the CL character variable, if any,
Specifies the name of the CL character variable, if any, that contains the help text when the message is received
that contains the message reference key identifying the by the program. This includes the message data fields
message received by the program containing this that were substituted for substitution variables in the text
RCVMSG command. At the time the RCVMSG before the message was sent (replies and immediate
command is processed, the system returns the message messages do not have second-level messages). A
reference key to the variable specified by KEYVAR in message data field is a variable length field, but most
this command and changes the received message to an help text is less than 3000 characters in length.
old message. The message reference key can then be
SECLVLLEN
used in the MSGKEY parameter in a subsequent
Specifies the name of the CL decimal variable, if any,
RCVMSG command to receive the old message. If the
that contains the total length of the second-level
message is not found, blanks are returned for the
message available to be received. The variable must be
KEYVAR variable. For reply type messages, use the
a decimal variable having a length of 5 positions.
MSGKEY parameter on this command in conjunction
with the KEYVAR parameter on the SNDPGMMSG MSGDTA
command. The message reference key can also be Specifies the name of the CL character variable, if any,
used by this program for building message subfiles. The that contains the message data record received by the
CL variable is the name of the field for which the program as part of the message. The message data
SFLMSGKEY keyword is specified in the DDS for the record contains the substitution values (in a single char-
message subfile. acter string) that are used in the text of the received
message. The amount of data returned and its format
Note: For message queues not associated with call
depend on the message. Pointers contained in system
stack entries, message reference keys can be
messages are invalidated.
Note: If you use data that has an invalidated pointer in – Program name (10) (for an ILE procedure, this
it an error message can occur. is the bound program name)
– Instruction number (4) (for an ILE procedure,
MSGDTALEN
this field is set to blanks)
Specifies the name of the CL decimal variable, if any,
The next 1 character identifies the sender type
that contains the total length of the message data record
– "0" if the sender is an OPM program or a SLIC
available to be received. The variable must be a
program with 12 characters or less
decimal variable having a length of 5 positions.
– "1" if the sender is an ILE procedure and the
MSGID name is 256 characters or less
Specifies the name of the CL character variable, if any, – "2" if the sender is an ILE procedure and the
that contains the message identifier of the message name is more than 256 characters
received by the program. If the message being received – "3" if the sender is a SLIC program with more
is an immediate message, a message identifier is not than 12 characters
returned. The minimum length of the variable is 7 char- The last 1 character identifies the sent-to type
acters. – "0" if the receiver is an OPM program
– "1" if the receiver is an ILE procedure and the
SEV name is 256 characters or less
Specifies the name of the CL decimal variable, if any, – "2" if the receiver is an ILE procedure and the
that contains the severity code of the message received name is more than 256 characters
by the program. The variable must be a decimal vari-
able having a length of two positions. If the message *LONG: The long format of the sender information is
being received is an immediate message, the message returned. The long format is 720 characters, with the
severity is not returned. last 46 characters set to blanks. The following informa-
tion is returned:
SENDER
Specifies the name of the CL character variable, if any, The first 26 characters identify the sending job
that contains the identification of the sender of the – Job name (10)
message received through the RCVMSG command. – User name (10)
The length of the CL variable depends on the – Job number (6)
SENDERFMT specification. If SENDERFMT(*SHORT) The next 13 characters are the date and time
is specified, the variable should be a minimum of 80 – Date (7) (in the format 0yymmdd)
characters. If SENDERFMT(*LONG) is specified, the – Time (6) (in the format hhmmss)
variable should be a minimum of 720 characters. The next 1 character identifies the sender type
– "0" if the sender is an OPM program or a SLIC
SENDERFMT program with 12 characters or less
Specifies which format of the sender identification is – "1" if the sender is an ILE procedure and the
returned. This parameter is valid only when the name is 256 characters or less
SENDER parameter is specified. – "2" if the sender is an ILE procedure and the
*SHORT: The short format of the sender information is name is more than 256 characters
returned. The short format is 80 characters, with the last – "3" if the sender is a SLIC program with more
9 characters set to blanks. The following information is than 12 characters
returned: The next 1 character identifies the sent-to type
– "0" if the receiver is an OPM program
The first 26 characters identify the sending job – "1" if the receiver is an ILE procedure and the
– Job name (10) name is 256 characters or less
– User name (10) – "2" if the receiver is an ILE procedure and the
– Job number (6) name is more than 256 characters .
The next 16 characters identify the sending program The next 12 characters are the sender's program
– Program name (12) (for an ILE procedure, this name (for an ILE procedure, this is the bound
is the bound program name); if the sender type program name); if the sender type is 3 and the
is 3, the first three characters of this field are program name is greater than 12 characters in
less than symbols (<<<) followed by the last length, the first three characters of this field are less
nine characters of the program name than symbols (<<<) followed by the last nine charac-
– Instruction number (4) (for an ILE procedure, ters of the program name .
this field is set to blanks) The next 10 characters are the sender's module
The next 13 characters are the date and time name (if the sender is not an ILE procedure, this
– Date (7) (in the format 0yymmdd) field is set to blanks)
– Time (6) (in the format hhmmss) The next 256 characters are the sender's procedure
The next 14 characters identify the sent-to call stack name (if the sender is not an ILE procedure, this
entry if the message is sent to a call message field is set to blanks)
queue
– For a nested procedure name, each procedure greater than 1, and each statement
name is separated by a colon (:) starting with number represents a point at which the
the outer-most procedure name , and ending message could have been sent. If it is
with the inner-most procedure name. not possible to return statement
– For a procedure name that is longer than 256 numbers, this count will be 0.
characters, three less than symbols (<<<) are – Statement numbers (30) (a maximum of 3
returned followed by the last 253 characters of statement numbers, 10 characters each)
the procedure name; the QMHRCPM API can
be used to obtain the entire procedure name RTNTYPE
Specifies the name of the CL variable, if any, that con-
The next 1 character is blank tains the type code for the message received by the
The next 4 characters are the number of statement program. The variable must be a character variable
numbers available having a length of 2 positions. The following values are
Note: A statement number represents a point in returned to indicate the message type:
the sending program at which the message
Value Message Type
was sent. For programs and non-optimized
01 Completion
procedures, this count is always 1. For opti-
02 Diagnostic
mized procedures, this count can be greater
04 Information
than 1, and each statement number repre-
05 Inquiry
sents a point at which the message could
06 Sender's Copy
have been sent. If it is not possible to return
08 Request
statement numbers, this count will be 0.
10 Request with prompting
The next 30 characters return a maximum of 3 14 Notify (exception already handled at time of
statement numbers, 10 characters each RCVMSG)
The next 320 characters return program or proce- 15 Escape (exception already handled at time of
dure information if the message being received was RCVMSG)
originally sent to a message queue associated with 16 Notify (exception not handled at time of
a call stack entry (otherwise, this field is set to RCVMSG)
blanks) 17 Escape (exception not handled at time of
– Sent-to program name (10) (for an ILE proce- RCVMSG)
dure, this is the bound program name) 21 Reply, not checked for validity
– Sent-to module name (10) (if the sender is not 22 Reply, checked for validity
an ILE procedure, this field is set to blanks) 23 Reply, message default used
– Sent-to procedure name (256) (if the sender is 24 Reply, system default used
not an ILE procedure, this field is set to blanks) 25 Reply, from System Reply List
- For a nested procedure name, each proce- ALROPT
dure name is separated by a colon (:) Specifies the name of the CL variable, if any, used to
starting with the outer-most procedure return the alert option of the message received by the
name, and ending with the inner-most pro- program. The variable must be a character variable 9
cedure name. positions in length.
- For a procedure name that is longer than
MSGF
256 characters, three less than symbols
Specifies the name of the CL variable, if any, used to
(<<<) are returned followed by the last 253
return the message file name of the message received
characters of the procedure name; the
by the program. If the message received is a stored
QMHRCVPM API can be used to obtain
message, the message file name of the file containing
the entire procedure name
the stored message is returned. If the received
– Blanks (10) message is not a stored message, the message file
– Number of statements available for the name is returned as blanks. The variable must be a
receiving call stack entry (4) character variable 10 positions in length.
Note: A statement number represents a point Note: The message file name returned on this param-
at which the sent-to program was sus- eter is the message file specified or defaulted on
pended (for example, due to a call oper- either the SNDPGMMSG or SNDUSRMSG
ation) at the time the message was command, not the overriding message file. If an
sent. For programs and non-optimized override was specified when sending the
procedures, this count is always 1. For message, the same override should be used
optimized procedures, this count can be when receiving the message.
Note: The message file library name returned on this This command receives the message having the message
parameter is the message file specified or reference key specified by the program variable &KEY from
defaulted on either the SNDPGMMSG or the message queue SMITH. The text of the message is
SNDUSRMSG command, not the overriding copied into the CL variable &WORK.
message file library. If an override was specified
when sending the message, the same override Example 2: Receiving a New Message
should be used when receiving the message. RCVMSG MSGQ(INV) WAIT(12ð) MSG(&WORK)
SNDMSGFLIB This command receives a new message from the message
Specifies the name of the CL variable, if any, used to queue named INV into the CL variable &WORK. The
return the name of the library that contains the message program waits no more than 120 seconds for the arrival of a
file used to send the message. If the message received new message if there are no new messages in the message
is stored in a message file, the name of the library con- queue. If there is more than one new message in the queue,
taining the message file is returned. For example, if the the first message in the queue is the message received by
name of the library containing the message file is the program.
MYLIB, and *LIBL is used to send a predefined
message, this parameter would return MYLIB. If the Example 3: Receiving a Message From a Procedure
message received is not a stored message, the
RCVMSG PGMQ(\SAME CURRENT_MONTH_TOTALS) MSGTYPE(\EXCP)
message file library name is returned as blanks. RMV(\KEEPEXCP) MSGID(&MID) MSG(&MTEXT)
TXTCCSID
This command receives an exception message from the pro-
Specifies the name of the CL variable, if any, used to
cedure CURRENT_MONTH_TOTALS. Since the specified
return the coded character set identifier (CCSID) associ-
name is more than 10 characters, the system does search
ated with the text returned by the MSG and SECLVL
for any programs. If the message is an unhandled excep-
parameters. If a conversion error occurs, or if the
tion, the message is left on the call message queue as a
CCSID you requested the text to be converted to is
new message and the exception is not handled by the
65535, the CCSID that the message description or the
RCVMSG command. The message ID is returned in the CL
text for an immediate message is stored in is returned.
variable &MID and the message text in the CL variable
Otherwise, the CCSID you wanted the text converted to
&MTEXT. To handle the exception and remove the
is returned. If you do not want the text converted before
message, run the following RCVMSG command:
it is returned to you but you do want to know which
CCSID that the message description or the text for an RCVMSG PGMQ(\SAME CURRENT_MONTH_TOTALS)
immediate message is stored in, specify 65535 on the MSGTYPE(\EXCP) RMV(\YES)
CCSID parameter, and the CCSID is returned by the
TXTCCSID parameter. You can also check for a con- Example 4: Receiving a Message from a Program or
version error by comparing the CCSID you passed in Procedure
against the TXTCCSID returned. If they are not equal RCVMSG PGMQ(\SAME TARGETPGM) MSGTYPE(\EXCP)
and they are not 65535, a conversion error occurred. RMV(\NO) MSGID(&MID) MSG(&MTEXT)
RCVMSG PGMQ(\SAME PRINT_RPT_FMT1 DEPTRPTS AREARPTS) tion. The message is always removed from the message
MSGTYPE(\EXCP) RMV(\YES) queue.
MSGID(&MID) MSG(&MTEXT)
Example 6: Receiving a Message Using a Partial Proce-
This command receives an exception message from the dure Name
message queue of the procedure named PRINT_RPT_FMT1.
RCVMSG PGMQ(\SAME HANDLE_FORM_NUM>>>)
The procedure must have been compiled into the module MSGID(&MID) MSG(&MTEXT)
DEPTRPTS and have been bound into the bound program
AREARPTS. Since RMV(*YES) is specified, the exception is This command receives a new message from the most
handled if the exception message is for an unhandled excep- recent procedure whose name begins with
HANDLE_FORM_NUM.
55──RCVNETF──FROMFILE(──file-name──)──┬──────────────────────────────────────────────┬──┬──────────────────────────────┬────────5
│ ┌─\LIBL/────────┐ ┌─\FROMFILE─┐ │ │ ┌─\ONLY───────┐ │
└─TOFILE(──┼───────────────┼──┴─file-name─┴──)─┘ └─FROMMBR(──┴─member-name─┴──)─┘
├─\CURLIB/──────┤
└─library-name/─┘
(P) ──┬──────────────────────────┬──┬────────────────────────────┬──────────────────────────────5
5──┬────────────────────────────┬───
│ ┌─\FROMMBR────┐ │ │ ┌─\REPLACE─┐ │ │ ┌─\LAST─────────┐ │
└─TOMBR(──┼─\FIRST──────┼──)─┘ └─MBROPT(──┴─\ADD─────┴──)─┘ └─NBR(──┼─\ONLY─────────┼──)─┘
└─member-name─┘ └─member-number─┘
5──┬─────────────────────────┬──┬────────────────────────────┬─────────────────────────────────────────────────────────────────5%
│ ┌─\CURRENT──┐ │ │ ┌─\NETFILE─┐ │
└─USER(──┴─user-name─┴──)─┘ └─FROMTYPE(──┴─\SRC─────┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose Note: To see the parameter and value descriptions for this
command, refer to the online help text. For more
The Receive Network File (RCVNETF) command receives a information about printing the help text, refer to
network file and copies the records into a physical database “Printing CL Command Descriptions” in Chapter 1.
file or a save file.
If the original file is a save file, it must be received into a Required Parameter
save file. Once the file has been received, it is removed
FROMFILE
from the queue of network files. Before a file can be
Specifies the name of the file that is received. This is
received, the file specified by the TOFILE parameter must
the name of the file on the sending system.
already exist.
When a source physical file is sent, the source sequence Optional Parameters
number and change date in positions 1 through 12 of the
record are sent with the file. These are kept if the file is TOFILE
received into a source physical file, and are truncated if the Specifies the qualified name of the file that receives the
file is received into a nonsource physical file. When a file copied records.
that was originally a nonsource physical file is received into a Note: If the network file sent is a database file, the
source physical file, the source sequence numbers are to-file must be a physical database file with a
created and placed in front of the records. record length at least as large as that of the ori-
ginal file. If the file sent is a save file, the to-file
If the file is a physical file, the record length of the to-file
must be a save file. Overrides to this file are
must be at least as large as the record length of the original
ignored.
file. If the record length of the to-file is larger than that of the
original file, the records are padded to the end with the The name of the file can be qualified by one of the fol-
default record value for the to-file. lowing library values:
member-name: Specify the name of the member that Received into a source file, the sequence numbers
receives the records. A member name cannot be speci- and date fields are added.
fied if the file is a save file.
If the file is a source file and is:
MBROPT
Received into a nonsource file, the sequence
Specifies whether the new records replace or are added
numbers and date fields are removed (the first 12
to the existing records.
bytes of each record).
*REPLACE: The system clears the existing member
Received into a source file, the file is received
and adds the new records.
unchanged.
*ADD: The system adds the new records to the end of
*SRC: The file being received is a source file. The
the existing records.
sequence numbers and date fields are in the file. If the
NBR file is received into another source file, the sequence
Specifies the number of the file member that is received. numbers and date fields are not added to the file being
This number is used to identify the member that is received. If the file is received into a nonsource file, the
received when there is more than one member of the sequence numbers and date fields are removed from the
same name available for the file. file.
*LAST: The last network file member with the specified Note: *SRC must not be specified if the network file
member name is received. The last member is deter- does not contain sequence numbers and date
mined as the last member to arrive at the user's system; fields in the first 12 bytes of each record.
both FROMFILE and FROMMBR parameter values are
used to determine the last network file member.
Note: The file member that arrived last at the user's Examples
system may not have been the last one sent by
Example 1: Receiving a Member
the sending user. The network does not guar-
antee the arrival sequence of separately sent RCVNETF FROMFILE(FILEA) TOFILE(FILEB/FILEA)
files. FROMMBR(PAYROLL)
*ONLY: Only one file member of the specified file name This command receives member PAYROLL of file FILEA into
is received. If more than one member of that name is member PAYROLL of file FILEA in library FILEB. If there is
available, an escape message is sent, and the command an existing member of that name, the records in the member
is not run. are replaced. If multiple members of that name are avail-
member-number: Specify the number of the member able, the last one to arrive at the destination system is
that is received. received.
name. Because the FROMMBR parameter is not specified, RCVNETF FROMFILE(FILEA) TOFILE(FILEB/FILEA)
there must be only one member name available for this file. FROMMBR(PAYROLL) FROMTYPE(\SRC)
Because USR1 is specified, only someone with a user profile
of USR1, someone with a group profile of USR1, or someone This command specifies that the file being received is a
with security officer authority can use this command. source file and the sequence numbers and date fields are
not added to the file being received.
Example 3: Receiving a Source File
┌─\LIBL────────┐
(P) ─┬──────────────────────┬──┬────────────────────────┬──┬─────────────────────────┬───5%
55──RCVTIEF──LIB(──┼─\CURLIB──────┼──)────
└─library-name─┘ │ ┌─\ALL───┐ │ │ ┌─\NONE──┐ │ │ ┌─1ðððð──┐ │
└─TYPE(──┼─\OTHER─┼──)─┘ └─OUTPUT(──┴─\PRINT─┴──)─┘ └─MAXRCDS(──┼─\NOMAX─┼──)─┘
└─\SAVF──┘ └─number─┘
Note:
P All parameters preceding this point can be specified in positional form.
(1) ─'directory-path-name'──)────
55──RD──DIR(─── (P) ─┬──────────────────────┬──────────────────────────────────────────────────────────5%
│ ┌─\NO──┐ │
└─RMVLNK(──┴─\YES─┴──)─┘
Notes:
1 You can specify a pattern for this path name.
objects are unlinked and directory W is removed. If you do which you have authority are unlinked and the directory is
not have authority to unlink all of the objects, only those for not removed.
(P) ──────────────────────────────────────────────────────────5%
55──REN──OBJ(──'object-path-name'──)──NEWOBJ(──new-object-name──)────
Note:
P All parameters preceding this point can be specified in positional form.
55──RETURN─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────5%
55──RGZDLO──DLO(──┬─\ALL────────────────────┬──)──┬─────────────────────────────────────┬───(P) ────────────────────────────────────5
├─\SYSOBJNAM──────────────┤ │ ┌─\NONE───────┐ │
└─document-or-folder-name─┘ ├─FLR(──┼─\ANY────────┼──)────────────┤
│ └─folder-name─┘ │
(1) ─system-object-name──)─┘
└─SYSOBJNAM(───
5──┬──────────────────────────────┬──┬─────────────────────┬───────────────────────────────────────────────────────────────────5%
│ ┌─ð──────────────┐ │ │ ┌─\NO───┐ │
└─DAYS(──┴─number-of-days─┴──)─┘ └─MAIL(──┼─\YES──┼──)─┘
└─\ONLY─┘
Notes:
1 The SYSOBJNAM parameter is valid only when DLO(*SYSOBJNAM) is specified.
Example 1: Reorganizing Folders and Documents This command reorganizes the document named DOC1 in
RGZDLO DLO(\ALL) FLR(\ANY) folder FLRA.
This command reorganizes all filed folders and documents Example 8: Reorganizing Documents Not Referenced
that exist on the system. RGZDLO DLO(\ALL) FLR(\ANY) DAYS(3ð)
Example 2: Reorganizing Folders, Documents, and This command reorganizes all filed documents and folders
Unfiled Mail that have not been referenced in the past 30 days.
RGZDLO DLO(\ALL) FLR(\ANY) MAIL(\YES)
┌─\LIBL/────────┐
(P) ────────────────────────────────────5
55──RGZPFM──FILE(──┼───────────────┼──physical-file-name──)──┬──────────────────────────┬───
├─\CURLIB/──────┤ │ ┌─\FIRST──────┐ │
└─library-name/─┘ └─MBR(──┼─\LAST───────┼──)─┘
└─member-name─┘
5──┬────────────────────────────────────┬──┬─────────────────────────────────────────────────────┬──────────────────────────────5
│ ┌─\SAME──────────────┐ │ │ ┌─1.ðð───────────┐ ┌─1.ðð────────────┐ │
│ │ ┌──
─────────────┐ │ │ └─SRCSEQ(──┴─starting-value─┴──┼─────────────────┼──)─┘
6 (1)
└─SRCOPT(──┴───┬─\SEQNBR─┬─┴────┴──)─┘ └─increment-value─┘
└─\DATE───┘
5──┬────────────────────────────────────────────────────────────────────┬──┬────────────────────────────────────┬──────────────5%
│ ┌─\NONE─────────────────────────────────────────────┐ │ │ ┌─\ONLY──────────────┐ │
└─KEYFILE(──┼─\FILE─────────────────────────────────────────────┼──)─┘ └─RCDFMT(──┴─record-format-name─┴──)─┘
│ ┌─\LIBL/────────┐ │
└─┼───────────────┼──logical-file-name──member-name─┘
├─\CURLIB/──────┤
└─library-name/─┘
Notes:
P All parameters preceding this point can be specified in positional form.
1 A maximum of 2 repetitions
*DATE: The records have a null date (000000) placed *NONE: The member is not reorganized; it is only com-
in the date field. If *DATE is specified, *SEQNBR can pressed by having its deleted records removed.
also be specified. *FILE: For a physical file member having a keyed
sequence access path, the arrival sequence of the
records in the member is changed to match their keyed record-format-name: Specify the name of a record
sequence. format in the multiple-format logical file that is used to
reorganize the physical file member.
Element 1: Logical File Name
Note: Compression of a file occurs when the space
The name of the logical file can be qualified by one of
occupied by a deleted record is freed to hold a
the following library values:
record that is not deleted.
*LIBL: All libraries in the job's library list are
searched until the first match is found.
*CURLIB: The current library for the job is Examples
searched. If no library is specified as the current
Example 1: Reorganizing by Deleting Records
library for the job, the QGPL library is used.
RGZPFM FILE(PAYROLL) MBR(MBR1)
library-name: Specify the name of the library to be
searched. This command compresses member MBR1 of the PAYROLL
logical-file-name: Specify the qualified name of the file by removing the deleted records from the file member.
logical file whose member's sequence is used to reor-
Example 2: Reorganizing in Keyed Sequence
ganize the physical file member.
RGZPFM FILE(QCLSRC) MBR(CLMBR2)
Element 2: Member Name SRCOPT(\SEQNBR \DATE) KEYFILE(\FILE)
member-name: Specify the name of the member whose SRCSEQ(1.ðð .25)
sequence is used to reorganize the physical file
member. This command reorganizes the member CLMBR2 of the CL
source file QCLSRC in keyed sequence, with the sequence
RCDFMT number field used as the key. The reorganized member has
Specifies the record format name if the physical file new sequence numbers (starting at 1.00 and incrementing by
member is reorganized in the sequence of a multiple- .25) and a null date (000000) placed in all records when the
format logical file. original member is reorganized.
*ONLY: The logical file specified by the KEYFILE
parameter has only one record format, which is used to
reorganize the physical file member.
(P) ────────────────────────────────────────────────────────────────────────────────────────5%
55──RLSCMNDEV──DEV(──device-name──)────
Note:
P All parameters preceding this point can be specified in positional form.
(P) ───────────────────────────────────────────────────────5%
55──RLSDSTQ──DSTQ(──distribution-queue-name──)──PTY(──┬─\NORMAL─┬──)────
(1) ┘
└─\HIGH───
Notes:
1 This value is not valid for a SystemView distribution services (SVDS) type of distribution queue.
Purpose DSTQ
Specifies the name of the distribution queue being
The Release Distribution Queue (RLSDSTQ) command released from being held. Both normal and high priority
releases a distribution queue from a held status and allows it portions of the specified distribution queue are shown or
to be sent. printed. The queue specified must have been previously
configured. See the Configure Distribution Services
Distribution queue names are translated to the graphic char- (CFGDSTSRV) command or the Add Distribution Queue
acter set and code page 930 500, using the job's coded char- (ADDDSTQ) command.
acter set identifier (CCSID).
PTY
Restrictions: Specifies whether the normal priority or high priority
1. This command is shipped with public *EXCLUDE portion of the specified queue is released from being
authority and the QPGMR and QSYSOPR user profiles held.
have private authorities to use the command. *NORMAL: Releases the normal priority queue, which
2. Messages that report errors about distribution queues is for distributions with a service level of data low.
may display or print different characters than the user
*HIGH: Releases the high priority queue, which is for
entered for the distribution queue name because of
distributions with a service level of fast, status, or data
internal system transformations. Similarly (depending on
high.
the language used for the work station), the internal
value for a distribution queue name may differ from the
characters shown on the Work with Distribution Queue Examples
(WRKDSTQ) command. An error may be reported if the
character-string value specified for the DSTQ parameter Example 1: Releasing the Normal Priority Portion of the
does not match the rules for an internal distribution Queue
queue value or if it does not match the internal value for RLSDSTQ DSTQ(CHICAGO) PTY(\NORMAL)
any defined distribution queue (ignoring case differ-
ences). This command releases the normal priority portion of the
CHICAGO distribution queue.
Note: To see the parameter and value descriptions for this
command, refer to the online help text. For more Example 2: Releasing the High Priority Portion of the
information about printing the help text, refer to Queue
“Printing CL Command Descriptions” in Chapter 1.
RLSDSTQ DSTQ(ATLANTA) PTY(\HIGH)
Required Parameters This command releases the high priority portion of the
ATLANTA distribution queue.
(P)─┬─RMTLOCNAME(───
55──RLSIFSLCK─── (1) ─'remote-location-name'──)─┬──────────────────────────────────────────────────────────────────5%
(1) ─'path-name'──)───────────────────┘
└─OBJ(───
Notes:
P All parameters preceding this point can be specified in positional form.
(P) ─┬────────────────────────────┬──────────────────────────5%
55──RLSJOB──JOB(────┬─────────────────────────────┬──job-name────)────
└─┬─────────────┬──user-name/─┘ │ ┌─\SELECT─┐ │
└─job-number/─┘ └─DUPJOBOPT(──┴─\MSG────┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
A job identifier is a qualified name with up to three ele- Example 2: Releasing a Job for Processing
ments. For example:
RLSJOB JOB(DEPTXYZ/987654)
job-name
user-name/job-name This command releases job name 987654 that was sub-
job-number/user-name/job-name mitted by a user through the user profile DEPTXYZ and later
held. The qualified form of the job name is used when jobs
with duplicate names exist in the system.
┌─\LIBL/────────┐
(P) ───────────────────────────────────────────────────────────────────5%
55──RLSJOBQ──JOBQ(──┼───────────────┼──job-queue-name──)────
├─\CURLIB/──────┤
└─library-name/─┘
Note:
P All parameters preceding this point can be specified in positional form.
┌─\ONLY────────┐
(P) ─ENTRYNBR(──┼─\ALL─────────┼──)──────────────────────────────────────────────5%
55──RLSJOBSCDE──JOB(──┬─\ALL──────────────┬──)────
├─job-name──────────┤ └─entry-number─┘
└─generic\-job-name─┘
Note:
P All parameters preceding this point can be specified in positional form.
┌─\LIBL/────────┐
(P) ────────────────────────────────────────────────────────────────5%
55──RLSOUTQ──OUTQ(──┼───────────────┼──output-queue-name──)────
├─\CURLIB/──────┤
└─library-name/─┘
Note:
P All parameters preceding this point can be specified in positional form.
(P) ───────────────────────────────────────────────────────────────────────────────────────5%
55──RLSRDR──RDR(──RDR-reader-name──)────
Note:
P All parameters preceding this point can be specified in positional form.
55──RLSRMTPHS──PHASE(──phase-cname──)──PLAN(──plan-cname──)──APPID(──application-identifier-name──)─────────────────────────────5
(P) ─────────────────────────────────────────────────────────────5%
5──RMTLOCNAME(──remote-location-cname──)──DEV(──device-name──)────
Note:
P All parameters preceding this point can be specified in positional form.
55──RLSSPLF──FILE(──┬─\SELECT───────────┬──)────────────────────────────────────────────────────────────────────────────────────5
└─spooled-file-name─┘
┌─\─────────────────────────────────────────┐ ┌─\ONLY───────────────┐
(1) ─┴─┬─────────────────────────────┬──job-name─┴──)──SPLNBR(──┼─\LAST───────────────┼──)────
5──┬─JOB(─── (P) ┬────────────────────────5%
│ └─┬─────────────┬──user-name/─┘ └─spooled-file-number─┘ │
│ └─job-number/─┘ │
│ ┌─\CURRENT──┐ │
(2)
└─SELECT(────┼─\ALL──────┼──┬───────────────────────────────────────────────────┬──)───────────────┘
└─user-name─┘ │ ┌─\ALL────────┐ │
└─┼─\OUTQ───────┼──┬──────────────────────────────┬─┘
└─device-name─┘ │ ┌─\ALL──────┐ ┌─\ALL──────┐ │
└─┼─\STD──────┼──┼───────────┼─┘
└─form-type─┘ └─user-data─┘
Notes:
1 Only valid when FILE(*SELECT) is not specified.
Purpose JOB
Specifies the name of the job that created the file being
The Release Spooled File (RLSSPLF) command releases a released for additional processing.
specified spooled file formerly held on an output queue for
A job identifier is a special value or a qualified name
processing by a spooling writer. The RLSSPLF command
with up to three elements. For example:
can release a spooled file that was held by:
\
A HLDSPLF command job-name
HOLD(*YES) being specified in the device file or on an user-name/job-name
override command job-number/user-name/job-name
SAVE(*YES) being specified in the device file, on an More information on this parameter is in Appendix A,
override command, or in the CHGSPLFA command “Expanded Parameter Descriptions.”
A HLDWTR command and a RLSWTR command with *: The job that issued this RLSSPLF command is the
OPTION(*BYPASS) specified job that produced the spooled file being released. If no
job qualifier is given, all of the jobs currently in the
The operator canceling a system request to put forms on system are searched for the simple job name.
the printer
job-name: Specify the name of the job that created the
Note: To see the parameter and value descriptions for this spooled file.
command, refer to the online help text. For more
information about printing the help text, refer to user-name: Specify the name of the user of the job that
“Printing CL Command Descriptions” in Chapter 1. created the file being released.
job-number: Specify the number of the job that created
the file being released.
Required Parameters
SPLNBR
FILE
Specifies the number of the spooled file being released.
Specifies the name of the spooled file that is being
More information on this parameter is in Appendix A,
released to be written to an output device.
“Expanded Parameter Descriptions.”
*SELECT: All spooled files that meet the selection
*ONLY: One spooled file from the job has the specified
requirements specified in the SELECT keyword are
file name. The number of the spooled file is not neces-
released. This value is mutually exclusive with the JOB
sary. If *ONLY is specified and more than one spooled
and SPLNBR parameters. Specifying *SELECT causes
file has the specified file name, a message is sent.
the JOB and SPLNBR parameters to be ignored.
*LAST: The spooled file with the highest number and
spooled-file-name: Specify the name of the spooled file
the specified file name is used.
being released.
spooled-file-number: Specify the number of the spooled
file to release that has the specified file name.
Optional Parameters
Element 1: User Values form-type: Only files with the specified form type are
released.
*CURRENT: Only files created by the user running this
command are released. Element 4: User Data Values
*ALL: Files created by all users are released. *ALL: Files with any user data tag specified are
released.
user-name: Specify the user name of the files being
released. user-data: Only files with the specified user data tag are
released.
Element 2: Device Values
*ALL: Files queued for any device or on any object
queue are released.
Example
RLSSPLF FILE(STOCK14) JOB(ðððð47/SMITH/MASTER)
*OUTQ: All files that are not queued for a device are
released. These files are on output queues that are not This command releases the spooled file named STOCK14
associated with printers. created in the job named MASTER. The file can now be
device-name: Specify the name of the device whose selected for processing by the spooling writer. The job was
queued files are released. run under the user profile named SMITH and was assigned
the job number 000047 by the system.
(P) ─┬──────────────────────────┬──────────────────────────────────────────────────────────────5%
55──RLSWTR──WTR(──writer-name──)────
│ ┌─\CURRENT─┐ │
├─OPTION(──┼─\BEGIN───┼──)─┤
│ ├─\BYPASS──┤ │
│ ├─+number──┤ │
│ └─–number──┘ │
└─PAGE(──page-number──)────┘
Note:
P All parameters preceding this point can be specified in positional form.
*CURRENT: The writer is released at the point where it Example 2: Releasing Writer at Specified Point
was held by the HLDWTR (Hold Writer) command. This
RLSWTR WTR(PRTR) OPTION(-3)
option may be specified when the writer is not producing
a file. This command releases writer PRTR to begin printing again
*BEGIN: The writer is released at the beginning of the at a point three pages before the point where the writer was
current file. This option may be specified only if the held. That is, the last three pages previously printed are the
writer was held while producing the current file. first three pages printed this time.
*BYPASS: The writer is released at the beginning of Example 3: Starting Printing on Page Ten
the next file. The current file is implicitly held on the
RLSWTR WTR(PRTR) PAGE(1ð)
queue. This option may be specified only if the writer
was held while producing the current file. This command releases writer PRTR to start printing again at
+number: Specify the number of pages past the point page ten.
where the writer was held that it is released. An error
(1) ─'directory-path-name'──)────
55──RMDIR──DIR(─── (P) ─┬──────────────────────┬───────────────────────────────────────────────────────5%
│ ┌─\NO──┐ │
└─RMVLNK(──┴─\YES─┴──)─┘
Notes:
1 You can specify a pattern for this path name.
objects are unlinked and directory W is removed. If you do which you have authority are unlinked and the directory is
not have authority to unlink all of the objects, only those for not removed.
┌──
─────────────┐
55──RMVACC──ACC(───6─access-code─┴───
(1) ──)────
(P) ────────────────────────────────────────────────────────────────────────────────────5%
Notes:
1 A maximum of 50 repetitions
Note: To see the parameter and value descriptions for this This command removes access code 300 from the system.
command, refer to the online help text. For more
┌─\LIBL/────────┐
(P) ─────────────────────────────────────5%
55──RMVAJE──SBSD(──┼───────────────┼──subsystem-description-name──)──JOB(──job-name──)────
├─\CURLIB/──────┤
└─library-name/─┘
Note:
P All parameters preceding this point can be specified in positional form.
Required Parameters
Example
SBSD
RMVAJE SBSD(MYLIB/PAYROLL) JOB(INITIAL)
Specifies the qualified name of the subsystem
description from which the autostart job entry is being This command removes job entry named INITIAL that starts
removed. automatically from the PAYROLL subsystem description in
The name of the subsystem description can be qualified the library MYLIB.
by one of the following library values:
┌─\LIBL/────────┐
(P) ────────────────────────────────────────5%
55──RMVALRD──MSGID(──message-ID──)──ALRTBL(──┼───────────────┼──alert-table-name──)────
├─\CURLIB/──────┤
└─library-name/─┘
Note:
P All parameters preceding this point can be specified in positional form.
┌──
─────────┐
55──RMVAUTLE──AUTL(──┬─authorization-list-name──────────┬──)──USER(───6─user-ID─┴───
(1) ──)────
(P) ─────────────────────────────────────5%
└─generic\-authorization-list-name─┘
Notes:
1 A maximum of 50 repetitions
2 A maximum of 10 repetitions
(P) ─────────────────────────────────────5%
55──RMVCCTRTE──CCTNAME(──IPX-circuit-name──)──RMTNETNBR(──remote-IPX-network-number──)────
Note:
P All parameters preceding this point can be specified in positional form.
CCTNAME
Specifies the unique name of the circuit from which this Example
static route is being removed. The circuit is usually an RMVCCTRTE CCTNAME(CIRCUIT2)
X.25 SVC on demand type circuit. The static route is RMTNETNBR(ð23D62A7)
only associated with this circuit. The circuit must have
been previously configured using the Add IPX Circuit This command removes a static route from the IPX config-
(ADDIPXCCT) CL command or by selecting option 1 uration associated with a circuit named CIRCUIT2 and a
from the Work with IPX Circuits display. remote IPX network number of '023D62A7'X.
(P) ──────────────────────5%
55──RMVCCTSRV──CCTNAME(──IPX-circuit-name──)──SRVNAME(──service-name──)──SRVTYPE(──┬─\ADVPRTSVR──┬──)────
├─\ARCHIVEQ───┤
├─\ARCHIVESVR─┤
├─\FILESVR────┤
├─\JOBQ───────┤
├─\JOBSVR─────┤
├─\NTWENHINTG─┤
├─\PRTQ───────┤
├─\PRTSVR─────┤
├─\RMTBRGSVR──┤
└─\SVRMAP─────┘
Note:
P All parameters preceding this point can be specified in positional form.
*SVRMAP: The AS/400 port mapping server is avail- This command removes a static service that had been
able for mapping service names to port numbers. The defined to a circuit named CIRCUIT2 in the IPX configuration
hex value of '0899'X is used. with a service name of FILEPRINTER and a service type of
file server.
┌─\LIBL/────────┐
55──RMVBNDDIRE──BNDDIR(──┼───────────────┼──binding-directory-name──)───────────────────────────────────────────────────────────5
├─\CURLIB/──────┤
├─\USRLIBL/─────┤
└─library-name/─┘
┌──
────────────────────────────────────────────────────────────────┐
│ ┌─\LIBL/────────┐ ┌─\SRVPGM─┐ │
6 (1) ──)──────────────────────────────────────────────5%
5──OBJ(────(──┼───────────────┼──┬─\ALL─────────────────┬──┼─────────┼──)─┴───
└─library-name/─┘ ├─object-name──────────┤ └─\MODULE─┘
└─generic\-object-name─┘
Note:
1 A maximum of 50 repetitions
(P) ─CFGL(───
55──RMVCFGLE──TYPE(──┬─\APPNDIR───┬──)──── (1) ─Async-network-address-list-name──)──────────────────────────────────────────5
├─\APPNLCL───┤
├─\APPNRMT───┤
├─\APPNSSN───┤
├─\ASYNCADR──┤
├─\ASYNCLOC──┤
├─\RTLPASTHR─┤
└─\SNAPASTHR─┘
5──┬──────────────────────────────────────────┬──┬────────────────────────────────────┬─────────────────────────────────────────5
│ ┌──
─────────────────────┐ │ └─APPNRMTE(──┤ APPNRMTE Details ├──)─┘
└─APPNLCLE(───6─local-location-name─┴───
(2) ──)─┘
5──┬───────────────────────────────────────┬──┬────────────────────────────────────────────┬────────────────────────────────────5
│ ┌──
─────────────────┐ │ │ ┌──
──────────────────────┐ │
└─ASYNCADRE(───6─network-address─┴─── 6─remote-location-name─┴───
(2) ──)─┘ └─ASYNCLOCE(─── (2) ──)─┘
5──┬───────────────────────────────────────────┬──┬────────────────────────────────────────────────┬────────────────────────────5
│ ┌──
────────────────────┐ │ │ ┌─\ANY──────────────────────┐ │
└─RTLPASTHRE(───6─retail-device-name─┴───
(2) ──)─┘ └─FTRCPNAME(───
(4) ─┼─generic\-filtered-CP-name─┼──)─┘
└─filtered-CP-name──────────┘
5──┬──────────────────────────────────────────────┬──┬────────────────────────────────────────────────────┬─────────────────────5
│ ┌─\NETATR────────────────┐ │ │ ┌─\ANY─────────────────────────┐ │
(4) ─┴─filtered-CP-network-ID─┴──)─┘ └─LCLLOCNAME(───
└─FTRCPNETID(─── (5) ─┼─generic\-local-location-name─┼──)─┘
└─local-location-name──────────┘
┌──
──────────────────────────────────────┐
5───6┬────────────────────────────────────┬┴────────────────────────────────────────────────────────────────────────────────────5%
(3) ─)─┘
└─SNAPASTHRE(──(──group-name──)───
APPNRMTE Details:
┌──
────────────────────────────────────────────────────────────────────────────────────────────┐
│ ┌─\NETATR───────────────────┐ │
6
├────(──┬─\ANY─────────────────┬──┼───────────────────────────┼──┬─────────────────────────┬──)─┴───────────────────────────────┤
└─remote-location-name─┘ └─remote-network-identifier─┘ │ ┌─\NETATR─────────────┐ │
└─┼─────────────────────┼─┘
└─local-location-name─┘
Notes:
1 Required only for TYPE(*ASYNCADR).
2 A maximum of 50 repetitions
Purpose TYPE
Specifies one of the possible configuration list types.
The Remove Configuration List Entries (RMVCFGLE)
*APPNDIR: An advanced peer-to-peer networking
command removes entries from a configuration list.
(APPN) directory search filter configuration list is used.
Note: The user may also use the full screen entry display of The user can specify one APPN directory search filter
the Change Configuration List (CHGCFGL) command entry in the configuration list.
to add, remove, or change entries in an existing list *APPNLCL: An APPN local location list is used. The
except for the configuration list TYPE(*SNAPASTHR). user can specify up to 476 APPN local location entries in
Note: To see the parameter and value descriptions for this the configuration list.
command, refer to the online help text. For more *APPNRMT: An APPN remote location list is used. The
information about printing the help text, refer to user can specify up to 1898 APPN remote location
“Printing CL Command Descriptions” in Chapter 1. entries in the configuration list.
*APPNSSN: An APPN session end point filter config-
Required Parameters uration list is used. The user can specify one APPN
session entry in the configuration list.
*ASYNCADR: An asynchronous network address list is location name being used. When a bind is received
used. The user can specify up to 294 asynchronous from another system, this is the Secondary Logical Unit
network address entries in the configuration list. (SLU) name being used.
*ASYNCLOC: An asynchronous remote location list is Note: This parameter is valid only if TYPE(*APPNSSN)
used. The user can specify up to 4995 asynchronous is specified.
remote location entries in the configuration list.
*ANY: Any local location name will be filtered by the
*RTLPASTHR: A retail pass-through list is used. The local system.
user can key up to 450 retail pass-through entries in the
generic*-local-location-name: Specify the generic local
configuration list.
location name (part of a name followed by an asterisk)
*SNAPASTHR: An SNA pass-through list is used. The of the local location(s) being filtered. The generic local
user can key one SNA pass-through entry in the config- location name allows one entry to be defined for all local
uration list. location names, on the system, with a name that
matches the characters preceding an *.
CFGL
Specifies the name of the configuration list. This param- local-location-name: Specify the local location name that
eter is valid only when *ASYNCADR is specified on the is being filtered by the local system.
TYPE parameter. Only one of the other configuration list
APPNLCLE
types is allowed on a system. The list types have
Specifies the APPN local location entry. If
system-supplied names: QAPPNDIR, QAPPNLCL,
TYPE(*APPNLCL) is specified, this value is required.
QAPPNRMT, QAPPNSSN, QASYNCADR,
Up to 50 entries can be specified for this parameter.
QASYNCLOC, QRTLPASTHR, QSNAPASTHR.
APPNRMTE
Specifies the APPN remote location entry. If
Optional Parameters TYPE(*APPNRMT) is specified, this value is required.
FTRCPNAME Up to 50 entries can be specified for this parameter.
Specifies the control point name of the adjacent control Element 1: Remote Location Name
point that is being filtered by the local system when a
directory search request is made. *ANY: The system potentially accepts all requests sent
to it.
Note: This parameter is valid only if TYPE(*APPNDIR)
is specified. remote-location-name: Specify the remote location of
the entry being removed from the configuration list.
*ANY: Any control point name is filtered.
Element 2: Remote Network Identifier
generic*-filtered-CP-name: Specify the generic control
point name (part of a name followed by an asterisk) of *NETATR: The RMTNETID value specified in the
the adjacent control point(s) being filtered. The generic system network attributes is used.
control point name allows one directory entry to be remote-network-identifier: Specify the remote network
defined for all control points, in a single network, with a identifier of the entry being removed from the configura-
name that matches the characters preceding an *. tion list.
filtered-CP-name: Specify the control point name of the Element 3: Local Location Name
adjacent control point being filtered.
*NETATR: The LCLLOCNAME value specified in the
FTRCPNETID system network attributes is used.
Specifies the control point network identifier of the adja- local-location-name: Specify the local location of the
cent control point being filtered by the local system when entry being removed from the configuration list.
a directory search request is made.
ASYNCADRE
Note: This parameter is valid only if TYPE(*APPNDIR)
Specifies the asynchronous network address entry. This
is specified.
value is required if TYPE(*ASYNCADR) is specified. Up
*NETATR: The LCLNETID value specified in the to 50 entries can be specified for this parameter.
system network attributes is used.
Note: All entries having the same network address as
filtered CP-network-ID: Specify the control point network that specified are removed from the configuration
identifier of the adjacent control point being filtered by list.
the local system.
ASYNCLOCE
LCLLOCNAME Specifies the asynchronous remote location entry. This
Specifies the local location name being supplied by the value is required if TYPE(*ASYNCLOC) is specified. Up
caller that is being filtered by the local system. When to 50 entries can be specified for this parameter.
the local system is initiating a session, this is the local
RTLPASTHRE SNAPASTHRE
Specifies the retail pass-through entry. This value is Specifies the SNA pass-through entry. This value is
required if TYPE(*RTLPASTHR) is specified. Up to 50 required if TYPE(*SNAPASTHR) is specified. One
entries can be specified for this parameter. group entry can be specified for this parameter.
Note: All entries that have the same retail device name
as the one the user specified are removed from Example
the configuration list.
RMVCFGLE TYPE(\ASYNCLOC) ASYNCLOCE(RMTLOC1)
┌─\LIBL/────────┐
(P) ───────────────5
55──RMVCMNE──SBSD(──┼───────────────┼──subsystem-description-name──)──┬─DEV(──┬─\ALL─────────────────┬──)────┬───
├─\CURLIB/──────┤ │ ├─\APPC────────────────┤ │
└─library-name/─┘ │ ├─\ASYNC───────────────┤ │
│ ├─\BSCEL───────────────┤ │
│ ├─\FINANCE─────────────┤ │
│ ├─\INTRA───────────────┤ │
│ ├─\RETAIL──────────────┤ │
│ ├─\SNUF────────────────┤ │
│ ├─device-name──────────┤ │
│ └─generic\-device-name─┘ │
└─RMTLOCNAME(──remote-location-name──)─┘
5──┬───────────────────────────┬───────────────────────────────────────────────────────────────────────────────────────────────5%
│ ┌─\ANY──────┐ │
(1) ─┴─mode-name─┴──)─┘
└─MODE(───
Notes:
P All parameters preceding this point can be specified in positional form.
DEV(*SNUF) is specified.
DEV
Restrictions:
Specifies the name of the device description or the type
1. The user of this command must have object operational of the device for which a communications device entry is
and object management authorities for the specified sub- being removed from the subsystem description.
system description.
Note: The DEV parameter and the RMTLOCNAME
2. All jobs that are active through the communications entry parameter are mutually exclusive.
being removed must be ended before this command can
*ALL: The *ALL communication entry is removed.
be run.
*APPC: The advanced program-to-program communica-
3. A communications entry cannot be removed from an
tions device entry is removed.
active subsystem while there are active jobs associated
with it. *ASYNC: The asynchronous communications device
entry is removed with this communications entry. This
Note: To see the parameter and value descriptions for this
value is valid only when MODE(*ANY) is specified.
command, refer to the online help text. For more
information about printing the help text, refer to *BSCEL: The binary synchronous equivalency link com-
“Printing CL Command Descriptions” in Chapter 1. munications device entry is removed. This value is valid
only when MODE(*ANY) is specified.
device-name: Specify the device description name or checking is not done on the remote location
the type of device to use with this communications name.
device entry. The name specified on the CRTDEVxxx
command associated with this device description name
is used. Optional Parameters
generic*-device-name: Specify the generic device MODE
description used with this remove communications Specifies the name of the mode of the device specified
device entry. A generic name is a character string of by the DEV parameter or the remote location specified
one or more characters followed by an asterisk (*); for by the RMTLOCNAME parameter from which the com-
example, ABC*. The asterisk substitutes for any valid munications device entry is removed.
characters. A generic name specifies all objects with
names that begin with the generic prefix for which the *ANY: The communications device entry which has a
user has authority. If an asterisk is not included with the value of *ANY for the device is removed.
generic (prefix) name, the system assumes it to be the mode-name: Specify the name of the mode entry of the
complete object name. If the complete object name is communications device or remote location from which
specified, and multiple libraries are searched, multiple the communications device entry is removed.
objects can be removed only if *ALL or *ALLUSR library
values can be specified for the name. For more infor-
mation on the use of generic names, refer to “Generic Example
Object Names” in Chapter 2. RMVCMNE SBSD(LIB2/SBS1) DEV(COMDEV)
RMTLOCNAME This command removes the communications device entry for
Specifies the name of the remote location that is used the device COMDEV from the subsystem description SBS1
with this object. in library LIB2.
Note: The remote location name specified on the
CRTDEV command can be used. Validity
(P) ─────────────────────────────────────────────────────5%
55──RMVCNNLE──CNNL(────connection-list-name────)──ENTRY(────entry────)────
Note:
P All parameters preceding this point can be specified in positional form.
Purpose CNNL
Specifies the name of the connection list.
The Remove Connection List Entry (RMVCNNLE) command
removes an entry from the specified connection list. ENTRY
Specifies which entry in the connection list is removed.
Note: To see the parameter and value descriptions for this
command, refer to the online help text. For more
information about printing the help text, refer to Example
“Printing CL Command Descriptions” in Chapter 1. RMVCNNLE CNNL(CHICAGO) ENTRY(CORPORATE)
(P) ─┬────────────────────────┬─────────────────────────────────────────────────────────5%
55──RMVCOMSNMP──COM(──community-name──)────
│ ┌─\YES─┐ │
└─ASCIICOM(──┴─\NO──┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
Note: To see the parameter and value descriptions for this *YES: The community name is translated to ASCII char-
command, refer to the online help text. For more acters before it is compared with a community name
information about printing the help text, refer to specified by an SNMP manager.
“Printing CL Command Descriptions” in Chapter 1. *NO: The community name is not translated to ASCII
characters before it is compared with a community name
Required Parameter specified by an SNMP manager.
COM
Specifies the name of the SNMP community being
Example
removed. The community must already exist in the RMVCOMSNMP COM(ROCHESTER)
SNMP agent community list.
This command removes community ROCHESTER from the
community-name: Specify the name of the SNMP com- SNMP agent community list.
munity being removed. The name may contain charac-
ters that cannot be displayed.
(1) ─'directory-path-name'──)────
55──RMVDIR──DIR(─── (P) ─┬──────────────────────┬──────────────────────────────────────────────────────5%
│ ┌─\NO──┐ │
└─RMVLNK(──┴─\YES─┴──)─┘
Notes:
1 You can specify a pattern for this path name.
(P) ─┬────────────────────────────────┬────────────────────────────────────────────5
55──RMVDIRE──USRID(──user-ID──user-address──)────
│ ┌─\FIRST───────────┐ │
└─USRD(──┼─\ALL─────────────┼──)─┘
└─user-description─┘
5──┬────────────────────────────────────────────────────┬──────────────────────────────────────────────────────────────────────5%
│ ┌─\SYSVAL──────────────────────────┐ │
└─CMDCHRID(──┼─\DEVD────────────────────────────┼──)─┘
└─graphic-character-set──code-page─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose from the directory. If the user responds no, the user
ID and address is not removed from the directory.
The Remove Directory Entry (RMVDIRE) command removes
If the request is not entered interactively (for
a specific entry from the system distribution directory. When
example, the request is from a batch CL program),
a user ID and address is removed from the directory, it is
the user ID and address is not removed from the
also removed from all distribution lists and the list of nick-
directory.
names for that user. However, the user ID and address for
that user is not removed in the list of nicknames for other Note: To see the parameter and value descriptions for this
users. command, refer to the online help text. For more
information about printing the help text, refer to
If an *ANY user is removed and an *ANY *ANY directory “Printing CL Command Descriptions” in Chapter 1.
entry exists, the user is not removed from the distribution
lists but the description is changed to the *ANY *ANY
description. Required Parameter
USRID
If a user ID and address has multiple descriptions associated
Specifies the user ID and address for the user entry to
with it, options exist to remove only a specific description or
be removed.
all descriptions.
Element 1: User ID
The RMVDIRE command does not provide interactive display
user-ID: Specify the user ID that is removed. Up to 8
support. This is provided by the Work with Directory Entries
characters can be specified.
(WRKDIRE) command.
Element 2: User Address
If the specified user ID, address, and description do not exist
user-address: Specify the user address to be removed.
in the directory, an error message is returned.
Up to 8 characters can be specified.
Restrictions:
1. The person running this command must have security Optional Parameters
administrator (*SECADM) authority.
USRD
2. The user ID and address being removed must not: Specifies the description associated with the user ID and
Be enrolled in OfficeVision address. Since more than one entry can exist in the
directory for a specific user ID and address, the
Have ownership of documents or folders in the Doc- description fully defines the user entry being removed.
ument Interchange Architecture (DIA) library
*FIRST: The first entry in the directory for the specified
If either of the above conditions are not met, the user ID user ID and address is removed. If only one entry
and address is not removed from the directory. exists, it is removed.
3. If the user ID and address being removed has not *ALL: All entries with the specified user ID and address
received mail from the mail queue, the following can are removed.
happen:
user-description: Specify up to 50 characters for the
If the request is entered interactively, a status description for the user. This description must be the
message is sent asking whether the queue should same as the one in the directory for this user ID and
be cleared. If the user responds yes, the mail is address.
cleared from the queue and the user is removed
(P) ─┬──────────────────────┬────────────────────────────────────────────────────5%
55──RMVDIRSHD──SYSNAME(──shadow-system-name──)────
│ ┌─\NO──┐ │
└─RMVDTA(──┴─\YES─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose are not part of an invariant character set and are not
available on all keyboards.
The Remove Directory Shadow System (RMVDIRSHD)
command removes a system that is currently shadowing
directory data to the local system. Optional Parameter
RMVDTA
Restriction: To use this command, you must have security
This parameter specifies whether to remove directory
administrator (*SECADM) authority.
data received from the system that is being removed.
Note: To see the parameter and value descriptions for this
*NO: Directory data that has been previously shadowed
command, refer to the online help text. For more
is left on the local system. Modifications are not made
information about printing the help text, refer to
to this data through shadowing unless you shadow data
“Printing CL Command Descriptions” in Chapter 1.
from another system that has shadowed data from the
system being removed.
Required Parameter *YES: Directory entry data that was shadowed from the
SYSNAME specified system is removed from the local system.
Specifies the name of the system for which shadowing is Department and location data is not removed.
to be removed. The name can contain a maximum of
eight alphanumeric characters. You can specify upper- Example
case letters A through Z, numbers 0 through 9, and
RMVDIRSHD SYSNAME(NYCITY) RMVDTA(\YES)
special characters @, #, $, and embedded blanks.
Embedded blanks must be enclosed in single quotation This command removes the system NYCITY from shadowing
marks ('). Leading blanks are not allowed. The @, #, and removes all the data shadowed from NYCITY.
and $ characters are not recommended because they
(2) ─┬─\SYSOBJNAM───────────────────┬──)──┬────────────────────────────┬──────────────────────────────────────5
55──RMVDLOAUT──DLO(───
├─\ALL─────────────────────────┤ │ ┌─\NONE───────┐ │
└─document-library-object-name─┘ (3) ─┴─folder-name─┴──)─┘
└─FLR(───
(P) ──┬───────────────────────────────────────┬─────────────────────────────────────5
5──┬────────────────────────────────────────┬───
│ ┌─\SAME────────────────────┐ │ │ ┌─\SAME───────────────────┐ │
└─USER(──┼─\ALL─────────────────────┼──)─┘ └─AUTL(──┴─authorization-list-name─┴──)─┘
│ ┌──
───────────────────┐ │
└──6─user-profile-name─┴───
(1) ─┘
5──┬─────────────────────────────────┬──┬───────────────────────────────────┬──────────────────────────────────────────────────5%
│ ┌─\SAME──────────────┐ │ └─SYSOBJNAM(──system-object-name──)─┘
└─ACC(──┼─\ALL───────────────┼──)─┘
│ ┌──
─────────────┐ │
└──6─access-code─┴───
(1) ─┘
Notes:
1 A maximum of 50 repetitions
ACC SYSOBJNAM
Specifies the access codes to be removed for the object. Specifies the system object name. This parameter is
valid only when DLO(*SYSOBJNAM) or
*SAME: The value does not change.
DOCL(*SYSOBJNAM) is specified. A full ten characters
*ALL: All access codes for the object are removed. must be specified.
access-code: Specify which currently assigned access
codes (ranging from 0 through 2047) are removed. Up Example
to 50 access codes can be specified. Access code zero
(0) stands for public access of *USE. RMVDLOAUT DLO(DOCA) FLR(MYFLR) AUTL(MYLIST)
55──RMVDSTLE──LSTID(──list-identification──list-qualifier──)────────────────────────────────────────────────────────────────────5
┌──
───────────────────────────────────────────────────────┐
5──USRID(───6─(──user-ID──┬────────────────────────────────────┬──)─┴───
(1) ──)────
(P) ──────────────────────────────────────────────────5
│ ┌─\FIRST───────────┐ │
└─user-address──┼──────────────────┼─┘
├─\ALL─────────────┤
└─user-description─┘
5──┬────────────────────────────────────────────────────┬──────────────────────────────────────────────────────────────────────5%
│ ┌─\SYSVAL──────────────────────────┐ │
└─CMDCHRID(──┼─\DEVD────────────────────────────┼──)─┘
└─graphic-character-set──code-page─┘
Notes:
1 A maximum of 300 repetitions
Restriction: The user must have security administrator A list ID and address can be used in place of the user
authority (*SECADM) to remove entries from a distribution list ID and address to identify a remote distribution list that
owned by another user. Users can remove entries from dis- is removed from the distribution list.
tribution lists that they created. Up to 300 sets of user IDs, addresses, and descriptions
Note: To see the parameter and value descriptions for this can be specified. Each valid set is removed from the
command, refer to the online help text. For more distribution list.
information about printing the help text, refer to Element 1: User ID
“Printing CL Command Descriptions” in Chapter 1.
user-ID: Specify the user ID (or the valid list ID for a
remote list entry) of the user for whom the entry is
Required Parameters removed.
list-ID: Specify the list identifier (ID) of the distribution Element 3: User Description
list. *FIRST: The first description in the specified user ID
Element 2: List Qualifier and address (or list ID and address) is removed. If only
one entry exists, it is the one removed from the list.
list-ID-qualifier: Specify the list ID qualifier of the distri-
bution list. *ALL: All the entries with the specified user ID and
address are removed from the distribution list.
Note: The distribution list identifier has two parts, the
ID and the qualifier, separated by at least one user-description: Specify the description for the user. If
space. If lowercase characters are specified, the a list ID is specified, specify the list description. The
system changes them to uppercase. description can be up to 50 characters in length.
55──RMVDSTQ──DSTQ(──distribution-queue──)──────────────────────────────────────────────────────────────────────────────────────5%
55──RMVDSTRTE──SYSNAME(──┬─\ANY────────┬──┬─\ANY──────────────┬──)─────────────────────────────────────────────────────────────5%
└─system-name─┘ └─system-group-name─┘
Purpose the routing table entry used to resolve the route to a dis-
tribution destination that does not match a specific
The Remove Distribution Route (RMVDSTRTE) command system name, but matches a group name. Only one
removes a remote system from the distribution services *ANY is allowed for each group in the routing table.
routing table. Once a system is removed from the table, dis-
system-name: Specify a maximum of 8 characters for
tributions can no longer be sent to that system from the local
the name of the remote system.
system.
Element 2: System Group Name
Interactive display support is provided by the Configure Dis-
*ANY: *ANY is used for the system group name. *ANY
tribution Services (CFGDSTSRV) command. More informa-
can be specified for the group name only if *ANY is also
tion on configuring a distribution network is in the SNA
specified for the system name. When SYSNAME(*ANY
Distribution Services book.
*ANY) is specified, the user removes the routing table
System names and system group names are translated to entry that is used to resolve a distribution destination
the graphic character set and code page 930 500, using the that does not match any other routing table entries.
job's coded character set identifier (CCSID). Only one SYSNAME(*ANY *ANY) entry is allowed in the
routing table.
Restriction: This command is shipped with public system-group-name: Specify a maximum of 8 charac-
*EXCLUDE authority, and the QPGMR and QSYSOPR user ters for the system group name. The system name and
profiles have private authorities to use the command. group name must be separated by at least one blank.
Note: To see the parameter and value descriptions for this
command, refer to the online help text. For more
Examples
information about printing the help text, refer to
“Printing CL Command Descriptions” in Chapter 1. Example 1: Removing a System from the Routing Table
RMVDSTRTE SYSNAME(SYSTEMA GROUPA)
Required Parameter
This command removes the routing table entry for the
SYSNAME system named SYSTEMA.
Specifies the system name and group name of the
remote system being removed from the routing table. Example 2: Removing a Generic Routing Table Entry
Element 1: System Name RMVDSTRTE SYSNAME(\ANY GROUPNM1)
*ANY: *ANY is used for the system name. When This command removes a routing table entry that has a
SYSNAME(*ANY group) is specified, the user removes system name of *ANY and a group name of GROUPNM1.
55──RMVDSTSYSN──SYSNAME(──system-name──system-group──)─────────────────────────────────────────────────────────────────────────5%
(P) ──────────────────────────────────────────────────────────────────────5%
55──RMVEMLCFGE──EMLCFGE(──configuration-entry-name──)────
Note:
P All parameters preceding this point can be specified in positional form.
55──RMVEWCBCDE──BCDGRP(────bar-code-group-name────)──INZMBR(────source-member-name────)─────────────────────────────────────────5
(P) ─────────────────────────────────────────────────────────────────5%
5──┬──────────────────────────────────────────────────────┬───
│ ┌─\LIBL/────────┐ ┌─QEWCSRC──────────┐ │
└─INZFILE(──┼───────────────┼──┴─source-file-name─┴──)─┘
├─\CURLIB/──────┤
└─library-name/─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose INZFILE
Specifies the name of the source physical file that con-
The Remove Extended Wireless Controller Bar Code Entry tains the source file member.
(RMVEWCBCDE) command removes the bar code entry for
The name of the source file can be qualified by one of
the specified bar code group.
the following library values:
Restriction: You must have *IOSYSCFG special authority *LIBL: All libraries in the job's library list are
to use this command. searched until the first match is found.
Note: To see the parameter and value descriptions for this *CURLIB: The current library for the job is
command, refer to the online help text. For more searched. If no library is specified as the current
information about printing the help text, refer to library for the job, the QGPL library is used.
“Printing CL Command Descriptions” in Chapter 1.
library-name: Specify the name of the library to be
searched.
Required Parameters
QEWCSRC: The source file name QEWCSRC is used.
BCDGRP
source-file-name: Specify the name of the source phys-
Specifies the name of the bar code group entry that is
ical file that contains the source member.
being removed.
INZMBR
Example
Specifies the name of the source file member containing
the bar code entry that is being removed. The bar code RMVEWCBCDE BCDGRP(BCDð1) INZMBR(EWCð1)
entry contains the extended wireless controller configura- INZFILE(QGPL/QEWCSRC)
tion data.
This command removes the bar code entry for bar code
group BCD01 in source file member EWC01 in source file
Optional Parameter QEWCSRC in library QGPL.
55──RMVEWCPTCE──PTCGRP(────ptc-group────)──INZMBR(────source-member-name────)───────────────────────────────────────────────────5
(P) ─────────────────────────────────────────────────────────────────5%
5──┬──────────────────────────────────────────────────────┬───
│ ┌─\LIBL/────────┐ ┌─QEWCSRC──────────┐ │
└─INZFILE(──┼───────────────┼──┴─source-file-name─┴──)─┘
├─\CURLIB/──────┤
└─library-name/─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose INZFILE
Specifies the name of the source physical file that con-
The Remove Extended Wireless Controller PTC Entry tains the source file member.
(RMVEWCPTCE) command removes the Portable Trans-
The name of the source file can be qualified by one of
action Computer (PTC) entry for the specified PTC group.
the following library values:
Restriction: You must have *IOSYSCFG special authority *LIBL: All libraries in the job's library list are
to use this command. searched until the first match is found.
Note: To see the parameter and value descriptions for this *CURLIB: The current library for the job is
command, refer to the online help text. For more searched. If no library is specified as the current
information about printing the help text, refer to library for the job, the QGPL library is used.
“Printing CL Command Descriptions” in Chapter 1.
library-name: Specify the name of the library to be
searched.
Required Parameters
QEWCSRC: The source file name QEWCSRC is used.
PTCGRP
source-file-name: Specify the name of the source phys-
Specifies the PTC group name of the entry being
ical file that contains the source member.
removed.
INZMBR
Example
Specifies the name of the source file member containing
the PTC entry that is being removed. The source file RMVEWCPTCE PTCGRP(PTCð1) INZMBR(EWCð1)
member contains extended wireless controller configura- INZFILE(QGPL/QEWCSRC)
tion data.
This command removes the PTC entry for PTC group PTC01
in source file member EWC01 in source file QEWCSRC in
Optional Parameter library QGPL.
(P) ───────────5%
55──RMVEXITPGM──EXITPNT(──exit-point-name──)──FORMAT(──exit-point-format-name──)──PGMNBR(──┬─program-number─┬──)────
└─\ALL───────────┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose PGMNBR
Specifies the program number of the exit program being
The Remove Exit Program (RMVEXITPGM) command removed.
removes an exit program entry for a specific exit point that is
*ALL: All exit programs for the specified exit point
registered or unregistered. An unregistered exit point is an
format (FORMAT parameter) from the specified exit
exit point that the registration facility created in the absence
point (EXITPNT parameter) are removed.
of an exit point at the time an exit program was added.
program-number: Specify the program number of the
Note: To see the parameter and value descriptions for this
exit program being removed.
command, refer to the online help text. For more
information about printing the help text, refer to
“Printing CL Command Descriptions” in Chapter 1.
Example
RMVEXITPGM EXITPNT(USER_EXIT_ONE) FORMAT(EXIT1)
Required Parameters PGMNBR(1)
EXITPNT
This command removes the exit program for exit point
Specifies the name of an existing exit point for which the
USER_EXIT_ONE that was added with program sequence
exit program is being removed.
number 1 for exit point format EXIT1.
FORMAT
Specifies the name of the exit point format of the exit
program that is being removed.
(P) ─┬──────────────────────────────┬──┬──────────────────────────────┬───────────────────5
55──RMVFNTTBLE──FNTTBL(──┬─\PHFCS─┬──)────
├─\PHCP──┤ └─PHFCS(──┤ PHFCS Details ├──)─┘ └─HPFCS(──┤ HPFCS Details ├──)─┘
├─\HPFCS─┤
└─\HPCP──┘
5──┬────────────────────────────────────────────────────┬──┬──────────────────────────────┬────────────────────────────────────5%
└─PHCP(────graphic-character-set──────code-page────)─┘ └─HPCP(────host-code-page────)─┘
PHFCS details:
┌─\NONE───────┐ ┌─\SYSVAL───────────────┐
├────font-identifier────┬─width───┬──┼─\BOLD───────┼──┴─graphic-character-set─┴──┬─point-size─┬─────────────────────────────────┤
├─\PTSIZE─┤ ├─\ITALIC─────┤ ├─\WIDTH─────┤
└─\NONE───┘ ├─\BOLDITC────┤ └─\NONE──────┘
├─\DBLWIDE────┤
└─\ITCDBLWIDE─┘
HPFCS details:
┌─\RASTER──┐
├────font-character-set────┴─\OUTLINE─┴─────────────────────────────────────────────────────────────────────────────────────────┤
Note:
P All parameters preceding this point can be specified in positional form.
PHFCS page. In this example, specify 697 for the graphic char-
Specifies the printer resident font entry to be removed. acter set.
Element 1: Font Identifier Element 5: Point Size
font-identifier: Specify the printer resident font identifier *WIDTH: The font point size is computed from the font
to be mapped to a host resident font. width value specified. When mapping a fixed pitch
raster font (1 - 750, 3840 - 4095), it is recommended
Element 2: Font Width
that a width value should be specified and the point size
*PTSIZE: The width for this font identifier will be calcu- value should be *WIDTH.
lated from the point size specified. When *PTSIZE is
*NONE: No point size is specified for this font identifier.
specified for width, the point size parameter can not be
*NONE should be specified when mapping to an outline
*NONE or *WIDTH. When mapping a typographic raster
font.
font (2304 - 3839, 4096 - 53247, 61440 - 65534), a point
size value should be specified. The width value can be point-size: Specify a point size ranging from 0.1 through
*PTSIZE or a value can be given. 999.9. When mapping a typographic raster font (2304 -
3839, 4096 - 53247, 61440 - 65534), a point size value
*NONE: No width is specified for this font identifier.
should be specified.
*NONE should be specified when mapping to an outline
font. HPFCS
font-width: Specify a width for the font identifier. When Specifies the host resident font entry to be removed.
mapping a fixed pitch raster font (1 - 750, 3840 - 4095), Element 1: Host Font Character Set
a width should be specified. The point size value can be
*WIDTH or a value can be given. See Appendix D in
font-character-set: Specify the font character set.
the Printer Device Programming manual for more infor- Element 2: Font Type
mation on font widths for printer resident fonts.
*RASTER: The host resident font is a raster font.
Element 3: Font Attributes
*OUTLINE: The host resident font is a outline font.
*NONE: No special font attributes are specified on this
PHCP
font.
Specifies the printer resident code page entry to be
*BOLD: The printer resident font is a bold font. removed.
*ITALIC: The printer resident font is an italic font. Element 1: Graphic Character Set
*BOLDITC: The printer resident font is a bold italic font. *SYSVAL: The graphic character set specified in the
*DBLWIDE: The printer resident font is a double wide system value QCHRID is used.
font. graphic-character-set: Specify the graphic character set
*ITCDBLWIDE: The printer resident font is an italic for the printer resident code page. The graphic char-
double wide font. acter set is the first part of the graphic character identi-
fier which consists of the graphic character set and code
Element 4: Graphic Character Set page. For example, for the graphic character identifier
Specifies the graphic character set for the font identifier. 697 500, 697 is the graphic character set and 500 is the
This parameter allows you to map a font identifier to code page. In this example, specify 697 for the graphic
more than one host font character set (based upon character set.
graphic character set). The value specified is mapped to Element 2: Code Page
a superset graphic character set. See the Printer Device
Programming manual for information on superset graphic code-page: Specify the printer resident code page value
character sets.
HPCP
*SYSVAL: The graphic character set specified in the Specifies the host resident code page entry to be
system value QCHRID is used. A change to this system removed.
value will only take effect for the font mapping tables
Element 1: Host Code Page
when the print writer is started. If QCHRID is changed
and a printer is currently active, you must end the print code-page: Specify the name of the host resident code
writer and start it again. page.
This command removes an entry from the QPHFCS table RMVFNTTBLE FNTTBL(\PHCP) PHCP(\SYSVAL 38)
(printer resident to host resident font character set table).
This command removes an entry from the QPHCP table
Example 2: Remove Code Page Entry (printer resident to host resident code page table).
┌─\LIBL/────────┐
(P) ──────────────────────────────────────5%
55──RMVFTRACNE──FILTER(──┼───────────────┼──filter-name──)──GROUP(────group-name────)────
├─\CURLIB/──────┤
└─library-name/─┘
Note:
P All parameters preceding this point can be specified in positional form.
┌─\LIBL/────────┐
(1) ──)────
55──RMVFTRSLTE──FILTER(──┼───────────────┼──filter-name──)──SEQNBR(────sequence-number───── (P) ─────────────────────────────5%
├─\CURLIB/──────┤
└─library-name/─┘
Notes:
1 Range is 1-9999
*LIBL: All libraries in the job's library list are This command removes selection entry 0010 from filter
searched until the first match is found. MYFILTER in library MYLIB.
┌─\LIBL/────────┐ ┌──
─────────────────────┐
55──RMVICFDEVE──FILE(──┼───────────────┼──file-name──)──PGMDEV(───6─program-device-name─┴───
(1) ──)────
(P) ─────────────────────────────5%
├─\CURLIB/──────┤
└─library-name/─┘
Notes:
1 A maximum of 50 repetitions
FILE
Specifies the qualified name of the ICF file from which Example
the device entries are removed. RMVICFDEVE FILE(ICFHIST)
PGMDEV (CHICAGO NEWYORK DENVER)
The name of the ICF file can be qualified by one of the
following library values: This command removes the program devices of CHICAGO,
*LIBL: All libraries in the job's library list are NEWYORK, and DENVER from the ICF file ICFHIST.
searched until the first match is found.
(P)─────────────────────────────────────────────5%
55──RMVIPIADR──RMTDEST(──remote-destination──)──SUBNETMASK(──┬─\HOST───────┬──)───
└─subnet-mask─┘
Note:
P All parameters preceding this point can be specified in positional form.
Required Parameters
Examples
RMTDEST
Specifies the remote destination for the AF_INET Example 1 - Removing an IPX Address Mapping for an IP
sockets over IPX address mapping entry being removed. Subnetwork
The remote destination is an internet address of the
network or host for the remote destination's IP over IPX RMVIPIADR RMTDEST('128.2.ð.ð')
address mapping entry. SUBNETMASK('255.255.255.128')
remote-destination: Specify the internet address associ- This command removes an address mapping entry for a sub-
ated with this address mapping entry. network with remote destination network 128.2 and subnet
mask of 255.255.255.128.
SUBNETMASK
Specifies the subnet mask for the AF_INET sockets over Example 2 - Removing an IPX Address Mapping for an IP
IPX address mapping entry being removed. Host address
*HOST: Specifies the internet address value of the
route destination. The subnetmask value is calculated to RMVIPIADR '128.3.3.3' \HOST
be 255.255.255.255.
This command removes an address mapping for an IP host
address.
(P, K) ────────────────────────────────────────────────────────────────────────────5%
55──RMVIPIIFC──INTNETADR(──internet-address──)─────
Notes:
P All parameters preceding this point can be specified in positional form.
(P)───────────────5%
55──RMVIPIRTE──RTEDEST(──route-destination──)──SUBNETMASK(──┬─\HOST───────┬──)──NEXTHOP(──internet-address──)───
└─subnet-mask─┘
Note:
P All parameters preceding this point can be specified in positional form.
(P) ─────────────────────────────────────────────────────────────────────────────5%
55──RMVIPSIFC──INTNETADR(──internet-address──)────
Note:
P All parameters preceding this point can be specified in positional form.
(P)───────────────────────────────────────5%
55──RMVIPSLOC──RMTDEST(──remote-route-destination──)──SUBNETMASK(──┬─\HOST───────┬──)───
└─subnet-mask─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose SUBNETMASK
Specifies the subnet mask of the location entry to be
The Remove IP over SNA Location Entry (RMVIPSLOC) removed.
command removes an AF_INET sockets over SNA location
*HOST: Specify this value when the internet address
entry. This command can be used to remove location entries
value specified in the remote route destination field is a
that have been specified with the Add IP over SNA Location
host address.
Entry (ADDIPSLOC) CL command. The location entry to be
removed is identified by its remote route destination subnet-mask: Specify the subnet mask in the form
(RMTDEST) and subnet mask (SUBNETMASK). nnn.nnn.nnn.nnn where nnn is a decimal number
ranging from 0 through 255. If the subnet mask is
Restriction: The user must have *IOSYSCFG authority to entered from a command line, the address must be
use this command. enclosed in apostrophes.
Note: To see the parameter and value descriptions for this
command, refer to the online help text. For more Examples
information about printing the help text, refer to
“Printing CL Command Descriptions” in Chapter 1. Example 1: Removing a Location Entry for a Subnet-
work
Required Parameters RMVIPSLOC RMTDEST('128.2.ð.ð')
SUBNETMASK('255.255.255.128')
RMTDEST
Specifies the remote route destination of the location This command removes a location entry for a subnetwork
entry to be removed. The remote route destination is with network 128.2 and subnet mask of 255.255.255.128.
specified in the form nnn.nnn.nnn.nnn where nnn is a
decimal number ranging from 0 through 255. If the Example 2: Removing a Location Entry for a Network
remote route destination address is entered from a RMVIPSLOC RMTDEST(128.3.ð.ð)
command line, the address must be enclosed in apostro- SUBNETMASK('255.255.ð.ð')
phes.
This command removes a location entry for network 128.3.
(P) ─NEXTHOP(──internet-address──)───────────────5%
55──RMVIPSRTE──RTEDEST(──route-destination──)──SUBNETMASK(──┬─\HOST───────┬──)────
└─subnet-mask─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose SUBNETMASK
Specifies the subnet mask of the route to be removed.
The Remove IP over SNA Route Entry (RMVIPSRTE)
*HOST: Specify this value when the internet address
command removes an AF_INET sockets over SNA route.
value specified in the route destination field is a host
This command can be used to remove routes that have been
address.
specified with the Add IP over SNA Route (ADDIPSRTE) CL
command. The route to be removed is identified by its route subnet-mask: Specify the subnet mask in the form
destination (RTEDEST), subnet mask (SUBNETMASK), and nnn.nnn.nnn.nnn where nnn is a decimal number
next hop (NEXTHOP). ranging from 0 to 255. If the subnet mask is entered
from a command line, the address must be enclosed in
Restriction: The user must have *IOSYSCFG authority to apostrophes.
use this command.
NEXTHOP
Note: To see the parameter and value descriptions for this Specifies the next hop of the route to be removed. The
command, refer to the online help text. For more next hop is specified in the form nnn.nnn.nnn.nnn where
information about printing the help text, refer to nnn is a decimal number ranging from 0 to 255.
“Printing CL Command Descriptions” in Chapter 1.
If the next hop address is entered from a command line,
the address must be enclosed in apostrophes.
Required Parameters
RTEDEST Example
Specifies the route destination of the route to be RMVIPSRTE RTEDEST('128.2.ð.ð')
removed. The route destination is specified in the form SUBNETMASK('255.255.255.128')
nnn.nnn.nnn.nnn where nnn is a decimal number NEXTHOP ('128.3.4.5')
ranging from 0 to 255.
This command removes a network route entry for a subnet-
If the route destination address is entered from a
work with network 128.2 and subnet mask of
command line, the address must be enclosed in apostro-
255.255.255.128.
phes.
(P) ───────────────────────────────────────────────────────────────────────────5%
55──RMVIPXCCT──CCTNAME(────IPX-circuit-name────)────
Note:
P All parameters preceding this point can be specified in positional form.
┌─\LIBL/────────┐ ┌─\LIBL/────────┐
(P) ─────────5%
55──RMVJOBQE──SBSD(──┼───────────────┼──subsystem-description-name──)──JOBQ(──┼───────────────┼──job-queue-name──)────
├─\CURLIB/──────┤ ├─\CURLIB/──────┤
└─library-name/─┘ └─library-name/─┘
Note:
P All parameters preceding this point can be specified in positional form.
┌─\ONLY────────┐
(P) ─ENTRYNBR(──┼─\ALL─────────┼──)──────────────────────────────────────────────5%
55──RMVJOBSCDE──JOB(──┬─job-name──────────┬──)────
└─generic\-job-name─┘ └─entry-number─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose ENTRYNBR
The Remove Job Schedule Entry (RMVJOBSCDE) command Specifies the number of the job schedule entry you want
allows you to remove an entry, entries, or generic entries to remove. The message sent when an entry is suc-
from the job schedule. Each job schedule entry contains the cessfully added contains the entry number. You can
information needed to automatically submit a batch job one also determine the entry number by using the Work with
time, or at regularly scheduled intervals. A message is sent Job Schedule Entries (WRKJOBSCDE) command.
to you and to the message queue specified in the job Press F11 from the Work with Job Schedule Entries
schedule entry when an entry is successfully removed. display to show the entry numbers of the selected
entries.
Restriction: To remove entries, you must have *JOBCTL *ONLY: One entry in the job schedule has the job name
special authority; otherwise you can remove only those specified on the JOB parameter. If *ONLY is specified
entries that you added. and more than one entry has the specified job name, no
Note: To see the parameter and value descriptions for this entries are removed and a message is sent.
command, refer to the online help text. For more *ALL: All entries with the specified job name are
information about printing the help text, refer to removed.
“Printing CL Command Descriptions” in Chapter 1.
entry-number: Specify the number of the job schedule
entry you want to remove.
Required Parameters
JOB Examples
Specifies the name of the job schedule entry.
Example 1: Removing Job Schedule Entries
job-name: Specify the name of the job schedule entry.
RMVJOBSCDE JOB(SAMPLE\) ENTRYNBR(\ALL)
generic*-job-name: Specify a generic name. A generic
name is a character string of one or more characters fol- This command removes all the job schedule entries whose
lowed by an asterisk (*); for example, ABC*. The job names start with SAMPLE.
asterisk substitutes for any valid characters. A generic
name specifies all objects with names that begin with the Example 2: Removing an Individual Job Schedule Entry
generic prefix for which the user has authority. If an RMVJOBSCDE JOB(PAYROLL) ENTRYNBR(\ONLY)
asterisk is not included with the generic (prefix) name,
the system assumes it to be the complete object name. This command removes the job PAYROLL in the job
If the complete object name is specified, and multiple schedule.
libraries are searched, multiple objects can be removed
only if *ALL or *ALLUSR library values can be specified Example 3: Removing a Generic Job Schedule Entry
for the name. For more information on the use of RMVJOBSCDE JOB(PAY\) ENTRYNBR(\ALL)
generic names, refer to “Generic Object Names” in
Chapter 2. If a generic name is specified, This command removes all entries in the job schedule that
ENTRYNBR(*ALL) must also be specified. have the prefix PAY in their names.
┌─\LIBL/────────┐
55──RMVJRNCHG──JRN(──┼───────────────┼──journal-name──)─────────────────────────────────────────────────────────────────────────5
├─\CURLIB/──────┤
└─library-name/─┘
┌──
─────────────────────────────────────────────────────────┐
│ ┌─\LIBL/────────┐ ┌─\FIRST──────┐ │
6 (1) ───┬──┼─────────────┼──)─┴───
5──FILE(────(──┼───────────────┼──┬─\ALL─── (2) ──)──┬────────────────────────────────────┬───
(P) ──────────5
├─\CURLIB/──────┤ └─file-name─┘ ├─\ALL────────┤ │ ┌─\CURRENT───────────┐ │
└─library-name/─┘ └─member-name─┘ └─RCVRNG(──┴─┤ RCVRNG Details ├─┴──)─┘
5──┬───────────────────────────────────────────┬──┬───────────────────────────────────────────────────────────────┬─────────────5
│ ┌─\LAST────────────────────┐ │ │ ┌─\FIRST─────────────────┐ │
└─FROMENT(──┼─\LASTSAVE────────────────┼──)─┘ └─┬─TOENT(──┴─ending-sequence-number─┴──)─────────────────────┬─┘
└─starting-sequence-number─┘ └─TOJOBO(────┬─────────────────────────────┬──job-name────)─┘
└─┬─────────────┬──user-name/─┘
└─job-number/─┘
5──┬──────────────────────┬────────────────────────────────────────────────────────────────────────────────────────────────────5%
│ ┌─\NO──┐ │
└─CMTBDY(──┴─\YES─┴──)─┘
RCVRNG Details:
┌─\LIBL/────────┐ ┌─\LIBL/────────┐
├──┼───────────────┼──starting-journal-receiver──┼───────────────┼──ending-journal-receiver─────────────────────────────────────┤
├─\CURLIB/──────┤ ├─\CURLIB/──────┤
└─library-name/─┘ └─library-name/─┘
Notes:
1 If *ALL is specified instead of file-name, the format must be library-name/*ALL.
Journal entry changes can be removed even if the sequence *LIBL: All libraries in the job's library list are
numbers have been reset. The system handles this condi- searched until the first match is found.
tion, sends an informational message, and continues the
*CURLIB: The current library for the job is
removal of journaled changes. If journal receivers are
searched. If no library is specified as the current
attached and detached in pairs (dual receivers), the system
library for the job, the QGPL library is used.
tries to use the first of the two receivers. (The order of the
receivers can be viewed on the Work with Receiver Directory library-name: Specify the name of the library to be
display, which can be accessed using the Work with Journal searched.
Attributes (WRKJRNA) command.) When the first receiver is
journal-name: Specify the name of the journal.
not usable (for example, because it is damaged or not
found), the system tries to use the second receiver of the FILE
pair. If neither receiver is usable, the removal of journaled Specifies a maximum of 300 qualified names of the
changes ends. physical database files whose journal entries are being
removed. The name of the member in the file whose
Restrictions: journal entries are being removed can also be specified.
1. This command is shipped with public *EXCLUDE Note: The maximum number of members that can have
authority and the QPGMR and QSRV user profiles have changes removed with this command is 32,767.
private authorities to use the command. If more than 32,767 members are included in the
2. The files specified on this command must currently be files specified, an error message is sent and no
having their changes journaled, and they must have changes are removed. You can change the
been journaled to the specified journal throughout the values specified on this parameter so that the
period indicated on the command. limit is not exceeded.
3. Before images are required for the files (see the Start Element 1: File Name
Journal Physical File (STRJRNPF) command). The name of the file can be qualified by one of the fol-
4. The files indicated on the command are allocated exclu- lowing library values:
sively while the changes are being removed. If a file
*LIBL: All libraries in the job's library list are
cannot be allocated exclusively, the command ends and
searched until the first match is found.
no journaled changes are removed from the files.
*CURLIB: The current library for the job is
5. If there is no journal entry that represents the entry
searched. If no library is specified as the current
specified on the FROMENT or TOENT parameter the
library for the job, the QGPL library is used.
command ends, and no journaled changes are removed
from the files. library-name: Specify the name of the library to be
searched.
6. If the journal sequence numbers have been reset in the
range of the receivers specified, and a sequence *ALL: All physical files in the specified library whose
number is specified on the FROMENT or TOENT param- changes are being journaled to the specified journal
eter, the first occurrence of the sequence number speci- have their journal entries removed. The library name
fied on either parameter is used. must be specified. If *ALL is specified and you do not
have the required authority to all of the files, an error
7. The TOJOBO parameter cannot be used to specify
message is sent and the command ends.
when the remove journaled changes operation is to end
if one or more journal receivers in the specified receiver file-name: Specify the name of the physical database
range was attached to a journal that had file whose journal entries are being removed.
RCVSIZOPT(*MINFIXLEN) in effect. Element 2: Member Name
| 8. This command cannot be used on or with a remote *FIRST: Journal entries are removed from the first
| journal. member of the file.
Note: To see the parameter and value descriptions for this *ALL: Journal entries are removed from all members in
command, refer to the online help text. For more the file.
information about printing the help text, refer to
“Printing CL Command Descriptions” in Chapter 1. member-name: Specify the name of the member in the
file whose journal entries are removed.
Required Parameters If *ALL is specified for the first part of this parameter, the
value specified for the member name is used for all
JRN applicable files in the library. For example, if *FIRST is
Specifies the qualified name of the journal that contains specified, journal changes are removed from the first
the journal entries being removed. member of all applicable files in the library.
The name of the journal can be qualified by one of the
following library values:
the FILE parameter, becomes the last job in which FROMENT parameter must identify a point that is at a
journal entry changes are removed by this command. commitment boundary.
The specified job could be a job suspected of causing
*YES: The journal entries are removed from the entry
errors when the job opens a file member.
specified on the FROMENT parameter to the entry indi-
This is the ending point for all members specified. This cated on the TO option, honoring commitment bounda-
parameter cannot be used to remove a specific job's ries.
journal entries; all entries for all jobs are removed.
If the journal entry specified on the FROMENT
The job identifier has a maximum of three elements. parameter is in the middle of the LUW of which it is
job-name a participant, an error message is sent and the
user-name/job-name operation is not attempted.
job-number/user-name/job-name
If the journal entry indicated on the TO option is in
The job name must be specified. The null value (*N) the middle of the LUW of which it is a participant,
may be used in place of the job number or the user the operation stops at the commitment boundary
profile name to maintain the position in the sequence. before that journal entry. A diagnostic message is
For example, 123456/*N/job-name specifies the job sent at the end of the operation.
number, 123456, and the job name, without specifying
the user profile under which the job is run. Note: If a journal entry is encountered that causes the
operation to end before the entry indicated on
CMTBDY the TO option, commitment boundaries might not
Specifies whether commitment boundaries are honored be honored.
when the journal entries from which journaled changes
are to be removed are part of a commitment control
logical unit of work (LUW). More information on the use Example
of commitment control is in the Backup and Recovery
RMVJRNCHG JRN(JRNA) FILE((LIB2/PAYROLL JAN))
book.
RCVRNG(RCV25 RCV22) TOENT(\FIRST)
Note: For purposes of this parameter description, the
TO option is used to describe either the TOENT This command causes the system to remove all journaled
or the TOJOBO parameter, whichever is speci- changes to journal JRNA to member JAN of file PAYROLL in
fied. library LIB2 that are journaled on the journal receiver chain
starting with receiver RCV25 and ending with receiver
*NO: The journal entries are removed from the entry
RCV22. Library search list *LIBL is used to find journal
specified on the FROMENT parameter to the entry indi-
JRNA and receivers RCV25 and RCV22.
cated on the TO option, regardless of commitment
boundaries. Even if a journal entry within this range is a The removal operation begins with the last journaled change
participant of the LUW, the operation is attempted. The on the receiver chain and ends with the first journaled
change.
(P) ─┬────────────────────────────────┬─────────────────────────────────────────────5%
55──RMVLANADPI──ADPTNAME(──┬─\ADPTADR─────┬────
└─adapter-name─┘ (1) ─adapter-address──)─┘
└─ADPTADR(───
Notes:
P All parameters preceding this point can be specified in positional form.
(P) ──)──┬────────────────────────────────┬─────────────────────5%
55──RMVLANADPT──LINE(──line-name──)──ADPTNAME(──┬─\ADPTADR─────┬───
└─adapter-name─┘ (1) ─adapter-address──)─┘
└─ADPTADR(───
Notes:
P All parameters preceding this point can be specified in positional form.
(P) ────────────────────────────────────────────────────────────────────────────────────────5%
55──RMVLIBLE──LIB(──library-name──)────
Note:
P All parameters preceding this point can be specified in positional form.
55──RMVLICKEY──┬────────────────────────────────┬──┬──────────────────────────────────────────────┬─────────────────────────────5
│ ┌─\LICKEYFILE─┐ (1) ─┬─\ALL────────────────────────┬──)─┘
│ └─PRDID(───
└─LICKEYINP(──┴─\PROMPT─────┴──)─┘ ├─generic\-product-identifier─┤
└─product-identifier──────────┘
5──┬────────────────────────────────┬──┬────────────────────────────┬─── (P) ──┬──────────────────────────────────────┬──────────────5
│ ┌─\ALL─────────┐ │ │ ┌─\ALL────┐ │ │ ┌─\LOCAL───────────────┐ │
(1) ─┴─license-term─┴──)─┘ └─FEATURE(───
└─LICTRM(─── (1) ─┴─feature─┴──)─┘ └─SERIAL(──┼─\REMOTE──────────────┼──)─┘
├─\ALL─────────────────┤
└─system-serial-number─┘
5──┬───────────────────────────────────────────────────────┬──┬─────────────────────────────────────────┬──────────────────────5%
│ ┌─\LIBL/────────┐ │ │ ┌─\FIRST─────────────┐ │
(2) ─┼───────────────┼──license-key-file──)─┘ └─LICKEYMBR(───
└─LICKEYFILE(─── (2) ─┼─\LAST──────────────┼──)─┘
├─\CURLIB/──────┤ └─license-key-member─┘
└─library-name/─┘
Notes:
1 This parameter is valid only when LICKEYINP(*PROMPT) is specified.
Optional Parameters *ALL: The software license key information for all
product identifiers is removed.
LICKEYINP
license-term: Specify the license term in Vx, VxRy, or
Specifies how the software license key information to be
VxRyMz format, where x and y can be a number from 0
removed is supplied by the user.
through 9, and z can be a number from 0 through 9 or a
*LICKEYFILE: The software license key information is letter from A through Z.
taken from the file specified on the LICKEYFILE param-
eter. FEATURE
Specifies the feature of the product specified on the
*PROMPT: The software license key information is PRDID parameter for which the software license key
entered through prompting. information is removed.
PRDID *ALL: The software license key information for all fea-
Specifies the seven-character identifier of the product for tures of the product is removed.
which software license key information is removed.
feature: Specify the number of the feature for which *LIBL: All libraries in the job's library list are
software license key information is removed. searched until the first match is found.
*LOCAL: The software license key information for the library-name: Specify the name of the library to be
local system is removed. searched.
*REMOTE: The software license key information to be license-key-file: Specify the name of the file that con-
removed is for remote systems only and depends on the tains the software license key information.
value specified on the LICKEYINP parameter.
LICKEYMBR
If LICKEYINP(*PROMPT) is specified, the software Specifies the name of the member in which the software
license key information for all remote systems is license key information to be removed is located. This
removed. member is in the file specified on the LICKEYFILE
parameter.
If LICKEYINP(*LICKEYFILE) is specified, the soft-
ware license key information for the remote systems *FIRST: The oldest member in the file is used.
named in the file specified on the LICKEYFILE
*LAST: The newest member in the file is used.
parameter is removed.
license-key-member: Specify the name of the member
*ALL: The software license key information to be that contains the software license key information.
removed is for all systems and depends on the value
specified on the LICKEYINP parameter.
Examples
If LICKEYINP(*PROMPT) is specified, the software
license key information for all systems is removed. Example 1: Removing License Key Information from
Prompt Input
If LICKEYINP(*LICKEYFILE) is specified, the soft-
ware license key information for all the remote RMVLICKEY LICKEYINP(\PROMPT) PRDID(1MYPROD)
systems named in the file specified on the LICTRM(V3) FEATURE(5ðð1) SERIAL(1234567)
LICKEYFILE parameter is removed.
This command removes from the license repository the soft-
system-serial-number: Specify the serial number of the ware license key information for the product 1MYPROD, the
system for which software license key information is license term V3, and the feature 5001 for the system with
removed. serial number 1234567.
LICKEYFILE Example 2: Removing License Key Information from File
Specifies the qualified name of the file in which the soft- Input
ware license key information to be removed is located.
RMVLICKEY LICKEYINP(\LICKEYFILE)
This input file must be in the format of
SERIAL(\REMOTE) LICKEYFILE(\LIBL/MYKEYFILE)
QSYS/QALZAKEY, and can be created by using the LICKEYMBR(\LAST)
LICKEYFILE parameter on the Display License Key
Information (DSPLICKEY) command. This command removes from the license repository the soft-
The name of the license key file can be qualified by one ware license key information for all the remote systems found
of the following library values: in the newest created member of the file MYKEYFILE.
(1) ─'object-link-path-name'──)────
55──RMVLNK──OBJLNK(─── (P) ──────────────────────────────────────────────────────────────────────────5%
Notes:
1 You can specify a pattern for this path name.
This command can also be issued using the following alter- Example
native command names:
RMVLNK OBJLNK('PAY')
DEL
ERASE This command removes a link named PAY.
2. You must have execute authority to each directory in the For QSYS.LIB restrictions, see the delete command for
path. the object you are removing. In general, the name of
this command is formed using the OS/400 object type
3. A directory cannot be unlinked. value, from which you remove the character * and add
4. The restrictions listed above are for the OS/400 objects the verb DLT to the beginning. For example:
of the types *DDIR, *DSTMF, *SOCKET, *STMF, and To delete an alert table, which has the object type
*SYMLNK. value of *ALRTBL, see the description for the
DLTALRTBL (Delete Alert Table) command for any
More information about restrictions for using this command
additional restrictions.
can be found in the “Additional Considerations” section at the
end of this command description. You can use the table in the "OBJTYPE Parameter"
section of Appendix A to identify the object type values.
Note: To see the parameter and value descriptions for this
command, refer to the online help text. For more Exceptions:
information about printing the help text, refer to 1. The names of the delete commands for the fol-
“Printing CL Command Descriptions” in Chapter 1. lowing objects are not formed in the general manner
described above, so they are supplied here for your
Required Parameter reference:
Object Type (Value) Command
OBJLNK
Specifies the path name of the object to unlink. Multiple Compiler unit (*MODULE) DLTMOD
links can be removed with a name pattern. File 1 (*FILE) DLTF
The object path name can be either a simple name or a Menu description (*MENU) DLTMNU
name that is qualified with the name of the directory in
which the object is located. A pattern can be specified Server storage space (*SVRSTG)
DLTNWSSTG
┌─\LIBL/────────┐
(P) ───────────────────────────────5%
55──RMVM──FILE(──┼───────────────┼──database-file-name──)──MBR(──┬─\ALL─────────────────┬──)────
├─\CURLIB/──────┤ ├─member-name──────────┤
└─library-name/─┘ └─generic\-member-name─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose MBR
Specifies the name of the physical or logical file member
The Remove Member (RMVM) command removes one or being removed. A specific or generic member name, or
more members from the specified physical or logical file. *ALL, can be requested.
Removing a physical file member deletes all the data in the
*ALL: All members found in the specified file are
member and frees the storage space allocated to that
removed.
member and its access path. Removing a logical file
member deletes its access path to the associated data member-name: Specify the specific name of the
stored in a physical file member. member removed.
generic*-member-name: Specify the generic name of
Restriction: If a member of another file is sharing the data
the member. A generic name is a character string of
of the member being deleted, the dependent member must
one or more characters followed by an asterisk (*); for
be removed first. To remove a member from a file, the user
example, ABC*. The asterisk substitutes for any valid
must have object existence authority for the file.
characters. A generic name specifies all objects with
Note: To see the parameter and value descriptions for this names that begin with the generic prefix for which the
command, refer to the online help text. For more user has authority. If an asterisk is not included with the
information about printing the help text, refer to generic (prefix) name, the system assumes it to be the
“Printing CL Command Descriptions” in Chapter 1. complete object name. If the complete object name is
specified, and multiple libraries are searched, multiple
objects can be removed only if *ALL or *ALLUSR library
Required Parameters values can be specified for the name. For more infor-
FILE mation on the use of generic names, refer to “Generic
Specifies the qualified name of the database file (phys- Object Names” in Chapter 2.
ical or logical) that contains the member being removed.
The name of the file can be qualified by one of the fol- Examples
lowing library values:
Example 1: Removing a File Member
*LIBL: All libraries in the job's library list are
RMVM FILE(JOBHIST1) MBR(JOBHIST1A)
searched until the first match is found.
*CURLIB: The current library for the job is This command removes file member JOBHIST1A from file
searched. If no library is specified as the current JOBHIST1. Library list *LIBL is used to find the file and
library for the job, the QGPL library is used. member. If JOBHIST1 contains other members, they remain
unchanged.
library-name: Specify the name of the library to be
searched. Example 2: Removing Members with Names that Start
database-file-name: Specify the name of the database with SRC
file that contains the member being removed. RMVM FILE(QGPL/JOBHISTL) MBR(SRC\)
(2) ────┬──)────
55──RMVMFS──TYPE(──┬─\NFS─── (P) ─MNTOVRDIR(──┬─'directory-path-name'─┬──)──MFS(──'file-system-path-name'──)────────────5%
(1) ───┤
├─\UDFS─── (3) ───────────────┘
└─\ALL───
├─\NETWARE─── (2) ┤
└─\ALL───────┘
Notes:
1 If the TYPE parameter is *UDFS, one parameter from the choices MFS or MNTOVRDIR is required.
3 If *ALL is specified for MNTOVRDIR, *ALL must also be specified for the TYPE parameter.
Note: To see the parameter and value descriptions for this MFS
command, refer to the online help text. For more Specifies the path name of the file system to be
information about printing the help text, refer to unmounted. This parameter can only be used to
“Printing CL Command Descriptions” in Chapter 1. unmount a Block Special File (*BLKSF), when *UDFS is
specified for the TYPE parameter.
Required Parameters
Examples
TYPE
Specifies the type of file system being unmounted. Example 1: Unmounting a Directory
*NFS: The file system being unmounted is a Network RMVMFS TYPE (\NFS) MNTOVRDIR('/tools')
File System. When *NFS is specified, you must specify a
directory for the MNTOVRDIR parameter. This command unmounts a Network File System that is
accessible on directory /tools.
*UDFS: The file system being unmounted is a user-
defined file system. When *UDFS is specified, you may Example 2: Unmounting an User Defined File System
specify either the MNTOVRDIR or the MFS parameter.
RMVMFS TYPE(\UDFS) MFS('/DEV/QASPð2/CUST1UDFS')
55──RMVMSG──┬─────────────────────────────────────────────────────────────────────────────────────────────────────┬─────────────5
│ ┌─\PRV──┐ ┌─\──────────────────────────────────────────────────────────────────────┐ │
├─PGMQ(──┬─┴─\SAME─┴──┼────────────────────────────────────────────────────────────────────────┼─┬──)─┤
│ │ └─program-or-procedure-name──┬─────────────────────────────────────────┬─┘ │ │
│ │ │ ┌─\NONE───────┐ ┌─\NONE──────────────┐ │ │ │
│ │ └─┴─module-name─┴──┼────────────────────┼─┘ │ │
│ │ └─bound-program-name─┘ │ │
│ (1) ┬───────────────────────────────────────────────────────────────────────┘
└─┬─\ALLINACT─── │
│ └─\EXT────────┘ │
└─MSGQ(──┬─\PGMQ─────────────────────────────────┬──)─────────────────────────────────────────────────┘
│ ┌─\LIBL/────────┐ │
└─┼───────────────┼──message-queue-name─┘
├─\CURLIB/──────┤
└─library-name/─┘
5──┬─────────────────────────────────┬──┬─────────────────────────────┬──┬─────────────────────────┬───────────────────────────5%
(2) ─&CL-variable-name──)─┘ │
└─MSGKEY(─── ┌─\BYKEY─────┐ │ │ ┌─\YES─┐ │
(3) ─┼─\ALL───────┼──)─┘ └─RMVEXCP(───
└─CLEAR(─── (4) ─┴─\NO──┴──)─┘
├─\KEEPUNANS─┤
├─\OLD───────┤
└─\NEW───────┘
Notes:
1 If PGMQ(*ALLINACT) is specified, the CLEAR parameter must be *ALL.
3 CLEAR(*KEEPUNANS) is valid only if a message queue name is specified for the MSGQ parameter.
program-or-procedure-name: Specify the name of the library-name: Specify the name of the library to be
program or procedure used. searched.
If Item 1 identifies a program, the name specified can be message-queue-name: Specify the name of the
a maximum of 10 characters. If Item 1 identifies a pro- message queue from which one or more messages are
cedure, the name specified can be a maximum of 256 removed.
characters.
MSGKEY
The procedure name alone may not identify the correct
Specifies the name of the CL variable that contains the
procedure. Several different procedures with the same
message reference key of the message being removed.
name can run in a job. To further identify a procedure,
MSGKEY cannot be specified if *ALL, *KEEPUNANS,
the name specified can be qualified by a module name,
*OLD, or *NEW is specified for the CLEAR parameter.
or by both a module name and a bound program name.
CLEAR
Item 2: Module Name
Specifies whether one message, all messages (except
The module name qualifier identifies the module into unanswered inquiry messages), or only old or new mes-
which the procedure was compiled. sages in the specified message queue are removed from
*NONE: No module name is specified. the queue.
module-name: Specify the module name to be used as *BYKEY: The message identified by the CL variable
a qualifier for the specified procedure name (modules named in the MSGKEY parameter is removed from the
are associated only with procedures). The module name message queue.
can be a maximum of 10 characters. *ALL: All messages are removed from the specified
If a module name is not specified but a bound program message queue.
name is, *NONE must be specified in the module name *KEEPUNANS: Messages other than unanswered
position. inquiry messages are removed from the specified
Item 3: Bound Program Name message queue. If CLEAR(*KEEPUNANS) is specified,
MSGQ(*PGMQ) cannot be specified (a message-queue
The bound program name qualifier identifies the program
name must be specified for MSGQ).
to which the procedure was bound.
*OLD: Old messages in the specified message queue
*NONE: No bound program name is specified.
are removed from the queue.
bound-program-name: Specify the bound program name *NEW: New messages in the specified message queue
to be used as a qualifier for the specified procedure
are removed from the queue.
name (and module name if specified). The bound
program name can be a maximum of 10 characters. RMVEXCP
Specifies the action to be taken when an unhandled
Other Single Values
exception message is found. An unhandled exception
*ALLINACT: All messages for all inactive call stack message is an escape, notify, or status message that
entries are removed from the user's job message queue. has been sent to an ILE procedure. When this
If this value is specified for the PGMQ parameter, the command is run, the ILE procedure has not yet taken
value *ALL must be specified on the CLEAR parameter. action to tell the system that the exception is handled.
*EXT: The message is removed from the external One action that the ILE procedure can take is to call a
message queue of the job. CL program that will remove the exception message.
More information on actions that an ILE procedure can
MSGQ take to handle an exception is in &ilec..
Specifies the qualified name of the message queue from
This parameter is valid only when working with a
which one or more messages are removed. If MSGQ is
message queue that is associated with a call stack entry
specified, the PGMQ parameter cannot be specified.
for an ILE procedure. This parameter is ignored when
*PGMQ: The call message queue specified in the working with a message queue associated with a call
PGMQ parameter is the only queue from which the mes- stack entry for a program.
sages are removed. If CLEAR(*KEEPUNANS) is speci-
*YES: The unhandled exception message on the speci-
fied, MSGQ(*PGMQ) cannot be specified.
fied message queue is removed. As a result, the excep-
The name of the message queue can be qualified by tion is handled.
one of the following library values:
*NO: The unhandled exception message on the speci-
*LIBL: All libraries in the job's library list are fied message queue is not removed. The message
searched until the first match is found. remains on the queue as an unhandled exception
message.
*CURLIB: The current library for the job is
searched. If no library is specified as the current
library for the job, the QGPL library is used.
┌─\LIBL/────────┐
(P) ─────────────────────────────────5%
55──RMVMSGD──MSGID(──message-identifier──)──MSGF(──┼───────────────┼──message-file-name──)────
├─\CURLIB/──────┤
└─library-name/─┘
Note:
P All parameters preceding this point can be specified in positional form.
┌─\PRIVATE─┐
(P) ────────────────────────────────────────────────────────────────────────────────5%
55──RMVNCK──NCK(──nickname──┴─\PUBLIC──┴──)────
Note:
P All parameters preceding this point can be specified in positional form.
A nickname is a short version of either a directory entry nickname: Specify the nickname you are removing.
name or a distribution list name. More information about Element 2: Nickname Access
nicknames is in the SNA Distribution Services book.
*PRIVATE: The private nickname that you own is being
Restrictions: removed.
1. You must have security administrator (*SECADM) *PUBLIC: The public nickname is being removed.
authority to remove a public nickname that you do not Public nicknames can be removed by a user with secu-
own. No special authority is needed for you to remove a rity administrator (*SECADM) authority or by the owner.
public or private nickname that you own.
2. Only the owner can remove a private nickname. No Example
special authority is needed. RMVNCK NCK(SEC44A \PUBLIC)
Note: To see the parameter and value descriptions for this
command, refer to the online help text. For more This command removes the public nickname SEC44A. If the
information about printing the help text, refer to user has proper authority to the nickname, the nickname is
“Printing CL Command Descriptions” in Chapter 1. removed.
(P) ─────────────────────────────────────────────────────────────────────────────────────5%
55──RMVNETJOBE──FROMUSRID(──user-ID──)────
Note:
P All parameters preceding this point can be specified in positional form.
Purpose Note: To see the parameter and value descriptions for this
command, refer to the online help text. For more
The Remove Network Job Entry (RMVNETJOBE) command information about printing the help text, refer to
removes a network job entry from the system. The network “Printing CL Command Descriptions” in Chapter 1.
job entry determines the action taken when an input stream
is sent to a user on this system by using the Submit Network
Job (SBMNETJOB) command. This entry is used to deter- Required Parameter
mine whether the input stream is automatically submitted, FROMUSRID
placed on the queue of received files for a user, or rejected. Specifies the two-part user ID that identifies the network
The entry also specifies the user profile that is used for job entry being removed. Specify the two-part user ID.
checking the authority to the job description referenced in the Both parts of the user ID are required.
batch job. There should be one entry for each user or group
of users who submit jobs to this system. Note: Depending on the work station being used, the
internal value for a new user identifier may differ
If this command is used to remove an entry for a specific from the characters shown by the Display
user, an entry may still exist that is in effect for that user. Network Job Entry (DSPNETJOBE) command. If
For example, if the user removes the entry for user ID, JOE the byte-string value specified for the
PGMRS, and if there is an entry with a user ID, *ANY FROMUSRID parameter does not match the
PGMRS or *ANY *ANY, that entry is used to handle any jobs rules for an internal user identifier value, or if it
submitted by JOE PGMRS. Additional information on the job does not match the internal value for any
entry table is in the SNA Distribution Services book. enrolled user, an error may be reported.
Restrictions:
1. This command is shipped with public *EXCLUDE Example
authority. RMVNETJOBE FROMUSRID(JOE SMITH)
2. The internal value for a node identifier may differ from
This command removes the network job entry that is used to
the characters shown by the RMVNETJOBE command
determine the action that is taken for any input streams
depending on the type of work station (language) being
received from user ID, JOE SMITH. The network job
used. If the byte-string value specified for the
authority for user ID, JOE SMITH, is taken from either the
FROMUSRID command parameter does not match the
network job entry *ANY SMITH, if that entry exists, or from
rules for an internal node identifier value, or if it does not
the network job entry *ANY *ANY, if that entry exists. If
match the internal value for any defined node (ignoring
neither of these entries exist, all jobs received from user ID,
case differences), an error may be reported.
JOE SMITH, are rejected.
(P) ─────────────────────────────────────────────────5%
55──RMVNETTBLE──NETWORK(──network-name──)──INTNETADR(──internet-address──)────
Note:
P All parameters preceding this point can be specified in positional form.
Purpose NETWORK
Specifies the name of the network entry to be removed.
The Remove Network Table Entry (RMVNETTBLE)
command is used to remove a network entry from the INTNETADR
network table. The network table is used to manage a list of Specifies the Internet address of the network to be
your networks and their associated Internet addresses. removed. Internet addresses are expressed in the
decimal form
Restriction: You must have system configuration nnn.nnn.nnn.nnn
(*IOSYSCFG) special authority to use this command.
where nnn is a number ranging from 0 through 255.
Note: To see the parameter and value descriptions for this
command, refer to the online help text. For more
information about printing the help text, refer to Example
“Printing CL Command Descriptions” in Chapter 1. RMVNETTBLE NETWORK(NETONE) INTNETADR(9.5.ð.ð)
┌─\LIBL/────────┐
(P) ─┬──────────────────────────────────────────────────┬──────────5
55──RMVNODLE──NODL(──┼───────────────┼────node-list-name────)────
├─\CURLIB/──────┤ │ ┌─\SNA─┐ │
└─library-name/─┘ (1) ┘
└─RMTLOCNAME(──remote-location-name──┴─\IP──┴──)───
5──┬──────────────────────────────────────────────────────────┬────────────────────────────────────────────────────────────────5%
│ ┌─\RMTLOC────────────────────────────────┐ │
(2) ┘
└─CPNAME(──┴─┬─\NETATR────┬──┬────────────────────┬─┴──)───
└─network-ID─┘ └─control-point-name─┘
Notes:
P All parameters preceding this point can be specified in positional form.
2 The *RMTLOC value is required for this parameter if a value is specified for the RMTLOCNAME parameter.
library-name: Specify the name of the library to be 2. When the RMTLOCNAME parameter is used to
searched. specify the name of a system to remove from the
node list, *RMTLOC must be specified for this
node-list-name: Specify the name of the node list to parameter.
which the entry is added.
*RMTLOC: The network ID and control point name are
specified using the RMTLOCNAME parameter.
Optional Parameters Element 1: Network ID
RMTLOCNAME *NETATR: The local network ID (LCLNETID) network
Specifies the name and address type of the system to attribute is used as the value of the network identifier
remove from the node list object. The name can be an (ID) of the system being removed from the node list.
SNA network ID and control point name, an internet pro-
tocol host name, or an internet address. network-ID: Specify the network ID of the system to
remove from the node list.
An SNA node name is specified using the format
nnnnnnnn.cccccccc, where nnnnnnnn is the network ID Element 2: Control Point Name
and cccccccc is the control point name. If only the control-point-name: Specify the control point name of
control point name is specified, the local network ID the system to remove from the node list.
(LCLNETID) network attribute is used as the value of the
Note: This field is left blank when *RMTLOC is speci- RMVNODLE NODL(MYLIB/NODLð2)
fied as the network ID. RMTLOCNAME(MYSYS.NET1.LOCAL \IP)
55──RMVNWSSTGL──NWSSTG(────network-server-storage-name────)──NWSD(────network-server-description-name────)─────────────────────5%
55──RMVOPTCTG──VOL(──┬─\IOSTATION────────┬──)──┬───────────────────────────┬───(P) ─────────────────────────────────────────────────5
└─volume-identifier─┘ │ ┌─\REMOVE─┐ │
(1) ─┴─\KEEP───┴──)─┘
└─VOLOPT(───
5──┬─────────────────────────────────────────────────┬──┬──────────────────────────────────┬───────────────────────────────────5%
│ ┌─\NONE──────────────────────┐ (3) ─optical-media-library──)─┘
│ └─MLB(───
(2) ─┴─removed-cartridge-location─┴──)─┘
└─RMVCTGLOC(───
Notes:
1 This parameter is valid only if a volume identifier is specified on the VOL parameter.
Purpose VOLOPT
Specifies whether to keep the optical volume description
The Remove Optical Cartridge (RMVOPTCTG) command in the optical index database files.
can be used to:
Note: This parameter is valid only if a volume identifier
Remove an optical disk cartridge and its volumes from is specified on the VOL parameter.
an optical media library.
*REMOVE: The volume description is removed from the
Remove a cartridge currently in the input/output station
optical index database files.
of an optical media library.
Move the input/output station of an optical media library *KEEP: The volume description is kept in the optical
to the out position. index database files. This allows the volume
Remove the volume description of an optical volume descriptions of removed volumes to be displayed when
previously removed using this command with using the Work with Optical Volumes (WRKOPTVOL)
VOLOPT(*KEEP) specified. command.
(P) ─────────────────5%
55──RMVOPTSVR──CSI(──┬─\ALL───────────────────────────────────────────────┬──)──┬─────────────────────────┬───
│ ┌──
─────────────────────────────────────────────┐ │ │ ┌─\REMOVE─┐ │
6 (1) ─┘
└───communications-side-information-object-name─┴─── └─VOLOPT(──┴─\KEEP───┴──)─┘
Notes:
1 A maximum of 16 repetitions
(P) ────────────────────────────────────────────────────────────────────────────────5%
55──RMVPCLTBLE──PROTOCOL(──protocol-name──)────
Note:
P All parameters preceding this point can be specified in positional form.
This command removes the TCP protocol entry from the pro-
tocol table.
(P) ───────────────────────────────────────────────────────────────────────5%
55──RMVPEXDFN──DFN(──┬─definition-name──────────┬──)────
├─generic\-definition-name─┤
└─\ALL─────────────────────┘
Note:
P All parameters preceding this point can be specified in positional form.
definition-name: Specify the name of the performance This command removes all definitions with names that start
explorer definition to be removed. with SAM by removing all members that start with SAM from
file QAPEXDFN in library QUSRSYS.
┌─\LIBL/────────┐
(P) ─┬───────────────────────┬─────5
55──RMVPFCST──FILE(──┼───────────────┼──physical-file──)──CST(──┬─\ALL───────────────────┬──)────
├─\CURLIB/──────┤ ├─\CHKPND────────────────┤ │ ┌─\ALL────┐ │
└─library-name/─┘ │ ┌──
─────────────────┐ │ └─TYPE(──┼─\REFCST─┼──)─┘
6 (1) ─┘
└───constraint-name─┴─── ├─\UNQCST─┤
├─\PRIKEY─┤
| └─\CHKCST─┘
5──┬─────────────────────────────┬─────────────────────────────────────────────────────────────────────────────────────────────5%
│ ┌─\RESTRICT─┐ │
(2) ─┼─\REMOVE───┼──)─┘
└─RMVCST(───
└─\KEEP─────┘
Notes:
1 A maximum of 300 repetitions.
*REFCST: The referential constraints are removed. constraint that is also a parent key is removed from the
The following are examples of the CST parameter parent file of a referential constraint.
dependencies:
Note: This parameter is ignored if the value on the
CST(*ALL) TYPE(*REFCST) - All referential con- TYPE parameter is *REFCST.
straints are removed *RESTRICT: The constraint is not removed if the con-
CST(*CHKPND) TYPE(*REFCST) - All referential straint is either defined or established between the
constraints in check pending are removed parent file and the dependent file. Neither the foreign
key access path nor the foreign key of the dependent file
CST(ABC) TYPE(*REFCST) - The referential con-
is removed.
straint ABC is removed
*REMOVE: The constraint and the constraint definition
*UNQCST: The unique constraints are removed. between the parent file and the dependent file are
Note: If the unique constraint is a primary key, the removed. The corresponding foreign key is removed.
unique constraint is removed, but the primary key The foreign key access path of the dependent file is
definition and the file's access path are not removed only if one exists and is not shared.
removed. *KEEP: The constraint between the parent file and the
The following are examples of the CST parameter dependent file is removed, but the constraint definition is
dependencies: not removed. The corresponding foreign key and the
foreign key access path of the dependent file are not
CST(*ALL) TYPE(*UNQCST) - All unique con- removed.
straints (except the primary key constraint) are
removed
Examples
CST(*CHKPND) TYPE(*UNQCST) - Not valid;
unique constraints cannot be in check pending In these examples, the unique constraint
CST(ABC) TYPE(*UNQCST) - The unique con- UNIQUE_Department_NUMBER and the referential con-
straint ABC is removed (unless it is a primary key straint EMPLOYEE_Department were added to the files by
constraint) issuing the following Add Physical File Constraint
(ADDPFCST) commands:
*PRIKEY: The primary key constraint is removed. The
ADDPFCST FILE(MYLIB/DEPARTMENTS) TYPE(\UNQCST)
following are examples of the CST parameter dependen-
KEY(DEPTNUM) CST(UNIQUE_Department_NUMBER)
cies: ADDPFCST FILE(MYLIB/PERSONNEL) TYPE(\REFCST)
CST(*ALL) TYPE(*PRIKEY) - The primary key con- KEY(DEPTNO) CST(EMPLOYEE_Department)
straint is removed
Example 1: Removing a Unique Constraint
CST(*CHKPND) TYPE(*PRIKEY) - Not valid; RMVPFCST FILE(MYLIB/DEPARTMENTS) CST(\ALL)
primary key constraints cannot be in check pending TYPE(\ALL)
CST(ABC) TYPE(*PRIKEY) - The primary key con-
straint ABC is removed This command removes the unique constraint
UNIQUE_Department_NUMBER from the file DEPART-
| *CHKCST: The check constraints are removed. The MENTS located in the library MYLIB.
| following are examples of the CST parameter dependen-
| cies: Example 2: Removing a Referential Constraint
┌─\LIBL/────────┐
(P) ──5%
55──RMVPFTRG──FILE(──┼─\CURLIB/──────┼──physical-file-name──)──┬──────────────────────────┬──┬───────────────────────────┬───
└─library-name/─┘ │ ┌─\ALL────┐ │ │ ┌─\ALL────┐ │
└─TRGTIME(──┼─\BEFORE─┼──)─┘ └─TRGEVENT(──┼─\INSERT─┼──)─┘
└─\AFTER──┘ ├─\DELETE─┤
└─\UPDATE─┘
Note:
P All parameters preceding this point can be specified in positional form.
1. You must have read authority and alter or object man- *AFTER: The triggers for programs called after a trigger
agement authority to the physical file and execute event are removed.
authority to the file library to use this command. TRGEVENT
2. If the physical file or a dependent logical file or Struc- Specifies the trigger event for which the associated trig-
tured Query Language (SQL) view is opened in this or gers are removed.
another job, the trigger cannot be removed. *ALL: All triggers for insert, delete, and update oper-
3. While this command is running, neither the physical file ations are removed.
nor any dependent logical files can be opened. *INSERT: The triggers for insert operations are
Note: To see the parameter and value descriptions for this removed.
command, refer to the online help text. For more *DELETE: The triggers for delete operations are
information about printing the help text, refer to removed.
“Printing CL Command Descriptions” in Chapter 1.
*UPDATE: The triggers for update operations are
removed.
Required Parameter
FILE Examples
Specifies the qualified name of the physical file from
which this trigger is removed. The file name must exist Example 1: Removing All Triggers for Insert Events
on the system. RMVPFTRG FILE(EMP) TRGEVENT(\INSERT)
The name of the physical file can be qualified by one of
This command removes all triggers for programs called by
the following library values:
insert operations from the physical file named EMP.
*LIBL: All libraries in the job's library list are
searched until the first match is found. Example 2: Removing All Triggers for Programs Called
Before a Trigger Event
(P) ────────────────────────────────────────────────────────────────────────────5%
55──RMVPGM──┬──────────────────────────────────┬───
│ ┌─\DFTPGM─────────────┐ │
└─PGM(──┼─\ALL────────────────┼──)─┘
│ ┌──
──────────────┐ │
└──6─program-name─┴───
(1) ─┘
Notes:
1 A maximum of 20 repetitions
┌─\LIBL/────────┐
(P) ───────────5%
55──RMVPJE──SBSD(──┼───────────────┼──subsystem-description-name──)──┬──────────────────────────────────────────┬───
├─\CURLIB/──────┤ │ ┌─\LIBL/────────┐ │
└─library-name/─┘ └─PGM(──┼───────────────┼──program-name──)─┘
├─\CURLIB/──────┤
└─library-name/─┘
Note:
P All parameters preceding this point can be specified in positional form.
(P) ─┬───────────────────────────────────┬──┬────────────────────┬──────────────────────5
55──RMVPTF──LICPGM(──licensed-program──)────
│ ┌─\ALL──────────────┐ │ │ ┌─\TEMP─┐ │
│ │ ┌──
────────────┐ │ │ └─RMV(──┴─\PERM─┴──)─┘
6
├─SELECT(──┴───PTF-number─┴───(1) ─┴──)─┤
│ ┌──
────────────┐ │
└─OMIT(───6─PTF-number─┴───
(1) ──)───────┘
5──┬───────────────────────┬──┬──────────────────────┬──┬────────────────────────────┬──┬───────────────────────────┬──────────5%
| │ ┌─\NO──┐ │ │ ┌─\YES─┐ │ │ ┌─\ONLY─────────┐ │ │ ┌─\NO──┐ │
| └─DELAYED(──┴─\YES─┴──)─┘ └─IPLRMV(──┴─\NO──┴──)─┘ └─RLS(──┴─release-level─┴──)─┘ └─RMVDEP(─── (2) ─┴─\YES─┴──)──)─┘
Notes:
| 1 A maximum of 300 repetitions
| 2 The RMVDEP parameter is valid only if *ALL is not specified in the SELECT parameter.
Purpose are sent to the job log indicating which PTFs are not
removed and the reasons they are not being removed.
The Remove Program Temporary Fix (RMVPTF) command
PTF-number: Specify the PTF identification number of
removes the specified program temporary fixes (PTFs) from
| each PTF being removed. Up to 300 PTF numbers can
the specified product. If the PTFs were temporarily applied,
| be specified.
the original objects that they replaced are returned. The
PTFs can be temporarily removed, in which case they are OMIT
held in the product PTF library and they can be applied later. Specifies that all PTFs are removed except for those
If the PTFs have not been applied, they can be permanently specified in this parameter. Specify the PTF numbers of
removed and moved to the QRPLOBJ library. the PTFs that are omitted (left in the system) when all
| the rest are removed. Up to 300 PTF numbers can be
The RMVPTF command is used to remove immediate PTFs | specified. The OMIT parameter cannot be specified if
at the time the command is processed, or when the user single PTF numbers are specified in the SELECT
wants to request that PTFs be removed during an unat- parameter.
tended initial program load (IPL).
RMV
Restriction: This command is shipped with public Specifies whether the PTFs are removed temporarily or
*EXCLUDE authority and the QPGMR user profile has permanently. Permanently removed PTF objects are
private authority to use the command. moved to QRPLOBJ or deleted. Temporarily removed
Note: To see the parameter and value descriptions for this PTFs are held in the product PTF library for application
command, refer to the online help text. For more at a later time.
information about printing the help text, refer to *TEMP: The PTFs are removed and held in the product
“Printing CL Command Descriptions” in Chapter 1. PTF library so that they can be applied again later, if
desired.
Required Parameter *PERM: The PTFs are permanently removed and
placed in QRPLOBJ.
LICPGM
Specifies the 7-character identifier of the product from DELAYED
which the PTFs are removed. Specifies whether immediate PTFs are removed at the
time the command is run, or whether immediate or
delayed PTFs are removed during the next unattended
Optional Parameters IPL.
SELECT *NO: Immediate PTFs that are identified are removed at
Specifies which of the PTFs to remove from the speci- the time the command is processed. Delayed PTFs are
fied product. The OMIT parameter cannot be specified if ignored during the RMVPTF request and are not
single PTF numbers are specified in the SELECT removed. Delayed PTFs, with a status type of Not
parameter. Applied, are permanently removed at the time the
*ALL: All the PTFs are removed from the product. command is run.
Those that were permanently applied are ignored by this *YES: Both delayed and immediate PTFs that are iden-
command. If all PTFs cannot be removed, messages tified are removed during the next unattended IPL. The
IPLAPY parameter in the APYPTF command determines | PTFs specified in the SELECT parameter are processed
whether the PTFs are removed during the next unat- | with the PTFs specified in the SELECT parameter list.
tended IPL, or whether a request to remove the PTFs
| *NO: The mutually dependent and dependent PTFs are
during the next unattended IPL is canceled.
| not processed with the SELECT parameter list. No
IPLRMV | PTFs are removed if any PTF specified in the list has
Specifies the action that is done for delayed or imme- | dependent PTFs not also in the list or already applied.
diate PTFs at the next unattended IPL. This parameter | Messages identify the missing dependent PTFs and the
is valid only if DELAYED(*YES) is also specified. | specified PTFs on which they depend.
*YES: The identified PTFs are removed at the next | *YES: The PTFs are removed with the SELECT param-
unattended IPL. The RMV parameter determines | eter list.
whether the remove is temporary or permanent.
*NO: Any previous request to remove the identified Examples
PTFs at the next unattended IPL is canceled.
Example 1: Temporarily Removing PTFs
RLS
RMVPTF LICPGM(5769SS1) DELAYED(\YES)
Specifies the release level of the PTFs being removed.
*ONLY: This value This command temporarily removes all temporarily applied
PTFs from the Operating System/400 product (program iden-
is valid when only one release of the product's base tifier 5769-SS1). At the next IPL the PTFs can be applied
option is installed on the system. PTFs for all installed again, if necessary, through the APYPTF command.
options of the product are removed regardless of the
release-level of the option. Example 2: Permanently Removing PTFs
RMVPTF LICPGM(5769RG1) SELECT(SF1ðððð2 SF1ðððð5)
release-level: Specify the release level in VxRyMz
RMV(\PERM)
format, where Vx is the version number, Ry is the
release number, and Mz is the modification level. The This command permanently removes two PTFs (numbers
variables x and y can be a number from 0 through 9, SF10002 and SF10005) from the ILE RPG/400 product
and the variable z can be a number from 0 through 9 or (5769-RG1). The two PTFs are moved to QRPLOBJ and
a letter from A through Z. must be loaded again using the LODPTF command before
If the release-level specified is the release-level of the they can be applied.
base option of the product, PTFs for all installed options
of the product are removed regardless of the release- | Example 3: Removing PTFs and their mutual depen-
level of the option. | dents
| RMVPTF LICPGM(5769SS1) SELECT(SFðððð3 SFðððð8 SFððð12)
If the release-level specified is not the release-level of
| DELAYED(\YES) RMVDEP(\YES)
the base option of the product, only PTFs for the options
installed at that release-level are removed. | This command temporarily removes PTFs SF00003,
| RMVDEP | SF00008, SF00012, their mutual dependents and their
| Specifies whether mutually dependent PTFs and | dependents within the same product and option from the
| dependent PTFs in the same product and option as the | Operating System/400 product in library QSYS at the next
| IPL.
(P) ─────────────────────────────────────────────────────────────5%
55──RMVRDBDIRE──RDB(──┬─\ALLRMT───────────────────────────┬──)────
├─\ALL──────────────────────────────┤
├─generic\-relational-database-name─┤
└─relational-database-name──────────┘
Note:
P All parameters preceding this point can be specified in positional form.
(P) ────────────────────────────────────────────────────────────────────────────5%
55──RMVREXBUF──┬───────────────────────────────┬───
│ ┌─\CURRENT──────┐ │
└─BUFFER(──┼─\ALL──────────┼──)─┘
├─variable-name─┤
└─buffer-number─┘
Note:
P All parameters preceding this point can be specified in positional form.
(P) ───────────────────────────────────────────────────────────────────5%
55──RMVRMTDFN──SYSTEM(──┬─\ANY──────────────────────┬──)────
├─\ALL──────────────────────┤
└─system-name──system-group─┘
Note:
P All parameters preceding this point can be specified positionally.
*ALL: Removes the definitions for all remote systems. This command removes all remote system definitions. All
Element 1: System Name systems now use the default values.
(P) ──────────────────────────────────────────────────────────────────────────────5%
55──RMVRPYLE──SEQNBR(──┬─\ALL────────────┬──)────
└─sequence-number─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose SEQNBR
Specifies the sequence number of the reply list entry
The Remove Reply List Entry (RMVRPYLE) command being removed from the system reply list.
removes an entry from the system reply list. The reply list is
*ALL: Specifies that all reply list entries are removed
used as a source for automatic responses to predefined
from the system reply list. Whenever *ALL has been
inquiry messages.
specified, and the reply list object had previously been
The reply list is only used when an inquiry message is sent marked as damaged, the reply list is deleted and recre-
by a job that has the inquiry message reply attribute of the ated. No reply list entries will be present after re-
system reply list specified (INQMSGRPY(*SYSRPLY) is creation. They must be reentered or a reinstall
specified). INQMSGRPY(*SYSRPLY) can be changed with operation must be done.
the CHGJOB command. Note: Specifying the sequence number 0 has the same
behavior as specifying the special value *ALL.
New entries may be added to the reply list with the Add
Reply List Entry (ADDRPYLE) command; entries can be sequence-number: Specify the sequence number of the
changed with the Change Reply List Entry (CHGRPYLE) file. Valid values range from 1 through 9999.
command. The entire list of entries can be shown with the
Work with System Reply List Entries (WRKRPYLE) display. Examples
From the display that is presented the user can add, change,
and remove individual entries. Example 1: Removing All Entries
RMVRPYLE SEQNBR(\ALL)
Restriction: This command is shipped with public
*EXCLUDE authority and the QPGMR user profile has This command removes all entries from the system reply list.
private authority to use the command.
Note: To see the parameter and value descriptions for this Example 2: Removing One Entry
command, refer to the online help text. For more RMVRPYLE SEQNBR(ððð1)
information about printing the help text, refer to
“Printing CL Command Descriptions” in Chapter 1. This command removes from the system reply list the entry
that has sequence number 0001.
Required Parameters
┌─\LIBL/────────┐
(P) ─SEQNBR(──sequence-number──)───────────────────────────5%
55──RMVRTGE──SBSD(──┼───────────────┼──subsystem-description-name──)────
├─\CURLIB/──────┤
└─library-name/─┘
Note:
P All parameters preceding this point can be specified in positional form.
┌─\LIBL/────────┐
(P) ─────────────────────────────5%
55──RMVSCHIDXE──SCHIDX(──┼───────────────┼──search-index-name──)──PNLGRP(──panel-group-name──)────
├─\CURLIB/──────┤
└─library-name/─┘
Note:
P All parameters preceding this point can be specified in positional form.
(P, K) ──────────────────────────5%
55──RMVSNILOC──RMTLOCNAME(──remote-location-name──)──RMTNETID(──┬─\NETATR───────────────────┬──)─────
└─remote-network-identifier─┘
Notes:
P All parameters preceding this point can be specified in positional form.
┌──
──────────────────────────────────────────┐
55──RMVSOCE─── 6─(──┬─\NETATR────┬──control-point-name──)─┴───
(P)─ENTRY(─── (1) ──)──────────────────────────────────────────────────────5%
└─network-ID─┘
Notes:
P All parameters preceding this point can be specified in positional form.
1 A maximum of 50 repetitions
ENTRY
Specifies the systems to remove from the alert sphere of Example
control. The systems are specified as a list of two ele- RMVSOCE ENTRY((\NETATR RCHSTR1) (\NETATR RCHSTR2))
ments which include the network ID and control point
name. This command removes two systems (RCHSTR1 and
RCHSTR2) from the alert sphere of control.
(P) ──────────────────────────────5%
55──RMVSRVTBLE──SERVICE(──service-name──)──PORT(──port-number──)──PROTOCOL(──protocol-name──)────
Note:
P All parameters preceding this point can be specified in positional form.
Purpose SERVICE
Specifies the name of the service entry to be removed.
The Remove Service Table Entry (RMVSRVTBLE) command
is used to remove a service entry from the service table. PORT
The service table is used to manage the mapping of network Specifies the port number assigned to the service to be
services to ports. You must know the service entry name, removed.
the port, and the protocol to remove the entry. PROTOCOL
Specifies the name of the protocol used by the service
Restriction: You must have system configuration
to be removed.
(*IOSYSCFG) special authority to use this command.
Note: To see the parameter and value descriptions for this
command, refer to the online help text. For more Example
information about printing the help text, refer to RMVSRVTBLE SERVICE(FTP) PORT(21) PROTOCOL(TCP)
“Printing CL Command Descriptions” in Chapter 1.
This command removes an FTP service entry from the
network service table. The service being removed is
Required Parameters assigned to port 21 and runs the TCP protocol.
| Required Parameters | This command removes the server authentication entry for
| MyDSOMServer from the current user profile.
| USRPRF
| Specifies the user profile for which the server
| authentication entry will be removed.
(P) ─┬─CTG(──┬─\ALL──────────────────────────┬──)──────┬─────────────────────────────5
55──RMVTAPCTG──DEV(──library-device-name──)────
│ ├─generic\-cartridge-identifier─┤ │
│ │ ┌──
──────────────────────┐ │ │
│ 6 (1) ───┘
└───cartridge-identifier─┴─── │
│ ┌─\CURRENT────┐ │
└─CGY(──┬─┬─\NOSHARE──────┬──┼─────────────┼─┬──)─┘
│ ├─\IPL──────────┤ └─system-name─┘ │
│ ├─\NL───────────┤ │
│ ├─\CNV──────────┤ │
│ └─category-name─┘ │
├─\SHARE4ðð──────────────────────────┤
└─\INSERT────────────────────────────┘
5──┬──────────────────────────┬────────────────────────────────────────────────────────────────────────────────────────────────5%
│ ┌─\DEV─────┐ │
└─STATION──┼─\CNV─────┼──)─┘
└─\HIGHCAP─┘
Notes:
1 A maximum of 40 repetitions.
This element identifies the system to which the category library does not have a convenience I/O station, the car-
belongs. The system name is obtained from the tridges are placed in either the high capacity output
pending system name field of a Display Network Attri- station or a storage slot within the library.
butes (DSPNETA) command. If there is no pending
*CNV: The tape cartridge is ejected into the conven-
system name, the current system attribute is used.
ience I/O station. The convenience I/O station allows
Attention: entry and removal of the tape cartridges from the library
without opening the library door.
If the system name is changed, the categories associ-
ated with all tape cartridges in library devices owned by *HIGHCAP: The tape cartridges either are ejected into
the system are no longer valid. the high capacity output station or are returned to a
storage slot in the library device. Both of these out-
*CURRENT: The category belongs to the system cur-
comes require that the library door be opened to phys-
rently running the command.
ically remove the tape cartridges from the library.
system-name: Specify the name of the system to which
the category belongs.
Examples
Single Values:
*SHARE400: The cartridge identifiers assigned to the Example 1: Removing a Single Cartridge to the *EJECT
*SHARE400 category are removed. The cartridge identi- Category
fiers in this category can be shared with other systems RMVTAPCTG DEV(LIBð1) CTG(VOL4)
attached to the same device. STATION(\HIGHCAP)
*INSERT: The cartridge identifiers assigned to the
This command removes the cartridge identifier VOL4 from its
*INSERT category are removed. The cartridge identi-
current category and places it in the *EJECT category. The
fiers in this category are for cartridges that have been
cartridge is placed in a storage slot or the high capacity
placed in the library device, but whose identifier has not
output station.
been added to the system.
Example 2: Removing All Cartridges from the *IPL Cate-
Optional Parameter gory
RMVTAPCTG DEV(LIBð1) CGY(\IPL)
STATION STATION(\CNV)
Specifies the station to receive the cartridges being
ejected. This command removes all cartridge identifiers in the *IPL
*DEV: If the tape library has a convenience input/output category and places them in the *EJECT category. The car-
(I/O) station, the cartridges are placed in it. If the tape tridges are placed in the convenience I/O station.
(P) ─────────────────────────────────────────────────────────────────────────────5%
55──RMVTCPHTE──INTNETADR(──internet-address──)────
Note:
P All parameters preceding this point can be specified in positional form.
(P) ─────────────────────────────────────────────────────────────────────────────5%
55──RMVTCPIFC──INTNETADR(──internet-address──)────
Note:
P All parameters preceding this point can be specified in positional form.
┌─\ONLY───────┐
(P) ──────────5%
55──RMVTCPPORT──PORT(──┬─lower-value─┬──┴─upper-value─┴──)──PROTOCOL(──┬─\UDP─┬──)──USRPRF(──user-profile-name──)────
└─\ALL────────┘ └─\TCP─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose PROTOCOL
Specifies the transport protocol associated with the port
The Remove TCP/IP Port Restriction (RMVTCPPORT) or range of ports having the user profile removed from
command removes a particular user profile from the list of the list of user profiles that have exclusive use of a port
user profiles that are allowed to use a port or range of ports. or range of ports.
The removal of the user profile takes effect as soon as that
*UDP: The port is a User Datagram Protocol (UDP)
user profile being removed is no longer using the port or any
transport protocol port.
of the ports within the range of ports.
*TCP: The port is a Transmission Control Protocol
There are two independent sets of ports. One set is for TCP (TCP) transport protocol port.
processing and the other is for UDP processing. They are
completely independent sets of ports and have no relation- USRPRF
ship to one another. Specifies the name of the user profile whose profile is to
be removed from the list of user profiles that have exclu-
Restriction: sive use of the port or range of ports.
user-profile-name: Specify the user profile that is to be
You must have *IOSYSCFG special authority to use this
removed.
command.
Note: To see the parameter and value descriptions for this
command, refer to the online help text. For more Example
information about printing the help text, refer to Example 1: Removing Restriction on a Single User
“Printing CL Command Descriptions” in Chapter 1. Profile
RMVTCPPORT PORT(159ð) PROTOCOL(\UDP)
Required Parameters USRPRF(USER1)
PORT This command removes the restriction for the user profile
Specifies the port number or range of port numbers that named USER1 for UDP port 1590. This user profile is
are having the user profile removed from the list of user removed from the list of user profiles that are allowed to use
profiles that are allowed to use that port or range of port number 1590.
ports. Valid values range from 1 through 65535.
However, ports 1 through 1023 are reserved for use by Example 2: Removing Restriction on a Range of Ports
system-supplied TCP/IP applications. If the user speci- RMVTCPPORT PORT(159ð 2ððð) PROTOCOL(\TCP)
fies ports 1 through 1023, it can affect the operation of USRPRF(USER2)
those applications.
Element 1: Lower Port Value This command removes the restriction for the user profile
named USER2 for TCP ports 1590 through port 2000. This
lower-value: Specify the port value or the lower port user profile is removed from the list of user profiles that are
value (in a range) from which you want the user profile allowed to use ports 1590 though 2000.
removed.
*ALL: The port range values that are removed are Example 3: Removing All Ports
1-65535. RMVTCPPORT PORT(\ALL) PROTOCOL(\TCP)
USRPRF(USER3)
Element 2: Upper Port Value
*ONLY: The port value specified in the lower port value This command removes the restriction for the user profile
is the only port value that has the user profile removed. named USER3 for TCP port 1 through port 65535. The
command will complete successfully even if the user did not
upper-value: Specify the upper port value (in a range)
have a port within this range restricted. This user profile is
from which you want the user profile removed.
removed from the list of user profiles that are allowed to use
any of the TCP ports.
(P) ─────────────────────────────────────────────────────────────────────────────5%
55──RMVTCPRSI──INTNETADR(──internet-address──)────
Note:
P All parameters preceding this point can be specified in positional form.
(P) ──────────────5
55──RMVTCPRTE──RTEDEST(──┬─\DFTROUTE─────────┬──)──SUBNETMASK(──┬─\NONE───────┬──)──┬─────────────────────────┬───
| ├─\DFTMCAST─────────┤ ├─\HOST───────┤ │ ┌─\NORMAL────┐ │
└─route-destination─┘ └─subnet-mask─┘ └─TOS(──┼─\MINDELAY──┼──)─┘
├─\MAXTHRPUT─┤
├─\MAXRLB────┤
└─\MINCOST───┘
5──NEXTHOP(──internet-address──)───────────────────────────────────────────────────────────────────────────────────────────────5%
Note:
P All parameters preceding this point can be specified in positional form.
| 55──RMVTCPTBL──TBL(──┬─\ALL───┬──)─────────────────────────────────────────────────────────────────────────────────────────────5%
| ├─\IPFTR─┤
| └─\IPNAT─┘
| Purpose | *IPFTR: Remove the IP Filter rule table from use. The
| IP Filter feature will no longer be operative.
| The Remove TCP/IP Table (RMVTCPTBL) command is used
| *IPNAT: Remove the IP Network Address Translation
| to remove from use previously loaded IP Filter table or an IP
| table from use. The IP Network Address Translation
| Network Address Translation table. The appropriate table
| feature will no longer be operative.
| type(s) are removed from all TCP/IP interfaces, regardless of
| the status (active or inactive) of the interface. Note that, for
| active interfaces, this may disrupt existing sessions. TCP/IP | Examples
| interfaces that currently have no associated table of the | Example 1: Remove All Tables
| requested type(s) are unaffected by this command.
| RMVTCPTBL TBL(\ALL)
| Required Parameter | This command removes both the IP Filter and IP Network
| Address Translation rule tables from use.
| TBL
| Specifies the rule table that is to be removed from use. | Example 2: Remove the IP Filter Table
| *ALL: Both the IP Filter and the IP Network Address | RMVTCPTBL TBL(\IPFTR)
| Translation rule tables will be removed from use. Both
| features will no longer be operative. | This command removes only the IP Filter rule table from use.
55──RMVTRC──┬────────────────────────────────────────────────────────────────────────────────────────┬──────────────────────────5
│ ┌─\ALL───────────────────────────────────────────────────────────────────┐ │
│ │ ┌──
─────────────────────────────────────────────────────────────────┐ │ │
└─STMT(─── 6
(1) ─┴───(──start-statement-identifier──┬───────────────────────────┬──)─┴───
(2) ─┴──)─┘
└─stop-statement-identifier─┘
(P) ────────────────────────────────────────────────────────────────────────────────────────────5%
5──┬───────────────────────────┬───
│ ┌─\DFTPGM──────┐ │
└─PGM(──┼─\ALL─────────┼──)─┘
└─program-name─┘
Notes:
1 STMT cannot be specified if PGM(*ALL) is specified.
2 A maximum of 5 repetitions
┌─\NONE────────────────┐ ┌─\NONE─────────────────────┐
55──RMVUSFCNNE──MMDEV(──device-name──┼──────────────────────┼──┼───────────────────────────┼──)─────────────────────────────────5
└─remote-location-name─┘ └─remote-network-identifier─┘
(P) ───────────────────────────────────────────────────────────────────────────────5%
5──DEVCNN(──device-connector──┬─\INPUT──┬──)────
└─\OUTPUT─┘
Note:
P All parameters preceding this point can be specified in positional form.
┌─\NONE────────────────┐ ┌─\NONE─────────────────────┐
(P) ────────────────────────────5%
55──RMVUSFDEVE──MMDEV(──device-name──┴─remote-location-name─┴──┴─remote-network-identifier─┴──)────
Note:
P All parameters preceding this point can be specified in positional form.
(P) ────────────────────────────────────────────────────────────────────────────────────5%
55──RMVUSFSVRE──SERVER(──server-name──)────
Note:
P All parameters preceding this point can be specified in positional form.
┌─\LIBL/────────┐
(P) ─┬─WRKSTN(──┬─work-station-name──────────┬──)─┬─────────5%
55──RMVWSE──SBSD(──┼───────────────┼──subsystem-description-name──)────
├─\CURLIB/──────┤ │ └─generic\-work-station-name─┘ │
└─library-name/─┘ └─WRKSTNTYPE(──┬─\ALL──────────────┬──)──────┘
├─\NONASCII─────────┤
├─\ASCII────────────┤
├─\CONS─────────────┤
└─work-station-type─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose WRKSTN
Specifies the device description name of the work station
The Remove Work Station Entry (RMVWSE) command is for which the job entry is being removed.
used, when the system is being set up, to remove a specified
work-station-name: Specify the name of the work station
work station or type of work station from a specified sub-
whose work station entry is removed.
system description.
generic*-work-station-name: Specify the generic name
Restrictions: of the work station. A generic name is a character string
1. The user, typically a system operator or system adminis- of one or more characters followed by an asterisk (*); for
trator, must have operational or object management example, ABC*. The asterisk substitutes for any valid
authority to change the subsystem description. characters. A generic name specifies all objects with
names that begin with the generic prefix for which the
2. Work station entries in the subsystem description of an user has authority. If an asterisk is not included with the
active subsystem may not be removed if there are active generic (prefix) name, the system assumes it to be the
workstations within that subsystem. complete object name. If the complete object name is
3. A *CON or CONS entry may not be removed from the specified, and multiple libraries are searched, multiple
controlling subsystem. objects can be removed only if *ALL or *ALLUSR library
values can be specified for the name. For more infor-
Note: To see the parameter and value descriptions for this
mation on the use of generic names, refer to “Generic
command, refer to the online help text. For more
Object Names” in Chapter 2.
information about printing the help text, refer to
“Printing CL Command Descriptions” in Chapter 1. The WRKSTN parameter and the WRKSTNTYPE
parameter are mutually exclusive. When a generic
name is specified, only the generic name entry is
Required Parameters removed. For more information on the use of generic
SBSD functions, see “Rules for Specifying Names.”
Specifies the qualified name of the subsystem WRKSTNTYPE
description containing the work station job entry that is Specifies the work station device type for which the job
being removed. entry is being removed. The following type codes are
The name of the subsystem description can be qualified valid:
by one of the following library values:
Type Code Device
*LIBL: All libraries in the job's library list are 3179 3179 Display station
searched until the first match is found. 3180 3180 Display Station
3196 3196 Display Station
*CURLIB: The current library for the job is
3197 3197 Display Station
searched. If no library is specified as the current
3277 3277 Display Station
library for the job, the QGPL library is used.
3278 3278 Display Station
library-name: Specify the name of the library to be 3279 3279 Display Station
searched. 3476 3476 Display Station
3477 3477 Display Station
subsystem-description-name: Specify the name of the
3486 3486 Display Station
subsystem description containing the work station entry
3487 3487 Display Station
that is being removed.
5251 5251 Display Station
5291 5291 Display Station
5292 5292 Color Display Station work-station-type: Specify the work station device type
5555 5555 Display Station (on systems sup- whose work station entry is being removed.
porting DBCS (double-byte character set))
The WRKSTN parameter and the WRKSTNTYPE
*ALL: The work station entry for all valid work station parameter are mutually exclusive.
types is removed.
*NONASCII: The work station entry for all valid work Example
stations that use 5250 data stream is removed. RMVWSE SBSD(LIB2/CHARLES) WRKSTN(B53)
*ASCII: The work station entries for all work stations
that use ASCII data streams are added. This command removes the work station entry for work
station B53 from the subsystem description named
*CONS: This value overrides a device type entry that CHARLES in library LIB2.
specifies the same device type as the device being used
as the console.
(P) ──────────────────────────────────────────────────────────5%
55──RNM──OBJ(──'object-path-name'──)──NEWOBJ(──new-object-name──)────
Note:
P All parameters preceding this point can be specified in positional form.
(P) ─────────────────────────────5%
55──RNMCNNLE──CNNL(────connection-list────)──ENTRY(────entry────)──NEWENTRY(────new-entry────)────
Note:
P All parameters preceding this point can be specified in positional form.
Purpose ENTRY
Specifies the name of the entry to be renamed.
The Rename Connection List Entry (RNMCNNLE) command
renames an entry in the specified connection list. NEWENTRY
Specifies the new name for the entry. Each entry in the
Note: To see the parameter and value descriptions for this connection list must have a unique name.
command, refer to the online help text. For more
information about printing the help text, refer to
“Printing CL Command Descriptions” in Chapter 1. Example
RNMCNNLE CNNL(CHICAGO)
ENTRY(CORPORATE)
Required Parameters NEWENTRY(SERVICE)
CNNL
This command renames entry CORPORATE in the con-
Specifies the name of the connection list.
nection list named CHICAGO. The new name will be
SERVICE, but all other information for the entry remains the
same.
55──RNMDIRE──OLDUSRID(──user-ID──address──)──NEWUSRID(──┬─\BACKOUT─────────┬──)──┬──────────────────────────────────┬───────────5
└─user-ID──address─┘ │ ┌─\NONE────────────┐ │
└─FWDFRM(──┼─\OLDUSRID────────┼──)─┘
└─user-ID──address─┘
5──┬─────────────────────────────┬─────────────────────────────────────────────────────────────────────────────────────────────5%
│ ┌─\SAME─────┐ │
└─NETUSRID(──┴─\NEWUSRID─┴──)─┘
55──RNMDKT──DEV(──device-name──)──┬────────────────────────────────┬──┬───────────────────────────────────┬─────────────────────5
│ ┌─\MOUNTED──────────┐ │ │ ┌─\SAME─────────────┐ │
└─VOL(──┴─volume-identifier─┴──)─┘ └─NEWVOL(──┴─volume-identifier─┴──)─┘
(P) ───────────────────────────────────────────────────────────────────────────────────5%
5──┬────────────────────────────────────┬───
│ ┌─\SAME────────────┐ │
└─NEWOWNID(──┴─owner-identifier─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
(P) ───5%
55──RNMDLO──DLO(──document-library-object-name──)──NEWDLO(──document-library-object-name──)──┬──────────────────────────┬───
│ ┌─\NONE───────┐ │
└─FLR(──┴─folder-name─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose DLO
Specifies the name of the document or folder that is
The Rename Document Library Object (RNMDLO) command being renamed.
changes the name of a document or folder. If the document
or folder being renamed is in use when the command is NEWDLO
used, the command is not run and a message is sent to the Specifies the new name of the document or folder.
user who entered the command.
Optional Parameters
Restriction: The user must have *ALL authority to the docu-
ment or folder being renamed, and must have *CHANGE FLR
authority to the folder that contains it. While using this Specifies the name of the folder that contains the docu-
command, the user may encounter an error message indi- ment.
cating that internal objects are locked. This means that
*NONE: The folder being renamed is not located in a
another user is using the document library functions which
folder. *NONE cannot be specified if the object being
cannot run at the same time as the RNMDLO command;
renamed is a document.
therefore, retry this command later.
folder-name: Specify the name of the folder that con-
Note: To see the parameter and value descriptions for this
tains the document or folder that is being renamed.
command, refer to the online help text. For more
information about printing the help text, refer to
“Printing CL Command Descriptions” in Chapter 1. Example
RNMDLO DLO(A) NEWDLO(B) FLR(FLR1)
Required Parameters This command changes the name of document or folder A
located in folder FLR1, to B.
(P) ───────────────────────────────5%
55──RNMDSTL──LSTID(──list-ID──list-ID-qualifier──)──NEWLSTID(──list-ID──list-ID-qualifier──)────
Note:
P All parameters preceding this point can be specified in positional form.
Purpose Note: The distribution list identifier has two parts, the
ID and the qualifier, separated by at least one
The Rename Distribution List (RNMDSTL) command space. If lowercase characters are specified, the
renames the list identifier (ID) of an existing distribution list. system changes them to uppercase.
A distribution list is a list of entries from the distribution The naming rules for the two-part list ID are iden-
directory. The distribution list can include entries for local, tical to the rules for the user ID and address. A
remote, indirect, and independent work station users. It also complete description of these rules is in the SNA
can include remote distribution lists, but it cannot include Distribution Services book.
local distribution lists. More information about distribution NEWLSTID
lists is in the SNA Distribution Services book. Specifies the new two-part list identifier of the distribution
list.
When renaming the distribution list, the new list ID must be
unique to all local user IDs and other list IDs in the directory. Element 1: List Identifier
If a new list ID is not unique, the list is not renamed and an list-ID: Specify the list identifier (ID) of the distribution
error message is returned. list.
Restriction: You must have security administrator Element 2: List Qualifier
(*SECADM) authority to rename a distribution list that you do list-ID-qualifier: Specify the list ID qualifier of the distri-
not own. No special authority is needed for you to rename a bution list.
distribution list that you own.
Note: The distribution list identifier has two parts, the
Note: To see the parameter and value descriptions for this ID and the qualifier, separated by at least one
command, refer to the online help text. For more space. If lowercase characters are specified, the
information about printing the help text, refer to system changes them to uppercase.
“Printing CL Command Descriptions” in Chapter 1.
The naming rules for the two-part list ID are iden-
tical to the rules for the user ID and address. A
Required Parameters complete description of these rules is in the SNA
Distribution Services book.
LSTID
Specifies the two-part list identifier of the distribution list
to be renamed.
Example
Element 1: List Identifier
RNMDSTL LSTID(DEPTABC DLIST) NEWLSTID(DEPTXYZ DLIST)
list-ID: Specify the list identifier (ID) of the distribution
list. This command renames a distribution list that contains the
members of Department ABC. The list ID is being changed
Element 2: List Qualifier
to correspond to a new department name, XYZ. If the new
list-ID-qualifier: Specify the list ID qualifier of the distri- list ID is unique, the distribution list is changed.
bution list.
(P) ──────────────────────────────────────────────────────5%
55──RNMLANADPI──ADPTNAME(──adapter-name──)──NEWNAME(──adapter-name──)────
Note:
P All parameters preceding this point can be specified in positional form.
Purpose ADPTNAME
Specifies the name that is currently associated with the
The Rename Local Area Network Adapter Information adapter.
(RNMLANADPI) command is used to change the name asso-
ciated with the LAN adapter information in the adapter file. NEWNAME
Specifies the new name associated with the adapter
Restriction: Adapter names must be unique. information.
Note: To see the parameter and value descriptions for this
command, refer to the online help text. For more Example
information about printing the help text, refer to RNMLANADPI ADPTNAME(ACCTG3A) NEWNAME(BILLING2)
“Printing CL Command Descriptions” in Chapter 1.
This command changes the name from ACCTG3A to
BILLING2.
Required Parameters
┌─\LIBL/────────┐
(P) ───────────────5%
55──RNMM──FILE(──┼───────────────┼──database-file-name──)──MBR(──member-name──)──NEWMBR(──new-member-name──)────
├─\CURLIB/──────┤
└─library-name/─┘
Note:
P All parameters preceding this point can be specified in positional form.
The name of the file can be qualified by one of the fol- This command renames member LEAD in file ELEMENT as
lowing library values: GOLD. The library list (*LIBL) is used to find the file.
*LIBL: All libraries in the job's library list are
searched until the first match is found.
┌─\PRIVATE─┐
(P) ──────────────────────────────────────────────────────────5%
55──RNMNCK──NCK(──nickname──┴─\PUBLIC──┴──)──NEWNCK(──nickname──)────
Note:
P All parameters preceding this point can be specified in positional form.
┌─\LIBL/────────┐
(1) ─object-type──)──NEWOBJ(──new-object-name──)────────────────────5
55──RNMOBJ──OBJ(──┼───────────────┼──object-name──)──OBJTYPE(───
├─\CURLIB/──────┤
└─library-name/─┘
(P) ────────────────────────────────────────────────────────────────────────────────────────────5%
5──┬───────────────────────────┬───
│ ┌─\LCL──────┐ │
└─SYSTEM(──┼─\RMT──────┼──)─┘
└─\FILETYPE─┘
Notes:
1 A list of the valid OS/400 object types for this command is in Appendix A.
Purpose Notes:
1. References made to the following items may need to be
The Rename Object (RNMOBJ) command changes the
updated by the user after a rename of a configuration
name of an object in a library. The new name specified for
object:
the object must be unique in the library for the object type. If
the object being renamed is in use when the command is Connection lists
entered, the command is not run and a message is sent to Work station entries
the user who enters the command. If a library is on an Communication entries
active user's library list when the library is renamed, a Display files
Display Library List (DSPLIBL) command reflects the new Printer files
name. Renaming a library can cause programming errors. Tape files
Therefore, it is not recommended. Diskette files
ICF files
Restrictions: User profiles
The user must have object management authority for the Job descriptions
object that is being renamed and have both update System objects
authority and execute authority for the library in which CL programs
the object is located. QPRTDEV system value
Display descriptions referencing this as an auxiliary
A PL/I program cannot be renamed after it has been printer
created. Communication side information (CSI) objects
Configuration objects including controller descriptions, Distributed data management files (APPC device
line descriptions, device descriptions, and network inter- name)
face descriptions must all be varied off in order to Integrated services digital network (ISDN) controller
rename them. descriptions that refer to a renamed connection list
(CNNL)
The following objects cannot be renamed:
ISDN line descriptions that refer to a renamed
– The job's temporary library (QTEMP) CNNL
– The system library (QSYS) Other configuration objects. For example, lines,
– The system operator message queue (QSYSOPR) controllers, and other devices that refer to the
– All work station user message queues renamed configuration objects.
– The system log (QHST)
2. References made to the renamed object by the following
– The configuration objects (QCTL and QCONSOLE)
items are automatically changed by the system after a
– The configuration lists (QAPPNRMT, QAPPNLCL,
rename operation. The reference changes reflect the
QASYNCLOC, QRTLPASTHR)
changes made to the renamed configuration objects.
– The Electronic Customer Support configuration
objects (QESLIN, QESPAP, QESCTL. QTILINE, QCONSOLE system values
QTICTL, QTIDA, QTIDA2, QIADSP, QIAPRT, message queues associated with display devices
QQAHOST) System/36 environment device tables
output queues associated with the old printer device
When renaming objects of type *CSI, *GSS, *FNTRSC,
local work station controllers associated with a
*FORMDF, *OVL, *PAGDFN, and *PAGSEG, the new
twinaxial data link control (TDLC) line
name for the object cannot exceed 8 characters in
length.
OBJTYPE Example
Specifies the type of the object to be renamed. More RNMOBJ OBJ(PAYROLL/FILEX) OBJTYPE(\FILE)
information on this parameter is in Appendix A, NEWOBJ(MSTR)
“Expanded Parameter Descriptions.”
The library named PAYROLL is searched for the file named
Note: Dependent logical files follow the renamed phys-
FILEX. If the file is found, and the user has object opera-
ical file.
tional authority for FILEX and update authority for the
PAYROLL library, FILEX is renamed MSTR.
(P) ───────────────────────────────────────5%
55──RNMTCPHTE──INTNETADR(──internet-address──)──NEWINTNETA(──new-internet-address──)────
Note:
P All parameters preceding this point can be specified in positional form.
Note: To see the parameter and value descriptions for this This command replaces the host table entry internet address
command, refer to the online help text. For more of 132.28.71.5 with the internet address of 142.48.81.6. All
host names and the text description field associated with the
entry remain the same.
55──ROLLBACK───────────────────────────────────────────────────────────────────────────────────────────────────────────────────5%
Purpose All record locks held for files opened under commitment
control for the commitment definition are released.
The Rollback (ROLLBACK) command is used to restart the
Locks on object level commitment control resources,
current transaction and reestablish the last commitment
acquired when the resources were created or changed
boundary as the current commitment boundary for the com-
during the transaction, are released.
mitment definition associated with the program issuing the
command. More information on the use of commitment control is in the
Backup and Recovery book.
When the ROLLBACK command is issued:
Changes made to database files and other commitment There are no parameters for this command.
resources under commitment control for the commitment
definition since the last commitment boundary was
Example
established are rolled back. Updates, additions, or
deletions made to the database file's data since that ROLLBACK
commitment boundary are rolled back or removed, and
This command reestablishes the last commitment boundary
the original entries are put back in the files. Records
(the point at which a Commit (COMMIT) command or
that were added to the files remain as deleted records.
Rollback (ROLLBACK) command was last issued) for the
The files are repositioned to the last commitment
commitment definition associated with the program issuing
boundary. Changes made to other commitment
the command.
resources are rolled back as well.
| However, the STRNFSSVR command has the following | If registration information is retrieved, servers do not
| restrictions: | have to re-register with the RPC server.
| RPCGEN Command
| For the description of the RPCGEN command, see the CVTRPCSRC (Convert RPC Source) command description.
┌─\LIBL/────────┐
(P) ────────────────────────────────5
55──RPLDOC──TODOC(──┬─\DOCID────────┬──)──DOCFILE(──┼───────────────┼──database-file-name──)────
└─document-name─┘ ├─\CURLIB/──────┤
└─library-name/─┘
5──┬────────────────────────────┬──┬─────────────────────────────────────────────────┬──┬─────────────────────────────┬─────────5
│ (1, 2) ──┐
┌─\NONE───── │ │ ┌─\NONE────────────────────────────┐ │ │ ┌─\FIRST──────┐ │
└─TOFLR(──┴─folder-name─┴──)─┘ └─DOCID(──┴─'library-assigned-document-name'─┴──)─┘ └─DOCMBR(──┴─member-name─┴──)─┘
5──┬────────────────────────┬──┬─────────────────────────────────────────┬──┬──────────────────────────────────────┬────────────5
│ ┌─\DOC──┐ │ │ ┌─\DFT─────────────────┐ │ │ ┌─\CURRENT──────────────┐ │
(3) ─┼─\FFT─────────────────┼──)─┘ └─USRID(──┴─user-ID──user-address─┴──)─┘
└─DOCPART(──┼─\IDP──┼──)─┘ └─DOCTYPE(───
└─\BOTH─┘ ├─\RFT─────────────────┤
└─document-type-number─┘
5──┬────────────────────────────────────────────────────┬──┬────────────────────────────────────────────────────┬──────────────5%
│ ┌─\SYSVAL──────────────────────────┐ │ │ ┌─\SYSVAL──────────────────────────┐ │
└─DOCCHRID(──┼─\DEVD────────────────────────────┼──)─┘ └─CMDCHRID(──┼─\DEVD────────────────────────────┼──)─┘
└─graphic-character-set──code-page─┘ └─graphic-character-set──code-page─┘
Notes:
P All parameters preceding this point can be specified in positional form.
1 This value cannot be specified when a document name is specified on the TODOC parameter.
2 This value must be specified when a document is specified on the DOCID parameter.
Purpose DOCFILE
Specifies the qualified name of the database file that
The Replace Document (RPLDOC) command is used to contains the document data being filed. The database
replace the document content and the interchange document file can be user-defined or it can be the output file speci-
profile (IDP) of a document that exists in the document fied on the Receive Distribution (RCVDST) or Retrieve
library. Document (RTVDOC) command. Database files that are
used to replace document data are used as is with any
Restrictions: changes. If an output file is specified, only the docu-
1. The document must be checked out with the Retrieve ment data and IDP record format are read from the
Document (RTVDOC) command by the user specified on output file and the prefix is removed from the document
the USRID parameter before using this command. data. More information on defining the format of data-
2. The user must have at least *CHANGE authority for the base files is in the DB2 for AS/400 Database Program-
document, *ALLOBJ authority, or be working on behalf ming book.
of a user who is authorized for the document. The name of the database file can be qualified by one of
3. Authority to work on behalf of another user is granted the following library values:
with the Grant User Permission (GRTUSRPMN)
command. *LIBL: All libraries in the job's library list are
searched until the first match is found.
folder-name: Specify the name of the folder that con- *IPD: Replace only the IDP of the document. If this
tains the document being replaced. A folder name can value is specified, IDP records (record code 500) must
consist of a series of folder names if the document being exist in the specified file or the command fails.
replaced is located in a folder that is contained in
*BOTH: Replace both the document content and the
another folder. Up to 63 characters can be specified.
IDP of the document. If this value is specified, IDP
DOCID records (record code 500) must exist in the specified file
Specifies the library-assigned name of the document or the command fails.
being replaced. This is the name assigned to the docu-
DOCTYPE
ment by the system when it is created. The library-
Specifies the type of replacement document. This identi-
assigned document name can be determined by using
fier is used by the system to determine whether it can
the Query Document Library (QRYDOCLIB) command.
handle the data stream correctly.
The library-assigned name is also returned in a com-
pletion message when using the File Document The system code (SYSCOD on the File Document
(FILDOC) command. (FILDOC) command) cannot be changed when the docu-
ment contents are replaced.
Library-assigned document names are 24 characters in
length with the following format: *DFT: The system creates the appropriate document
YYYYMMDDHHMNSSHSSNSNSNSN where type identifier depending on where the data comes from.
If the document file is an output file created by the
YYYY = year
RCVDST or RTVDOC command, then the document
MM = month
type is taken from this file. If the file does not contain a
DD = day
document type or if the value in this file is document
HH = hour
type 0, then an error message is sent. If the document
MN = minute
file is a user-defined file, then the document type is 223
SS = second
(data file).
HS = hundredths of a second
SNSNSNSN = system name Document Description
Type
*NONE: No library-assigned document name is required
when the document is identified by the TODOC param-
2 Final form text document (FFTDCA)
eter.
3 5520 revisable form text document
'library-assigned-document-name': Specify the library- (RFT5520)
assigned document name to be replaced. More informa- 4 Word processing EBCDIC (EBCDIC)
tion on library-assigned document names is in the SNA 5 Word processing information file
Distribution Services book. (WRDPRCINFF)
Note: When the user is replacing a document and a 6 Image-data subset document (IMAGE)
cancel request is entered, the document may or 7 3730 text data stream (TEXT3730)
may not be replaced. 8 DIA document library descriptor document
(DOCDESCDOC)
DOCMBR 9 3732 display document data stream
Specifies the document database file member that con- (DATAST3732)
tains the data and IDP to replace the current data and 10 DIA display document data stream
IDP in the document. (DOCUNITCTL)
*FIRST: The first member (in order of creation) in the 11 Revisable form text document (RFTDCA)
database file contains the replacement data. 12 1403 compatible data stream with vari-
able length, unblocked records
member-name: Specify the name of the database file (PRT1403)
that contains the replacement data.
13 Digitized ADS audio (AUDIO)
DOCPART 14 IBM PC data file (PCFILE)
Specifies the part of the document to be replaced. 15 Hard copy of document (HARDCOPY)
223 Data file
Note: If you specify DOCPART(*BOTH) and the
32753 List of documents created from search
replacement of one fails, neither is replaced and
(DOCLIST)
the document remains checked out.
32756 Version 2 DIA document, library docu-
*DOC: Replace the document content only. If no docu- ment, descriptor document
ment content records exist in the specified file, the docu- 32768 AS/400 system revisable-form document
ment is replaced but a message is returned to alert the (RFTAS400)
user that no document content was replaced. 32769 AS/400 system final-form document
(FFTAS400)
32770 IBM DW4 revisable-form document tive CL program or a batch job, an error message is
(RFTDW4) sent.
32912 ASCII data (ASCIIDATA)
Element 1: Character Set
65262 IBM S/38 revisable document (RFTS38)
graphic-character-set: Specify the graphic character set
*FFT: The document is Final Form Text. This type of used to create the data being filed.
document is intended to be shown and printed and not
Element 2: Code Page
edited by the receiver.
*RFT: The document is Revisable Form Text. This type
code-page: Specify the code page value used to create
the command parameters. Valid values range from 1
of document can be shown, printed, and edited by the
through 999.
receiver.
document-type-number: Specify a number from 2 CMDCHRID
through 65535. The numbers from 2 through 32767 are Specifies the character identifier (graphic character set
controlled by registering them with the IBM Document and code page) for data being specified as parameter
Interchange Architecture and are used for IBM-defined values on this command. This character identifier
document types. The numbers 32768 through 65535 (CHRID) is related to the display device used to specify
are not registered with IBM and can be used for the command. More information about CHRID pro-
non-IBM defined document types. cessing is in the Application Display Programming book.
Note: This value translates the USRID parameter to the
USRID
character set and code page of '930 500'. The SNA Dis-
Specifies the user ID and address of the user for whom
this request is made. The current user of this command
tribution Services book contains the character set and
code page table for '930 500'.
must have the authority to work on behalf of the named
user ID. Authority to work on behalf of another user is *SYSVAL: The system determines the graphic char-
given with the Grant User Permission (GRTUSRPMN) acter set and code page values for the command param-
command. eters from the QCHRID system values.
*CURRENT: The user profile that is currently running is *DEVD: The system determines the graphic character
used. set and code page values for the command parameter
from the display device description where the command
Element 1: User ID
is entered. This option is valid only when specified from
user-ID: Specify the user ID of the user whose the doc- an interactive job. If this value is specified in an interac-
ument is replaced. tive CL program or a batch job, an error message is
Element 2: User Address sent.
user-address: Specify the user address of the user for Element 1: Character Set
whom the document is replaced. graphic-character-set: Specify the graphic character set
values used to create the command parameter. Valid
DOCCHRID
values range from 1 through 999.
Specifies the character identifier (graphic character set
and code page) for the data being filed. The character Element 2: Code Page
identifier is related to the display station that was used to
code-page: Specify the code page value used to create
create the data being filed. More information about
the command parameters. Valid values range from 1
CHRID processing is in the DB2 for AS/400 Database
through 999.
Programming book.
*SYSVAL: The system determines the graphic char-
acter set and code page values for the command param-
Example
eters from the QCHRID system values. RPLDOC TODOC(\DOCID) DOCFILE(\LIBL/MYFILE)
DOCPART(\BOTH) DOCID('1987ð6ð71ð1ð2ð53SYSTEM1')
*DEVD: The system determines the graphic character DOCTYPE(\FFT)
set and code page values for the command parameter
from the display device description where the command This command replaces the document data and IDP with
is entered. This option is valid only when specified from data in the file MYFILE. The data is placed in the document
an interactive job. If this value is specified in an interac- identified by the document identifier
'1987060710102053SYSTEM1'. The document type is
changed to Final Form Text.
55──RQSORDAST──────────────────────────────────────────────────────────────────────────────────────────────────────────────────5%
(P) ──────────────────────────────────────────5%
55──RRTJOB──┬────────────────────────────────┬──┬────────────────────────────────┬───
│ ┌─QCMDI──────────┐ │ │ ┌─\NONE──────────┐ │
└─RTGDTA(──┼─\RQSDTA────────┼──)─┘ └─RQSDTA(──┼─\RTGDTA────────┼──)─┘
└─'routing-data'─┘ └─'request-data'─┘
Note:
P All parameters preceding this point can be specified in positional form.
Restriction: The job must not be a group job. *RTGDTA: Routing data specified in the RTGDTA
parameter is also placed at the end of the job's message
Note: To see the parameter and value descriptions for this queue.
command, refer to the online help text. For more
information about printing the help text, refer to 'request-data': Specify the character string placed at the
“Printing CL Command Descriptions” in Chapter 1. end of the job's message queue for use by the new
routing step or some subsequent routing step in the job.
Up to 256 characters can be entered, enclosed in apos-
Optional Parameters trophes if necessary. When a CL command is entered,
it must be enclosed in single apostrophes, and where
RTGDTA
apostrophes would normally be used inside the
Specifies the routing data used with this job description
command, double apostrophes must be used.
to start jobs. The routing data is used to determine the
routing entry (in the subsystem description) that identi-
fies the program in which the job runs. Example
QCMDI: This routing data matches a routing entry in RRTJOB RTGDTA(INQUIRY)
the IBM-supplied subsystem description (QINTER),
which indicates a routing step that is processed by the This command reroutes the job in which the command is
issued by starting a new routing step with the routing data
INQUIRY. The job remains in the same subsystem.
55──RSMBKP─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────5%
(P) ────────────────────────────────────────────────────────────────────────────────────5%
55──RSMCTLRCY──CTL(──controller-name──)────
Note:
P All parameters preceding this point can be specified in positional form.
Purpose CTL
Specifies the controller whose recovery is started again.
The Resume Controller Recovery (RSMCTLRCY) command Valid types of controllers are:
resumes error recovery procedures for a specific controller.
The error recovery procedures can be ended by the End CTL Value Controller
Controller Recovery (ENDCTLRCY) command or by 5251 Display station
responding to a failure-related inquiry message with a cancel *PU2 Physical unit (type 2); SDLCs for basic BSC
option. and RJE
*BSC BSC device (basic BSC and RJE)
The RSMCTLRCY command allows the user to resume auto- *BSCT BSC device (Multipoint tributary and 3270
matic error recovery procedures after they have been Device Emulation)
stopped, and to reactivate a controller after it has been can- *APPC Advanced program-to-program communica-
celed (if the C response was entered to the inquiry message tions
associated with a controller failure). When the controller is *WSC Local work station
canceled with the C response, all jobs are ended; once the *WSCE Local work station (extended)
controller is repaired and the RSMCTLRCY command is
Specify the name of the controller (as specified in the
entered, jobs are allowed to start using the controller again.
controller description) for which error recovery proce-
Restriction: To use this command, the user must have dures are to resume.
object operational authority for the controller.
Note: To see the parameter and value descriptions for this Example
command, refer to the online help text. For more RSMCTLRCY CTL(TROLL3)
information about printing the help text, refer to
“Printing CL Command Descriptions” in Chapter 1. This command resumes error recovery procedures for the
controller TROLL3.
Required Parameters
(P) ────────────────────────────────────────────────────────────────────────────────────────5%
55──RSMDEVRCY──DEV(──device-name──)────
Note:
P All parameters preceding this point can be specified in positional form.
Purpose DEV
Specifies the device whose recovery is started again.
The Resume Device Recovery (RSMDEVRCY) command Valid types of devices are:
resumes error recovery procedures for a specific device.
The error recovery procedures are ended by the DEV Type Device
ENDDEVRCY command or by responding to a failure-related 5219 Printer (work station)
inquiry message with a cancel option. 5224 Printer (work station)
5225 Printer (work station)
The RSMDEVRCY command allows you to resume auto- 5251 Display station
matic error recovery procedures after they have been 5252 Dual display station
stopped, and to reactivate a device after it has been can- 5256 Printer (work station)
celed (if you entered the C response to the inquiry message 5291 Display station
associated with a device failure). When the device is can- 5292 Display station
celed with the C response, all jobs are ended; once the *PLU1 Physical unit (type 1)
device is repaired and the RSMDEVRCY command is *BSC BSC device
entered, jobs are allowed to start using the device again. *BSCT BSC multipoint tributary
*APPC Advanced program-to-program communica-
Restriction: To use this command, you must have object tions
operational authority for the device.
Specify the name of the device (as specified in the
Note: To see the parameter and value descriptions for this device description) for which error recovery procedures
command, refer to the online help text. For more are to resume.
information about printing the help text, refer to
“Printing CL Command Descriptions” in Chapter 1.
Example
RSMDEVRCY DEV(WSPRð3)
Required Parameters
This command resumes error recovery procedures for the
device WSPR03 to resume.
(P) ─────────────────────────────────────────────────────────────────────────────────────────5%
55──RSMLINRCY──LINE(──line-name──)────
Note:
P All parameters preceding this point can be specified in positional form.
The RSMLINRCY command allows the user to resume auto- Required Parameters
matic error recovery procedures after they stop, and to reac-
tivate a line after it is canceled (if the C response was LINE
entered to the inquiry message associated with a line failure). Specifies the line whose recovery is started again.
When the line is canceled with the C response, all jobs are
ended; once the line is repaired and the RSMLINRCY
Example
command is entered, jobs are allowed to start using the line
again. RSMLINRCY LINE(NYC2)
(P) ────────────────────────────────────────────────────────────5%
55──RSMNWIRCY──NWID(────network-interface-description-name────)────
Note:
P All parameters preceding this point can be specified in positional form.
55──RST──DEV(──┬─'save-file-path-name'─────────────────┬──)─────────────────────────────────────────────────────────────────────5
├─'diskette-device-path-name'───────────┤
├─'optical-device-path-name'────────────┤
├─'tape-media-library-device-path-name'─┤
│ ┌──
───────────────────────────┐ │
└──6──'tape-device-path-name'──┴───
(1) ──────┘
(P) ──┬────────────────────────┬─────────5
5──┬───────────────────────────────────────────────────────────────────────────────────┬───
│ ┌──
───────────────────────────────────────────────────────────────────┐ │ │ ┌─\ALL──┐ │
│ │ ┌─'\'──────────────────┐ ┌─\INCLUDE─┐ ┌─\SAME───────────┐ │ │ └─SUBTREE(──┼─\DIR──┼──)─┘
6 (2) (3)
└─OBJ(────(──┴─'object-path-name'───┴──┼──────────┼──┼─────────────────┼──)─┴─────)─┘ ├─\NONE─┤
└─\OMIT────┘ └─'new-path-name'─┘ └─\OBJ──┘
5──┬──────────────────────┬──┬──────────────────────────────┬──┬──────────────────────────────┬──┬──────────────────────┬───────5
│ ┌─\LCL─┐ │ └─SAVDATE(──date-when-saved──)─┘ └─SAVTIME(──time-when-saved──)─┘ │ ┌─\ALL─┐ │
└─SYSTEM(──┼─\RMT─┼──)─┘ └─OPTION(──┼─\NEW─┼──)─┘
└─\ALL─┘ └─\OLD─┘
5──┬────────────────────────────────────┬──┬───────────────────────────────────┬──┬──────────────────────────┬──────────────────5
│ ┌─\NONE───────────┐ │ │ ┌─\SYSVAL────────┐ │ │ ┌─\SAVED─┐ │
└─ALWOBJDIF(──┼─\ALL────────────┼──)─┘ └─FRCOBJCVN(──┼─\NO────────────┼──)─┘ └─SOMOBJID(──┴─\SYS───┴──)─┘
│ ┌──
──────────┐ │ │ ┌─\RQD─┐ │
└──6┬─\OWNER─┬┴───
(4) ─┘ └─\YES──┴─\ALL─┴─┘
└─\AUTL──┘
5──┬─────────────────────────────────────────┬──┬─────────────────────────────────────────┬─────────────────────────────────────5
│ (5) ────────────────┐
┌─\MOUNTED─── │ │ ┌─\SEARCH──────────────────┐ │
│ │ ┌──
─────────────────────┐ │ │ └─LABEL(──┼─diskette-file-identifier─┼──)─┘
6 (6)
└─VOL(──┴────volume-identifier──┴────┴──)─┘ └─tape-file-identifier─────┘
5──┬─────────────────────────────────┬──┬─────────────────────────┬──┬─────────────────────────────────────────┬────────────────5
│ ┌─\SEARCH─────────┐ │ │ ┌─\REWIND─┐ (7) ─'optical-file-path-name'──)─┘
│ └─OPTFILE(───
└─SEQNBR(──┴─sequence-number─┴──)─┘ └─ENDOPT(──┼─\LEAVE──┼──)─┘
└─\UNLOAD─┘
5──┬─────────────────────────────────────────┬──┬───────────────────────────┬──────────────────────────────────────────────────5%
│ ┌─\NONE───────────────────┐ │ │ ┌─\ALL─────┐ │
└─OUTPUT(──┼─\PRINT──────────────────┼──)─┘ └─INFTYPE(──┼─\ERR─────┼──)─┘
├─'user-space-path-name'──┤ └─\SUMMARY─┘
└─'stream-file-path-name'─┘
Notes:
1 A maximum of 4 repetitions.
4 A maximum of 2 repetitions.
5 This value cannot be specified when using an optical media library device.
6 A maximum of 75 repetitions.
Purpose Note: To see the parameter and value descriptions for this
command, refer to the online help text. For more
The Restore (RST) command restores a copy of one or more information about printing the help text, refer to
objects that can be used in the integrated file system. “Printing CL Command Descriptions” in Chapter 1.
'diskette-device-path-name': Specify the path name of *SAME: The objects are to be restored with the same
the diskette device used to restore the objects. names they had when they were saved.
'optical-device-path-name': Specify the path name of the 'new-path-name': Specify the path name with which to
optical device used to restore the objects. restore the object. If a pattern is specified in element 1,
the new name must be an existing directory into which
'tape-media-library-device-path-name': Specify the path
to restore any objects that match the pattern. If an
name of the tape media library device used to restore
object name is specified in element 1, each component
the objects.
in the new path name must exist with the exception of
'tape-device-path-name': Specify the path name of the the last component. If the object described in the last
tape device used to restore the objects. A maximum of component doesn't exist, it will be restored as new.
four tape devices can be specified.
SUBTREE
Specifies whether directory subtrees are included in the
Optional Parameters restore operation.
OBJ *ALL: The entire subtree of each directory that matches
Specifies the path name of the object to restore. You the object name pattern is processed. The subtree
can specify a pattern for this path name. A maximum of includes all subdirectories and the objects within those
300 path names can be specified. For more information subdirectories.
on specifying path names, refer to Chapter 2, “Path
*DIR: The objects in the first level of each directory that
Names (*PNAME).”
matches the object name pattern are processed. The
Additional information about name patterns is in the Inte- subdirectories of each matching directory are included,
grated File System Introduction book. but the objects in the subdirectories are not included.
Element 1: Object Name *NONE: No subtrees are included in the restore opera-
The first element specifies the path names of the objects tion. If a directory matches the object name pattern
saved on the media. Directory abbreviations (for specified, the objects in the directory are included. If the
example, the current directory) are expanded with their directory has subdirectories, neither the subdirectories
current values, not with the values they had at the time nor the objects in the subdirectories are included.
of the save operation. *OBJ: Only the objects that match the object name
'*': The objects in the current directory are restored. pattern are processed. If the object name pattern speci-
fies a directory, objects in the directory are not included.
'object-path-name': Specify an object path name or a
pattern that can match many names. If the default is SYSTEM
specified in element 3, each component in the path Specifies whether to process objects that exist on the
name must exist with the exception of the last compo- local system or remote systems.
nent. The object name in the last component is restored *LCL: Only local objects are processed.
as new if it doesn't exist.
*RMT: Only remote objects are processed.
Element 2: Include or Omit
*ALL: Both local and remote objects are processed.
The second element specifies whether names that
match the pattern should be included or omitted from the SAVDATE
operation. Note that in determining whether a name Specifies the date the objects were saved. If the most
matches a pattern, relative name patterns are always recently saved version is not the one being restored, or
treated as relative to the current working directory. if multiple saved versions reside on the media, specify
the date that identifies which version of the objects to
Note: The SUBTREE parameter determines whether
restore. If this parameter is not specified, the restored
the subtrees are included or omitted.
version of the objects is the first version found.
*INCLUDE: The objects that match the object name
The date must be specified in the job date format. If
pattern are restored, unless overridden by an *OMIT
separators, specified by the system value QDATSEP,
specification.
are used, the value must be enclosed in apostrophes.
*OMIT: The objects that match the object name pattern
are not restored. This overrides an *INCLUDE specifica- SAVTIME
tion and is intended to be used to omit a subset of a Specifies the time the objects were saved. If this param-
previously selected pattern. eter is not specified, the version of the objects to be
restored is the first version found on the volume.
Element 3: New Path Name
The time is specified in 24-hour format with or without a
The third element specifies the new path name of the time separator as follows:
object.
With a time separator, specify a string of 5 or 8
digits, where the time separator for the job sepa-
rates the hours, minutes, and seconds. If you issue *AUTL: The system of an object with an authorization
this command from the command line, the string list can be different. The new object, which is being
must be enclosed in apostrophes. If a time sepa- restored to a system that is different from which it was
rator other than the separator specified for your job saved, is restored and linked to its authorization list. If
is used, this command fails. the system of an object with an authorization list cannot
be different, the object is restored but not linked to an
Without a time separator, specify a string of 4 or 6
authorization list.
digits (hhmm or hhmmss) where hh = hours, mm =
minutes, and ss = seconds. Valid values for hh FRCOBJCVN
range from 00 through 23. Valid values for mm and Specifies whether to convert user objects to the format
ss range from 00 through 59. required for use in the current version of the operating
system when the objects are restored.
Notes:
Notes:
1. This parameter is valid only if the SAVDATE param-
1. This parameter applies only to user objects of the
eter is specified.
*MODULE, *PGM, *SRVPGM, and *SQLPKG object
2. This parameter is ignored when the SEQNBR types.
parameter is specified.
2. An object must be observable (have the required
OPTION observable information) in order to be converted.
Specifies whether to restore objects that already exist on
3. If an object needs to be converted (because it is for-
the system or objects that do not already exist on the
matted for an earlier version of the operating
system.
system), but is not converted during this restore
*ALL: All of the specified objects are restored, whether operation, the object is automatically converted the
they already exist on the system or not. first time it is used.
*NEW: Objects are restored only if they do not already Element 1: Force Conversion
exist on the system.
*SYSVAL: The objects are converted based on the
*OLD: Objects are restored only if they already exist on value of the QFRCCVNRST system value.
the system.
Note: If this value is specified and the system value
ALWOBJDIF QFRCCVNRST has a value of "1," the restore
Specifies whether differences are allowed between the operation proceeds as if FRCOBJCVN(*YES
saved object and the restored object. The differences *RQD) is specified. If QFRCCVNRST has a
include: value of "0", the restore operation proceeds as if
FRCOBJCVN(*NO) is specified.
Ownership: The owner of an object on the system
is different than the owner of an object from the *NO: The objects are not converted during the restore
save operation. operation.
Authorization list linking: The system on which an *YES: The objects are converted during the restore
object with an authorization list is being restored is operation.
different from the system on which it was saved. Note: Specifying this value increases the time of the
restore operation, but avoids the need to convert
*NONE: No differences are allowed between the saved
the objects when they are first used.
object and the restored object. If the owner is different,
the object is not restored. If the system is different for Element 2: Objects to Convert
an object with an authorization list, the object is restored,
*RQD: The objects are converted only if they require
but the object is not linked to its authorization list.
conversion to be used by the current operating system.
*ALL: All differences are allowed between the saved If the objects are not observable, the objects are
object and the restored object. If the owner is different, restored but are not converted.
the object is restored with the owner of the system on
*ALL: All objects are converted regardless of their
which it is restored. If the system is different for an
current format. Even the objects are in the current
object with an authorization list, the object is restored
format, they are converted again. However, if the
and linked to its authorization list.
objects are not observable, the objects are not restored.
*OWNER: The object owner can be different. If an
SOMOBJID
object already exists on the system with a different
Specifies whether the SOM object ID of the restored
owner than the saved object, the object is restored with
object will be the SOM object ID of the object from the
the owner of the object on the system. If owner differ-
save media, the SOM object ID of the object that exists
ences are not allowed, the object is not restored.
on the system prior to the restore, or a new SOM object
Example 5: Restoring All Objects in the Current Direc- Assume the current directory contains the following symbolic
tory links.
RST DEV('/QSYS.LIB/TAPð1.DEVD') DevLink = /QSYS.LIB/TAP01.DEVD
DirLink = /SomeDirectory
This command uses the default value on the OBJ parameter FileLink = /SomeDirectory/SomeFile
to restore all objects in the current directory and its subdirec-
tories. Symbolic links can be used to specify the device and output
file. When symbolic links are restored, only the names of the
RST DEV('/QSYS.LIB/TAPð1.DEVD') OBJ('\')
SUBTREE(\NONE) associated objects are restored, not the content of the asso-
ciated objects. A symbolic link to a directory can be used to
This command restores all objects in the current directory but restore objects in the directory. Additional information about
not in subdirectories. symbolic link is in the Integrated File System Introduction
book. To restore the names associated with DirLink and
RST DEV('/QSYS.LIB/TAPð1.DEVD') OBJ('.')
SUBTREE(\DIR) FileLink from device TAP01:
RST DEV('DevLink') OBJ(('DirLink') ('FileLink'))
This command restores the current directory and all of the
To restore the objects in SomeDirectory from device TAP01:
objects in the current directory. It does not restore objects in
the subdirectories of the current directory. RST DEV('DevLink') OBJ(('DirLink/\'))
Purpose Note: Steps 2 through 7 can be done more than once. For
example, after the user profiles are restored (step 2),
The Restore Authority (RSTAUT) command restores the the user can restore only critical application libraries
private authorities to user profiles. This command restores (step 3), followed by a restore of object authority
the same object use authority to specified objects in the user (step 7). This supplies an operational system limited
profile that each user profile had when all the profiles were to using only the critical libraries. Later, the
saved by the Save System (SAVSYS) or Save Security Data remaining user profiles can be restored, followed by
(SAVSECDTA) commands. It allows existing authorities, the operations to restore the libraries and object
given after the save, to remain. Authority is not restored to authority.
the user profiles until the profiles are first restored to the
system by the Restore User Profiles (RSTUSRPRF) If authorities for a user profile are restored using the
command and all the objects (for which authority is being RSTAUT command, the user profile must be restored
given) are restored to the same libraries where they are again before other authorities for it can be restored.
saved. The objects can be restored with the Restore Library
(RSTLIB) or Restore Object (RSTOBJ), Restore Document If one user profile is being restored, the following sequence
Library Object (RSTDLO), Restore Configuration (RSTCFG), must be followed. Using the RSTAUT command must be the
or Restore Objects in Directories (RST) commands. last step.
1. Restore the specified user profile to the system by using
If the whole system is being restored, the following sequence the RSTUSRPRF command.
must be followed. Using the RSTAUT command must be the
last step in the sequence. 2. Restore all the device configuration and SRM objects to
the system by using the RSTCFG command.
1. Restore the operating system. This is an alternative
method to load the program. This restores the QSYS 3. Restore the specified user libraries to the system by
library and ensures that the IBM-supplied user profiles using the RSTLIB command or the RSTOBJ command.
are there. If the user profile is being restored because the current
profile on the system is damaged, then the needed
2. Restore all the saved user profiles to the system (*ALL libraries already exist on the system and restoring of the
is the default for the USRPRF parameter) by using the libraries is not necessary.
RSTUSRPRF command.
4. Restore all document library objects to the system using
3. Restore all the configuration and system resource man- the RSTDLO command.
agement (SRM) objects to the system by using the
RSTCFG command. 5. Restore all objects in directories using the RST
command.
4. Restore all the user libraries (including the other
IBM-supplied libraries) by using the RSTLIB command. 6. Restore the object authority to the user profile by using
Unless saved with the *IBM or *ALLUSR parameter, the RSTAUT command. The specified profile may have
*NONSYS must be specified on the SAVLIB parameter been restored using the RSTUSRPRF command.
to restore all user libraries in one operation.
Restrictions:
5. Restore all document library objects to the system by
1. This command is shipped with public *EXCLUDE
using the RSTDLO command.
authority.
6. Restore all objects in directories using the RST
2. You must have *SAVSYS special authority to use this
command.
command.
7. Restore the object authority to user profiles by using the
3. Only one RSTAUT command can be run on a system at
RSTAUT command.
one time.
Note: To see the parameter and value descriptions for this RSTUSRPRF USRPRF(USER1 USER2 USER3 USER4)
command, refer to the online help text. For more
information about printing the help text, refer to RSTLIB SAVLIB(USERLIB)
“Printing CL Command Descriptions” in Chapter 1.
RSTAUT USRPRF(USER1 USER2 USER3)
Optional Parameter To each specified user profile that was successfully restored,
this command restores the authority to use each object that
USRPRF the profile had at the time the system was saved. The user
Specifies the names of one or more user profiles whose profiles and the libraries and their objects must be restored
private authorities are being restored. The specified before the RSTAUT command is sent. Because USER4 was
user profiles must first be restored using the not specified in the RSTAUT command, its authorities are
RSTUSRPRF command. still available and may be restored at a later date.
*ALL: Private authorities are being restored for all of
the user profiles that are restored but do not have their Example 3
private authorities restored. This includes user profiles RSTUSRPRF USRPRF(\ALL)
that were restored using multiple RSTUSRPRF com-
mands. RSTLIB SAVLIB(USERLIBA)
generic*-user-profile-name: Specify the generic name of RSTLIB SAVLIB(USERLIBB)
the user profile. A generic name is a character string of
one or more characters followed by an asterisk (*); for RSTLIB SAVLIB(USERLIBC)
example, ABC*. The asterisk (*) substitutes for any valid
characters. For more information on the use of generic RSTAUT USRPRF(\ALL)
functions, refer to “Rules for Specifying Names.”
This command restores private authorities for all restored
user-profile-name: Specify one or more names of spe-
user profiles on the system. This includes authorities for all
cific user profiles. Both generic names and specific
user profiles restored by the RSTUSRPRF command. Other
names can be specified in the same command.
user profiles on the system that did not have their authorities
restored before these commands were specified are also
Examples restored by the RSTAUT(*ALL) command.
Example 1 Example 4
RSTAUT RSTUSRPRF USRPRF(USER1 USER2)
This command restores to each user profile the authority to RSTLIB SAVLIB(USERLIBA)
use each object that the profile had at the time when the
system was saved. The user profiles and the libraries and RSTUSRPRF USRPRF(USER1 USER3)
their objects must be restored before the RSTAUT command
is sent. RSTLIB SAVLIB(USERLIBB)
55──RSTCFG──OBJ(──┬─\ALL────────────────────────────┬──)──DEV(──┬─\SAVF──────────────────────────┬──)───────────────────────────5
├─\SRM────────────────────────────┤ ├─tape-media-library-device-name─┤
│ ┌──
──────────────────────────┐ │ │ ┌──
────────────────────┐ │
6 (1) ─┘
└───┬─generic\-object-name─┬─┴─── └──6─tape-device-name───
(2) ┴─────────┘
└─object-name──────────┘
5──┬───────────────────────────────────┬──┬───────────────────────────────────────┬─── (P) ──────────────────────────────────────────5
│ ┌─\ALL─────────────┐ │ │ ┌─\MOUNTED─────────────────┐ │
│ │ ┌──
───────────┐ │ │ │ │ ┌──
───────────────────┐ │ │
└─OBJTYPE(──┴──6─┬─\CFGL─┬─┴─── 6─volume-identifier─┴───
(3) ─┴──)─┘ └─VOL(──┴── (4) ─┴──)─┘
├─\CNNL─┤
├─\COSD─┤
├─\CTLD─┤
├─\DEVD─┤
├─\IPXD─┤
├─\LIND─┤
├─\MODD─┤
├─\NTBD─┤
├─\NWID─┤
└─\NWSD─┘
5──┬──────────────────────────────────────┬──┬─────────────────────────┬──┬────────────────────────────────────────────┬────────5
│ ┌─\SEARCH──────────────┐ │ │ ┌─\REWIND─┐ │ │ ┌─\LIBL────────┐ │
└─SEQNBR(──┴─file-sequence-number─┴──)─┘ └─ENDOPT(──┼─\LEAVE──┼──)─┘ └─SAVF(──┼──────────────┼──save-file-name──)─┘
└─\UNLOAD─┘ ├─\CURLIB──────┤
└─library-name─┘
5──┬────────────────────┬──┬──────────────────────────┬──┬──────────────────────────┬───────────────────────────────────────────5
│ ┌─\ALL──┐ │ │ ┌─\NONE─┐ │ │ ┌─\NONE────┐ │
└─SRM(──┼─\NONE─┼──)─┘ └─ALWOBJDIF(──┴─\ALL──┴──)─┘ └─OUTPUT(──┼─\PRINT───┼──)─┘
├─\HDW──┤ └─\OUTFILE─┘
└─\TRA──┘
5──┬──────────────────────────────────────────────────────┬──┬─────────────────────────────────────────────┬───────────────────5%
│ ┌─\LIBL/────────┐ │ │ ┌─\FIRST──────┐ ┌─\REPLACE─┐ │
(5) ─┼───────────────┼──database-file-name──)─┘ └─OUTMBR(───
└─OUTFILE(─── (5) ─┴─member-name─┴──┼──────────┼──)─┘
├─\CURLIB/──────┤ └─\ADD─────┘
└─library-name/─┘
Notes:
1 A maximum of 300 repetitions
2 A maximum of 4 repetitions
3 A maximum of 8 repetitions
4 A maximum of 75 repetitions
Purpose Restrictions:
1. To use this command, the user must have *SAVSYS
The Restore Configuration (RSTCFG) command restores to
authority, or object existence authority for (or be the
the system a configuration object that was saved by the
owner of) each object specified if the object already
Save System (SAVSYS) or Save Configuration (SAVCFG)
exists on the system.
command. The types of objects that can be restored by this
command are listed in the OBJTYPE parameter. 2. This command is shipped with public *EXCLUDE
authority.
The user profile of the system default owner (QDFTOWN)
3. The device configuration object must be varied off when
becomes the default owner of any objects being restored on
it is being restored. To vary off a device configuration
the system when the profile of the owner is not known to the
object, use the Vary Configuration (VRYCFG) command.
system.
4. With the exception of overrides for the output listing file,
If an object already exists, in the library to which the object is this command ignores all file overrides currently in effect
restored, the public and private authorities of the existing for the job.
object are kept. If the object does not exist in the library, all
5. System resource management (SRM) objects are not
public authorities are restored, but any private authorities
restored if the RSTCFG command is run using media
must be granted again.
that was created prior to V2R2M0.
6. If the RSTCFG command and the SAVSYS or SAVCFG tape-media-library-device-name: Specify the name of
commands are not run on the same system, the config- the tape media library device used for the restore opera-
uration objects may not match the physical hardware on tion.
the target system.
tape-device-name: Specify the names of one or more
7. If you restore system resource management objects on tape devices used for the restore operation. If you are
a system other than the one on which the SAVSYS or using more than one tape device (up to a maximum of
SAVCFG command was saved, the system then treats four), specify the names of the devices in the order in
the target system hardware as new and creates all new which they are used.
resource names, making the existing configuration
The device name must already be known on the system
descriptions useless. If this occurs, you need to restore
by a device description. If using more than one tape
the correct system resource management database from
drive (up to four), specify the names of the drives in the
the most current SAVSYS or SAVCFG command for that
order they are used. If the objects are on more than
command. If neither of these is available, you must
one tape volume, the user may want to use more than
change existing configuration descriptions to reflect the
one tape drive, so that one tape volume can be rewound
new resource names.
and unloaded while another tape drive processes the
Note: To see the parameter and value descriptions for this next volume.
command, refer to the online help text. For more
information about printing the help text, refer to
“Printing CL Command Descriptions” in Chapter 1.
Optional Parameters
OBJTYPE
Specifies the types of OS/400 system objects that are
Required Parameters
restored.
OBJ
*ALL: All device configuration object types that are
Specifies the names of one or more configuration
specified by name are restored. If *ALL is also specified
objects being restored.
on the OBJ parameter, all of the saved device configura-
System resource management (SRM) objects cannot be tion objects are restored.
restored individually or by specifying a generic name.
object-type: Specify the value for each of the types of
To restore only SRM objects, specify *SRM on the OBJ
objects that are being restored. The following types can
parameter and a value on the SRM parameter.
be specified:
*ALL: All the device configuration objects are restored,
*CFGL Configuration list
depending on the values specified for the OBJTYPE
*CNNL Connection list
parameter.
*COSD Class-of-service description
*SRM: The device configuration objects are not *CTLD Controller description
restored, but system resource management (SRM) *DEVD Device description
objects are restored based on the SRM parameter value. *IPXD Internet Packet Exchange description
generic*-object-name: Specify the generic name of the *LIND Line description
object. A generic name is a character string of one or *MODD Mode description
more characters followed by an asterisk (*); for example, *NTBD NetBIOS description
ABC*. The asterisk substitutes for any valid characters. *NWID Network interface description
A generic name specifies all objects with names that *NWSD Network server description
begin with the generic prefix, for which the user has
The object types shown are the ones saved in the
authority. If an asterisk is not included with the generic
device configuration media file by using the Save
(prefix) name, the system assumes it to be the complete
System (SAVSYS) or Save Configuration (SAVCFG)
object name. For more information on the use of
command.
generic functions, refer to “Rules for Specifying Names.”
Note: *SRMSPC are also saved, but not restored as an
object-name: Specify one or more names of specific object type. Specify *SRM on the OBJ param-
objects being restored. Both generic names and specific
eter to restore SRM data.
names can be specified in the same command. A
maximum of 300 object names can be specified. VOL
Specifies the volume identifiers of the tape volumes from
DEV
which the objects are being restored. The volumes must
Specifies the name of the tape device used to restore
be placed in the tape device in the same order as they
the objects.
were when the objects were saved. The volume that
*SAVF: The save file specified on the SAVF parameter contains the beginning of the file to be restored should
is used for the restore operation. be placed in the tape unit. More information on this
parameter is in Appendix A, “Expanded Parameter
Descriptions.”
Note: The version of the objects that is restored is the *CURLIB: The current library for the job is
first version found in the specified location. searched. If no library is specified as the current
library for the job, the QGPL library is used.
*MOUNTED: The objects are restored from the volumes
placed in the device specified on the DEV parameter. library-name: Specify the name of the library to be
For a media library device, the volume to be used is the searched.
next cartridge in the category mounted by the Set Tape
Category (SETTAPCGY) command.
save-file-name: Specify the name of the save file.
*LIBL: All libraries in the job's library list are 2. The informational message causes a diagnostic
searched until the first match is found. message to be sent indicating that security or integ-
rity changes occurred during the restore operation.
This results in an escape message for the restore
operation.
(P) ──────────────────────────────────5
55──RSTDLO──DLO(──┬─\ALL─────────────────┬──)──DEV(──┬─\SAVF──────────────────────────┬──)────
├─\MAIL────────────────┤ ├─diskette-device-name───────────┤
├─\SYSOBJNAM───────────┤ ├─optical-device-name────────────┤
│ ┌──
───────────────┐ │ ├─tape-media-library-device-name─┤
6 (1) ─┘
└───document-name─┴─── │ ┌──
──────────────────┐ │
└──6─tape-device-name─┴───
(2) ────────┘
5──┬──────────────────────────────────────────┬──┬──────────────────────────────────────────┬───────────────────────────────────5
│ ┌─\ANY─────────────────────┐ │ │ ┌─\SAME────────────────────┐ │
(3) ─────────────────┼──)─┘ │
└─SAVFLR(──┼─\NONE─── │ ┌──
───────────────────┐ │ │
│ ┌──
───────────────────┐ │ 6 (1)
└─RENAME(──┴───new-document-name─┴────┴──)─┘
└──6─saved-folder-name─┴───(1) ─┘
5──┬───────────────────────────────────────┬──┬──────────────────────────────────────────────┬──────────────────────────────────5
│ ┌─\SAME─────────────────┐ │ │ ┌─\NONE─────────────────────┐ │
(4) ┴──)─┘ │
└─RSTFLR(──┴─restore-folder-name─── │ ┌──
────────────────────┐ │ │
6 (1)
└─SYSOBJNAM(──┴───system-object-name─┴────┴──)─┘
5──┬───────────────────────────────────────┬──┬───────────────────────────────────────────────────────────────────────────┬─────5
│ (5) ──────────────┐
┌─\MOUNTED─── │ │ ┌─\SEARCH───────────────────────────────────────────────┐ │
│ │ ┌──
───────────────────┐ │ │ │ │ ┌─\ONLY──────────────────┐ │ │
└─VOL(──┴──6─volume-identifier─┴───(6) ─┴──)─┘ └─SEQNBR(─────
(7, 8) ─┴─beginning-sequence-number──┼────────────────────────┼─┴──)─┘
└─ending-sequence-number─┘
5──┬───────────────────────────┬──┬─────────────────────────────────────┬──┬─────────────────────────────────────────────┬──────5
│ ┌─\REWIND─┐ │ │ ┌─\GEN─────────────────┐ │ │ ┌─\LIBL/────────┐ │
(8) ─┼─\LEAVE──┼──)─┘ └─LABEL(──┴─data-file-identifier─┴──)─┘ └─SAVF(──┼───────────────┼──save-file-name──)─┘
└─ENDOPT(───
└─\UNLOAD─┘ ├─\CURLIB/──────┤
└─library-name/─┘
5──┬───────────────────────┬──┬──────────────────────────────┬──┬──────────────────────────────┬────────────────────────────────5
│ ┌─\SAME─┐ │ └─SAVDATE(──date-when-saved──)─┘ └─SAVTIME(──time-when-saved──)─┘
└─NEWOBJ(──┴─\NEW──┴──)─┘
5──┬──────────────────────────┬──┬──────────────────────────┬──┬────────────────────────────┬──┬──────────────────────────┬─────5
│ ┌─\NONE─┐ │ │ ┌─\ANY─────┐ │ │ (10) ┐
┌─\SAVASP──── │ │ ┌─\NONE────┐ │
(9) ┴──)─┘ └─RSTASP(──┴─ASP-ID─────┴──)─┘ └─OUTPUT(──┼─\PRINT───┼──)─┘
└─ALWOBJDIF(──┴─\ALL──┴──)─┘ └─SAVASP(──┴─ASP-ID───
└─\OUTFILE─┘
5──┬───────────────────────────────────────────────────────┬──┬──────────────────────────────────────────────┬──────────────────5
│ ┌─\LIBL/────────┐ │ │ ┌─\FIRST──────┐ ┌─\REPLACE─┐ │
(11) ─┼───────────────┼──database-file-name──)─┘ └─OUTMBR(────
└─OUTFILE(──── (11) ─┴─member-name─┴──┼──────────┼──)─┘
├─\CURLIB/──────┤ └─\ADD─────┘
└─library-name/─┘
5──┬──────────────────────────────────────────┬────────────────────────────────────────────────────────────────────────────────5%
(12) ─'optical-file-path-name'──)─┘
└─OPTFILE(────
Notes:
1 A maximum of 300 repetitions
2 A maximum of 4 repetitions
5 This value cannot be specified when using an optical media library device.
6 A maximum of 75 repetitions
7 For restore from diskette, or if SEQNBR(*SEARCH) is used to restore from tape, only the first file on diskette or tape that
9 This value is not valid when a user-defined value is specified on the LABEL parameter.
*SAVF: The document library objects are restored from specified and the media contains the folder specified on
a save file. the SAVFLR parameter.
diskette-device-name: Specify the name of the diskette *SAME: The documents to be restored are placed into
device to be used to restore the document library the same folder from which they were saved.
objects.
restore-folder-name: Specify the name of the folder in
optical-device-name: Specify the name of the optical which the restored documents and folders are to be
device used for the restore operation. placed.
tape-media-library-device-name: Specify the name of SYSOBJNAM
the tape media library device used for the restore opera- Specifies the system object name of the documents to
tion. be restored. This parameter is valid only when
tape-device-name: Specify the names of one or more DLO(*SYSOBJNAM) is specified.
tape devices used for the restore operation. If more *NONE: A system object name is not specified.
than one tape device is used, specify the names of the
devices in the order in which they are used. Using more
system-object-name: Specify the 10-character system
object names of the documents to be restored. A
than one tape device permits one tape volume to be
maximum of 300 names can be specified.
rewound and unloaded while another tape device pro-
cesses the next tape volume. VOL
Specifies the volume identifiers of the tape, diskette, or
Optional Parameters optical volumes, or the cartridge identifier of a tape
media library device, from which the objects are being
SAVFLR restored. The volumes must be in the same order as
Specifies the name of the folder on the media from they were when the objects were saved. The volume
which the documents and folders are restored. that contains the beginning of the file to be restored
*ANY: All document library objects that meet the values should be placed in the tape or diskette unit. More infor-
specified on the DLO parameter are restored, regardless mation on this parameter is in Appendix A, “Expanded
of the folders (if any) from which they were saved. This Parameter Descriptions.”
value is valid only if *ALL, *MAIL, or *SYSOBJNAM is *MOUNTED: The objects are restored from the volumes
specified on the DLO parameter. placed in the device specified on the DEV parameter.
*NONE: The documents to be restored were saved as For a media library device, the volume to be used is the
documents without folders. next cartridge in the category mounted by the Set Tape
Category (SETTAPCGY) command.
Note: *NONE is valid only when DLO(*ALL) is speci-
fied. Note: This value cannot be specified when using an
optical media library device.
saved-folder-name: Specify the name of the saved
folder from which documents or folders are to be volume-identifier: Specify the identifiers of one or more
restored. Up to 63 characters can be specified for the volumes in the order they are placed in the device and
folder name. When DLO(*ALL) is specified, up to 300 used to restore the libraries.
folder names can be specified. The name of a saved SEQNBR
folder must be specified when DLO(document-name) is Specifies the tape sequence numbers used for the
specified. restore operation. This parameter is valid for tape only.
RENAME *SEARCH: The tape is searched for the first data file
Specifies the new user-assigned name for the restored with an identifier matching the LABEL parameter value
document. and with contents of a minimum of one of the specified
*SAME: The documents being restored have the same document library objects. If the last operation on the
user-assigned names that they have on the media. device specified ENDOPT(*LEAVE) (that is, the tape is
positioned at the location at which the last operation
new-document-name: Specify the new document names ended), the file search begins with the first data file
that the documents have after they are restored. Up to beyond the current tape position. If ENDOPT(*LEAVE)
300 user-assigned names can be specified for docu- was not specified on the last operation (or if the tape
ments being restored. has been rewound since an ENDOPT(*LEAVE) opera-
RSTFLR tion), the search begins with the first data file on the
Specifies the name of the folder in which the folders and volume.
documents to be restored will be placed. The name can Note: If a folder is contained in more than one file or
be any fully-qualified folder name up to 63 characters. on more than one tape, a message is sent indi-
The folder named is not required to exist if DLO(*ALL) is cating that the folder may not have been fully
restored. To restore the rest of the folder, run
the RSTDLO command again specifying the next *SAME: The library-assigned name is restored to the
sequence number. name used when the document library objects were
saved.
Element 1: Beginning Sequence Number
*NEW: A new library-assigned name is created for each
Specifies the sequence number of the first file to be
document or folder being restored. If *NEW is specified
used for the restore operation.
on this parameter, then ALWOBJDIF(*ALL) cannot be
Element 2: Ending Sequence Number specified.
*ONLY: The ending sequence number is the same as SAVDATE
the beginning sequence number.
Specifies the date on which the document library objects
ending-sequence-number: Specify the sequence were saved. If more than one version of the document
number of the last file used for the restore operation. library objects exist on the media, use this parameter to
| Valid values range from 1 through 16777215. identify which version of the document library objects to
restore. The date must be expressed in the job date
ENDOPT
format; if separators are used, the value must be
Specifies the operation that is automatically performed
enclosed in apostrophes. If the SAVDATE parameter is
on the tape volume after the operation ends. If more
not specified, the version of the documents and folders
than one volume is included, this parameter applies only
to be restored will be the first version found on the
to the last tape volume used; all other tape volumes are
volume or the version found with the specified file label.
rewound and unloaded when the end of the tape is
reached. SAVTIME
Specifies the time when the document library objects
*REWIND: The tape is automatically rewound, but not
were saved. If more than one version of the document
unloaded, after the operation has ended.
library objects exist on the media with the same value
*LEAVE: The tape does not rewind or unload after the for the date saved, use this parameter to identify which
operation ends. It remains at the current position on the version of the document library objects to restore.
tape drive. Express the time as a 6-digit value, in the format hours,
*UNLOAD: The tape is automatically rewound and minutes, seconds (hhmmss). If separators are used, the
unloaded after the operation ends. value must be enclosed in apostrophes ('hh:mm:ss'). If
a volume identifier is specified, but SAVTIME is not
LABEL specified, the version of the document library objects to
Specifies the file label that is used to find the file that be restored will be the first version found on the volume
was written to the media during the save operation. or the version found with the specified file label.
*GEN: The system generates the default name of the This parameter is valid only if SAVDATE is also speci-
file label for which to search. fied.
data-file-identifier: Specify the media data file identifier, ALWOBJDIF
which includes up to 17 alphanumeric characters, of the
Specifies whether the following differences encountered
file that contains the documents and folders to be
during the RSTDLO operation are allowed:
restored.
The owner of the object on the system is different
SAVF
than the owner of the object from the save.
Specifies the qualified name of the save file that con-
tains the saved document library objects to be restored. The system object name on the system does not
match the system object name on the tape or
The name of the save file can be qualified by one of the
diskette being restored.
following library values:
The object is secured by an authorization list and is
*LIBL: All libraries in the job's library list are being restored to a system other than the one on
searched until the first match is found. which it was saved.
*CURLIB: The current library for the job is
The ALWOBJDIF parameter can be used to allow an
searched. If no library is specified as the current
object to be restored whose owner or object name on
library for the job, the QGPL library is used.
the system is different than on the media used for the
library-name: Specify the name of the library to be restore operation. By specifying the *ALL special value,
searched. an object with a different name is restored to the name
on the media, while an object with a different owner
save-file-name: Specify the name of the save file from keeps the owner name from the system instead of the
which to restore DLOs.
media.
NEWOBJ Note: In order to use this parameter, *ALLOBJ
Specifies whether a new library-assigned name is authority is required.
created for the folder or document being restored.
*NONE: The differences described above are not *PRINT: The output is printed with the job's spooled
allowed on the restore operation. For authorization list output.
cases, the object is restored, but the object is not linked
*OUTFILE: The output is directed to the database file
to the authorization list, and public authority is set to
specified on the OUTFILE parameter.
*EXCLUDE. For other cases, a diagnostic message is
sent for the object, and the object is not restored. Note: You must specify the database file name on the
OUTFILE parameter when OUTPUT(*OUTFILE)
*ALL: All the differences described above are allowed
is specified.
for the restore operation. The object is restored.
OUTFILE
Notes:
Specifies the qualified name of the database file to
If the owners of the object do not match, the object which the information about the object is directed when
is restored, but it keeps the ownership and authori- *OUTFILE is specified on the OUTPUT parameter. If
ties of the object on the system before the restore the file does not exist, this command creates a database
operation. file in the specified library. If a new file is created, the
system uses QAOJRSTO in QSYS with the format name
The informational message flags a diagnostic
QOJRST as a model.
message to be sent indicating that security or integ-
rity changes occurred during the restore operation. The name of the database file can be qualified by one of
This results in an escape for the restore function. the following library values:
If *ALL is specified on this parameter, then *LIBL: All libraries in the job's library list are
NEWOBJ(*NEW) cannot be specified. searched until the first match is found.
If the user is restoring objects to a system different *CURLIB: The current library for the job is
from the one on which they were saved and the searched. If no library is specified as the current
objects are secured by an authorization list, speci- library for the job, the QGPL library is used.
fying *ALL automatically links the objects to the
authorization list. If the authorization list does not
library-name: Specify the name of the library to be
searched.
exist on the new system, a message that includes
the name of the missing list is issued. database-file-name: Specify the name of the database
file to which the output of the command is directed.
SAVASP
Specifies the identifier (ID) of the auxiliary storage pool OUTMBR
(ASP) on media from which saved documents and Specifies the name of the database file member to which
folders are to be restored. the output is directed. If a member already exists, the
*ANY: The documents and folders saved in any ASP system uses the second element of this parameter to
are restored. determine whether the member is cleared before the
new records are added. If the member does not exist
ASP-ID: Specify a value ranging from 1 through 16, and a member name is not specified, the system creates
which is the ID of the ASP from which documents and
a member with the name of the output file specified on
folders are restored.
the OUTFILE parameter. If an output file member name
RSTASP is specified, but the member does not exist, the system
Specifies the identifier (ID) of the auxiliary storage pool creates it.
(ASP) on media in which restored documents and Element 1: Member to Receive Output
folders are to be placed.
*FIRST: The first member in the file receives the output.
*SAVASP: The documents and folders are placed in If OUTMBR(*FIRST) is specified and the member does
the same ASP from which they were saved. not exist, the system creates a member with the name of
ASP-ID: Specify a value ranging from 1 through 16, the file specified on the OUTFILE parameter.
which is the ID of the ASP in which restored documents member-name: Specify the name of the file member
and folders are placed. that receives the output. If OUTMBR(member-name) is
specified and the member does not exist, the system
OUTPUT
creates it. If the member exists, the user can add
Specifies whether a listing that shows information about
records to the end of the existing member or clear the
the status of the object is created and directed to an
existing member and add the records.
output file. The listing shows the restore information and
shows all objects, restored, not restored, and excluded. Element 2: Operation to Perform on Member
Information about each object's security is listed for the
*REPLACE: The existing records in the specified data-
restored objects. More information on this parameter is
base file member are replaced by the new records.
in Appendix A, “Expanded Parameter Descriptions.”
*ADD: The new records are added to the existing infor-
*NONE: No output is created.
mation in the specified database file member.
Note: This parameter is required when using an optical Example 6: Renaming Documents
device.
RSTDLO DLO(A B) DEV(TAPð1) SAVFLR(C) RENAME(Y Z)
RSTFLR(X)
This command restores the document named A from folder Example 8: Specifying Allowed Differences
X. RSTDLO DLO(A) DEV(TAPð1) SAVFLR(X)
ALWOBJDIF(\ALL)
Example 3: Restoring All Documents
RSTDLO DLO(\ALL) DEV(TAPð1) This command restores document A from folder X. If docu-
ment A in folder X exists on the system and the owner of the
This command restores all documents and folders that are document on the system does not match the owner of the
on the first tape file on tape unit TAP01. document being restored, the document is restored and the
owner of the document on the system remains unchanged.
Example 4: Restoring a Folder Saved from the System
ASP to a User ASP Example 9: Reporting Information about Objects
RSTDLO DLO(\ALL) FLR(Y) SAVASP(1) RSTASP(2) Restored and Not Restored
RSTDLO DLO(\ALL) DEV(TAPð1) OUTPUT(\OUTFILE)
This command restores folder Y, which was saved from ASP OUTFILE(INFO92) OUTMBR(FOURQT \ADD)
1, to user ASP 2. Folder Y must be deleted from ASP 1
before it can be restored to ASP 2. This command restores all documents and folders from the
tape device TAP01. A list reporting information about objects
Example 5: Creating New Library-Assigned Name restored and objects not restored is directed to the output file
INFO92. The output is received in the member FOURQT as
an addition to existing information in the member.
55──RSTLIB──SAVLIB(──┬─\NONSYS──────┬──)──DEV(──┬─\SAVF──────────────────────────┬──)───────────────────────────────────────────5
├─\ALLUSR──────┤ ├─diskette-device-name───────────┤
├─\IBM─────────┤ ├─optical-device-name────────────┤
└─library-name─┘ ├─tape-media-library-device-name─┤
│ ┌──
──────────────────┐ │
└──6─tape-device-name─┴───
(1) ────────┘
5──┬───────────────────────────────────────┬──┬────────────────────────────────────────┬───(P) ─────────────────────────────────────5
│ (2) ──────────────┐
┌─\MOUNTED─── │ │ ┌─\SEARCH──────────────┐ │
(4) ─┴─file-sequence-number─┴──)─┘
└─VOL(──┼─\SAVVOL──────────────────┼──)─┘ └─SEQNBR(───
│ ┌──
───────────────────┐ │
└──6─volume-identifier─┴───(3) ─┘
5──┬─────────────────────────────────────┬──┬───────────────────────────┬──┬────────────────────────────────┬───────────────────5
│ ┌─\SAVLIB──────────────┐ │ │ ┌─\REWIND─┐ │ │ ┌─\FIRST───────┐ │
(4) ─┼─\LEAVE──┼──)─┘ └─STRLIB(───
└─LABEL(──┴─data-file-identifier─┴──)─┘ └─ENDOPT(─── (5) ─┴─library-name─┴──)─┘
└─\UNLOAD─┘
5──┬────────────────────────────────────────┬──┬─────────────────────────────────────────────┬──┬───────────────────────┬───────5
│ ┌─\NONE───────────────┐ │ │ ┌─\LIBL/────────┐ │ │ ┌─\ALL──┐ │
│ │ ┌──
──────────────┐ │ │ └─SAVF(──┼───────────────┼──save-file-name──)─┘ └─OPTION(──┼─\NEW──┼──)─┘
└─OMITLIB(─── 6─library-name─┴───
(5) ─┴── (6) ─┴──)─┘ ├─\CURLIB/──────┤ ├─\OLD──┤
└─library-name/─┘ └─\FREE─┘
5──┬────────────────────────┬──┬──────────────────────────────┬──┬──────────────────────────────┬───────────────────────────────5
│ ┌─\MATCH─┐ │ └─SAVDATE(──date-when-saved──)─┘ └─SAVTIME(──time-when-saved──)─┘
└─MBROPT(──┼─\ALL───┼──)─┘
├─\NEW───┤
└─\OLD───┘
5──┬───────────────────────────┬──┬───────────────────────────────────┬──┬────────────────────────────────┬─────────────────────5
│ ┌─\NONE──┐ │ │ ┌─\SYSVAL────────┐ │ │ ┌─\SAVLIB────────┐ │
(7) ┴──)─┘ └─FRCOBJCVN(──┼─\NO────────────┼──)─┘ └─RSTLIB(──┴─library-name───
└─ALWOBJDIF(──┴─\ALL─── (8) ┴──)─┘
│ ┌─\RQD─┐ │
└─\YES──┴─\ALL─┴─┘
5──┬────────────────────────────────┬──┬──────────────────────────┬─────────────────────────────────────────────────────────────5
│ ┌─\SAVASP────────┐ │ │ ┌─\NONE────┐ │
└─RSTASP(──┴─asp-identifier─┴──)─┘ └─OUTPUT(──┼─\PRINT───┼──)─┘
└─\OUTFILE─┘
5──┬──────────────────────────────────────────────────────┬──┬─────────────────────────────────────────────┬────────────────────5
│ ┌─\LIBL/────────┐ │ │ ┌─\FIRST──────┐ ┌─\REPLACE─┐ │
(9) ─┼───────────────┼──database-file-name──)─┘ └─OUTMBR(───
└─OUTFILE(─── (9) ─┴─member-name─┴──┼──────────┼──)─┘
├─\CURLIB/──────┤ └─\ADD─────┘
└─library-name/─┘
5──┬─────────────────────────┬──┬──────────────────────────────────────────┬───────────────────────────────────────────────────5%
│ ┌─\OBJ─┐ (10) ─'optical-file-path-name'──)─┘
│ └─OPTFILE(────
(9) ─┴─\MBR─┴──)─┘
└─INFTYPE(───
Notes:
1 A maximum of 4 repetitions
2 This value cannot be specified when using an optical media library device.
3 A maximum of 75 repetitions
8 If an SQL database is restored to a library other than the one in which it was saved, the journals are not restored.
Purpose Notes:
1. To restore a save file to a library where it does not
The Restore Library (RSTLIB) command restores to the already exist, a user must have authority to the Create
system one or a group of libraries saved on diskette or tape Save File (CRTSAVF) command.
or it restores a user library saved on an optical volume or in
a save file. Any library that was saved by the Save Library 2. The RSTLIB command ignores all file overrides currently
(SAVLIB) command can be restored by this command. The in effect for the job, except the overrides for the restore
RSTLIB command restores the whole library, which includes output file.
the library description, object descriptions, and contents of
Restrictions:
the objects in the library.
1. This command is shipped with public *EXCLUDE
For job queues, message queues, output queues, data authority.
queues, and logical files, only the object descriptions are
2. The user of this command must have *SAVSYS
restored, because only the definitions are saved. Also,
authority specified in the user profile by the SPCAUT
logical file access paths may be restored if they were saved.
parameter, or must have all of the following:
More information on restoring access paths is in the DB2 for
AS/400 Database Programming book. a. Read and add authority for, or be the owner of,
each library specified.
This command can be used to restore libraries whose
b. Object existence authority for, or be the owner of,
objects had their storage freed by the corresponding SAVLIB
each object in the library if the object already exists
command of the restore operation, or libraries deleted by the
in the library on the system. Object existence and
Delete Library (DLTLIB) command. If the data portions of
use authority are required for message queue
the objects in the saved libraries were not freed, each library
objects. If the object does not exist, the user must
is copied into the same area of storage that it previously
have add authority for the user profiles that own
occupied. If the storage was freed, the system finds the
each object being restored. If the user does not
needed storage to store the library contents (the object
have the correct authority for all the libraries and
description and data portion of every file, module, program,
objects specified, only those for which the authority
service program, Structured Query Language (SQL)
has been given are restored.
package, and journal receiver in the library). If the library
does not exist on the system because it has been deleted or c. If VOL(*SAVVOL) is specified, use authority to the
is being restored on a different system, the system must find saved-from library.
the storage for everything that is in the library, including the d. Use authority for the save file is required when
library description. restoring libraries from a save file. Use authority for
the device description and the device file are
When the owner profile does not exist on the system, the
required when restoring libraries from a tape, a
user profile of the system default owner (QDFTOWN)
diskette, or an optical device.
becomes the default owner of any object being restored in
the system. 3. The current versions of programs on the system should
not be run while the library that contains those programs
If an object already exists in the library in which it is being is being restored. If any program is running while it is
restored, the public and private authorities of the existing being restored, the program will not be restored.
object are retained. If the object does not exist in the library,
4. When saving or restoring to an existing database file
all public authorities are restored, but private authorities must
using the OUTFILE parameter, the user must have
be granted again. For an existing output queue object that is
execute authority to the output file library.
actively spooling during the restore operation, or a data
queue that already exists in the library, the object is not Note: To see the parameter and value descriptions for this
restored, and a diagnostic message is sent. command, refer to the online help text. For more
information about printing the help text, refer to
If an object is being restored over an existing object on the “Printing CL Command Descriptions” in Chapter 1.
system, the object auditing value of the existing object is
kept. If the object is being restored as new to the system,
the object auditing value is restored from the media. Addi- Required Parameters
tionally, if the object is a library, the default auditing value for SAVLIB
each object created in the library is restored if the library is Specifies the name of the library, or the *NONSYS,
being restored as new; otherwise, the default auditing value *ALLUSR, or *IBM group of libraries, to be restored on
is restored from the media. the system. You cannot specify *NONSYS, *ALLUSR,
or *IBM if RSTLIB(*SAVLIB) is not specified.
Note: For values *NONSYS and *IBM, all other oper-
ations on the system must be ended before this
option is specified. This requires ending all sub-
systems through the End Subsystem *SAVF: The restore operation is done by using the save
(ENDSBS(*ALL)) command or End System file specified on the SAVF parameter.
(ENDSYS) command.
diskette-device-name: Specify the name of the diskette
*NONSYS: Libraries saved by the Save Library device that is used for the restore operation.
(SAVLIB) command with LIB(*NONSYS) specified are
optical-device-name: Specify the name of the optical
restored.
device used for the restore operation.
You can do a RSTLIB SAVLIB(*IBM) and a RSTLIB
tape-media-library-device-name: Specify the name of
SAVLIB(*ALLUSR) from a SAVLIB LIB(*NONSYS).
the tape media library device used for the restore opera-
*ALLUSR: All user libraries are restored. All libraries tion.
with names that do not begin with the letter Q are
tape-device-name: Specify the names of one or more
restored except for the following:
tape devices used for the restore operation. If more
#CGULIB #DSULIB #SEULIB than one tape device is used, specify the names of the
#COBLIB #RPGLIB devices in the order in which they are used. Using more
#DFULIB #SDALIB than one tape device permits one tape volume to be
Although the following Qxxx libraries are provided by rewound and unloaded while another tape device pro-
IBM, they typically contain user data that changes fre- cesses the next tape volume.
quently. Therefore, these libraries are considered "user
libraries", and are also restored:
Optional Parameters
| QDSNX QPFRDATA QUSRBRM QUSRSYS
| QGPL QRCL QUSRIJS QUSRVxRxMx VOL
| QGPL38 QS36F QUSRINFSKR Specifies the volume identifiers of the tape, diskette, or
| QMQMDATA QUSER38 QUSRNOTES optical volumes, or the cartridge identifier of a tape
| QMQMPROC QUSRADSM QUSRRDARS media library device, from which the objects are being
*IBM: Restores all system (IBM) libraries except for the restored. The volumes must be in the same order as
following: they were when the library was saved. If the library was
known to the system before the restore operation, the
| QDOC QINSYS QSPL QUSRBRM system can verify whether the volumes put on tape
| QDOCxxxx QMQMDATA QSRV QUSRIJS contain the current version of the library. The volume
| QDSNX QMQMPROC QSYS QUSRINFSKR
that contains the beginning of the file to be restored
| QGPL QPFRDATA QS36F QUSRNOTES
should be placed in the tape or diskette unit. More infor-
| QGPL38 QRCL QTEMP QUSRRDARS
| QINMEDIA QRECOVERY QUSER38 QUSRSYS mation on this parameter is in Appendix A, “Expanded
| QINPRIOR QRPLOBJ QUSRADSM QUSRVxRxMx Parameter Descriptions.”
Note: A different library name, in the format *MOUNTED: The library is restored from the volumes
QUSRVxRxMx, can be created by the user for that are currently placed in the device specified on the
each previous release supported by IBM to DEV parameter. For a media library device, the volume
contain any user commands to be compiled in a to be used is the next cartridge in the category mounted
CL program for the previous release. For the by the Set Tape Category (SETTAPCGY) command.
QUSRVxRxMx user library, VxRxMx is the The first version of the saved library that is found on the
version, release, and modification level of a pre- media is restored, unless a specific version is identified
vious release that IBM continues to support. by the SAVDATE parameter and SAVTIME parameter,
or for tape, the SEQNBR parameter.
The following libraries with names that do not begin with
the letter Q are also restored: Note: This value cannot be specified when using an
optical media library device.
#CGULIB #DSULIB #SEULIB
#COBLIB #RPGLIB *SAVVOL: The system, by using the save or restore
#DFULIB #SDALIB history information, determines which volumes contain
the most recently saved version of the library. If the
library-name: Specify the name of the library to restore.
device type specified in the DEV parameter does not
The library name must be the same name that was used
match the device type of the most recently saved
when the library was saved. The names QSYS, QSRV,
version of the library, an error message is sent to the
QTEMP, QSPL, QDOC, QDOC0002-QDOC0016,
user, and the function is ended. If *SAVVOL is speci-
QRPLOBJ, and QRECOVERY cannot be specified.
fied, the parameters SAVDATE and SAVTIME cannot be
DEV specified. IF *SAVVOL is specified, *SEARCH must be
Specifies the name of the device used for the restore specified on the SEQNBR parameter.
operation. The device name must already be known on volume-identifier: Specify the identifiers of one or more
the system by a device description. volumes in the order they are placed in the device and
used to restore the libraries.
STRLIB SAVF
Specifies the name of the starting library for a Specifies the qualified name of the save file used to
*NONSYS, *IBM, or *ALLUSR restore operation. restore the save data.
If an irrecoverable media error occurs during the restore The name of the save file can be qualified by one of the
operation, this parameter can be used to restart the following library values:
operation.
*LIBL: All libraries in the job's library list are
This parameter is valid only when *NONSYS, *IBM, or searched until the first match is found.
*ALLUSR is specified for the restore operation.
*CURLIB: The current library for the job is objects being restored. If verification fails, the
searched. If no library is specified as the current file is not restored.
library for the job, the QGPL library is used.
*MATCH: The saved members are restored if the lists
library-name: Specify the name of the library to be of the members where they exist match, member for
searched. member, the lists of the current system version.
*MATCH cannot be specified if *ALL is specified on the
save-file-name: Specify the name of the file from which ALWOBJDIF parameter.
to perform the restore operation.
*ALL: All members in the saved file are restored.
OPTION
*NEW: Only new members (members not known to the
Specifies how to handle restoring each object.
system) are restored.
*ALL: All the objects in the saved library are restored to
*OLD: Only members already known to the system are
the library. Old objects on diskette, tape, or in a save
restored.
file replace the current versions in the library on the
system, and the objects not having a current version are SAVDATE
added to the library on the system. Objects presently in Specifies the date the library was saved. If the most
the library but not on the media, remain in the library. recently saved version is not restored, or if more than
*NEW: Only the objects in the saved library that do not one saved version is on the volumes, enter the date that
exist in the current version of the library on the system specifies which version of the library is restored. The
are added to the library. Only objects not known to the date must be entered in the job date format. If separa-
library on the system are restored; known objects are tors (specified by the system value QDATSEP) are used,
not restored. This option restores objects that were the value must be enclosed in apostrophes. If a volume
deleted after they were saved or that are new to this identifier or VOL(*MOUNTED) is specified, but
library. If any saved objects have a version already in SAVDATE is not, the first version of the library found is
the library on the system, they are not restored, an infor- restored. This parameter is valid only if a volume identi-
mational message is sent for each object, and the fier is specified, VOL(*MOUNTED) is specified, or if a
restore operation continues. save file (SAVF parameter) is specified. Specify the
date when the file was saved.
*OLD: Only the objects in the library having a saved
version are restored; that is, the version of each object SAVTIME
currently in the library is replaced by the saved version. Specifies the time when the library was saved, if the
Only objects known to the library are restored. If any current version is not restored. The time can be speci-
saved objects are no longer part of the online version of fied with or without a time separator:
the library, they are not added to the library and an infor-
Without a time separator, specify a string of 4 or 6
mational message is sent for each object, but the restore
digits (hhmm or hhmmss) where hh = hours, mm =
operation continues.
minutes, and ss = seconds.
*FREE: The saved objects are restored only if they
With a time separator, specify a string of 5 or 8
exist in the library on the system with their space freed.
digits where the time separator specified for your job
The saved version of each object is restored on the
is used to separate the hours, minutes, and
system in its previously freed space. This option
seconds. If you enter this command from the
restores objects that had their space freed when they
command line, the string must be enclosed in apos-
were saved. If any saved objects are no longer part of
trophes. If a time separator other than the sepa-
the current version of the library, or if the space is not
rator specified for your job is used, this command
free for any object, the object is not restored and an
will fail.
informational message is sent for each object. The
restore operation continues, and all of the freed objects If a volume identifier or *MOUNTED is specified on the
are correctly restored. VOL parameter, but this parameter is not, the first
version of the library found on the volume is restored.
MBROPT
This parameter is valid only if the SAVDATE parameter
Specifies, for database files currently on the system,
is also specified.
which file members are restored.
This parameter is valid only if SAVDATE is also speci-
Note: If MBROPT(*MATCH) is used, the member list in
fied.
the saved file must match, member for member,
the current version in the system. All members ALWOBJDIF
are restored for files that do not exist. Before Specifies whether certain differences encountered during
restoring a file, the system verifies whether the a restore operation are allowed. The differences
file and member creation dates of the known include:
system objects match the creation dates of the
Ownership: The owner of an object on the system 2. For programs that do have a validation value
is different than the owner of an object from the stored on the media and the system fails to
save operation. recreate the program, the original version of the
program is restored and an entry is logged in
File creation date: The creation date of the data-
the security journal and job log.
base file on the system does not match the creation
date of the file that was saved. The informational message causes a diagnostic
message to be sent indicating that security or integ-
Member creation date: The creation date of the
rity changes occurred during the restore operation.
database file on the system does not match the cre-
This results in sending an escape message for the
ation date of the member that was saved.
restore operation.
Validation value verification: The validation value
If the user is restoring objects to a system different
created at the time an object was created does not
from the one on which they were saved and the
match the validation value created during the
objects are secured by an authorization list, speci-
restore operation of an object on a system with a
fying *ALL automatically links the objects to the
QSECURITY level of 40 or higher.
authorization list again. If the authorization list does
Authorization list linking: The object is being not exist on the new system, a message that
restored to a system different from the one on which includes the name of the missing list is issued and
it was saved. the public authority is set to *EXCLUDE.
If the objects are not observable, the objects are restored objects. More information on this parameter is
restored but are not converted. in Appendix A, “Expanded Parameter Descriptions.”
*ALL: All objects are converted regardless of their *NONE: No output listing is created.
current format. Even if the objects are in the current
*PRINT: The output is printed with the job's spooled
format, they are converted again. However, if the
output.
objects are not observable, the objects are not restored.
*OUTFILE: The output is directed to the database file
RSTLIB specified on the OUTFILE parameter.
Specifies whether the library contents are restored to the
Note: You must specify a database file name on the
same library in which they were saved, or to a different
OUTFILE parameter when OUTPUT(*OUTFILE)
library. If a different library is specified, the user cannot
is specified.
specify *NONSYS, *ALLUSR, or *IBM on the SAVLIB
parameter. OUTFILE
*SAVLIB: The library contents are restored to the same Specifies the qualified name of the database file to
library or libraries in which they were saved. which the information is directed when *OUTFILE is
specified on the OUTPUT parameter. If the file does not
library-name: Specify the name of the library where the exist, this command creates a database file in the speci-
saved library contents are being restored. If *NONSYS,
fied library. If a new file is created, the system uses
*ALLUSR, or *IBM is specified on the SAVLIB param-
QASRRSTO in QSYS with the format name QSRRST as
eter, a library name cannot be specified on this param-
a model.
eter.
The name of the database file can be qualified by one of
Note: If an SQL database is restored to a library other
the following library values:
than the one in which it was saved, the journals
are not restored. *LIBL: All libraries in the job's library list are
searched until the first match is found.
RSTASP
Specifies whether the libraries and objects are restored *CURLIB: The current library for the job is
to the same auxiliary storage pool (ASP) from which searched. If no library is specified as the current
they were saved or to another specific ASP. ASP 1 is library for the job, the QGPL library is used.
the system ASP. User ASPs can be configured as library-name: Specify the name of the library to be
ASPs 2 through 16. searched.
A user ASP can contain either:
database-file-name: Specify the name of the database
Libraries and all objects in the libraries. file to which output from the command is directed. If this
file does not exist, it is created in the specified library.
Journals, journal receivers, and save files for
More information on defining the format of database files
libraries in the system ASP.
as output files is in the DB2 for AS/400 Database Pro-
This parameter applies to all libraries that are specified. gramming book.
More information about user ASPs is in the Backup and
OUTMBR
Recovery book. Specifies the name of the database file member to which
Attention: the output is directed. This parameter is valid only if
OUTPUT(*OUTFILE) is specified.
System or product libraries (libraries that begin with a Q
or #) must not be created in or restored to a user ASP. Element 1: Member to Receive Output
Doing so can cause unpredictable results.
*FIRST: The first member in the file receives the output.
*SAVASP: The objects are restored to the same auxil- If OUTMBR(*FIRST) is specified and the member does
iary storage pools from which they were saved. not exist, the system creates a member with the name of
the file specified on the OUTFILE parameter.
asp-identifier: Specify the ASP identifier. When the
specified ASP is 1, the objects are restored to the member-name: Specify the file member that receives
system ASP, and when the specified ASP is 2 through the output. If OUTMBR(member-name) is specified and
16, the objects are restored to the user-defined ASP the member does not exist, the system creates it.
specified by the identifying number.
If the member exists, the user can add records to the
OUTPUT end of the existing member or clear the existing member
Specifies whether a listing that shows information about and add the records.
the status of the object is created and directed to an Element 2: Operation to Perform on Member
output file. The listing shows the restore information and
*REPLACE: The existing records in the specified data-
shows all objects, restored, not restored, and excluded.
base file member are replaced by the new records.
Information about each object's security is listed for the
*ADD: The new records are added to the existing infor- save must be loaded. An inquiry message instructs the user
mation in the specified database file member. to load the tape containing MIKESLIB. If necessary, the
same message is sent until the tape containing MIKESLIB is
INFTYPE
found.
Specifies the type of information directed to the data-
base file. This parameter is valid only if Example 4: Restoring a Version From a Specific Date
OUTPUT(*OUTFILE) is specified. and Time
*OBJ: The list contains an entry for each object RSTLIB SAVLIB(PAYROLL) DEV(TAPð1) SAVDATE(ð6ð193)
requested to be restored. SAVTIME(1ð3214) RSTLIB(OLDPAY) VOL(PAY)
*MBR: The list contains an entry for each object or, for
This command restores the version of the PAYROLL library
database files, each member requested to be restored.
from the device TAP01, whose volume identifier is PAY. The
OPTFILE version to be restored was saved at 10:32:14 on the date
Specifies the path name of the optical file that is used 06/01/93. All of the objects in the saved PAYROLL library
for the restore operation, beginning with the root direc- are restored to the library OLDPAY. All new files are
tory of the volume. For more information on specifying restored. Old files are restored only if the member lists of
path names, refer to Chapter 2, “Path Names the files on the tape match the member lists of the files on
(*PNAME).” the system.
Note: This parameter is required when using an optical Example 5: Restoring From Multiple Tape Volumes
device.
RSTLIB SAVLIB(QGPL) DEV(TAPð1) VOL(QGPL QGPL)
Example 3: Specifying Where the Restore Operation Example 8: Restoring a Library From a Save File
Begins RSTLIB SAVLIB(LIB1) DEV(\SAVF) SAVF(SAVF1)
RSTLIB SAVLIB(\NONSYS) DEV(TAPð1) STRLIB(MIKESLIB)
This command restores library LIB1 from the save file
This command restores the saved nonsystem libraries begin- SAVF1.
ning with library MIKESLIB from the tape device, TAP01.
The nonsystem libraries are saved in alphabetic order. Example 9: Restoring to a User-Defined ASP
Therefore, all libraries beginning with and following the name RSTLIB SAVLIB(LIB1) DEV(\SAVF) SAVF(SAVF1)
MIKESLIB are restored. The first tape of the nonsystem RSTASP(2)
This command restores the library named LIB1 from the save ASP 2 does not exist on the system.
file named SAVF1. The library and all objects in the saved
There are object types in the library which cannot be
version of LIB1 are restored to ASP 2 unless:
restored to user ASPs. These objects will not be
The library already exists in a different ASP. restored.
ASP 2 contains a journal, journal receiver, or SAVF
which is part of a library in the system ASP.
(P) ────────────────────────────────────5
55──RSTLICPGM──LICPGM(──licensed-program──)──DEV(──┬─\SAVF──────────────────────────┬──)────
├─optical-device-name────────────┤
├─tape-media-library-device-name─┤
│ ┌──
──────────────────┐ │
└──6─tape-device-name─┴───
(1) ────────┘
5──┬───────────────────────────────────────────┬──┬───────────────────────────────────────────────────┬─────────────────────────5
│ (6) ──────────────┐
┌─\MOUNTED─── │ │ ┌─\BASE─────────────────────────────┐ │
│ │ ┌──
───────────────────┐ │ │ └─OPTION(──┴─number-of-licensed-program-option─┴──)─┘
(2, 7) 6 (3)
└─VOL(──────┴───volume-identifier─┴────┴──)─┘
5──┬──────────────────────┬──┬───────────────────────────┬──┬──────────────────────────────────────────┬────────────────────────5
│ ┌─\ALL─┐ │ │ ┌─\PRIMARY─────┐ │ │ ┌─\SEARCH──────────────┐ │
(2, 7) ─┴─file-sequence-number─┴──)─┘
└─RSTOBJ(──┼─\PGM─┼──)─┘ └─LNG(──┼─\SAVVOL──────┼──)─┘ └─SEQNBR(─────
└─\LNG─┘ └─feature-code─┘
5──┬─────────────────────────────┬──┬───────────────────────────────────────────────┬──┬────────────────────────┬───────────────5
│ ┌─\REWIND─┐ │ │ ┌─\LIBL/────────┐ │ │ ┌─\NONE──┐ │
(2, 7) ─┼─\LEAVE──┼──)─┘ └─SAVF(───
└─ENDOPT(───── (4) ─┼─\CURLIB/──────┼──save-file-name──)─┘ └─OUTPUT(──┴─\PRINT─┴──)─┘
└─\UNLOAD─┘ └─library-name/─┘
5──┬────────────────────────────┬──┬───────────────────────────────────┬──┬──────────────────────────────────┬──────────────────5
│ ┌─\FIRST────────┐ │ │ ┌─\ONLY─────────┐ │ │ ┌─\SAME───────────────┐ │
└─RLS(──┴─release-level─┴──)─┘ └─REPLACERLS(──┼─\NO───────────┼──)─┘ │ │ ┌──
──────────────┐ │ │
└─release-level─┘ 6 (5)
└─LIB(──┴───library-name─┴────┴──)─┘
5──┬──────────────────────────────┬──┬──────────────────────────┬───────────────────────────────────────────────────────────────5
│ ┌─\SAME────────┐ │ │ ┌─\SAME───────┐ │
└─LNGLIB(──┴─library-name─┴──)─┘ └─FLR(──┴─folder-name─┴──)─┘
5──┬───────────────────────────────────────────────────────────────┬────────────────────────────────────────────────────────────5
| │ ┌──
─────────────────────────────────┐ │
| │ │┌─\SAME─────────────────────────┐│ │
| └─CODHOMEDIR(──── 6
(10) ─┬──┴─code-home-directory-path-name─┴┴───
(8) ─┬──)─┘
| └─\PROMPT────────────────────────────────┘
5──┬──────────────────────────────────────────────────────────────────┬──┬───────────────────────────────────┬─────────────────5%
| │ ┌──
─────────────────────────────────────┐ │ │ ┌─\SYSVAL────────┐ │
| │ │┌─\SAME─────────────────────────────┐│ │ └─FRCOBJCVN(──┼─\NO────────────┼──)─┘
| (9) 6 (8)
└─LNGHOMEDIR(────┬──┴─language-home-directory-path-name─┴┴────┬──)─┘ │ ┌─\RQD─┐ │
| └─\PROMPT────────────────────────────────────┘ └─\YES──┴─\ALL─┴─┘
Notes:
1 A maximum of 4 repetitions for tape device names.
3 A maximum of 50 repetitions.
5 A maximum of 11 repetitions
6 This value cannot be specified when using an optical media library device.
6. Some licensed programs can only be restored if the user to be used is the next cartridge in the category mounted
is enrolled in the system distribution directory. See the by the Set Tape Category (SETTAPCGY) command.
publication for each licensed program for a description of
volume-identifier: Specify the identifiers of one or more
this restriction.
volumes in the order they are mounted on the device
7. This command does not restore code and language and used to restore the licensed program.
objects for the base OS/400 system.
OPTION
8. This command does not support the use of other ASPs Specifies which licensed program option to restore.
(auxiliary storage pools). All objects supplied by a
*BASE: Only the base part of the licensed program is
licensed program must remain in the system ASP.
restored.
number-of-licensed-program-option: Specify the number
Required Parameters associated with the optional part of the listed licensed
LICPGM program being restored.
Specifies the 7-character identifier of the licensed
RSTOBJ
program being restored. A list of IBM-supplied licensed
Specifies the type of licensed program objects being
programs is in the Software Installation book.
restored.
DEV *ALL: All objects of the licensed program are restored.
Specifies the name of the device from which the This includes both the program objects and the language
licensed program objects are restored. The device objects.
name must be known by a device description on the
system. If multiple devices are specified, they must If a tape device is specified on the DEV parameter, then
have compatible media formats. the RSTOBJ(*ALL) value is used when the saving of the
licensed program has been done with the SAVLICPGM
Up to four device names can be specified. Use the command such that the language objects immediately
Work with Device Descriptions (WRKDEVD) command follow the program objects on the tape media. If the lan-
to display the names of the tape devices available on guage objects (*LNG) and programming objects (*PGM)
this system. Only one save file name can be specified. are not in consecutive order on the distribution tape,
*SAVF: The restore operation is done using the save *ALL cannot be used in most cases. Instead, the
file name specified on the SAVF parameter. program and language objects must be restored sepa-
rately. The DSPTAP command can be used to deter-
optical-device-name: Specify the name of the optical
mine the order of the objects on the tape. An example
device that supports the CD-ROM media class used for
of how to restore language and program objects sepa-
the restore operation.
rately is in the "Examples" section at the end of this
tape-media-library-device-name: Specify the name of command.
the media library device used for the restore operation.
If *SAVF is specified on the DEV parameter, then the
tape-device-name: Specify the names of one or more RSTOBJ(*ALL) value can be used when the saving of
tape devices used for the restore operation. If multiple the licensed program has been done with the
tape devices are used, they must have compatible SAVLICPGM command using OBJTYPE(*ALL).
media formats and their names must be specified in the
*PGM: Only the program objects for the licensed
order in which they are used. Using more than one tape
program are restored. This value is used when restoring
device permits one tape volume to be rewound and
the program objects from the distribution media where
unloaded while another tape device processes the next
the program objects and the selected language objects
tape volume.
are not on the same distribution media or are not in con-
secutive order.
Optional Parameters *LNG: The objects associated with the language identi-
VOL fied by the language feature indicated on the LNG
Specifies the volume identifiers of the tape volumes from parameter are restored.
which the licensed program is restored. The volumes LNG
must be installed on the device in the same order they Specifies the language to be used for restoring the
were in when the licensed program was saved. The licensed program. If the language feature of the
volume that contains the beginning of the file to be licensed program on the save media matches the
restored should be mounted on the device. A maximum system language feature, the language objects are
of 50 entries can be specified. restored to the licensed program's libraries. If the lan-
*MOUNTED: The licensed program is restored from the guage features do not match, the language objects are
volumes that are mounted on the device specified on the restored into the multilingual library for that language
DEV parameter. For a media library device, the volume feature.
*PRIMARY: The language feature of the operating shows all objects, restored, not restored, and excluded.
system is restored for the specified product. Information about each object's security is listed for the
restored objects. More information on this parameter is
Note: Use the GO LICPGM function with option 20 to
in Appendix A, “Expanded Parameter Descriptions.”
display the primary language of the operating
system. *NONE: No output is created.
*SAVVOL: The language file on the mounted volume is *PRINT: The output is printed with the job's spooled
to be restored for the licensed program specified by the output.
user. This option is not valid with DEV(*SAVF).
RLS
feature-code: Specify the language feature identifier for Specifies the version, release, and modification level of
the language file that is to be restored for the licensed the product being restored.
program specified by the user. More information on
*FIRST: The first version, release, and modification
feature identifications and a list of the IBM-supplied
level found on the distribution media is restored.
feature codes is in the &sftinst..
release-level: Specify the release level in VxRyMz
SEQNBR
format, where Vx is the version number, Ry is the
Specifies which sequence number to use for the restore
release number, and Mz is the modification level. The
operation.
variables x and y can be a number from 0 through 9,
*SEARCH: The volume on the device is searched for a and the variable z can be a number from 0 through 9 or
data file for the licensed program; when a match is a letter from A through Z.
found, the objects are restored.
REPLACERLS
| file-sequence-number: Specify the sequence number of Specifies the version, release, and modification level of
| the file. Valid values range from 1 through 16777215. the product being replaced.
ENDOPT *ONLY: Replace only the version, release, and modifi-
Specifies the operation that is automatically done in the cation level of the product currently installed.
tape volume after the restore operation ends. If more
*NO: The product currently installed on the system is
than one reel is included, this parameter applies only to
not replaced. The product being restored must be a dif-
the last reel used; all other reels are rewound and
ferent release than the product currently installed. If the
unloaded when the end of tape is reached.
product being restored exists in the same libraries as the
*REWIND: The tape is automatically rewound, but not installed product, then an override parameter must be
unloaded, after the operation has ended. specified indicating to which libraries the product is
restored.
*LEAVE: The tape is not rewound. Another restore
operation can start at the current position on the tape. release-level: Specify the release level in VxRyMz
format, where Vx is the version number, Ry is the
*UNLOAD: The tape is automatically rewound and
release number, and Mz is the modification level. The
unloaded after the restore operation has ended.
variables x and y can be a number from 0 through 9,
SAVF and the variable z can be a number from 0 through 9 or
Specifies the qualified name of the save file containing a letter from A through Z.
the product.
LIB
The name of the save file can be qualified by one of the Specifies the libraries into which the product is being
following library values: restored. This function is not supported by all products.
*LIBL: All libraries in the job's library list are *SAME: The product is restored into the library speci-
searched until the first match is found. fied by the vendor.
*CURLIB: The current library for the job is library-name: Specify the name of the library into which
searched. If no library is specified as the current the product is being restored.
library for the job, the QGPL library is used.
LNGLIB
library-name: Specify the name of the library to be Specifies the secondary language library into which the
searched. product is being restored. This function is not supported
by all products.
save-file-name: Specify the name of the save file.
*SAME: The product is restored into the secondary lan-
OUTPUT
guage library specified by the vendor.
Specifies whether a listing that shows information about
the status of the object is created and directed to an library-name: Specify the name of the secondary lan-
output file. The listing shows the restore information and guage library into which the product is restored.
FLR Notes:
Specifies the name of the root folder into which the
1. This parameter applies only to user objects of the
product is being restored. This function is not supported
*MODULE, *PGM, *SRVPGM, and *SQLPKG object
by all products.
types.
*SAME: The root folder specified by the vendor is used.
2. An object must be observable (have the required
folder-name: Specify the name of the root folder. observable information) in order to be converted.
| CODHOMEDIR 3. If an object needs to be converted (because it is for-
| Specifies the directories into which the code part of the matted for an earlier version of the operating
| product is being restored. This function is not supported system), but is not converted during this restore
| by all products. operation, the object is automatically converted the
first time it is used.
| Note: This parameter is mutually exclusive with the
| FLR parameter. Element 1: Force Conversion
| *SAME: The code part of the product is restored into *SYSVAL: The objects are converted based on the
| the directories specified when packaged or already value of the QFRCCVNRST system value.
| installed. *SAME may be specified as the only param-
Note: If this value is specified or defaulted and the
| eter value or within a list of directories. If used within a
system value QFRCCVNRST has a value of "1,"
| list, *SAME specifies that a particular directory is
the restore operation proceeds as if
| unchanged, though other directories may be different
FRCOBJCVN(*YES *RQD) is specified.
| than when the product was packaged or previously
| installed. *NO: The objects are not converted during the restore
operation.
| *PROMPT: The code directories to be used are dis-
| played. If the product is not currently installed, the direc- *YES: The objects are converted during the restore
| tory names can be changed. operation.
| path-name: Specify the home path directory name into Note: Specifying this value increases the time of the
| which the code part of the product is being restored. Up restore operation, but avoids the need to convert
| to 300 directories may be specified. For directory name the objects when they are first used.
| entries which are unchanged, *SAME can be specified
Element 2: Objects to Convert
| for the path name.
*RQD: The objects are converted only if they require
| LNGHOMEDIR conversion to be used by the current operating system.
| Specifies the directories into which the language part of If the objects are not observable, the objects are
| the product is being restored. This function is not sup- restored but are not converted.
| ported by all products.
*ALL: All objects are converted regardless of their
| Note: This parameter is mutually exclusive with the current format. Even if the objects are in the current
| FLR parameter. format, they are converted again. However, if the
| *SAME: The language part of the product is restored objects are not observable, the objects are not restored.
| into the directories specified when packaged or already
RSTLICPGM Examples
| installed. *SAME may be specified as the only param-
| eter value or within a list of directories. If used within a
Example 1: Restoring Program Using Defaults
| list, *SAME specifies that a particular directory is
| unchanged, though other directories may be different RSTLICPGM LICPGM(5716CD1) DEV(TAPð1)
| than when the product was packaged or previously
This command restores the CoOperative Development
| installed.
Environment/400 (CODE/400) licensed program to the
| *PROMPT: The language directories to be used are dis- system. The tape containing the licensed program objects
| played. If the product is not currently installed, the direc- must be put on the TAP01 tape drive. Because no other
| tory names can be changed. parameters are specified, the defaults are used for the
| path-name: Specify the home path directory name into command.
| which the language part of the product is being restored.
Example 2: Restoring a Third Version of a Product
| Up to 300 directories may be specified. For directory
| name entries which are unchanged, *SAME can be RSTLICPGM LICPGM(1MYPROD) OPTION(\BASE) DEV(TAPð1)
| specified for the path name. RLS(V3R6Mð) REPLACERLS(\NO) LIB(A B C)
Example 3: Restoring One Version of a Product Over This command restores the CODE/400 licensed program to
Another Version the system from the save file MYSAVF in MYLIB. Because
RSTLICPGM LICPGM(2MYPROD) OPTION(\BASE) DEV(TAPð1) no other parameters are specified, the defaults are used for
RLS(\FIRST) REPLACERLS(\ONLY) the command.
This command restores the first version release modification Example 5: Restoring a Third Version of a Product From
level of the base part of the 2MYPROD product that is found a Save File
on the tape in the TAP01 drive. It does not matter if the RSTLICPGM LICPGM(1MYPROD) OPTION(\BASE) DEV(\SAVF)
version release modification level of the base of the product RLS(V3R6Mð) REPLACERLS(\NO) LIB(A B C)
on the tape matches the version release modification level of SAVF(MYLIB/MYSAVF)
the base of the product on the system.
This command restores the base part of the V3R6M0
Example 4: Restoring Product From Save File 1MYPROD product to the system from save file MYSAVF in
RSTLICPGM LICPGM(5716CD1) DEV(\SAVF) MYLIB if the base of the V3R6M0 1MYPROD product is not
SAVF(MYLIB/MYSAVF) currently installed on the system.
55──RSTOBJ──OBJ(──┬─\ALL────────────────────────────┬──)──SAVLIB(──library-name──)──────────────────────────────────────────────5
│ ┌──
──────────────────────────┐ │
└──6─┬─generic\-object-name─┬─┴───
(1) ─┘
└─object-name──────────┘
5──DEV(──┬─\SAVF──────────────────────────┬──)──┬────────────────────────────────────┬──────────────────────────────────────────5
├─diskette-device-name───────────┤ │ ┌─\ALL────────────┐ │
├─optical-device-name────────────┤ │ │ ┌──
─────────────┐ │ │
├─tape-media-library-device-name─┤ (3) 6
└─OBJTYPE(────┴───object-type─┴─┴──)─┘
│ ┌──
──────────────────┐ │
└──6─tape-device-name─┴───
(2) ────────┘
5──┬───────────────────────────────────────┬──┬───────────────────────────┬──┬─────────────────────────────────────────────┬────5
│ ┌─\SAVLIB──────────────┐ │ │ ┌─\REWIND─┐ │ │ ┌─\LIBL/────────┐ │
(8) ─┴─data-file-identifier─┴──)─┘ └─ENDOPT(───
└─LABEL(─── (7) ─┼─\LEAVE──┼──)─┘ └─SAVF(──┼───────────────┼──save-file-name──)─┘
└─\UNLOAD─┘ ├─\CURLIB/──────┤
└─library-name/─┘
5──┬────────────────────────┬───────────────────────────────────────────────────────────────────────────────────────────────────5
│ ┌─\ALL───┐ │
(9) ┼──)─┘
└─OPTION(──┼─\NEW───
├─\OLD───┤
└─\FREE──┘
5──┬────────────────────────────────────────────────────────────────────────────────────────────────┬───────────────────────────5
│ ┌──
────────────────────────────────────────────────────────────────────────┐ │
│ │ ┌─\ALL───────────────┐ ┌─\ALL─────────────────────────────────┐ │ │
└─FILEMBR(──── 6
(10) ───(──┴─database-file-name─┴──┼──────────────────────────────────────┼──)─┴────
(11) ──)─┘
├─\NONE────────────────────────────────┤
│ ┌──
────────────────────────┐ │
└─(───6┬─generic\-member-name─┬┴────
(11) ──)─┘
└─member-name──────────┘
5──┬────────────────────────┬──┬─────────────────────────────────┬──┬─────────────────────────────────┬─────────────────────────5
│ ┌─\MATCH─┐ (12) ─date-when-saved──)─┘ └─SAVTIME(────
│ └─SAVDATE(──── (12) ─time-when-saved──)─┘
└─MBROPT(──┼─\ALL───┼──)─┘
├─\NEW───┤
└─\OLD───┘
5──┬────────────────────────────┬──┬───────────────────────────────────┬──┬──────────────────────────────┬──────────────────────5
│ ┌─\NONE───┐ │ │ ┌─\SYSVAL────────┐ │ │ ┌─\SAVLIB──────┐ │
(13) ┴──)─┘ └─FRCOBJCVN(──┼─\NO────────────┼──)─┘ └─RSTLIB(──┴─library-name─┴──)─┘
└─ALWOBJDIF(──┴─\ALL────
│ ┌─\RQD─┐ │
└─\YES──┴─\ALL─┴─┘
5──┬────────────────────────────────┬──┬──────────────────────────┬─────────────────────────────────────────────────────────────5
│ ┌─\SAVASP────────┐ │ │ ┌─\NONE────┐ │
└─RSTASP(──┴─asp-identifier─┴──)─┘ └─OUTPUT(──┼─\PRINT───┼──)─┘
└─\OUTFILE─┘
5──┬───────────────────────────────────────────────────────┬──┬──────────────────────────────────────────────┬──────────────────5
│ ┌─\LIBL/────────┐ │ │ ┌─\FIRST──────┐ ┌─\REPLACE─┐ │
(14) ─┼───────────────┼──database-file-name──)─┘ └─OUTMBR(────
└─OUTFILE(──── (14) ─┴─member-name─┴──┼──────────┼──)─┘
├─\CURLIB/──────┤ └─\ADD─────┘
└─library-name/─┘
5──┬──────────────────────────┬──┬──────────────────────────────────────────┬──────────────────────────────────────────────────5%
│ ┌─\OBJ─┐ (15) ─'optical-file-path-name'──)─┘
│ └─OPTFILE(────
(14) ─┴─\MBR─┴──)─┘
└─INFTYPE(────
Notes:
1 A maximum of 300 repetitions
2 A maximum of 4 repetitions
3 A list of the valid OS/400 object types for this command is in Appendix A.
4 This value cannot be specified when using an optical media library device.
5 A maximum of 75 repetitions
If logical file access paths were saved (ACCPTH(*YES) was 3. When saving or restoring to an existing database file
specified when the objects were saved), the access paths using the OUTFILE parameter, the user must have
are restored if (1) all based-on physical files are also being execute authority to the output file library.
restored by the same restore command, (2) the logical file is 4. With the exception of overrides for the restore listing file
also being restored by the same restore command, or the and database files specified on the OUTFILE parameter,
logical file already exists on the system (the same file exists, this command ignores all file overrides that are currently
not a re-created version), and (3) MAINT(*IMMED or *DLY) in effect for the job.
is in effect for the logical file if it still exists on the system.
5. To use this command, the user must have the special
If the storage was freed, the system finds the storage space authority *SAVSYS, specified in the user profile
needed to store the contents (only the data portion) of each (SPCAUT parameter), or the following:
file, module, program, service program, journal receiver, and Add and execute authority for the specified library
Structured Query Language (SQL) package. If the objects and save file library.
Object existence authority for, or be the owner of, *ALL: All the objects saved from the specified library
each object specified if the object already exists in are restored, depending on the values specified for the
the library on the system. Object existence OBJTYPE and OPTION parameters.
authority and use authority are required for message
generic*-object-name: Specify the generic name of the
queue objects. If the object does not already exist
object. A generic name is a character string of one or
in the library on the system, the user must have add
more characters followed by an asterisk (*); for example,
authority for the user profiles that own each object
ABC*. The asterisk (*) substitutes for any valid charac-
being restored.
ters. A generic name specifies all objects with names
If VOL(*SAVVOL) is specified, use authority to the that begin with the generic prefix, for which the user has
saved-from library. authority. If an asterisk is not included with the generic
(prefix) name, the system assumes it to be the complete
6. The RSTOBJ command does not restore the library's
object name. For more information on the use of
data dictionary or its associated database files. To do
generic functions, refer to “Rules for Specifying Names.”
this, the RSTLIB command must be used.
7. The user must have use authority for the save file to
object-name: Specify one or more names of specific
objects to restore. Both generic names and specific
restore from the save file. In addition, the user must
names can be specified in the same command.
have use authority for the device description when
restoring from tape, diskette, or optical device. SAVLIB
8. If this command is used to restore a program, the copy Specifies the name of the library from which the objects
of that program that is currently in the system must not were saved. If RSTLIB is not specified, this is also the
be running while the program is being restored. If this name of the library to which the objects are restored.
occurs, the running program will not be restored. DEV
9. Objects saved by separate commands must also be Specifies the name of the device used to restore the
restored by separate commands. If a single command is objects. The device name must already be known on
used, some of the objects are not restored. the system by a device description.
10. If the user domain object user space (*USRSPC), user *SAVF: The restore operation is done using the save
index (*USRIDX), or user queue (*USRQ) is restored to file specified on the save file (SAVF) parameter.
a library that is not permitted in the system value diskette-device-name: Specify the name of the diskette
QALWUSRDMN (allow user domain objects in libraries), device used to restore objects.
the object is converted to the system domain.
optical-device-name: Specify the name of the optical
Note: To see the parameter and value descriptions for this device used for the restore operation.
command, refer to the online help text. For more
information about printing the help text, refer to tape-media-library-device-name: Specify the name of
“Printing CL Command Descriptions” in Chapter 1. the tape media library device used for the restore opera-
tion.
If the OBJTYPE parameter is not specified when the *ALL: All object types that are specified by name and
command is run, all of the object types listed in the that were saved from the specified library are restored.
description of the OBJTYPE parameter are restored, if If *ALL is also specified for the OBJ parameter, then all
they are in the specified library on the media or in the objects saved for that library are restored.
save file and have the specified names. object-type: Specify the value for each of the types of
objects that are restored (such as command (*CMD), file
(*FILE), or program (*PGM)). This value can be
repeated; the maximum repetitions varies depending on If the characteristics of the device specified in the
the environment. DEV parameter do not match the device and
location of the most recently saved version of the
The object types that can be restored also can be saved
library, an error message is sent to the user, and
and restored by the Save Library (SAVLIB), Save
the function is ended.
Change Object (SAVCHGOBJ), Save Object (SAVOBJ),
Restore Library (RSTLIB), and Restore Licensed If the wrong volume is placed in a device in the
Program (RSTLICPGM) commands. Data dictionaries location specified by the command, a message is
(*DTADCT) are only restored with the RSTLIB sent to the system operator that identifies the first
command. Other object types can be saved only by the volume that must be placed in the device before the
Save System (SAVSYS) command and restored by the objects can be restored.
OS/400 system restore operation, or saved by the Save
When OBJ(*ALL) and OBJTYPE(*ALL) is specified,
Document Library Object (SAVDLO) command and
the objects are considered in the order they would
restored by the Restore Document Library Object
appear in a display produced by the Display Library
(RSTDLO) command.
(DSPLIB) command. The object names and types
Note: *CFGL object types can be restored using the specified in the RSTOBJ command are used to
RSTOBJ command only from objects saved on determine which file of saved objects is used in the
releases prior to V2R2M0. *CFGL object types restore operation. One file is produced for each
saved on V2R2M0 and newer releases are SAVLIB or SAVOBJ command run. The file chosen
restored using the Restore Configuration is the one in which the first considered object was
(RSTCFG) command. last saved. Objects that were not saved in the file
chosen to be processed, or that were more recently
VOL
saved, are not restored; an error message is sent to
Specifies the volume identifiers of the tape, diskette, or
the user for each unrestored object.
optical volumes, from which the objects are being
restored. The volumes must be in the same order as If *SAVVOL is specified, the SAVDATE and
they were when the library was saved. If the library was SAVTIME parameters cannot be specified.
known to the system before the restore operation, the If *SAVVOL is specified and the RSTLIB value is
system can verify whether the volumes put on tape equal to the SAVLIB value, OPTION(*NEW) cannot
contain the current version of the library. The volume be specified.
that contains the beginning of the file to be restored
If *SAVVOL is specified, SEQNBR(*SEARCH) and
should be placed in the tape or diskette unit. More infor-
LABEL(*SAVLIB) must be specified.
mation on this parameter is in Appendix A, “Expanded
Parameter Descriptions.” volume-identifier: Specify the identifiers of one or more
Note: The version of the objects that is restored is the volumes in the order in which they are placed in a
first version found in the specified location, device and used to restore the objects.
unless a specific version is identified on the
SEQNBR
SAVDATE and SAVTIME parameters.
Specifies, only when tape is used, the sequence number
*MOUNTED: The objects are restored from the volumes used for the restore operation.
placed in the device specified on the DEV parameter.
*SEARCH: The volume on a tape device is searched
For a media library device, the volume to be used is the
for a data file with an identifier that is a match for the
next cartridge in the category mounted by the Set Tape
SAVLIB parameter value; when a match is found, the
Category (SETTAPCGY) command.
object is restored. If the last operation on the device
Note: This value cannot be specified when using an specifies ENDOPT(*LEAVE) (that is, the tape is posi-
optical media library device. tioned at the location where the last operation ended),
the file search starts with the first data file beyond the
*SAVVOL: The system, using the save/restore history
current tape position. If ENDOPT(*LEAVE) was not
information, determines which volumes contain the most
used for the last operation (or if the tape was manually
recently saved version of the objects.
rewound after an ENDOPT(*LEAVE) operation), the
Note: If this is a restore from an optical device, only the search starts with the first data file on the volume.
first 6 characters of the volume name are avail-
able. If the volume name of the optical media
| sequence-number: Specify the sequence number of the
| file. Valid values range from 1 through 16777215.
exceeds 6 characters, the volume may not be
found. You should specify the complete volume LABEL
or file name on the command instead of using Specifies the name that identifies the data file on the
VOL(*SAVVOL) when the name of the optical tape or diskette used for the restore operation. This
media exceeds 6 characters. label must have been specified on the save command.
When *SAVVOL is specified, the following operational
characteristics and restrictions apply:
*SAVLIB: The file label is the name of the library speci- *OLD: Only objects in the library that have a saved
fied on the SAVLIB parameter. version are restored; the current version of each object
is replaced by the saved version. Only objects known to
data-file-identifier: Specify the data file identifier (up to
the library are restored. If any saved objects are no
17 characters) of the data file used for the restore opera-
longer part of the current version of the library, they are
tion. This option is valid only for a single library restore.
not added to the library; an informational message is
ENDOPT sent for each object, but the restore operation continues.
Specifies, when tape is used, what positioning operation
*FREE: The saved objects are restored only if they
is automatically done on the tape volume after the
exist in the library in the system with their space freed.
restore operation ends. If more than one volume is
The saved version of each object is restored in the
included, this parameter applies only to the last tape
system in its previously freed space. This option
volume used; all other tape volumes are rewound and
restores objects that had their space freed when they
unloaded when the end of the tape is reached.
were saved. If any saved objects are no longer part of
*REWIND: The tape is automatically rewound, but not the current version of the library, or if the space is not
unloaded, after the operation has ended. free for any object, the object is not restored and an
informational message is sent for each object. The
*LEAVE: The tape does not rewind or unload after the
restore operation continues and all of the freed objects
operation ends. It remains at the current position on the
are correctly restored.
tape drive.
*UNLOAD: The tape is automatically rewound and FILEMBR
unloaded after the operation ends. Specifies the database file members to restore. This
parameter is made up of two parts: the file name and
SAVF the member name. This parameter cannot be specified
Specifies the qualified name of the save file that con- if MBROPT(*MATCH) is specified.
tains the save data for the objects that are restored.
Notes:
The name of the save file can be qualified by one of the
following library values: 1. Each database file specified on the FILEMBR
parameter must also be specified on the OBJ
*LIBL: All libraries in the job's library list are parameter by either its complete name, a generic
searched until the first match is found. name, or *ALL.
*CURLIB: The current library for the job is 2. The OBJTYPE parameter value must be *ALL, or it
searched. If no library is specified as the current must include the *FILE value.
library for the job, the QGPL library is used.
3. Generic names are not valid for the database file
library-name: Specify the name of the library to be name, but are allowed for the member name.
searched.
4. Duplicate file names are not allowed.
save-file-name: Specify the name of the save file from
Element 1: Database File Names
which to perform the restore.
*ALL: The member list following this value applies to all
OPTION
files specified on the OBJ parameter.
Specifies how to handle restoring each object.
database-file-name: Specify the name of the database
*ALL: All the objects in the saved library are restored to
file that contains the members to be restored. Up to 50
the library. All objects in the saved library are restored
of the file/member combinations can be specified for a
to the library on the system. Objects in the saved library
single command.
replace the objects in the library on the system. Saved
objects not on the system are added to the library on the Element 2: Member Names
system. Objects in the system library but not in the *ALL: All members are restored from the specified file.
saved library remain in the library.
*NONE: No members are restored from the specified
*NEW: Only the objects in the saved library that do not file. Only the file description is restored.
exist in the current version of the library in the system
are added to the library. Only objects not known to the
generic*-member-name: Specify the generic name of
the members to be restored from the specified file. A
library in the system are restored; known objects are not
generic name is a character string of one or more char-
restored. This option adds objects that were deleted
acters followed by an asterisk (*); for example, ABC*.
after they were saved or that are new to this library. If
The asterisk substitutes for any valid characters. A
any saved objects have a current version in the library in
generic name specifies all objects with names that begin
the system, they are not restored; an informational
with the generic prefix, for which the user has authority.
message is sent for each object, but the restore opera-
If an asterisk is not included with the generic (prefix)
tion continues.
name, the system assumes it to be the complete object
name. For more information on the use of generic func- QDATSEP, are used, the value must be enclosed in
tions, refer to “Rules for Specifying Names.” apostrophes. If a volume identifier or VOL(*MOUNTED)
is specified, but SAVDATE is not, the restored version of
member-name: Specify the name of the member to be
the objects is the first version found on the volume. This
restored from the specified file.
parameter is valid only if a volume identifier or
Notes: VOL(*MOUNTED) is specified, or if a save file (SAVF
parameter) is specified. Specify the date when the
1. If the nongeneric member names are specified, all
objects were saved.
specified members must exist in the file in order for
any part of the file to be restored. SAVTIME
2. If generic member names are specified, the file is Specifies the time that the objects were saved.
not restored if it does not contain any members that The time can be specified with or without a time sepa-
match the generic names. For example, if the user rator:
specifies PAY* as a generic member name, and the
system is unable to find any members whose Without a time separator, specify a string of 4 or 6
names start with PAY, the file is not restored. If no digits (hhmm or hhmmss) where hh = hours, mm =
files specified by the FILEMBR parameter are minutes, and ss = seconds.
restored because no members with the specific With a time separator, specify a string of 5 or 8
generic name can be found, a diagnostic message digits where the time separator specified for your job
is sent, the restore operation ends, and an escape is used to separate the hours, minutes, and
message is sent specifying the number of files not seconds. If you enter this command from the
restored. If at least one of the files processed for command line, the string must be enclosed in apos-
the FILEMBR parameter is restored, the diagnostic trophes. If a time separator other than the sepa-
message is not sent, and the number of files not rator specified for your job is used, this command
restored is shown on the final completion message. fails.
3. The members are first checked by using the
If a volume identifier or *MOUNTED is specified on the
MBROPT parameter. If a match is found, the
VOL parameter, but this parameter is not specified, the
members are checked against the list of the
version of the objects to be restored is the first version
FILEMBR parameter.
found on the volume. This parameter is ignored when
MBROPT the SEQNBR parameter is specified.
Specifies, for database files currently on the system, This parameter is valid only if the SAVDATE parameter
which file members are restored. is also specified.
If MBROPT(*MATCH) is used, the member list in the
ALWOBJDIF
saved file must match, member for member, the current
Specifies whether certain differences encountered during
version on the system.
a restore operation are allowed. The differences
Note: Before restoring a file, the system verifies that include:
the file and member creation dates of the known
Ownership: The owner of an object on the system
system objects match the creation dates of the
is different than the owner of an object from the
objects to be restored. If this check fails, the file
save operation.
is not restored.
File creation date: The file creation date of the
*MATCH: The saved members are restored if the lists
database file on the system does not match the cre-
of the files where they reside match, member for
ation date of the file that was saved.
member, the lists of the current system version.
Member creation date: The file creation date of the
*ALL: All members in the saved file are restored.
database file on the system does not match the cre-
*NEW: Only new members (members not existing on ation date of the member that was saved. The
the system) are restored. member creation date on the system does not
*OLD: Only members already existing on the system match the creation date from the save operation.
are restored. Validation value verification: The validation value
created at the time an object was created does not
SAVDATE
match the validation value created during the
Specifies the date the objects were saved. If the most
restore operation of an object on a system with a
recently saved version is not the one being restored, or
QSECURITY level of 40 or higher.
if multiple saved versions reside on the media volume,
specify the date that identifies which version of the Authorization list linking: The object is being
objects to restore. The date must be specified in the job restored to a system different from the one on which
date format. If separators, specified by the system value it was saved.
Either the file itself or members of the file are Note: If this value is specified or defaulted and the
restored based on the following facts: system value QFRCCVNRST has a value of "1,"
the restore operation proceeds as if
1. If there is a file level mismatch and
FRCOBJCVN(*YES *RQD) is specified.
ALWOBJDIF(*ALL) has been specified, the
existing version of the file is renamed and the *NO: The objects are not converted during the restore
saved version of the file is restored. operation.
2. If there is a member level mismatch, the *YES: The objects are converted during the restore
existing version of the member is renamed and operation.
the saved version of the member is restored. Note: Specifying this value increases the time of the
Validation value verification: restore operation, but avoids the need to convert
the objects when they are first used.
1. For programs with no validation value stored on
the media (in reference to program data saved Element 2: Objects to Convert
on an OS/400 system prior to version 1, release *RQD: The objects are converted only if they require
3.0), the program is restored and the system conversion to be used by the current operating system.
does not attempt to recreate it. Nothing is If the objects are not observable, the objects are
logged in the security journal and no informa- restored but are not converted.
tional messages are sent.
*ALL: All objects are converted regardless of their
2. For programs that do have a validation value current format. Even if the objects are in the current
stored on the media and the system fails to format, they are converted again. However, if the
recreate the program, the original version of the objects are not observable, the objects are not restored.
program is restored and an entry is logged in
the security journal and job log. RSTLIB
Specifies whether the objects are restored to a different
The informational message causes a diagnostic library or to the same library where they were saved.
message to be sent indicating that security or integ-
rity changes occurred during the restore operation. *SAVLIB: The objects are restored to the same library
This results in sending an escape message for the from which they were saved.
restore operation. library-name: Specify the name of the library to which
If the user is restoring objects to a system different the saved objects are restored.
from the one on which they were saved and the RSTASP
objects are secured by an authorization list, speci- Specifies whether the objects are restored to the same
fying *ALL automatically links the objects to the auxiliary storage pool (ASP) from which they were saved
authorization list again. If the authorization list does
or to another specific ASP. This parameter affects only *CURLIB: The current library for the job is
object types, journals, journal receivers, save files, and searched. If no library is specified as the current
libraries. All other object types are restored to the ASP library for the job, the QGPL library is used.
of the library unless the library is in a user ASP and the
library-name: Specify the name of the library to be
object type is not one of the valid user ASP object types.
searched.
A list of the valid user ASP object types and additional
information about user ASPs are in the Backup and database-file-name: Specify the name of the database
Recovery book. file to which the output of the command is directed.
Journals, journal receivers, and save files can be OUTMBR
restored to a user ASP with the library in the system Specifies the name of the database file member to which
ASP if the objects do not already exist in a different the output is directed when OUTPUT(*OUTFILE) is
ASP, and if the ASP to which they are being restored specified.
contains no libraries.
Element 1: Member to Receive Output
User ASPs that contain one or more libraries cannot
*FIRST: The first member in the file receives the output.
contain valid ASP object types, journals, journal
If OUTMBR(*FIRST) is specified and the member does
receivers, and save files in libraries on the system ASP.
not exist, the system creates a member with the name of
*SAVASP: The objects are restored to the same auxil- the file specified on the OUTFILE parameter.
iary storage pools from which they were saved.
member-name: Specify the name of the file member
asp-identifier: Specify the ASP identifier. When the that receives the output. If OUTMBR(member-name) is
specified ASP is 1, the objects are restored to the specified and the member does not exist, the system
system ASP, and when the ASP is 2 through 16, the creates it. If the member exists, the user can add
objects are restored to the user ASP specified. records to the end of the existing member or clear the
Note: System libraries (QSYS, QUSRSYS, and QDOC) existing member and add the records.
must not be created in or restored to user ASPs Element 2: Operation to Perform on Member
(2 through 16). Doing so can cause unpredict-
*REPLACE: The existing records in the specified data-
able results.
base file member are replaced by the new records.
OUTPUT
*ADD: The new records are added to the existing infor-
Specifies whether a listing that shows information about
mation in the specified database file member.
the status of the object is created and directed to an
output file. The listing shows the restore information and INFTYPE
shows all objects, restored, not restored, and excluded. Specifies the type of information directed to the data-
Information about each object's security is listed for the base file. This parameter is valid only when
restored objects. More information on this parameter is OUTPUT(*OUTFILE) is specified.
in Appendix A, “Expanded Parameter Descriptions.”
*OBJ: The list contains an entry for each object
*NONE: No output is created. requested to be restored.
*PRINT: The output is printed with the job's spooled *MBR: The list contains an entry for each object or, for
output. database files, each member requested to be restored.
*OUTFILE: The output is directed to the database file OPTFILE
specified on the OUTFILE parameter. Specifies the path name of the optical file that is used
Note: You must specify the database file name on the for the restore operation, beginning with the root direc-
OUTFILE parameter when OUTPUT(*OUTFILE) tory of the volume. For more information on specifying
is specified. path names, refer to Chapter 2, “Path Names
(*PNAME).”
OUTFILE
Note: This parameter is required when using an optical
Specifies the qualified name of the database file to
device.
which the information about the object is directed when
*OUTFILE is specified on the OUTPUT parameter. If
the file does not exist, this command creates a database
file in the specified library. If a new file is created, the Examples
system uses QASRRSTO in QSYS with the format name
Example 1: Restoring Most Recently Saved Version
QSRRST as a model.
RSTOBJ OBJ(PAYROLL) SAVLIB(LIBX) DEV(TAPð1)
The name of the database file can be qualified by one of OBJTYPE(\PGM) VOL(\SAVVOL)
the following library values:
This command restores to LIBX the program named
*LIBL: All libraries in the job's library list are
PAYROLL that was saved from LIBX. The tape drive named
searched until the first match is found.
TAP01 is used to restore the most recently saved version of Example 4: Printing An Output List
the program. RSTOBJ OBJ(\ALL) SAVLIB(LIB) DEV(TAPð1) OBJTYPE(\PGM)
VOL(SVOL) SEQNBR(2) SAVDATE(ð82392)
Example 2: Specifying Save Date and Time SAVTIME(143ððð) OUTPUT(\PRINT)
RSTOBJ OBJ(PAY\) SAVLIB(LIBX) DEV(DKTð1) VOL(ABCD)
OPTION(\OLD) SAVDATE(1ð2292) All programs that were saved from the library named LIB that
SAVTIME(143ððð) RSTLIB(LIBY) exist in the saved version on the tape volume named SVOL,
sequence number 2, saved at 14:30:00 on 08/23/92, are
All objects whose names start with PAY and that were saved restored to the library named LIB. An output list of all
from the library named LIBX on diskette volume ABCD at objects restored as well as objects not restored is provided.
14:30:00 on 10/22/92 are restored to LIBY. Volume ABCD
must be put on the diskette device named DKT01. Because Example 5: Restoring Journal Receivers
OPTION(*OLD) is specified, the only objects restored are RSTOBJ OBJ(\ALL) SAVLIB(BACKUP) DEV(\SAVF)
those having the same object name and type both in LIBY on OBJTYPE(\JRNRCV) SAVF(SAVEJ) RSTASP(3)
the system and in LIBX on diskette.
All journal receivers that were saved from the library named
Example 3: Adding a New Program to the QGPL Library BACKUP into the save file named SAVEJ are restored to the
RSTOBJ OBJ(NEWPROG) SAVLIB(QGPL) DEV(DKTð1) library named BACKUP. The journal receivers are restored
OBJTYPE(\PGM) VOL(PGMS) OPTION(\NEW) to ASP 3 (unless they already exist in the library named
BACKUP and are in a different ASP or ASP 3 contains a
A new program named NEWPROG is added to the general library).
purpose library, QGPL. It is restored from a volume labeled
PGMS that is inserted in the diskette device named DKT01.
┌──
──────────────────┐
55──RSTSHF──SHELF(──┬──6─bookshelf-name───(1) ┴─┬──)──DEV(──┬─device-name─┬──)────
(P) ─┬─────────────────────────────────┬───────────────5
├─\ALL─────────────────┤ └─\SAVF───────┘ │ ┌─\SYSTEM─────────┐ │
(2) ─────────────┤
├─\LIST─── └─SAVDIR(──┴─saved-directory─┴──)─┘
└─\PRODUCT─────────────┘
5──┬───────────────────────────────────┬──┬──────────────────────────────────┬──┬───────────────────────────┬───────────────────5
│ ┌─\SAVDIR───────────┐ │ │ ┌─\MOUNTED──────────┐ │ │ ┌─\REWIND─┐ │
(3) ─┴─volume-identifier─┴──)─┘ └─ENDOPT(───
└─RSTDIR(──┴─restore-directory─┴──)─┘ └─VOL(─── (3) ─┼─\LEAVE──┼──)─┘
└─\UNLOAD─┘
5──┬───────────────────────────────────────────────┬───────────────────────────────────────────────────────────────────────────5%
│ ┌─\LIBL/────────┐ │
(4) ─┼───────────────┼──save-file-name──)─┘
└─SAVF(───
├─\CURLIB/──────┤
└─library-name/─┘
Notes:
1 A maximum of 300 repetitions.
SAVF
Optional Parameters Specifies the qualified name of the save file that con-
tains the saved bookshelves to be restored.
SAVDIR
Specifies the name of the directory on the media from The name of the save file can be qualified by one of the
which the bookshelves are restored. following library values:
*SYSTEM: The bookshelves are restored from the *LIBL: All libraries in the job's library list are
system bookshelf directory, searched until the first match is found.
'/QDLS/QBKBOOKS/BOOKS'.
*CURLIB: The current library for the job is
saved-directory: Specify the name of the saved direc- searched. If no library is specified as the current
tory from which bookshelves are restored. Up to 63 library for the job, the QGPL library is used.
characters can be specified for the directory name. The
library-name: Specify the name of the library to be
directory name must be enclosed in apostrophes (').
searched.
RSTDIR
save-file-name: Specify the name of the save file from
Specifies the name of the directory in which the
which to restore bookshelves.
bookshelves being restored are placed. The name can
be any directory name up to 63 characters.
*SAVDIR: The bookshelves being restored are placed
Examples
into the same directory from which they were saved. Example 1: Restoring All Bookshelves from Tape
(1) ─┬─\PHYFILE───────────┬──)────
55──RSTS36F──TOFILE(──┬─\SET──────┬──)──TOLIB(──library-name──)──DEV(─── (P) ──────────────────────────5
└─file-name─┘ │ ┌──
─────────────┐ │
6 (2) ─┘
└───device-name─┴───
5──┬─────────────────────────────┬──┬──────────────────────┬──┬───────────────────────────┬─────────────────────────────────────5
│ ┌─#SAVE──────────┐ │ │ ┌─\NO──┐ │ └─FROMLABEL(──file-label──)─┘
└─SET(──┴─set-identifier─┴──)─┘ └─IGCDTA(──┴─\YES─┴──)─┘
5──┬─────────────────────────────────┬──┬───────────────────────┬──┬──────────────────────────────────────┬─────────────────────5
└─CRTDATE(──file-creation-date──)─┘ │ ┌─\NO──┐ │ │ ┌─\SEARCH──────────────┐ │
└─DATDIFF(──┴─\YES─┴──)─┘ └─SEQNBR(──┴─file-sequence-number─┴──)─┘
5──┬───────────────────────────────────────┬──┬─────────────────────────┬──┬─────────────────────────────────────────────┬──────5
│ ┌─\MOUNTED─────────────────┐ │ │ ┌─\REWIND─┐ │ │ ┌─\LIBL/────────┐ │
│ │ ┌──
───────────────────┐ │ (4) ─┼───────────────┼──file-name──)─┘
│ └─ENDOPT(──┼─\LEAVE──┼──)─┘ └─PHYFILE(───
6 (3) ─┴──)─┘
└─VOL(──┴───volume-identifier─┴─── └─\UNLOAD─┘ ├─\CURLIB/──────┤
└─library-name/─┘
5──┬────────────────────────────┬──────────────────────────────────────────────────────────────────────────────────────────────5%
│ ┌─\NOREPLACE─┐ │
└─MBROPT(──┴─\REPLACE───┴──)─┘
Notes:
1 Up to 4 devices may be specified if more than one tape device is being used. (Only one device is allowed with diskette.)
2 A maximum of 4 repetitions
3 A maximum of 50 repetitions
File (CHGPF) command (after the restore operation is com- where 'yymmdd' represents the original creation date (in
pleted) to set SIZE(*EXTEND) to zero. If the file was saved year/month/day format) of the file.
from the AS/400 system, the file is restored and the extend
Because all members of a physical file share the same
value does not change.
file attributes (for example, record length and key infor-
This function is intended only for exchanging files with a mation), date-differentiated files with the same name that
System/36. are restored to the same library are required to have the
same file attributes. If an attribute mismatch is present,
Restrictions: the files are not restored.
1. This command is shipped with public *EXCLUDE 6. Object-level and record-level functions, including read
authority. operations, should not be used for a file being restored
by the RSTS36F command. If another operation is
2. The following authorities are required when running on a
being done at the same time on the file (for example,
system using resource security:
moving the file or reading or adding records), the restore
*USE, *SECADM, and *ALLOBJ authorities for this operation stops if it cannot allocate the file.
command
Note: To see the parameter and value descriptions for this
*USE authority for the library specified in the TOLIB
command, refer to the online help text. For more
parameter
information about printing the help text, refer to
*CHANGE authority for the library specified in the
“Printing CL Command Descriptions” in Chapter 1.
TOLIB parameter when restoring a file that does not
already exist on the system
*CHANGE and *OBJMGMT authority for the existing Required Parameters
file (needed to add a new member) when restoring
TOFILE
a date-differentiated physical file and a file by the
Specifies the name of a single file that is restored to the
same name but with a different creation date
system or that a group of files that are all saved at the
*ALL authority for the file when restoring to an
same time using the System/36 SAVE procedure (a
existing physical file with the same creation date
Save All Set) are to be restored to the system.
and MBROPT(*REPLACE) specified
*CHANGE authority for the based-on physical file *SET: A group of files from a Save All Set are restored
(this physical file was referred to as the parent file to the system.
on System/36) if the file being restored is a file-name: Specify the file name given to a single file
System/36 alternative index file (that is, a logical when the file is restored to the system.
file)
*USE authority for the diskette device description TOLIB
object and *USE authority for device file QSYSDKT Specifies the library that will contain the file being
in library QSYS, when restoring from diskette restored from the input file.
*USE authority for the tape device description object
DEV
and *USE authority for device file QSYSTAP in
Specifies the names of the devices used for the restore
library QSYS, when restoring from tape
operation. Each device name must already be known on
*USE authority for the file and *USE authority for the
the system by a device description.
library that contains the file (PHYFILE parameter) if
restoring from a database physical file *PHYFILE: The input file is the database physical file
If the file doesn't exist on the system but a file specified by the PHYFILE parameter.
authorization holder object by the same name does device-name: Specify the name of the diskette device,
exist, *ALL authority or ownership for the authori- the media library device, or the names of tape devices
zation holder object that are used for the operation. If more than one tape
3. There is no replace function supported when restoring device is used, specify the names of the devices in the
System/36 alternative index files (logical files). If order in which they are used. When more than one tape
restoring an alternative index file, no file object by the volume is used, using more than one tape device
same name can already exist in the specified library. permits one tape volume to be rewound or unloaded
while another tape device processes the next tape
4. If restoring a logical file, the based-on physical file must
volume. More information on device names is in the
already exist in the library specified for the TOLIB
APPC Programming book.
parameter.
5. The AS/400 system files that are the same as the
System/36 date-differentiated files are multiple-member Optional Parameters
physical files. Date-differentiated alternative index files SET
are not supported. The data for a physical file is stored Specifies the name used to identify the Save All Set files
in a member that is named using the syntax 'Myymmdd' saved on the diskette or tape by the SAVE procedure or
the $COPY utility on the System/36, System/34, or For tapes from System/36 or AS/400 system, there can
System/32. be multiple files on a tape with the same name. The
user can use the CRTDATE parameter or SEQNBR
#SAVE: The files are restored from a Save All Set with
parameter to choose the correct file. If a numeric
a set identifier of #SAVE.
SEQNBR parameter and the CRTDATE parameter are
set-identifier: Specify the set identifier of the Save All specified, the SEQNBR parameter takes precedence (if
Set that is restored. Valid values range from 1 through the file at the specified sequence number has a different
8 characters. The first character must be alphabetic (A creation date, the restore operation ends).
through Z, #, $, or @). The remaining characters can be
Specify the creation date of the tape or diskette file used
any combination of characters (numeric, alphabetic, and
for the restore operation. The date specified is changed
special) except a comma (,), an apostrophe ('), or a
to Julian format (cyyddd) for tape files and international
blank.
format (yymmdd) for diskette files.
IGCDTA
If no value is specified, the diskette file or tape file cre-
Specifies whether the file being restored can contain
ation date is not used to select the input file. For
double-byte character set (DBCS) data.
diskette, take the first file in the diskette volume table of
*NO: The file being restored cannot contain DBCS data. contents (VTOC) with the name specified on the
If a file already exists by the name specified on the FROMLABEL parameter. For tape, take the first file on
TOFILE parameter in the specified library and the file the tape with the name specified on the FROMLABEL
allows DBCS data, an informational message is sent and parameter. If the previous tape operation had specified
the restore operation continues. The resulting file allows ENDOPT(*LEAVE), the search for a matching file does
DBCS data (the file's IGC attributes are not changed by not start at the beginning of the tape reel.
the restore operation).
DATDIFF
*YES: The file processes DBCS data. Specifies whether the restore operation should allow
date-differentiated files (that is, multiple files with the
FROMLABEL
same name but different file creation dates).
Specifies the label of the diskette or tape file that con-
tains the file being copied to the AS/400 system (it iden- *NO: Date-differentiated files are not allowed.
tifies the input file for the restore operation). Up to 8
If a file already exists by the name specified on the
characters can be used to label the diskette or tape file.
TOFILE parameter in the specified library, and the file
For a group restore operation, this parameter can be contains a member with a different creation date (as
used to specify the diskette or tape file label with a save determined by the member name), an error message is
all set where the restore operation is to begin. If no sent and the file is not restored.
value is specified, the restore operation begins with the
If a file already exists by the name specified on the
first file in the set.
TOFILE parameter in the specified library, and the file
If no value is specified, the value of the TOFILE param- contains a member with the same creation date (as
eter is used as the diskette or tape label. If the TOFILE determined by the member name), either the data in that
parameter is an extended name, the characters between member is replaced (if MBROPT(*REPLACE) is speci-
the quotation marks are used as the label. For example, fied) or an error message is sent (if
specifying TOFILE("MIKE&BOB") and no FROMLABEL MBROPT(*NOREPLACE) is specified).
parameter would be the same as specifying
If no file exists by the name specified on the TOFILE
FROMLABEL('MIKE&BOB').
parameter in the specified library, the file is restored
CRTDATE normally.
Specifies the creation date of the object. *YES: Date-differentiated files are allowed.
The date must be entered in the job date format If a file already exists by the name specified on the
(DATFMT); if separators, specified by the job date sepa- TOFILE parameter in the specified library, and the file
rator character (DATSEP), are used, the value must be contains a member with a different creation date (as
enclosed in apostrophes. The CRTDATE parameter determined by the member name), a member is added
cannot be specified if the FROMLABEL parameter is not to the file (only if the file attributes match), and the file's
specified. data is restored into the new member.
For diskettes coming from a System/36, there may be If a file already exists by the name specified on the
multiple files on one diskette with the same name and TOFILE parameter in the specified library, and the file
different creation dates. Specifying a value for the contains a member with the same creation date (as
CRTDATE parameter is the only way of choosing which determined by the member name), either the data in that
diskette file to use. member is replaced (if MBROPT(*REPLACE) is speci-
fied) or an error message is sent (if
MBROPT(*NOREPLACE) is specified).
If no file exists by the name specified on the TOFILE *UNLOAD: The tape is automatically rewound and
parameter in the specified library, the file is restored unloaded after the operation ends.
normally.
PHYFILE
SEQNBR Specifies the qualified name of the database physical file
Specifies, only when tape is used, which sequence that is used as the input file for the restore operation.
number is used for the restore operation.
The file must have a record length of 256 bytes.
*SEARCH: The volume in the device is searched for a
If the specified file does not exist or is not a physical file,
data file with an identifier that matches the FROMLABEL
the file is not restored. If the physical file contains mul-
parameter value; when a match is found, the data file is
tiple members, the first member of the file is used.
restored. If the last operation on the tape device speci-
fied ENDOPT(*LEAVE), the file search starts with the The name of the physical file can be qualified by one of
data file at the current tape position. Otherwise, the the following library values:
search starts with the first data file on the tape volume.
*LIBL: All libraries in the job's library list are
The header label name from the file found by the
searched until the first match is found.
SEQNBR parameter is compared to the name specified
for the FROMLABEL parameter. If the names are the *CURLIB: The current library for the job is
same, the restore operation can continue. If the names searched. If no library is specified as the current
are different, the restore operation ends. library for the job, the QGPL library is used.
file-sequence-number: Specify the sequence number of library-name: Specify the name of the library to be
the file that is used. Valid values range from 1 through searched.
9999.
file-name: Specify the name of the database file that is
VOL used as the input file for the restore operation.
Specifies the volume identifiers of the tape volumes or
MBROPT
diskette volumes from which the objects are being
Specifies whether the new records replace or are added
restored. The volumes must be in the same order as
to the existing records.
they were when the library was saved. If the library was
known to the system before the restore operation, the *NOREPLACE: If a file already exists by the name
system can verify whether the volumes put on tape specified on the TOFILE parameter in the specified
contain the current version of the library. The volume library, and the file contains a member with the same
that contains the beginning of the file to be restored creation date (as determined by the member name), an
should be placed in the tape or diskette unit. More infor- error message is sent and the data in that member is
mation on this parameter is in Appendix A, “Expanded not replaced.
Parameter Descriptions.” *REPLACE: If a file already exists by the name speci-
*MOUNTED: The objects are restored from the volumes fied on the TOFILE parameter in the specified library,
placed in the device specified on the DEV parameter. and the file contains a member with the same creation
date as the file being restored, the data in that member
volume-identifier: Specify the volume identifiers of the of the file is replaced.
tapes or diskettes to be used for restoring the file. For
each tape or diskette volume name, up to 6 characters
can be specified using any combination of letters and Examples
digits. Up to 50 volume names can be specified.
Example 1: Restoring From Diskette
ENDOPT
RSTS36F TOFILE(ACCTRCV) TOLIB(QS36F) DEV(I1)
Specifies the operation that is automatically performed CRTDATE('ð1/22/85') VOL(SAVE1)
on the tape volume after the operation ends. If more
than one volume is included, this parameter applies only This command restores the file ACCTRCV into library
to the last tape volume used; all other tape volumes are QS36F. Assuming that I1 is the name of a diskette device
rewound and unloaded when the end of the tape is description object, the file is restored from the diskette placed
reached. in the diskette device. The diskette must have a volume
name of SAVE1. The diskette file used for the restore must
Note: This parameter is ignored if a diskette device is have a file label of ACCTRCV and a creation date of January
specified in the DEV parameter. 22, 1985 (assuming the job date format is *MDY and the
*REWIND: The tape is automatically rewound, but not date separator is a '/').
unloaded, after the operation has ended.
Example 2: Restoring From Tape
*LEAVE: The tape does not rewind or unload after the
operation ends. It remains at the current position on the RSTS36F TOFILE(PAY.VIEW) TOLIB(PAYLIB) DEV(T1)
tape drive. FROMLABEL('P\V') ENDOPT(\LEAVE)
The file P*V is restored from device T1 as a file named RSTS36F TOFILE(\SET) TOLIB(QS36F) DEV(T1 T2)
PAY.VIEW in library PAYLIB. Assuming T1 is a tape device, SET(PAYFILES) FROMLABEL(FILE1ð) MBROPT(\REPLACE)
the file is copied from one or more tapes that are on device DATDIFF(\YES) SEQNBR(\SEARCH) VOL(\MOUNTED)
T1. No check is made on the tape volume name. When the ENDOPT(\REWIND)
restore operation ends, the tape is left positioned at the end
This command restores a subset of the files in the save all
of tape file P*V.
set called PAYFILES to library QS36F from tape. The
Example 3: Restoring from a Physical File restore operation begins with a tape file whose label is file
10. If one of the files being restored already exists in library
RSTS36F TOFILE(ACCTPAY) TOLIB(QS36F) DEV(\PHYFILE)
QS36F with the same creation date as the saved file, the file
PHYFILE(NETLIB/SENDFILE)
is replaced. If a file already exists in library QS36F with a
This command restores the file ACCTPAY in library QS36F different creation date, a new date-differentiated number is
from physical file SENDFILE in library NETLIB. added to the file. The restore operation uses the tape
volumes that are placed in tape drives T1 and T2. After the
Example 4: Specifying Sequence Numbers restore operation is complete, the last tape volume is
rewound to the beginning of the tape.
(P) ─┬────────────────────────────────┬─────────────────5
55──RSTS36FLR──FROMFLR(──folder-name──)──DEV(──┬─\PHYFILE───────────┬──)────
│ ┌──
─────────────┐ │ │ ┌─\FROMFLR────┐ │
6 (1) ─┘
└───device-name─┴─── ├─TOFLR(──┴─folder-name─┴──)─────┤
│ ┌─\FROMFLR─────┐ │
└─TODTADCT(──┴─library-name─┴──)─┘
5──┬─────────────────────────────────────────────┬──┬──────────────────────────┬──┬────────────────────────────┬────────────────5
│ ┌─\LIBL/────────┐ │ │ ┌─\FIRST──────┐ │ └─CRTDATE(──creation-date──)─┘
(2) ─┼───────────────┼──file-name──)─┘ └─MBR(──┴─member-name─┴──)─┘
└─PHYFILE(───
├─\CURLIB/──────┤
└─library-name/─┘
5──┬───────────────────────────────────────┬──┬─────────────────────────────────┬──┬─────────────────────────┬──────────────────5
│ ┌─\MOUNTED─────────────────┐ │ │ ┌─\SEARCH─────────┐ │ │ ┌─\REWIND─┐ │
│ │ ┌──
───────────────────┐ │ │ └─SEQNBR(──┴─sequence-number─┴──)─┘ └─ENDOPT(──┼─\LEAVE──┼──)─┘
6 (3)
└─VOL(──┴───volume-identifier─┴────┴──)─┘ └─\UNLOAD─┘
5──┬───────────────────────────────────────────┬──┬──────────────────────────┬─────────────────────────────────────────────────5%
│ ┌─\SYSVAL──────────────────┐ │ │ ┌─\RENAME──┐ │
└─KBDTYPE(──┼─\MULTI───────────────────┼──)─┘ └─DUPDOC(──┴─\REPLACE─┴──)─┘
└─character-set-identifier─┘
Notes:
1 A maximum of 4 repetitions
3 A maximum of 50 repetitions
Purpose Notes:
1. When restoring a folder from the System/36, the user
The Restore System/36 Folder (RSTS36FLR) command
that issues the restore command becomes the owner
reads a diskette, tape, or database file that was prepared by
and the one authorized to the folder.
the System/36 SAVEFLDR command. The data is converted
so that it can be used by the AS/400 system. Both com- 2. When restoring a folder from the System/36 that con-
pressed and uncompressed data is supported when restoring tains an invalid name for the AS/400 system, the name
data from a diskette. is automatically changed to a different name generated
by the system.
Two types of System/36 folders are supported as input: doc-
ument folders and interactive data definition utility (IDDU) Restrictions:
folders. 1. This command is shipped with public *EXCLUDE
Document folders are converted to AS/400 system authority.
folders, and the documents contained in them are con- 2. The user must have *USE authority to the from-folder,
verted to AS/400 system documents. If a System/36 *CHG authority to the to-folder, and *USE authority to
document is in the process of being edited when the the device file or device description.
SAVEFLDR is done, there are two existing versions of 3. If the source folder is a document folder, the user must
the document: an unchanged original, and one con- be enrolled in the system distribution directory and have
taining modifications. When this folder is restored on the either operational and data authorities to the folder or
AS/400 system, the unchanged original and the modifi- *ALLOBJ special authority. If replacing a document, the
cation version are created. If the editing is completed by user must have *ALL authority to the document.
using OfficeVision on the AS/400 system, the modifica- Note: To see the parameter and value descriptions for this
tion version is removed. command, refer to the online help text. For more
System/36 IDDU folders do not create folders on the information about printing the help text, refer to
AS/400 system. Instead, a library is created and the “Printing CL Command Descriptions” in Chapter 1.
data dictionary is converted to an AS/400 system data
dictionary.
Required Parameters
FROMFLR
Specifies the name of the folder that is being restored.
Specify the name of the folder.
sequence-number: Specify the sequence number of the Table 33 (Page 1 of 2). Keyboard Mapping
file. Valid values range from 1 through 9999. Language/Country Iden- ASCII
tifier Device
ENDOPT Group
Specifies the operation that is automatically performed Denmark DMB B
on the tape volume after the operation ends. If more Denmark Multinational DMI B
than one volume is included, this parameter applies only Estonia ESB
Finland/Sweden FNB B
to the last tape volume used; all other tape volumes are
Finland/Sweden Multinational FNI B
rewound and unloaded when the end of the tape is
France (Azerty) FAB A, B
reached. France (Azerty) Multinational FAI A, B
Note: This parameter is ignored if a diskette device is France (Qwerty) FQB
specified in the DEV parameter. France (Qwerty) Multinational FQI
Greece 1 GNB 1
*REWIND: The tape is automatically rewound, but not Hebrew NCB D
unloaded, after the operation has ended. Hungary HNB
Iceland ICB
*LEAVE: The tape does not rewind or unload after the Iceland Multinational ICI
operation ends. It remains at the current position on the International INB
tape drive. International Multinational INI
Iran (Farsi) IRB
*UNLOAD: The tape is automatically rewound and
Italy ITB A, B
unloaded after the operation ends. Italy Multinational ITI A, B
KBDTYPE Japan English JEB
Japan English Multinational JEI
Specifies the character set and code page of the
Japan Kanji JKB
System/36 that created the data in the folder. (for PS/55 and 5295
*SYSVAL: The System/36, from which the folder was display stations)
saved, uses the same character set and code page as Japan Latin Extended JPB
Japan United States Basic JUB
the AS/400 system.
Japan Katakana KAB
*MULTI: The System/36, from which the folder was (for 5251, 5291, 5292,
saved, is configured as a multinational system. and 3180 Katakana
display stations)
character-set-identifier: Specify one of the identifiers Korea KOB
from the Keyboard Mapping table if the System/36 is a | Lao People's LAB
non-multinational system and the AS/400 system is not | Democratic Republic
using the same character set and code page as the Latin-2/ROECE ROB
System/36. On the System/36, a list of language or Latvia LVB
country names is presented from which to make a Lithuania LTB
FYR Macedonia MKB
selection. If multinational is chosen, the System/36
(Former Yugoslav Republic)
maps it into a single code regardless of language. For Netherlands NEB
example, if Denmark is chosen and not multinational, Netherlands Multinational NEI
use DMB with RSTS36FLR. If Denmark is chosen with Norway NWB B
multinational on the System/36, use *MULTI with Norway Multinational NWI B
RSTS36FLR. Poland PLB
Portugal PRB B
Table 33 (Page 1 of 2). Keyboard Mapping Portugal Multinational PRI B
Language/Country Iden- ASCII Romania RMB
tifier Device Russia RUB
Group Serbia (Cyrillic) SQB
Albania ALI Serbia (Latin) YGI
Arabic X/Basic CLB D Slovakia SKB
Austria/Germany AGB A, B Slovenia YGI
Austria/Germany Multinational AGI A, B Spain SPB B
Belgium Multinational BLI B Spain Multinational SPI B
Brazilian Portuguese BRB Spanish Speaking SSB B
Bulgaria BGB Spanish Speaking Multinational SSI B
Canadian French CAB A, B Sweden SWB B
Canadian French Multinational CAI A, B Sweden Multinational SWI B
| Catalan SPB Switzerland/French SFI B
Chinese (Simplified) RCB Multinational
Chinese (Traditional) TAB Switzerland/German SGI B
Croatia YGI Multinational
Cyrillic CYB Thai THB
Czech Republic CSB Turkey (Qwerty) TKB
*RENAME: If a folder already exists with the name Example 3: Restoring to a Data Dictionary
specified in the TOFLR parameter and a document in
RSTS36FLR FROMFLR(DONDCT) DEV(\PHYFILE)
that folder exists with the same name as an incoming
TODTADCT(NEWDCT) PHYFILE(MYLIB/MYFILE)
document, the incoming document is created in the MBR(THISONE)
folder with a new system-generated name. All other
documents are created in the specified folder. This command restores the folder DONDCT to a data dic-
*REPLACE: If a folder already exists by the name tionary named NEWDCT. Assuming that MYFILE is a phys-
specified in the TOFLR parameter, and a document in ical file located in library MYLIB and contains the member
that folder exists with the same name as an incoming THISONE, the folder is restored from member THISONE.
document, the existing document is replaced. All other
documents are created in the specified folder.
(1) ─┬─\PHYFILE───────────┬──)────
55──RSTS36LIBM──TOMBR(──┬─\ALL─────────────────┬──)──TOLIB(──library-name──)──DEV(─── (P) ─────────────5
├─member-name──────────┤ │ ┌──
─────────────┐ │
└─generic\-member-name─┘ 6 (2) ─┘
└───device-name─┴───
5──┬────────────────────────┬──┬────────────────────────┬──┬──────────────────────┬──┬──────────────────────┬───────────────────5
│ ┌─\ALL──┐ │ │ ┌─\NONE─┐ │ │ ┌─\NEW─┐ │ │ ┌─\NO──┐ │
└─SRCMBRS(──┼─\SRC──┼──)─┘ └─OBJMBRS(──┼─\SBR──┼──)─┘ └─MBROPT(──┼─\OLD─┼──)─┘ └─IGCDTA(──┴─\YES─┴──)─┘
├─\PRC──┤ ├─\LOD──┤ └─\ALL─┘
└─\NONE─┘ └─\ALL──┘
5──┬─────────────────────────────┬──┬─────────────────────────────────┬──┬──────────────────────────────────────┬───────────────5
(3) ─file-label──)─┘ └─CRTDATE(──file-creation-date──)─┘ │
└─FROMLABEL(─── ┌─\SEARCH──────────────┐ │
└─SEQNBR(──┴─file-sequence-number─┴──)─┘
5──┬───────────────────────────────────────┬──┬─────────────────────────┬──┬─────────────────────────────────────────────┬─────5%
│ ┌─\MOUNTED─────────────────┐ │ │ ┌─\REWIND─┐ │ │ ┌─\LIBL/────────┐ │
│ │ ┌──
───────────────────┐ │ (5) ─┼───────────────┼──file-name──)─┘
│ └─ENDOPT(──┼─\LEAVE──┼──)─┘ └─PHYFILE(───
6 (4) ─┴──)─┘
└─VOL(──┴───volume-identifier─┴─── └─\UNLOAD─┘ ├─\CURLIB/──────┤
└─library-name/─┘
Notes:
1 Up to four devices may be specified if more than one tape device is being used. (Only one device is allowed with diskette.)
2 A maximum of 4 repetitions
4 A maximum of 50 repetitions
Purpose the library is created with a default authority of *ALL (that is,
the same as AUT(*ALL)).
The Restore System/36 Library Members (RSTS36LIBM)
command reads a file containing library members, creates If a sector-mode FROMLIBR file or a SAVELIBR file created
database source or data file members on the AS/400 system, on a System/36 is being restored, data files QS36LOD and
and copies the member data from the file into each restored QS36SBR may also be created to hold restored load and
member. The input file can be a diskette file, tape file, or subroutine members. Restored load and subroutine
database physical file on the AS/400 system. The file could members are not converted on the current system.
have been created on a System/36, a System/34, or a
System/32 using either the FROMLIBR or SAVELIBR system Restrictions:
OCL procedure (or the equivalent call of $MAINT), or on an The following authorities are required when running on a
AS/400 system using the SAVS36LIBM CL command. system using resource security:
Diskette files created on a System/34 using the BACKUP 1. *SECADM and *ALLOBJ authorities
procedure or $BACK utility are not accepted by this 2. *USE authority for this command and *USE
command. Compressed SAVELIBR diskette files (used by authority for the Create Library (CRTLIB) command
IBM to distribute system libraries for System/36 after release if the library needs to be created
5.0) are not accepted by this command. 3. *USE authority for the CRTSRCPF command if
QS36SRC or QS36PRC must be created
In System/36 terms, the input file format could be a 4. *USE authority for the CRTPF command if
SAVELIBR diskette file or tape file, a record-mode LIBRFILE QS36LOD or QS36SBR must be created
diskette file, tape file, or physical file, or a sector-mode 5. *CHANGE authority for the library specified in the
LIBRFILE diskette file, tape file, or physical file. In other TOLIB parameter
words, the input file can be any diskette file, tape file, or 6. *CHANGE and *OBJMGMT authority for file
physical file created by the System/36 $MAINT SSP utility. QS36SRC in the specified library if restoring source
library members
If the library identified by the TOLIB parameter value does 7. *CHANGE and *OBJMGMT authority for file
not exist, it is created. Also, the source files QS36SRC and QS36PRC in the specified library if restoring proce-
QS36PRC are created if they do not exist in the restore-to dure library members
library. 8. *CHANGE and *OBJMGMT authority for file
QS36LOD in the specified library if restoring load
If the restore operation creates the library, the new library is library members
owned by the user running the RSTS36LIBM command and
9. *CHANGE and *OBJMGMT authority for file lowed by an asterisk (*); for example, ABC*. The
QS36SBR in the specified library if restoring subrou- asterisk substitutes for any valid characters. A generic
tine library members name specifies all objects with names that begin with the
10. *USE authority for the diskette device description generic prefix for which the user has authority. If an
object, *USE authority for device file QSYSDKT in asterisk is not included with the generic (prefix) name,
library QSYS if restoring from diskette the system assumes it to be the complete object name.
11. *USE authority for the tape device description object If the complete object name is specified, and multiple
and *USE authority for device file QSYSTAP in libraries are searched, multiple objects can be restored
library QSYS, if restoring from tape only if *ALL or *ALLUSR library values can be specified
12. *USE authority for the file and *USE authority for the for the name. For more information on the use of
library that contains the file (PHYFILE parameter) if generic names, refer to “Generic Object Names” in
restoring from a database physical file Chapter 2.
No object-level or record-level operations should be TOLIB
active for files QS36SRC, QS36PRC, QS36SBR, and Specifies the library that will contain the members to
QS36LOD while members are being restored by restore from the input file.
RSTS36LIBM. If the necessary files cannot be allocated
exclusively, no members are restored. DEV
Specifies the names of the devices to use for the restore
The member name or generic member name specified
operation. Each device name must already be known on
(TOMBR parameter) must meet AS/400 system naming
the system by a device description.
standards.
*PHYFILE: The input file is the database physical file
If a generic member name or *ALL is specified, a
specified by the PHYFILE parameter.
member may be selected to be restored that has a
name containing characters not allowed in an AS/400 device-name: Specify the name of the diskette device,
system simple object name. In this case, the member the media library device, or the names of tape devices
name is restored using the AS/400 system extended that are used for the operation. If more than one tape
name syntax (for example, A!B would become 'A!B'). device is used, specify the names of the devices in the
order in which they are used. When more than one tape
If the name contains a blank, a single quotation mark (') a volume is used, using more than one tape device
double quotation mark ("), an asterisk (*), a question mark permits one tape volume to be rewound or unloaded
(?), or a device control character (hexadecimal '00'-'3F' or while another tape device processes the next tape
hexadecimal 'FF'), these characters are replaced by under- volume. More information on device names is in the
lines and the member is restored using the resulting simple APPC Programming book.
or extended name (for example, A*/? would become A_/_
and A? would become A_).
Optional Parameters
An informational message is sent each time invalid charac- SRCMBRS
ters are replaced to get a valid name. An additional informa- Specifies which source member types (source and pro-
tional message is sent if the resulting name change caused a cedure members on System/36) are restored.
member to be replaced. No message is sent if a member is
restored using the extended name syntax without replacing *ALL: All source and procedure members in the input
invalid characters. file that match the member name specified (TOMBR
parameter) are restored. For example, if TOMBR(PAY*)
Note: To see the parameter and value descriptions for this and SRCMBRS(*ALL) is specified, all source and proce-
command, refer to the online help text. For more dure members that start with the letters 'PAY' are
information about printing the help text, refer to restored.
“Printing CL Command Descriptions” in Chapter 1.
*SRC: Only System/36 source members (to file
QS36SRC) that match the member name specified
Required Parameters (TOMBR parameter) are restored.
TOMBR *PRC: Only System/36 OCL procedure members (to file
Specifies the names of the members to restore. QS36PRC) that match the member name specified
(TOMBR parameter) are restored.
*ALL: All members of the specified member types are
restored. *NONE: No source or procedure library members are
restored.
member-name: The members that have the specified
member name are restored. OBJMBRS
generic*-member-name: All members that have the Specifies which object member types (load and subrou-
specified generic member name are restored. A generic tine members on System/36) are restored. Because the
name is a character string of one or more characters fol- System/36 and the AS/400 system are not object com-
FROMLABEL
file-sequence-number: Specify the sequence number of
the file that is used. Valid values range from 1 through
Specifies the label (8 characters maximum) of the
9999.
diskette file or tape file that contains the members to
copy to the AS/400 system (it identifies the input file for VOL
the restore operation). If the DEV parameter value is Specifies the volume identifiers of the tape volumes or
not *PHYFILE, a FROMLABEL value must be specified. diskette volumes from which the objects are being
restored. The volumes must be in the same order as
they were when the library was saved. If the library was
known to the system before the restore operation, the
system can verify whether the volumes put on tape If the specified file does not exist or is not a physical file,
contain the current version of the library. The volume no library members are restored. If the physical file con-
that contains the beginning of the file to be restored tains several members, the first member of the file is
should be placed in the tape or diskette unit. More infor- used.
mation on this parameter is in Appendix A, “Expanded
The name of the physical file can be qualified by one of
Parameter Descriptions.”
the following library values:
*MOUNTED: The objects are restored from the volumes
*LIBL: All libraries in the job's library list are
placed in the device specified on the DEV parameter.
searched until the first match is found.
volume-identifier: Specify the volume identifiers of the
*CURLIB: The current library for the job is
tapes or diskettes to be used for restoring the file. For
searched. If no library is specified as the current
each tape or diskette volume name, up to 6 characters
library for the job, the QGPL library is used.
can be specified using any combination of letters and
digits. Up to 50 volume identifiers can be specified. library-name: Specify the name of the library to be
searched.
ENDOPT
Specifies the operation that is automatically performed file-name: Specify the name of the database physical
on the tape volume after the operation ends. If more file that is used as the input file for the restore operation.
than one volume is included, this parameter applies only
to the last tape volume used; all other tape volumes are
rewound and unloaded when the end of the tape is
Examples
reached. Example 1: Restoring All Members
Note: This parameter is ignored if a diskette device is RSTS36LIBM TOMBR(XYZ1) TOLIB(JOHNSON) DEV(I1)
specified in the DEV parameter. SRCMBRS(\PRC) MBROPT(\ALL) FROMLABEL('XYZ1')
*REWIND: The tape is automatically rewound, but not The single OCL procedure member XYZ1 is restored as a
unloaded, after the operation has ended. member of source file QS36PRC in library JOHNSON.
*LEAVE: The tape does not rewind or unload after the Assuming I1 refers to a diskette device, the input diskette file
operation ends. It remains at the current position on the must have the label XYZ1.
tape drive.
Example 2: Specifying a Generic Member Name
*UNLOAD: The tape is automatically rewound and
RSTS36LIBM TOMBR(X\) TOLIB(ORDER) DEV(\PHYFILE)
unloaded after the operation ends.
PHYFILE(NETLIB/S36SRC)
PHYFILE All source and procedure members with names starting with
Specifies the qualified name of the database physical file the character 'X' and that do not already exist as members of
that is used as the input file for the restore operation. QS36SRC and QS36PRC in library ORDER are restored.
The file must have a record length of between 40 and The members are restored from file S36SRC in library
120 bytes if it contains members saved in record mode. NETLIB.
The record length must be 256 if it contains members
saved on a System/36 in sector mode.
55──RSTUSFCNR──SAVCNR(──container-identifier──)──RSTCNR(──┬─\SAVCNR──────────────┬──)───────────────────────────────────────────5
└─container-identifier─┘
5──DEV(──┬─\SAVF──────────────────────────┬──)──┬─────────────────────────────────────────┬─────────────────────────────────────5
├─tape-media-library-device-name─┤ │ ┌─\MOUNTED─────────────────┐ │
│ ┌──
──────────────────┐ │ │ │ ┌──
───────────────────┐ │ │
└──6─tape-device-name─┴───
(1) ────────┘ 6─volume-identifier─┴───
(2) ─┴──
└─VOL(─── (3) ─┴──)─┘
5──┬────────────────────────────────────────┬──┬───────────────────────────────────────┬──┬───────────────────────────┬─────────5
│ ┌─\SEARCH──────────────┐ │ │ ┌─\SAVCNR──────────────┐ │ │ ┌─\REWIND─┐ │
(2) ─┴─file-sequence-number─┴──)─┘ └─LABEL(───
└─SEQNBR(─── (2) ─┴─data-file-identifier─┴──)─┘ └─ENDOPT(───
(2) ─┼─\LEAVE──┼──)─┘
└─\UNLOAD─┘
5──┬───────────────────────────────────────────────┬──┬──────────────────────────────┬──┬────────────────────────────────┬──────5
│ ┌─\LIBL/────────┐ (5) ─time-when-saved──)─┘
│ └─SAVDATE(──date-when-saved──)─┘ └─SAVTIME(───
(4) ─┼───────────────┼──save-file-name──)─┘
└─SAVF(───
├─\CURLIB/──────┤
└─library-name/─┘
5──┬──────────────────────────┬────────────────────────────────────────────────────────────────────────────────────────────────5%
│ ┌─\NONE─┐ │
└─ALWOBJDIF(──┴─\ALL──┴──)─┘
Notes:
1 A maximum of 4 repetitions.
3 A maximum of 75 repetitions.
Purpose SAVCNR
Specifies the identifier of the multimedia container object
The Restore Ultimedia System Facilities Container that is to be restored. This is the identifier of the con-
(RSTUSFCNR) command restores to the system the multi- tainer object saved with the SAVUSFCNR command.
media objects that have been saved using the Save
Ultimedia System Facilities Container (SAVUSFCNR) RSTCNR
command. The multimedia objects that can be restored Specifies the identifier of the multimedia container object
using this command are the following: to which the saved container is to be restored.
Multimedia objects that have been copied to a shared *SAVCNR: The container objects are restored to the
folder container container with the same identifier as the container in
which they were saved. If a container with this identifier
Document library objects (DLOs) that hold the Ultimedia does not exist on the target system, the container is
Facilities data stream files. created as a first level container under the QUMBREPO
folder.
For more information on the Ultimedia* Facilities function,
see the Ultimedia System Facilities User Guide book. container-identifier: Specify the identifier of the container
to which the saved container objects are to be restored
Restriction: Only those objects that have been placed in an from tape. If the container specified does not exist, an
Ultimedia Facilities container and whose data stream files are error message is sent to the job log and processing
in the Ultimedia Facilities repository when they were saved ends for this command.
are restored. If the data stream file was not in the Ultimedia
Facilities repository at the time of the save, only the object's DEV
DLO is restored. Specifies the name of the device from which the multi-
media objects are to be restored.
Note: To see the parameter and value descriptions for this
command, refer to the online help text. For more *SAVF: The objects are restored from the save file
information about printing the help text, refer to specified on the SAVF parameter.
“Printing CL Command Descriptions” in Chapter 1. tape-media-library-device-name: Specify the name of
the tape media library device used for the restore opera-
tion.
Required Parameters
tape-device-name: Specify the names of one or more
tape devices used for the restore operation. If multiple
VOL *LEAVE: The tape does not rewind or unload after the
Specifies the volume identifier of the tape from which the operation ends. It remains at the current position on the
multimedia objects are to be restored. tape drive.
*MOUNTED: The objects are restored from the volumes *UNLOAD: The tape is automatically rewound and
placed in the device specified on the DEV parameter. unloaded after the operation ends.
For a media library device, the volume to be used is the SAVF
next cartridge in the category mounted by the Set Tape Specifies the qualified name of file that contains the
Category (SETTAPCGY) command. multimedia objects that are being restored.
volume-identifier: Specify the identifiers of one or more The name of the save file can be qualified by one of the
volumes in the order in which they are put on the device following library values:
and used. Each volume identifier contains a maximum
of 6 alphanumeric characters. A blank is used as a sep- *LIBL: All libraries in the job's library list are
arator character when listing multiple identifiers. You searched until the first match is found.
can specify a maximum of 75 volumes. *CURLIB: The current library for the job is
SEQNBR searched. If no library is specified as the current
Specifies the starting sequence number of the files on library for the job, the QGPL library is used.
the tape used for the restore operation. library-name: Specify the name of the library to be
*SEARCH: The volume on the device is searched for a searched.
data file containing the multimedia objects to be save-file-name: Specify the name of the save file to
restored; when a match is found, the data file is restore.
searched for the multimedia objects to be restored. If
the specified multimedia objects are not found in that SAVDATE
data file, the search continues for the next data file that Specifies the date on which the container was saved. If
matches the value specified on the LABEL parameter. more than one version of the container exists on the
media, this parameter identifies which version of the
Note: If the last operation on the device specified the
container to restore. If this parameter is not specified,
same volume and ENDOPT(*LEAVE) (that is, the
the version of the multimedia objects being restored is
specified tape is positioned at the location at
the first version found on the volume or, if the LABEL
which the last operation ended), the search oper-
parameter is specified, the version found with the speci-
ation starts with the first data file beyond the
fied label.
current tape position. The files located in front of
the current tape position are not searched. The date must be specified in the system date format
specified by the system value QDATFMT; if the separa-
sequence-number: Specify the sequence number of the
tors specified by the system value QDATSEP are used,
file to be used as the starting point for the restore opera-
the value must be enclosed in apostrophes.
tion.
SAVTIME
LABEL
Specifies the time when the container was saved. If
Specifies the label of the container object that is used to
more than one version of the container exists on the
find the file that was written to tape during the save
media, this parameter identifies which version of the
operation.
container is restored. If this parameter is not specified,
*SAVCNR: The container label is the same as the last the version of the multimedia objects being restored is
17 characters of the Ultimedia Facilities container identi- the first version found on the volume or, if the LABEL
fier specified on the SAVCNR parameter. parameter is specified, the version found with the speci-
data-file-identifier: Specify the data file identifier which is fied file label.
the label of the data file that contains the multimedia The time must be specified as a 6-digit value, in the
data to be restored. format hours, minutes, and seconds (hhmmss). If colons
are used as separators, the value must be enclosed in For more information on multimedia objects, see the
apostrophes. Ultimedia System Facilities User Guide book.
Note: This parameter is valid only if SAVDATE is spec- *ALL: The differences listed are allowed for the restore
ified. operation. An informational message is sent and the
multimedia object is restored.
ALWOBJDIF
Specifies whether the following differences that may be *NONE: The differences listed are not allowed on the
encountered during a restore operation are allowed. restore operation. A diagnostic message is sent for the
multimedia object, and the multimedia object is not
The byte stream for a multimedia object resides restored.
within the Ultimedia Facilities repository on the
target system but is not on the tape.
Examples
The byte stream for a multimedia object is on the
tape but is not stored within the Ultimedia Facilities RSTUSFCNR SAVCNR(SEMINARVIDEOSPOTððð4)
object repository on the target system. RSTCNR(\SAVCNR) DEV(TAPð1)
The members of a multimedia key object on the
This command restores the multimedia container object with
tape are different than those on the target system.
the container identifier SEMINARVIDEOSPOT0004 to the
The members of a multimedia sequence object on multimedia container object with the same container identi-
the tape are different than those on the target fier. The container is restored from the tape unit TAP01.
system.
55──RSTUSRPRF──DEV(──┬─\SAVF──────────────────────────┬──)──┬───────────────────────────────────────────────────────┬───────────5
├─diskette-device-name───────────┤ │ ┌─\ALL──────────────────────────────────┐ │
├─tape-media-library-device-name─┤ │ │ ┌──
────────────────────────────────┐ │ │
│ ┌──
──────────────────┐ │ 6 (2) ─┴──)─┘
└─USRPRF(──┴───┬─generic\-user-profile-name─┬─┴───
6 (1) ────────┘
└───tape-device-name─┴─── └─user-profile-name──────────┘
(P) ──┬───────────────────────────────────┬──┬───────────────────────────┬───────────5
5──┬───────────────────────────────────────┬───
│ ┌─\MOUNTED─────────────────┐ │ │ ┌─\SEARCH─────────┐ │ │ ┌─\REWIND─┐ │
│ │ ┌──
───────────────────┐ │ │ (4) ─┴─sequence-number─┴──)─┘ └─ENDOPT(───
└─SEQNBR(─── (4) ─┼─\LEAVE──┼──)─┘
6 (3)
└─VOL(──┴───volume-identifier─┴────┴──)─┘ └─\UNLOAD─┘
5──┬────────────────────────────────────────────┬──┬────────────────────┬──┬──────────────────────────┬─────────────────────────5
│ ┌─\LIBL/───────┐ │ │ ┌─\NO──┐ │ │ ┌─\NONE─┐ │
└─SAVF(──┼──────────────┼──save-file-name──)─┘ └─MAIL(──┴─\YES─┴──)─┘ └─ALWOBJDIF(──┴─\ALL──┴──)─┘
├─\CURLIB/─────┤
└─library-name─┘
5──┬──────────────────────────┬──┬──────────────────────────────────────────────────────┬───────────────────────────────────────5
│ ┌─\NONE────┐ │ │ ┌─\LIBL/────────┐ │
(5) ─┼───────────────┼──database-file-name──)─┘
└─OUTPUT(──┴─\OUTFILE─┴──)─┘ └─OUTFILE(───
├─\CURLIB/──────┤
└─library-name/─┘
5──┬─────────────────────────────────────────────┬─────────────────────────────────────────────────────────────────────────────5%
│ ┌─\FIRST──────┐ ┌─\REPLACE─┐ │
(5) ─┴─member-name─┴──┼──────────┼──)─┘
└─OUTMBR(───
└─\ADD─────┘
Notes:
1 A maximum of 4 repetitions
2 A maximum of 50 repetitions
3 A maximum of 75 repetitions
Note: This command ignores all file overrides that are cur- generic*-user-profile-name: Specify one or more generic
rently in effect for the job. names of sets of user profiles to restore. A generic
name is a character string of one or more characters fol-
Restrictions: lowed by an asterisk (*); for example, ABC*. The
1. This command is shipped with public *EXCLUDE asterisk (*) substitutes for any valid characters. A
authority. generic name specifies all objects with names that begin
with the generic prefix, for which the user has authority.
2. The user of this command must have *SAVSYS
If an asterisk is not included with the generic (prefix)
authority in the user profile, specified by
name, the system assumes it to be the complete object
SPCAUT(*SAVSYS).
name. For more information on the use of generic func-
3. Before this command is specified, all other operations on tions, refer to “Rules for Specifying Names.”
the system must be ended. The End System (ENDSYS)
user-profile-name: Specify one or more names of spe-
or End Subsystem (ENDSBS) command can be used to
cific user profiles that are restored. Both generic names
end these operations. You must have *JOBCTL
and specific names can be specified in the same
authority to use the ENDSYS or ENDSBS command.
command.
4. To restore authorization lists and authority holders,
VOL
USRPRF(*ALL) must be specified.
Specifies the volume identifiers of the tape volumes or
Note: To see the parameter and value descriptions for this diskette volumes from which the objects are being
command, refer to the online help text. For more restored. The volumes must be in the same order as
information about printing the help text, refer to they were when the library was saved. The volume that
“Printing CL Command Descriptions” in Chapter 1. contains the beginning of the file to be restored should
be placed in the tape or diskette unit. More information
Required Parameter on this parameter is in Appendix A, “Expanded Param-
eter Descriptions.”
DEV
Note: For tape, the user profiles are restored from the
Specifies the name of the diskette device, tape device,
volumes placed on the tape devices, in the order
or save file used to restore the user profiles. The device
that those devices were specified. This opera-
names must already be known on the system by a
tion is normally performed immediately after a
device description. Up to four tape devices may be
restore of the system is performed and the user
specified.
profiles are on the same volume.
*SAVF: The save file specified on the SAVF parameter
*MOUNTED: The objects are restored from the volumes
is used for the restore operation.
placed in the device specified on the DEV parameter.
diskette-device-name: Specify the name of the diskette For a media library device, the volume to be used is the
device used to restore the user profiles. next cartridge in the category mounted by the Set Tape
tape-media-library-device-name: Specify the name of Category (SETTAPCGY) command.
the tape media library device used to restore the user volume-identifier: Specify the identifiers of up to 75
profiles. volumes in the order in which they are placed in the
tape-device-name: Specify the names of one or more devices and used to restore the user profiles.
tape devices used for the restore operation. If more SEQNBR
than one tape device is used, specify the names of the Specifies the sequence number of the tape file used for
devices in the order in which they are used. Using more the restore process.
than one tape device permits one tape volume to be
rewound and unloaded while another tape device pro- *SEARCH: The volume placed in the device is
cesses the next tape volume. searched for a file containing the saved user profiles;
when a match is found, the user profiles are restored. If
a match is not found, you must load another tape and try
Optional Parameters the command again. If the last operation on the device
specified ENDOPT(*LEAVE) (the tape is positioned at
USRPRF
the location where the last operation ended), the file
search starts with the first file beyond the current tape
Specifies the names of one or more user profiles to
position. If ENDOPT(*LEAVE) was not used for the last
restore. To be restored, the user profiles must exist on
operation (or if the tape was manually rewound since an
the media from the Save System (SAVSYS) or Save
ENDOPT(*LEAVE) operation), the search begins with
Security Data (SAVSECDTA) commands.
the first file on the volume.
*ALL: All of the user profiles, authorization lists, and
| sequence-number: Specify the sequence number of the
authority holders saved by the SAVSYS or SAVSECDTA
| file. Valid values range from 1 through 16777215.
commands are restored.
The owner of the object on the system is different The name of the database file can be qualified by one of
than the owner of the object from the save. the following library values:
The object is secured by an authorization list and is *LIBL: All libraries in the job's library list are
being restored to a system other than the one on searched until the first match is found.
which it was saved.
*CURLIB: The current library for the job is *ADD: The new records are added to the existing infor-
searched. If no library is specified as the current mation in the specified database file member.
library for the job, the QGPL library is used.
library-name: Specify the name of the library to be Examples
searched.
Example 1: Restoring All Profiles
database-file-name: Specify the name of the database
file to which the output of the command is directed. RSTUSRPRF DEV(TAPð1) SEQNBR(\SEARCH) ENDOPT(\REWIND)
OUTMBR The saved version of all user profiles contained on the tape
Specifies the name of the database file member to which currently put on the tape drive named TAP01 is restored to
the output is directed. If a member already exists, the the system. The tape is searched for the file, and the tape is
system uses the second element of this parameter to rewound on completion or at the end of restore.
determine whether the member is cleared before the
new records are added. If the member does not exist Example 2: Restoring Specific User Profiles
and a member name is not specified, the system creates RSTUSRPRF DEV(TAPð1) USRPRF(USRA USRB USRC USER\)
a member with the name of the output file specified on
the OUTFILE parameter. If an output file member name The saved version of all the user profiles must exist on the
is specified, but the member does not exist, the system tape placed on tape drive TAP01. User profiles USRA,
creates it. USRB, and USRC, along with all the user profiles whose
names start with USER, are restored to the system.
Element 1: Member to Receive Output
*FIRST: The first member in the file receives the output. Example 3: Restoring User Profiles from a Save File
If OUTMBR(*FIRST) is specified and the member does RSTUSRPRF DEV(\SAVF) USRPRF(USRX USRY)
not exist, the system creates a member with the name of SAVF(QGPL/SAVESEC)
the file specified on the OUTFILE parameter.
This command restores user profiles USRX and USRY to the
member-name: Specify the name of the file member system from the save file SAVESEC in library QGPL.
that receives the output. If OUTMBR(member-name) is
specified and the member does not exist, the system Example 4: Reporting Information about User Profiles
creates it. If the member exists, the user can add Restored and Not Restored
records to the end of the existing member or clear the
RSTUSRPRF DEV(TAPð1) USRPRF(\ALL) OUTPUT(\OUTFILE)
existing member and add the records.
OUTFILE(PRFS92) OUTMBR(FOURQT \ADD)
Element 2: Operation to Perform on Member
This command restores all user profiles from the tape device
*REPLACE: The existing records in the specified data-
TAP01. A list reporting information about user profiles
base file member are replaced by the new records.
restored and not restored is directed to the output file
PRFS92. The output is received in the member FOURQT as
an addition to existing information in the member.
(P) ─┬────────────────────────────┬───────────────────────5
55──RTVAUTLE──AUTL(──authorization-list-name──)──USER(──┬─\PUBLIC─┬──)────
└─user-ID─┘ └─ALL(──&CL-variable-name──)─┘
5──┬───────────────────────────────┬──┬────────────────────────────┬──┬────────────────────────────────┬────────────────────────5
└─CHANGE(──&CL-variable-name──)─┘ └─USE(──&CL-variable-name──)─┘ └─EXCLUDE(──&CL-variable-name──)─┘
5──┬─────────────────────────────────┬──┬─────────────────────────────────┬──┬───────────────────────────────┬──────────────────5
└─OBJALTER(──&CL-variable-name──)─┘ └─OBJEXIST(──&CL-variable-name──)─┘ └─OBJMGT(──&CL-variable-name──)─┘
5──┬───────────────────────────────┬──┬───────────────────────────────┬──┬─────────────────────────────┬────────────────────────5
└─OBJOPR(──&CL-variable-name──)─┘ └─OBJREF(──&CL-variable-name──)─┘ └─READ(──&CL-variable-name──)─┘
5──┬────────────────────────────┬──┬───────────────────────────────┬──┬───────────────────────────────┬─────────────────────────5
└─ADD(──&CL-variable-name──)─┘ └─UPDATE(──&CL-variable-name──)─┘ └─DELETE(──&CL-variable-name──)─┘
5──┬────────────────────────────────┬──┬────────────────────────────────┬──────────────────────────────────────────────────────5%
└─EXECUTE(──&CL-variable-name──)─┘ └─AUTLMGT(──&CL-variable-name──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
Users who have *AUTLMGT authority or who own the Required Parameters
authorization list can retrieve authority for any user on the
AUTL
list. Other users can retrieve their own authorities or the
Specifies the name of the authorization list that specifies
authority of *PUBLIC.
the user's authorities.
The following values are returned if the user has the USER
authority specified by the keyword: Specifies the name of the user whose information is
being retrieved. If a variable is specified, it must be 10
Keyword Value characters in length and contain a user name or the
ADD *ADD value *PUBLIC.
ALL *ALL
*PUBLIC: The information returned in the specified
AUTLMGT *AUTLMGT parameter is for the users who do not have any specific
CHANGE *CHANGE authority to the authorization list, and whose user groups
DELETE *DLT do not have any specific authority to the authorization
list.
EXCLUDE *EXCLUDE
EXECUTE *EXECUTE user profile name: Specify the user profile name of the
user whose information is being retrieved.
OBJALTER *OBJALTER
OBJEXIST *OBJEXIST
OBJMGT *OBJMGT
Optional Parameters
OBJOPR *OBJOPR
ALL READ
Specifies the name of a variable that is used to return Specifies the name of a variable that is used to return
*ALL if the user has *ALL authority. In CL programs, the *READ if the user has *READ authority. In CL pro-
variable has a length of 10 characters. Blanks are grams, the variable has a length of 10 characters.
returned in the variable if the user does not have *ALL Blanks are returned in the variable if the user does not
authority. have *READ authority.
CHANGE ADD
Specifies the name of a variable that is used to return Specifies the name of a variable that is used to return
*CHANGE if the user has *CHANGE authority. In CL *ADD if the user has *ADD authority. In CL programs,
programs, the variable has a length of 10 characters. the variable has a length of 10 characters. Blanks are
Blanks are returned in the variable if the user does not returned in the variable if the user does not have *ADD
have *CHANGE authority. authority.
USE UPDATE
Specifies the name of a variable that is used to return Specifies the name of a variable that is used to return
*USE if the user has *USE authority. In CL programs, *UPD if the user has *UPD authority. In CL programs,
the variable has a length of 10 characters. Blanks are the variable has a length of 10 characters. Blanks are
returned in the variable if the user does not have *USE returned in the variable if the user does not have *UPD
authority. authority.
EXCLUDE DELETE
Specifies the name of a variable that is used to return Specifies the name of a variable that is used to return
*EXCLUDE if the user has *EXCLUDE authority. In CL *DLT if the user has *DLT authority. In CL programs,
programs, the variable has a length of 10 characters. the variable has a length of 10 characters. Blanks are
Blanks are returned in the variable if the user does not returned in the variable if the user does not have *DLT
have *EXCLUDE authority. authority.
OBJALTER EXECUTE
Specifies the name of a variable that is used to return Specifies the name of a variable that is used to return
*OBJALTER if the user has *OBJALTER authority. In *EXECUTE if the user has *EXECUTE authority. In CL
CL programs, the variable has a length of 10 characters. programs, the variable has a length of 10 characters.
Blanks are returned in the variable if the user does not Blanks are returned in the variable if the user does not
have *OBJALTER authority. have *EXECUTE authority.
OBJEXIST AUTLMGT
Specifies the name of a variable that is used to return Specifies the name of a variable that is used to return
*OBJEXIST if the user has *OBJEXIST authority. In CL *AUTLMGT if the user has *AUTLMGT authority. In CL
programs, the variable has a length of 10 characters. programs, the variable has a length of 10 characters.
Blanks are returned in the variable if the user does not Blanks are returned in the variable if the user does not
have *OBJEXIST authority. have *AUTLMGT authority.
OBJMGT
Specifies the name of a variable that is used to return Example
*OBJMGT if the user has *OBJMGT authority. In CL ADDAUTLE AUTL(PAYROLL) USER(TOM)
programs, the variable has a length of 10 characters. AUT(\OBJOPR \READ \UPD \AUTLMGT)
Blanks are returned in the variable if the user does not
have *OBJMGT authority. When user Smith calls a CL program containing the fol-
lowing:
OBJOPR
Specifies the name of a variable that is used to return DCL &CHG \CHAR 1ð
*OBJOPR if the user has *OBJOPR authority. In CL DCL &ALL \CHAR 1ð
DCL &USE \CHAR 1ð
programs, the variable has a length of 10 characters.
DCL &EXCL \CHAR 1ð
Blanks are returned in the variable if the user does not
DCL &OBJOP \CHAR 1ð
have *OBJOPR authority. DCL &ALTER \CHAR 1ð
OBJREF DCL &REFER \CHAR 1ð
Specifies the name of a variable that is used to return DCL &READ \CHAR 1ð
DCL &ADD \CHAR 1ð
*OBJREF if the user has *OBJREF authority. In CL pro-
DCL &UPD \CHAR 1ð
grams, the variable has a length of 10 characters.
DCL &DLT \CHAR 1ð
Blanks are returned in the variable if the user does not DCL &EXEC \CHAR 1ð
have *OBJREF authority. DCL &AUTLM \CHAR 1ð
RTVAUTLE AUTL(PAYROLL) USER(TOM) USE(&USE) This command retrieves the following authorities from the
OBJOPR(&OBJOP) AUTLMGT(&AUTLM) authorization list PAYROLL for user TOM: *USE, *OBJOPR,
and *AUTLMGT. If TOM does not have the authority, blanks
are returned.
(P)─┬────────────────────────────┬──┬───────────────────────────────┬───────────────────5
55──RTVBCKUP──BCKUPOPT(──┬─\DAILY───┬──)───
├─\WEEKLY──┤ └─DEV(──&CL-variable-name──)─┘ └─TAPSET(──&CL-variable-name──)─┘
└─\MONTHLY─┘
5──┬───────────────────────────────┬──┬───────────────────────────────┬──┬────────────────────────────────┬─────────────────────5
└─CLRTAP(──&CL-variable-name──)─┘ └─SBMJOB(──&CL-variable-name──)─┘ └─CHGONLY(──&CL-variable-name──)─┘
5──┬───────────────────────────────┬──┬────────────────────────────┬──┬────────────────────────────┬────────────────────────────5
└─PRTRPT(──&CL-variable-name──)─┘ └─LIB(──&CL-variable-name──)─┘ └─FLR(──&CL-variable-name──)─┘
5──┬────────────────────────────┬──┬───────────────────────────────┬──┬────────────────────────────┬────────────────────────────5
└─DIR(──&CL-variable-name──)─┘ └─SECDTA(──&CL-variable-name──)─┘ └─CFG(──&CL-variable-name──)─┘
5──┬─────────────────────────────┬──┬────────────────────────────┬──┬────────────────────────────────┬──────────────────────────5
└─MAIL(──&CL-variable-name──)─┘ └─CAL(──&CL-variable-name──)─┘ └─EXITPGM(──&CL-variable-name──)─┘
5──┬───────────────────────────────────┬───────────────────────────────────────────────────────────────────────────────────────5%
└─EXITPGMLIB(──&CL-variable-name──)─┘
Note:
P All parameters preceding this point can be specified positionally.
Purpose SBMJOB
Specifies the name of the CL variable that receives the
The Retrieve Backup (RTVBCKUP) command is used in a indicator of whether the backup is run as a batch job.
CL program or REXX procedure to retrieve the options in The variable must have a minimum length of 4 charac-
one of the predefined backups into CL variables. More infor- ters. The value returned is either *YES or *NO.
mation on backup is in the Backup and Recovery book.
CHGONLY
Note: To see the parameter and value descriptions for this Specifies the name of the CL variable that receives the
command, refer to the online help text. For more indicator for saving changed objects only. The variable
information about printing the help text, refer to must have a minimum length of 4 characters. The value
“Printing CL Command Descriptions” in Chapter 1. returned is either *YES or *NO.
PRTRPT
Required Parameters Specifies the name of the CL variable that receives the
BCKUPOPT indicator for printing a report of saved objects. The vari-
Specifies the backup options to be retrieved. able must have a minimum length of 4 characters. The
value returned is either *YES or *NO.
*DAILY: The daily backup options are retrieved.
LIB
*WEEKLY: The weekly backup options are retrieved.
Specifies the name of the CL variable that receives the
*MONTHLY: The monthly backup options are retrieved. value specifying the libraries to save with this backup.
The variable must have a minimum length of 10 charac-
ters. A value of *ALLUSR, *FROMLIST, or *NONE is
Optional Parameters returned.
DEV
FLR
Specifies the name of the CL variable that receives the
Specifies the name of the CL variable that receives the
device value. The variable has a minimum length of 43
value specifying the folders to save with this backup.
characters. The value returned is a character string of
The variable must have a minimum length of 10 charac-
four 10-character device names, separated by blanks.
ters. A value of *ALL, *FROMLIST, or *NONE is
TAPSET returned.
Specifies the name of the CL variable that receives the
DIR
tape set names. The variable has a minimum length of
Specifies the name of the CL variable that receives the
34 characters (seven 4-character tape set names, sepa-
value specifying the user directories to save with this
rated by blanks).
backup. The variable must have a minimum length of
CLRTAP 10 characters. A value of *ALLUSR or *NONE is
Specifies the name of the CL variable that receives the returned.
indicator for clearing the tape for backup. The variable
SECDTA
must have a minimum length of 4 characters. The value
Specifies the name of the CL variable that receives the
returned is either *YES or *NO.
indicator for saving security data. The variable must
CAL Example
Specifies the name of the CL variable that receives the
indicator for saving OfficeVision calendars. The variable RTVBCKUP BCKUPOPT(\DAILY) SBMJOB(&SBMJOBVAR)
must have a minimum length of 4 characters. The value LIB(&LIBVAR)
returned is either *YES or *NO.
This command retrieves the SBMJOB and LIB values for the
daily backup into the CL variables SBMJOBVAR and LIBVAR
respectively.
┌──
─────────────────────────────────────────────┐
│ ┌─\LIBL/────────┐ │
6 (1) ──)────
55──RTVBNDSRC──MODULE(──────┼───────────────┼──┬─\ALL─────────────────┬─┴───── (P) ───────────────────────────────────────────5
├─\CURLIB/──────┤ ├─generic\-module-name─┤
├─\USRLIBL/─────┤ └─module-name──────────┘
└─library-name/─┘
5──┬──────────────────────────────────────────────────────┬──┬─────────────────────────────────────────┬────────────────────────5
│ ┌─\LIBL/────────┐ ┌─QSRVSRC──────────┐ │ │ ┌─\DFT────────────────────┐ │
└─SRCFILE(──┼─\CURLIB/──────┼──┴─source-file-name─┴──)─┘ └─SRCMBR(──┴─source-file-member-name─┴──)─┘
└─library-name/─┘
5──┬──────────────────────────┬────────────────────────────────────────────────────────────────────────────────────────────────5%
│ ┌─\REPLACE─┐ │
└─MBROPT(──┴─\ADD─────┴──)─┘
Notes:
1 A maximum of 300 module entries can be specified.
an asterisk (*); for example, ABC*. The asterisk substi- If the member does not exist in the source file specified,
tutes for any valid characters. A generic name specifies the member is created.
all objects with names that begin with the generic prefix
*DFT: The name of the source file member is taken
for which the user has authority. If an asterisk is not
from the value specified on the MODULE parameter.
included with the generic (prefix) name, the system
assumes it to be the complete object name. For more If only one module is specified, the name of that
information on the use of generic names, refer to module is the member used.
“Generic Object Names” in Chapter 2.
If more than one module is specified, the name of
module-name: Specify the name of the module from the first module specified is used.
which to retrieve the exported symbols.
If the value *ALL or a generic name is specified, the
module name of the first occurrence found is the
Optional Parameters source member name used.
55──RTVCFGSRC──CFGD(──┬─\ALL─────────────────────────────────────────────┬──)──CFGTYPE(──┬─\ALL──┬──)───────────────────────────5
│ ┌──
───────────────────────────────────────────┐ │ ├─\NWSD─┤
└──6┬─generic\-configuration-description-name─┬┴───
(1) ─┘ ├─\NWID─┤
└─configuration-description-name──────────┘ ├─\LIND─┤
├─\CTLD─┤
├─\DEVD─┤
├─\MODD─┤
├─\COSD─┤
├─\CNNL─┤
├─\NTBD─┤
└─\IPXD─┘
(P) ──────────────────────────5
5──┬──────────────────────────────────────────────────────┬──┬────────────────────────────────────┬───
│ ┌─\LIBL/────────┐ ┌─QCLSRC───────────┐ │ │ ┌─\CFGD──────────────┐ │
└─SRCFILE(──┼───────────────┼──┴─source-file-name─┴──)─┘ └─SRCMBR(──┴─source-member-name─┴──)─┘
├─\CURLIB/──────┤
└─library-name/─┘
5──┬──────────────────────┬──┬──────────────────────────┬──┬─────────────────────────────┬─────────────────────────────────────5%
│ ┌─\NET─┐ │ │ ┌─\REPLACE─┐ │ │ ┌─\CFGDTXT──────┐ │
└─RTVOPT(──┴─\OBJ─┴──)─┘ └─MBROPT(──┴─\ADD─────┴──)─┘ └─TEXT(──┼─\BLANK────────┼──)─┘
└─'description'─┘
Notes:
1 A maximum of 256 repetitions
*LIND: All lines matching the specified names are This parameter cannot be specified if CFGTYPE(*ALL) is
retrieved. specified. If CFGTYPE(*ALL) is specified, the source is
retrieved for objects of all types with names as specified
*CTLD: All controllers matching the specified names are
on the CFGD parameter, followed by switched attach-
retrieved.
ment information (SWTCTLLST, SWTNWILST, and
*DEVD: All devices matching the specified names are SWTLINLST parameters on Change Line, Change
retrieved. Network Interface, and Change Controller commands).
*MODD: All modes matching the specified names are *NET: The source for the configuration object names
retrieved. specified on the CFGD parameter, of the type specified
*COSD: All classes-of-service matching the specified on the CFGTYPE parameter are retrieved. Also
names are retrieved. retrieved are the downward-attached configuration
objects. For example, if CFGTYPE(*CTLD) is specified,
*CNNL: All connection lists matching the specified the configuration source for devices attached to the
names are retrieved. specified controllers is also retrieved. For
*NTBD: All NetBIOS descriptions matching the specified CFGTYPE(*CTLD), the switched attachment configura-
names are retrieved. tion information (if any) is retrieved in the form of
Change Controller (CHGCTLxxx) commands including
*IPXD: All Internet Packet Exchange descriptions
the SWTLINLST parameter following the Create Con-
matching the specified names are retrieved.
troller (CRTCTLxxx) commands.
*OBJ: The source for the configuration object names
Optional Parameters specified on the CFGD parameter, of the type specified
SRCFILE on the CFGTYPE parameter, is retrieved.
Specifies the name of the previously created database
MBROPT
source file where the retrieved source is written.
Specifies whether the new records replace or are added
The name of the source file can be qualified by one of to the existing records.
the following library values:
*REPLACE: The system clears the existing member
*LIBL: All libraries in the job's library list are and adds the new records.
searched until the first match is found. *ADD: The system adds the new records to the end of
*CURLIB: The current library for the job is the existing records.
searched. If no library is specified as the current
TEXT
library for the job, the QGPL library is used.
Specifies the text that briefly describes the configuration
library-name: Specify the name of the library to be description. More information on this parameter is in
searched. Appendix A, “Expanded Parameter Descriptions.”
QCLSRC: The retrieved source is written in the *CFGDTXT: If *ALL is specified on the CFGD param-
QCLSRC source file. eter or a generic name or list of names, then *BLANK is
used as the text. If MBROPT(*ADD) is specified, the
source-file-name: Specify the name of the source file
member's text is replaced; otherwise, the text of the con-
where the retrieved source is being written.
figuration object being retrieved is used as the text.
SRCMBR *BLANK: Text is not specified.
Specifies the member name in the source file where the
retrieved source is written. If the member does not 'description': Specify no more than 50 characters of text,
exist, it is created. enclosed in apostrophes.
(P) ───────────────────5%
55──RTVCFGSTS──CFGD(──configuration-description-name──)──CFGTYPE(──┬─\NWS─┬──)──STSCDE(──&CL-variable──)────
├─\NWI─┤
├─\LIN─┤
├─\CTL─┤
└─\DEV─┘
Note:
P All parameters preceding this point can be specified in positional form.
| 63 ACTIVE READER– The device is in use by 110 DIAGNOSTIC MODE–The network inter-
| a spool reader. face, network server, line, controller, or
| 66 ACTIVE WRITER– The device is in use by device resource is being used by problem
| a spool writer. analysis procedures to diagnose problems,
and the resource cannot be used by other
70 HELD–This status is only valid for Device users.
Descriptions. The user or the system held
the communications device to prevent it 111 DAMAGED–The network interface, network
from communicating. The Release Commu- server, line, controller, or device description
nications Device (RLSCMNDEV) command is damaged. This is a system error condi-
can be used to release the device. tion. Information indicating when this
damage occurred appears in the history log
80 RCYPND–Error recovery is pending for the (QHST). The description must be deleted
network interface, line, controller, or device. and created once more before it can be
A message indicating what error occurred used again.
appears on the QSYSOPR message queue.
112 LOCKED–The actual status of the resource
90 RCYCNL–Error recovery is canceled for the cannot be determined because another job
network interface, line, controller, or device. has an exclusive lock on the description.
An error occurred, and the operator replied Retry at a later time, or use the Work with
with a C (to cancel error recovery) to a Object Lock (WRKOBJLCK) command to
message, or the operator used a command determine which job has the lock on the
(ENDNWIRCY, ENDLINRCY, ENDCTLRCY, description.
ENDDEVRCY) to end error recovery.
113 UNKNOWN–The status indicator of the
| 95 SYSTEM REQUEST– The display device description cannot be determined. This is a
| has been requested by the system and its system error condition. Use the Dump
| associated job has been suspended. This Object (DMPOBJ) command to dump the
| occurs as a result of a user pressing the contents and/or attributes of the description
| System Request key. to a spooled printer file, and contact an IBM
100 FAILED– An error occurred for the network representative.
interface, network server, line, controller, or
device that can be recovered only by
varying off and on again.
Example
RTVCFGSTS CFGD(NDð1) CFGTYPE(\LIN)
| 103 FAILED READER– An error occurred for
STSCDE(&STSCODE)
| the device while in use by a spool reader.
| 106 FAILED WRITER– An error occurred for the This command retrieves the configuration status of the line
| device while in use by a spool writer. configuration description ND01 for use in the CL variable
&STSCODE.
| 107 SHUTDOWN– The NWSD was shut down
| using an AIX interface.
(P)─┬─────────────────────────────────┬──┬────────────────────────────────┬──┬───────────────────────────────┬──────5
55──RTVCLNUP───
└─ALWCLNUP(──&CL-variable-name──)─┘ └─STRTIME(──&CL-variable-name──)─┘ └─USRMSG(──&CL-variable-name──)─┘
5──┬───────────────────────────────┬──┬───────────────────────────────┬──┬───────────────────────────────┬──────────────────────5
└─SYSMSG(──&CL-variable-name──)─┘ └─SYSPRT(──&CL-variable-name──)─┘ └─SYSLOG(──&CL-variable-name──)─┘
5──┬───────────────────────────────┬──┬─────────────────────────────┬──┬────────────────────────────────┬──────────────────────5%
└─CALITM(──&CL-variable-name──)─┘ └─JOBQ(──&CL-variable-name──)─┘ └─JOBQLIB(──&CL-variable-name──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
DCL VAR(&CLNUPTIME) TYPE(CHAR) LEN(1ð) These commands retrieve the time that the cleanup opera-
RTVCLNUP STRTIME(&CLNUPTIME) tion starts.
┌─\LIBL/────────┐ ┌─\LIBL/────────┐
55──RTVCLSRC──PGM(──┼───────────────┼──program-name──)──SRCFILE(──┼───────────────┼──source-file-name──)────────────────────────5
├─\CURLIB/──────┤ ├─\CURLIB/──────┤
└─library-name/─┘ └─library-name/─┘
(P) ───────────────────────────────────────────────────────────────────────────────────5%
5──┬────────────────────────────────────┬───
│ ┌─\PGM───────────────┐ │
└─SRCMBR(──┴─source-member-name─┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
library-name: Specify the name of the library to be source-member-name: Specify the name of the source
searched. file member that contains the CL source statements.
(P) ─────────────────────────────────────────────5%
55──RTVCURDIR──RTNDIR(──&CL-variable-name──)──DIRNAMLEN(──&CL-variable-name──)────
Note:
P All parameters preceding this point can be specified in positional form.
Purpose Note: To see the parameter and value descriptions for this
command, refer to the online help text. For more
The Retrieve Current Directory (RTVCURDIR) command is information about printing the help text, refer to
used in a CL program or REXX procedure to retrieve the “Printing CL Command Descriptions” in Chapter 1.
name of the current directory into the specified CL variable.
An absolute path name containing no symbolic links is
retrieved. The length of the name of the current directory is Required Parameters
also retrieved. RTNDIR
Specifies the name of the CL variable that receives the
The CL prompt for this command lists the minimum length for
name of the current directory. The variable must be a
retrieved variables next to the appropriate parameters. For
character variable. If the current directory name has
character variables, a single number is shown. For decimal
fewer characters than the variable allows, the value is
variables, two numbers are shown. The first number indi-
not padded.
cates the minimum variable length and the second number
indicates the minimum number of decimal positions. DIRNAMLEN
Specifies the name of the CL variable that receives the
Restrictions: length (in bytes) of the current directory name. This
1. *X authority is required to the current directory, and the length can be longer than the length of the character
user must have *RX authority to each directory in the variable to receive the directory name. The variable
path. must be a 7-digit decimal variable specified with no
decimal positions.
2. The maximum length of a directory name that can be
retrieved is limited by the maximum length of a character
variable. Example
Note: The maximum length of a character variable RTVCURDIR RTNDIR(&CD) DIRNAMLEN(&CDLEN)
cannot exceed 9999 bytes.
This command retrieves the name of the current directory
and the length of the name of the current directory.
55──RTVDLOAUT──DLO(──┬─\ROOT─────────┬──)──┬─────────────────────────────────────────┬──────────────────────────────────────────5
├─\DOCID────────┤ │ ┌─\NONE───────┐ │
├─\LADNTSP──────┤ (1) ─┴─folder-name─┴──)───
├─FLR(─── (P)───────────┤
├─\SYSOBJNAM────┤ │ ┌─\NONE───────────────┐ │
├─document-name─┤ ├─DOCID(───(2) ─┴─Document identifier─┴──)────┤
└─folder-name───┘ │ ┌─\NONE──────────┐ │
├─LADNTSP(─── (3) ─┴─LADN-timestamp─┴──)───────┤
│ ┌─\NONE──────────────┐ │
└─SYSOBJNAM(─── (4) ─┴─system-object-name─┴──)─┘
5──┬────────────────────────────────────────────────────────────┬──┬──────────────────────────────────┬─────────────────────────5
│ ┌─1────────────────────────────────────┐ │ └─OWNER(────&CL-variable-name────)─┘
(5) ─┴─starting-user-authority-entry-number─┴──)─┘
└─STRUSRAUTE(───
5──┬─────────────────────────────────┬──┬─────────────────────────────────────┬──┬───────────────────────────────────┬──────────5
└─AUTL(────&CL-variable-name────)─┘ └─SENSITIV(────&CL-variable-name────)─┘ └─PUBAUT(────&CL-variable-name────)─┘
5──┬──────────────────────────────────────┬──┬────────────────────────────────┬──┬───────────────────────────────────┬──────────5
└─CHKOUTUSR(────&CL-variable-name────)─┘ └─ACC(────&CL-variable-name────)─┘ └─USRAUT(────&CL-variable-name────)─┘
5──┬───────────────────────────────────┬──┬────────────────────────────────┬───────────────────────────────────────────────────5%
└─GRPAUT(────&CL-variable-name────)─┘ └─PGP(────&CL-variable-name────)─┘
Notes:
1 FLR (*NONE) must be specified if *DOCID, *LADNTSP, *SYSOBJNAM or *ROOT is specified on the DLO parameter.
Note: FLR(*NONE) must be specified if the object is a the value is greater than the number of specific user
first-level folder. authorities for the DLO, an error message will be sent
and no specific user authorities will be returned.
DOCID
Specifies the library-assigned name of the document or OWNER
folder. Specifies the name of a 10-character CL variable used
to retrieve the owner of the selected document or folder.
*NONE: The object is not identified using its document
identifier (DOCID). AUTL
document-identifier: Specify the document identifier of Specifies the name of a 10-character CL variable used
the document or folder. The document identifier is 24 to retrieve the authorization list assigned to the selected
hexadecimal characters in length in the format document or folder. The value *NONE is returned if no
YYYYMMDDHHMNSSHSSNSNSNSN, where: authorization list has been assigned.
*NONE: The object is not identified using its system *EXCLUDE: All users who are not otherwise authorized
object name. to this document or folder are denied access.
system-object-name: Specify the 10-character system USER DEF: Authority to this document is user-defined
object name of the document or folder. and is not one of the system-defined sets of authorities
(*ALL, *CHANGE, *USE, *EXCLUDE).
STRUSRAUTE
*AUTL: Authority specified in the authorization list being
Allows a user to specify the starting user authority entry
used by this document should determine public authority.
number to use when retrieving specific user authorities
(USRAUT parameter). STRUSRAUTE will enable CHKOUTUSR
retrieving specific user authorities for a DLO that has Specifies the name of a 32-character CL variable used
more than 50 specific user authorities. If no CL variable to retrieve the user profile who has the document
is provided for the USRAUT parameter, this parameter is checked out and the user profile on whose behalf the
ignored. document was checked out. If no user has checked out
1: User authority will be returned starting with the first the documented, the 32-character variable will be blank.
specific user authority. If the document was not checked out by a user working
on behalf of another user, the last 16 characters will be
starting-user-authority-entry-number: User authority will blanks.
be returned starting with the specified entry number. If
ACC
Specifies the name of a 220-character CL variable used
to retrieve the access codes assigned to the specified
document or folder.
5──┬───────────────────────────────────┬──┬───────────────────────────────────┬──┬─────────────────────────────────────┬────────5
└─RTNDLO(────&CL-variable-name────)─┘ └─RTNFLR(────&CL-variable-name────)─┘ └─RTNDOCID(────&CL-variable-name────)─┘
5──┬───────────────────────────────────────┬──┬──────────────────────────────────────┬──────────────────────────────────────────5
└─RTNLADNTSP(────&CL-variable-name────)─┘ └─RTNOBJNAM(────&CL-variable-name────)─┘
5──┬──────────────────────────────────────┬──┬───────────────────────────────────┬──┬──────────────────────────────────────┬───5%
└─RTNOBJCLS(────&CL-variable-name────)─┘ └─RTNASP(────&CL-variable-name────)─┘ └─RTNOVRFLW(────&CL-variable-name────)─┘
Notes:
1 FLR (*NONE) must be specified if *DOCID, *LADNTSP, or *SYSOBJNAM is specified on the DLO parameter.
*LADNTSP: The timestamp from the library-assigned document-ID: Specify the library-assigned name of the
document name (LADN) specified on the LADNTSP document or folder object. Library-assigned names are
parameter is used to identify the document or folder. 16 to 24 characters in length in the format
YYYYMMDDHHMNSSHSSNSNSNSN, where:
*SYSOBJNAM: The system object name specified on
the SYSOBJNAM parameter is used to identify the docu- YYYY = year
ment or folder.
*DST: The object is a distribution document. N = No, the object has not overflowed its ASP
Y = Yes, the object has overflowed its ASP and part
RTNDLO or all of the object resides in the system ASP
Specifies the name of a 12-character CL variable used
to retrieve the user-assigned name of the selected docu-
ment or folder. The *NONE value is returned for a distri- Example
bution document or a document without a folder. RTVDLONAM DLO(MYDOC) FLR(MYFLR) OBJCLS(\DOC)
RTNFLR RTNDOCID(&DOCID)
Specifies the name of a 63-character CL variable used
This command finds the document MYDOC in folder MYFLR
to retrieve the folder path of the selected document or
and returns its document identifier in the variable &DOCID.
folder. The *NONE value is returned for a distribution
(1) ───────┬──)──┬────────────────────────────────┬───
55──RTVDOC──FROMDOC(──┬─\DOCID─── (P) ─────────────────────────────────────────────5
└─document-name───(2) ┘ │ (4) ────┐
┌─\NONE─── │
(3) ─┴─folder-name─┴──)─┘
└─FROMFLR(───
5──┬─────────────────────────────────────────────────┬──┬──────────────────────────────────────┬──┬──────────────────────┬──────5
│ (5) ─────────────────────────┐
┌─\NONE─── │ │ ┌─\CURRENT──────────────┐ │ │ ┌─\NO──┐ │
└─DOCID(──┴─library-assigned-document-name───(4) ┴──)─┘ └─USRID(──┴─user-ID──user-address─┴──)─┘ └─CHKOUT(──┴─\YES─┴──)─┘
5──┬────────────────────────────────────────────────────────┬──┬───────────────────────────────────────────┬────────────────────5
│ ┌─\NONE─────────────────────────────────┐ │ │ ┌─\FIRST──────┐ ┌─\REPLACE─┐ │
│ │ ┌─\LIBL/────────┐ │ │ └─OUTMBR(──┴─member-name─┴──┼──────────┼──)─┘
└─OUTFILE(──┴─┼───────────────┼──database-file-name─┴──)─┘ └─\ADD─────┘
├─\CURLIB/──────┤
└─library-name/─┘
5──┬────────────────────────────────────────┬──┬────────────────────────────────────────────────────┬──────────────────────────5%
│ ┌─\DFT────────────────┐ │ │ ┌─\SYSVAL──────────────────────────┐ │
└─OUTDTATYP(──┼─\ALL────────────────┼──)─┘ └─CMDCHRID(──┼─\DEVD────────────────────────────┼──)─┘
│ ┌──
──────────────┐ │ └─graphic-character-set──code-page─┘
└──6─┬─\DOCD────┬─┴───
(6) ─┘
├─\DOCCLS──┤
├─\SUBJECT─┤
├─\FILCAB──┤
├─\AUTHOR──┤
├─\KWD─────┤
├─\CPYLST──┤
├─\FILDATE─┤
├─\EXPDATE─┤
├─\DOCDATE─┤
├─\CRTDATE─┤
├─\ACTDATE─┤
├─\CHGDATE─┤
├─\CMPDATE─┤
├─\REF─────┤
├─\STATUS──┤
├─\PROJECT─┤
├─\IDP─────┤
└─\DOC─────┘
Notes:
1 FROMFLR(*NONE) and DOCID( library-assigned-document-name) must be specified if this value is specified.
3 This parameter must be specified if a document name is specified on the FROMDOC parameter.
6 A maximum of 19 repetitions
is specified, but the member does not exist, the system *DOCD: The document information record is written to
creates it. the output file.
Element 1: Member to Receive Output *DOCCLS: The document class record is written to the
output file.
*FIRST: The first member in the file receives the output.
If OUTMBR(*FIRST) is specified and the member does *SUBJECT: The subject records are written to the
not exist, the system creates a member with the name of output file.
the file specified on the OUTFILE parameter.
*FILCAB: The filing cabinet reference code is written to
member-name: Specify the file member that receives the output file.
the output. If OUTMBR(member-name) is specified and
*AUTHOR: The author records are written to the output
the member does not exist, the system creates it.
file.
Element 2: Operation to Perform on Member
*KWD: The keyword records are written to the output
*REPLACE: The system clears the existing member file.
and adds the new records.
*CPYLST: The copy list records are written to the
Note: Document data for more than one document can output file.
be added to the same member. However, an
*FILDATE: The file date record is written to the output
error occurs if the member is filed to another
file.
document with the FILDOC command. The
FILDOC command only files the first document in *EXPDATE: The expiration date record is written to the
the member and issues an error message. output file.
*ADD: The system adds the new records to the end of *DOCDATE: The document date record is written to the
the existing records. output file.
*DEVD: The system determines the graphic character This command copies all information about document
set and code page values for the command parameter MYDOC located in folder PERSONAL for the current user of
from the display device description where the command this command. CHECKOUT(*NO) is assumed; therefore, the
is entered. This option is valid only when specified from document data can only be read. The output is directed to
an interactive job. If this value is specified in an interac- the database file MYFILE in the user's current library and is
tive CL program or a batch job, an error message is added to the first member in that file.
sent.
Example 2: Copying Default Information
Element 1: Character Set
RTVDOC FROMDOC(SECOP) FROMFLR(PERSONAL)
graphic-character-set: Specify the graphic character set USRID(MARY SYSTEM1 ) CHKOUT(\YES)
values used to create the command parameter. OUTFILE(MARLIB/SECFILE) OUTMBR(\FIRST \ADD)
Element 2: Code Page
This command copies the default information (*DOCD and
code-page: Specify the code page value used to create *DOC) about document SECOP located in folder PERSONAL
the command parameters. Valid values range from 1 for MARY. The document can be updated with new data
through 999. and then replaced. The current user of this command must
have the authority to work on behalf of MARY given by Mary
by using the GRTUSRPMN command. The output is
Examples
directed to the database file SECFILE in Mary's library
Example 1: Copying All Information MARLIB. The output is added to the first member of
SECFILE.
RTVDOC FROMDOC(MYDOC) FROMFLR(PERSONAL)
USRID(\CURRENT) OUTFILE(\CURLIB/MYFILE)
OUTMBR(\FIRST) MBROPT(\ADD) OUTDTATYP(\ALL)
55──RTVDSKINF──────────────────────────────────────────────────────────────────────────────────────────────────────────────────5%
┌─\LIBL/────────┐ ┌─\ALL──────────────────────────────────────────┐
(3) ──────5
55──RTVDTAARA──DTAARA(──┬─┼───────────────┼──data-area-name─┬──)──┴─substring-starting-position──substring-length─┴──)────
│ ├─\CURLIB/──────┤ │
│ └─library-name/─┘ │
(1) ───────────────────────────┤
├─\GDA───
├─\LDA──────────────────────────────┤
(2) ──────────────────────────┘
└─\PDA(───
(P) ───────────────────────────────────────────────────────────────────────────────────────────5%
5──RTNVAR(──&CL-variable-name──)────
Notes:
1 This value is valid only if this job is a group job.
The substring retrieval option, which is valid for char- Fractional data is truncated if the fraction contains more
acter data areas only, specifies the starting position and digits than the CL variable.
the length of the portion of the data area that is being
retrieved into the CL character variable.
Examples
Element 3: Starting Position of the Data Area
*ALL: The entire data area is retrieved. Assume data area DA1 has been created by the following
command:
substring-starting-position: Specify the starting position
of the data area being retrieved. CRTDTAARA DTAARA(DA1) TYPE(\CHAR) LEN(3) VALUE(ABC)
Element 4: Length of the Data Area and variable &CLVAR1 has been declared as:
substring-length: Specify the length of the data area DCL VAR(&CLVAR1) TYPE(\CHAR) LEN(5) VALUE(VWXYZ)
substring being retrieved.
Example 1: Running This Command
It is not possible to retrieve data outside the data area.
The combination of starting position and length must RTVDTAARA DTAARA(DA1) RTNVAR(&CLVAR1)
always specify positions within the data area.
results in:
RTNVAR &CLVAR1 = 'ABC '
Specifies the name of the CL program variable that
receives the contents of the data area being returned. Example 2: Running This Command
No type conversion is performed by the RTVDTAARA RTVDTAARA DTAARA(DA1 (2 1)) RTNVAR(&CLVAR1)
command:
results in:
If RTNVAR is declared as TYPE(*DEC), the data
&CLVAR1 = 'B '
area retrieved must be TYPE(*DEC).
If RTNVAR is declared as TYPE(*CHAR), the data Example 3: Decimal Data Area Example
area retrieved must be either TYPE(*CHAR) or
TYPE(*LGL). Assume data area DA2 has been created with the following
attributes:
If RTNVAR is declared as TYPE(*LGL), the data
area retrieved must be either TYPE(*LGL) or CRTDTAARA DTAARA(DA2) TYPE(\DEC) LEN(5 2) VALUE(12.39)
TYPE(*CHAR) with a value of either '0' or '1'.
and variable &CLVAR2 has been declared as:
If a retrieved character string is shorter than the length
DCL VAR(&CLVAR2) TYPE(\DEC) LEN(5 1) VALUE(4567.8)
of the variable specified by the RTNVAR parameter, the
value is padded on the right with blanks. The retrieved Example 4: Running This Command
string length must be less than or equal to the CL vari-
able length. RTVDTAARA DTAARA(MYLIB/&DTAARA) RTNVAR(&CLVAR2)
When decimal data areas are retrieved, the decimals are results in:
aligned. The value of the integer portion of the data
CLVAR2 = ðð12.3
area must fit into the integer portions of the CL variable.
Note that fractional digits are truncated instead of rounded.
(P) ─────5
55──RTVGRPA──┬───────────────────────────────┬──┬────────────────────────────────┬──┬──────────────────────────────────┬───
└─GRPJOB(──&CL-variable-name──)─┘ └─GRPJOBL(──&CL-variable-name──)─┘ └─GRPJOBCNT(──&CL-variable-name──)─┘
5──┬─────────────────────────────┬──┬────────────────────────────────┬──┬──────────────────────────────────┬────────────────────5
└─MSGQ(──&CL-variable-name──)─┘ └─MSGQLIB(──&CL-variable-name──)─┘ └─PRVGRPJOB(──&CL-variable-name──)─┘
5──┬───────────────────────────────┬───────────────────────────────────────────────────────────────────────────────────────────5%
└─CTLCDE(──&CL-variable-name──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose GRPJOBL
Specifies the name of the CL variable that receives the
The Retrieve Group Attributes (RTVGRPA) command is used list of jobs in the group. Each entry contains the job's
in a CL program or REXX procedure to retrieve information group job name, the job number, and the 50 characters
about the group in which the job that issued the RTVGRPA of descriptive text.
command belongs. The following attributes can be retrieved:
The maximum number of entries in the variable is 16.
The group job name of the job calling the RTVGRPA The entries are ordered by most recently active job (the
command group job that is issuing the RTVGRPA command is
A list that contains information about all active jobs in always first in the variable).
the group
The variable must be a character variable with a
A count of the number of active jobs in the group
minimum length of 1056 characters. If the group job list
The name of the group message queue
has fewer characters than the variable allows, the value
The library where the group message queue resides
is padded on the right with blanks.
The group job name and job number of the previously
active job in the group The group job list has the following format:
A control code indicating why the currently active job in Entry-1
the group gained control
Group-job-name CHAR(10)
The prompt for this command lists the minimum length for Job-number CHAR(6)
retrieved variables next to the appropriate parameters. For Group-job-text CHAR(50)
character variables, a single number is shown. For decimal
variables, two numbers are shown. The first number indi- Entry-2
cates the minimum variable length, and the second number .
indicates the minimum number of decimal positions. .
.
Optional Parameters Entry-16
GRPJOB Group-job-name CHAR(10)
Specifies the name of the CL variable that receives the Job-number CHAR(6)
group job name of the job. The variable must be a char- Group-job-text CHAR(50)
acter variable with a minimum length of 10 characters. If
the group job name has fewer characters than the vari- This list contains all of the active jobs in the group. Jobs
able allows, the value is padded on the right with blanks. in the group that have not completely ended (jobs that
have been canceled) are not listed.
Note: This is the only parameter of the RTVGRPA
command that is meaningful if the job that issued GRPJOBCNT
the RTVGRPA command is not a group job. Specifies the CL variable that receives the count of
When this occurs, the variable is set to the active jobs in the group. The CL variable must be a
special value of *NONE, and other parameters three-position decimal variable with no decimal positions.
specified in the command are filled with zeros or
The CL variable contains the number of nonblank entries
blanks (numeric variables with zeros, character
in the group job list. The count includes all of the active
variables with blanks). If this parameter is not
jobs in the group. Jobs that have not completely ended
specified and the job issuing this command is not
(jobs that have been canceled) are not counted.
a group job, an error message is sent.
&GRPCOUNT: ðð2
&MSGQNAME: GROUPMSGQ
&MSGQLIB: QGPL
&PRVJOB: GROUPJ1 ððð1
&CTLCODE: ð1ð
(P) ─────────────────5
55──RTVJOBA──┬────────────────────────────┬──┬─────────────────────────────┬──┬────────────────────────────┬───
└─JOB(──&CL-variable-name──)─┘ └─USER(──&CL-variable-name──)─┘ └─NBR(──&CL-variable-name──)─┘
5──┬───────────────────────────────┬──┬───────────────────────────────┬──┬────────────────────────────────┬─────────────────────5
└─LOGLVL(──&CL-variable-name──)─┘ └─LOGSEV(──&CL-variable-name──)─┘ └─LOGTYPE(──&CL-variable-name──)─┘
5──┬─────────────────────────────────┬──┬──────────────────────────────────┬──┬─────────────────────────────┬───────────────────5
└─LOGCLPGM(──&CL-variable-name──)─┘ └─INQMSGRPY(──&CL-variable-name──)─┘ └─OUTQ(──&CL-variable-name──)─┘
5──┬────────────────────────────────┬──┬───────────────────────────────┬──┬─────────────────────────────┬───────────────────────5
└─OUTQLIB(──&CL-variable-name──)─┘ └─ACGCDE(──&CL-variable-name──)─┘ └─DATE(──&CL-variable-name──)─┘
5──┬────────────────────────────┬──┬─────────────────────────────┬──┬───────────────────────────────┬───────────────────────────5
└─SWS(──&CL-variable-name──)─┘ └─TYPE(──&CL-variable-name──)─┘ └─RTNCDE(──&CL-variable-name──)─┘
5──┬───────────────────────────────┬──┬───────────────────────────────┬──┬──────────────────────────────────┬───────────────────5
└─ENDSTS(──&CL-variable-name──)─┘ └─RUNPTY(──&CL-variable-name──)─┘ └─TIMESLICE(──&CL-variable-name──)─┘
5──┬──────────────────────────────┬──┬────────────────────────────────┬──┬────────────────────────────────┬─────────────────────5
└─PURGE(──&CL-variable-name──)─┘ └─DFTWAIT(──&CL-variable-name──)─┘ └─USRLIBL(──&CL-variable-name──)─┘
5──┬────────────────────────────────┬──┬───────────────────────────────────┬──┬───────────────────────────────┬─────────────────5
└─SBMMSGQ(──&CL-variable-name──)─┘ └─SBMMSGQLIB(──&CL-variable-name──)─┘ └─PRTTXT(──&CL-variable-name──)─┘
5──┬───────────────────────────────┬──┬───────────────────────────────┬──┬───────────────────────────────┬──────────────────────5
└─DDMCNV(──&CL-variable-name──)─┘ └─BRKMSG(──&CL-variable-name──)─┘ └─DATFMT(──&CL-variable-name──)─┘
5──┬───────────────────────────────┬──┬───────────────────────────────┬──┬───────────────────────────────┬──────────────────────5
└─DATSEP(──&CL-variable-name──)─┘ └─CURLIB(──&CL-variable-name──)─┘ └─PRTDEV(──&CL-variable-name──)─┘
5──┬────────────────────────────────┬──┬────────────────────────────────┬──┬────────────────────────────────┬───────────────────5
└─SYSLIBL(──&CL-variable-name──)─┘ └─CURUSER(──&CL-variable-name──)─┘ └─SUBTYPE(──&CL-variable-name──)─┘
5──┬──────────────────────────────────┬──┬───────────────────────────────┬──┬────────────────────────────────┬──────────────────5
└─PRTKEYFMT(──&CL-variable-name──)─┘ └─TIMSEP(──&CL-variable-name──)─┘ └─TSEPOOL(──&CL-variable-name──)─┘
5──┬──────────────────────────────────┬──┬───────────────────────────────┬──┬───────────────────────────────┬───────────────────5
└─DEVRCYACN(──&CL-variable-name──)─┘ └─STSMSG(──&CL-variable-name──)─┘ └─SRTSEQ(──&CL-variable-name──)─┘
5──┬──────────────────────────────────┬──┬───────────────────────────────┬──┬────────────────────────────────┬──────────────────5
└─SRTSEQLIB(──&CL-variable-name──)─┘ └─LANGID(──&CL-variable-name──)─┘ └─CNTRYID(──&CL-variable-name──)─┘
5──┬──────────────────────────────┬──┬──────────────────────────────────┬──┬──────────────────────────────────┬─────────────────5
└─CCSID(──&CL-variable-name──)─┘ └─JOBMSGQMX(──&CL-variable-name──)─┘ └─JOBMSGQFL(──&CL-variable-name──)─┘
5──┬─────────────────────────────────┬──┬─────────────────────────────────┬──┬───────────────────────────────┬─────────────────5%
| └─DFTCCSID(──&CL-variable-name──)─┘ └─CYMDDATE(──&CL-variable-name──)─┘ └─DECFMT(──&CL-variable-name──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose JOB
Specifies, if the job name is returned, the name of the
The Retrieve Job Attributes (RTVJOBA) command is used in CL variable that receives the name of the job. The vari-
a CL program or REXX procedure to retrieve the values of able must be a character variable with a minimum length
one or more job attributes and to place those values into the of 10 characters. If the job name has fewer characters
specified CL variable. The attributes are retrieved for the job than the variable allows, the value is padded on the right
in which this command is used. with blanks.
The CL prompt for this command lists the minimum length for USER
retrieved variables next to the appropriate parameters. For Specifies, if the user name is returned, the name of the
character variables, a single number is shown. For decimal CL variable that receives the name of the user profile
variables, two numbers are shown. The first number indi- associated with the job when the job was started. The
cates the minimum variable length and the second number user name is the second part of the qualified job name.
indicates the minimum number of decimal positions. The variable must be a character variable with a
minimum length of 10 characters. If the user name has
Note: To see the parameter and value descriptions for this
fewer characters than the variable allows, the value is
command, refer to the online help text. For more
padded on the right with blanks.
information about printing the help text, refer to
“Printing CL Command Descriptions” in Chapter 1. NBR
Specifies, if the job number is being returned, the name
of the CL variable that receives the unique 6-character
Optional Parameters
number assigned to the job by the system. The job file or the job description, will be used for the spooled
number is the first part of the qualified job name. output of this job.
LOGLVL OUTQLIB
Specifies the name of the CL variable that receives the Specifies the name of the CL variable that receives the
1-character value, ranging from 0 through 4, that is the name of the library that contains the output queue being
message logging level used to determine the type of used by the job for spooled output. The library name is
messages logged in the job log. The variable must be a the second part of the qualified output queue name
character variable with a minimum length of 1 character. (output-queue/library-name). The variable must be a
character variable with a minimum length of 10 charac-
LOGSEV
ters. If the output queue library name has fewer charac-
Specifies the name of the CL variable that receives the
ters than the variable allows, the value is padded on the
2-digit value, ranging from 00 through 99, which is the
right with blanks.
minimum severity level a message must have before it is
logged in the job log. The variable must be a 2-digit ACGCDE
decimal variable specified with no decimal positions. Specifies the name of the CL variable that receives the
accounting code for the job. The variable must be a
LOGTYPE
character variable with a minimum length of 15 charac-
Specifies the name of the CL variable that receives the
ters. If the accounting code has fewer characters than
special value that indicates the level of text that appears
the variable allows, the value is padded on the right with
for any message written to the job log. The variable
blanks.
must be a character variable with a minimum length of
10 characters. If the special value has fewer characters DATE
than the variable allows, the value is padded on the right Specifies, if the job date is to be returned, the name of
with blanks. the CL variable that receives the date assigned to the
job by the system when the job was started. The vari-
LOGCLPGM
able must be a character variable with a minimum length
Specifies the name of the CL variable that receives the
of 6 characters. The job date is returned in the system
special value that indicates whether processed com-
date format specified by the system value QDATFMT.
mands in a CL program are being logged in the job log.
Note that this logging flag only has meaning for com- SWS
mands processed in CL programs which were created Specifies, if the job switch settings are being returned,
with LOG(*JOB) specified on the Create CL Program the name of the CL variable that receives the status (on
(CRTCLPGM) command. Additional information on the or off) value of the eight job switches used by the job.
job's CL program logging flag is in the LOGCLPGM The job switches are retrieved as a single 8-character
parameter description in the Change Job (CHGJOB) value with each of the characters specifying a 1 (on) or
command. The variable must be a character variable 0 (off) as the value of the associated switch. The CL
with a minimum length of 10 characters. If the special variable must be a character variable with a minimum
value has fewer characters than the variable allows, the length of 8 characters.
value is padded on the right with blanks.
TYPE
INQMSGRPY Specifies, if the type of job environment is being
Specifies the name of the CL variable that receives the returned, the name of the CL variable that receives the
special value that indicates how inquiry messages are 1-character value representing the environment of the
being handled by the job. Additional information on the job. A character value of 0 indicates the job is running
value returned in the variable is in the INQMSGRPY as a batch job, and a 1 indicates an interactive job. The
parameter description in the Change Job (CHGJOB) variable must be a character variable with a minimum
command. The variable must be a character variable length of 1 character.
with a minimum length of 10 characters. If the special
RTNCDE
value has fewer characters than the variable allows, the
Specifies (if the completion status of an RPG, COBOL,
value is padded on the right with blanks.
DFU, or sort utility program is being returned) the name
OUTQ of the CL variable that receives the 5-digit decimal return
Specifies the name of the CL variable that receives the code. The return code is set by these programs before
name of the output queue being used by the job for they return to the programs that called them. The return
spooled output. The variable must be a character vari- code indicates the completion status of the last program
able with a minimum length of 10 characters. If the (of these types) that has completed processing within
output queue name has fewer characters than the vari- the job, as follows:
able allows, the value is padded on the right with blanks.
0 Normal return (RPG, COBOL, DFU, or sort Utility)
The special value *DEV can be retrieved. This value
1 LR (last record) indicator on (RPG)
indicates that the output queue with the same name as
the printer device, which is specified on either the printer
PRTTXT CURUSER
Specifies the name of the CL variable that receives the Specifies, if the user name is returned, the 10-character
print text for the job. This must be a character variable CL variable that receives the name of the current user
with a minimum length of 30 characters. More informa- profile. If the current user name has fewer characters
tion on this parameter is in Appendix A, “Expanded than the variable allows, the value is padded on the right
Parameter Descriptions.” with blanks.
DDMCNV SUBTYPE
Specifies the name of a CL variable that receives the Specifies, if the SUBTYPE of job environment is being
special value that indicates the action taken for DDM returned, the 1-character CL variable that receives the
conversations on the job. The variable must be a char- name of the job environment. The valid character
acter variable with a minimum length of 5 characters. If values are:
the special value has fewer characters than the variable
Character Value
allows, the value is padded on the right with blanks.
* Job has no subtype
BRKMSG
Specifies the name of a CL variable that receives the E Job is running as an evoked job
special value that indicates the mode for break message T Job is running as a Multiple
handling that is in effect for the job. The variable must Requester Terminal (MRT) job
be a character variable with a minimum length of 7 char-
J Job is running as a prestart job
acters. If the special value has fewer characters than
the variable allows, the value is padded on the right with P Job is running as a print driver
blanks.
PRTKEYFMT
DATFMT Specifies the name of the CL variable that receives the
Specifies the name of a CL variable that receives the print key format for the job. The variable must have a
special value being used as the date format for the job. minimum length of 7 characters. The special value
The variable must be a character variable with a *NONE, *PRTBDR, *PRTHDR, or *PRTALL is returned.
minimum length of 4 characters. If the special value has
TIMSEP
fewer than 4 characters, the value is padded on the right
Specifies the name of a CL variable that receives the
with blanks.
character being used as the time separator character for
DATSEP the job. The variable must be a character variable with
Specifies the name of a CL variable that receives the a minimum length of one character.
character being used as the date separator character for
TSEPOOL
the job. The variable must be a character variable with
Specifies the name of the CL variable that receives the
a minimum length of 1 character.
special value indicating whether interactive jobs are
CURLIB moved to another main storage pool when they reach
Specifies the name of a CL variable that is used to the time slice end. The variable must be a character
| retrieve the name of the current library for the thread. variable with a minimum length of 10 characters.
| The variable must be a character variable with a
DEVRCYACN
minimum length of 10 characters. If the current library
Specifies the name of the CL variable that receives the
name has fewer characters than the variable allows, the
special value indicating the recovery action to take for
value is padded on the right with blanks.
the job when an I/O error is encountered on the
| Note: If the thread does not have a current library, a *REQUESTER device for interactive jobs. The variable
| value of *NONE is returned in this variable. must be a character variable with a minimum length of
13 characters.
PRTDEV
Specifies the name of the CL variable that receives the STSMSG
name of the printer device. The variable must be a Specifies the name of the CL variable that receives the
character variable with a minimum length of 10 charac- special value indicating how status messages are
ters. If the printer device name has fewer characters handled for the job. The variable must be a character
than the variable allows, the value is padded on the right variable with a minimum length of 7 characters.
with blanks.
SRTSEQ
SYSLIBL Specifies the name of the CL variable that receives the
Specifies the name of the CL variable that receives the name of the sort sequence table used for the job. The
| system portion of the thread's library list. The variable special value *LANGIDUNQ, *LANGIDSHR, or *HEX can
| must be a character variable with up to 165 characters. be returned to the variable. The variable must be a
Each library name returned is left-justified in an
11-character field and padded on the right with blanks.
character variable with a minimum length of 10 charac- century, YY is the year, MM is the month and DD is the
ters. day.
SRTSEQLIB | DECFMT
Specifies the name of the CL variable that receives the | Specifies the name of a CL variable that receives the
name of the library containing the sort sequence table to | character being used as the decimal format for the job.
be used for the job. The variable must be a character | The variable must be a character variable with a
variable with a minimum length of 10 characters. If | minimum length of 1 character.
SRTSEQ is *LANGIDUNQ, *LANGIDSHR, or *HEX,
blanks are returned in the variable.
Example
LANGID RTVJOBA NBR(&JOBNBR) DATE(&JOBDATE) DFTCCSID(&DFTCSID)
Specifies the name of the CL variable that receives the
value indicating the language identifier to be used for the This command retrieves the job number and job date attri-
job. The variable must be a character variable with a butes from the job in which this command is located. The
minimum length of 3 characters. 6-digit job number is copied into the CL variable &JOBNBR.
The job date is copied into the CL variable &JOBDATE; the
CNTRYID
values for both &JOBNBR and &JOBDATE must be 6 char-
Specifies the name of the CL variable that receives the
acters in length. The 5-digit DFTCCSID value is copied into
value indicating the country identifier to be used for the
the CL variable &DFTCCSID; this value must be 5 characters
job. The variable must be a character variable with a
in length. The format of the date is determined by the con-
minimum length of 2 characters.
tents of the system value QDATFMT, which controls the
CCSID system date format.
Specifies the name of a CL variable that receives the /\ Declare Variables \/
CCSID value being used for the job. The variable must DCL &LIBL \CHAR 275
be a 5-digit decimal variable with no decimal positions. DCL &CHGLIBL \CHAR 285
JOBMSGQMX /\ save library list \/
Specifies the name of a CL variable that receives the RTVJOBA USRLIBL(&LIBL)
maximum size of the job message queue. The variable
must be a 2-digit decimal variable with no decimal posi-
tion.
/\ temporarily change library list \/
JOBMSGQFL CHGLIBL LIBL(MYLIB QGPL)
Specifies the action that should be taken when the job
message queue is full. The variable must have a
minimum length of 10 characters. The special value
*NOWRAP, *WRAP, or *PRTWRAP is returned. /\ build command string \/
CHGVAR &CHGLIBL ('CHGLIBL (' \CAT &LIBL \TCAT ')')
DFTCCSID
Specifies the name of a CL variable that receives the /\ restore library list \/
DFTCCSID value being used for the job. The variable CALL QCMDEXC (&CHGLIBL 285)
must be a 5-digit decimal variable with no decimal posi-
tions. The above command retrieves the user portion of the library
list so that it later can be restored from its temporary state,
CYMDDATE where only MYLIB and QGPL were in the user portion of the
Specifies the name of the CL variable that receives the library list, to its original state.
date assigned to the job by the system when the job
was started. The variable must be a character variable If there are no libraries on the user portion of the library list,
with a minimum length of 7 characters. The job date is blanks are returned in the variable. If a library on the library
returned in the format CYYMMDD, where C is the list has been deleted, the value '*DELETED' is put in the var-
iable position for that name.
┌─\LIBL/────────┐
55──RTVJRNE──JRN(──┼───────────────┼──journal-name──)───────────────────────────────────────────────────────────────────────────5
├─\CURLIB/──────┤
└─library-name/─┘
5──┬───────────────────────────────────────────────────────────────────────────────────────┬────────────────────────────────────5
│ ┌─\ALLFILE────────────────────────────────────────────────────────────────┐ │
│ │ ┌──
──────────────────────────────────────────────────────────────────┐ │ │
│ │ │ ┌─\LIBL/────────┐ ┌─\FIRST──────┐ │ │ │
6 (1) (2)
└─FILE(──┴───(──┼───────────────┼──┬─\ALL───────────────┬──┼─────────────┼──)─┴────┴──)─┘
├─\CURLIB/──────┤ └─physical-file-name─┘ ├─\ALL────────┤
└─library-name/─┘ └─member-name─┘
(P) ────────────────5
5──┬────────────────────────────────────────────────────────────────────────────────────────────────────────┬───
│ ┌─\CURRENT───────────────────────────────────────────────────────────────────────────────┐ │
│ ├─\CURCHAIN──────────────────────────────────────────────────────────────────────────────┤ │
│ │ ┌─\CURRENT────────────────────────────────┐ │ │
│ │ ┌─\LIBL/────────┐ │ ┌─\LIBL/────────┐ │ │ │
└─RCVRNG(──┴─┼───────────────┼──start-journal-receiver──┴─┼───────────────┼──end-journal-receiver─┴─┴──)─┘
├─\CURLIB/──────┤ ├─\CURLIB/──────┤
└─library-name/─┘ └─library-name/─┘
5──┬────────────────────────────────────────────────┬──┬──────────────────────────────────────────┬─────────────────────────────5
│ ┌─\FIRST───────────────────┐ │ │ ┌─\LAST──────────────────┐ │
├─FROMENT(──┼─\LAST────────────────────┼──)──────┤ ├─TOENT(──┼─\FIRST─────────────────┼──)────┤
│ └─starting-sequence-number─┘ │ │ └─ending-sequence-number─┘ │
└─FROMTIME(──starting-date──┬───────────────┬──)─┘ └─TOTIME(──ending-date──┬─────────────┬──)─┘
└─starting-time─┘ └─ending-time─┘
5──┬──────────────────────────┬──┬───────────────────────────────────────────────────────┬──────────────────────────────────────5
│ ┌─\ASCEND──┐ │ │ ┌─\ALL──────────────────────────────────┐ │
└─SEARCH(──┴─\DESCEND─┴──)─┘ └─JRNCDE(──┼─\CTL──────────────────────────────────┼──)─┘
│ ┌──
────────────────────────────────┐ │
│ │ ┌─\ALLSLT──────┐ │ │
6 (3) (4)
└───journal-code──┴─\IGNFILSLT───┴─┴────┘
5──┬───────────────────────────────────┬──┬────────────────────────────────────────────────────────┬────────────────────────────5
│ ┌─\ALL──────────────┐ │ │ ┌─\ALL──────────────────────────────────────┐ │
└─ENTTYP(──┼─\RCD──────────────┼──)─┘ └─JOB(──┼─\─────────────────────────────────────────┼──)─┘
│ ┌──
────────────┐ │ └─┬─────────────────────────────┬──job-name─┘
└──6─entry-type─┴───
(5) ─┘ └─┬─────────────┬──user-name/─┘
└─job-number/─┘
5──┬───────────────────────────┬──┬───────────────────────────┬──┬───────────────────────────────────────────┬──────────────────5
│ ┌─\ALL─────────┐ │ │ ┌─\ALL──────┐ │ │ ┌─\ALL────────────────────┐ │
└─PGM(──┴─program-name─┴──)─┘ └─USRPRF(──┴─user-name─┴──)─┘ └─CMTCYCID(──┴─commit-cycle-identifier─┴──)─┘
5──┬───────────────────────┬──┬──────────────────────────┬──┬────────────────────────────────┬──────────────────────────────────5
│ ┌─\ALL──┐ │ │ ┌─\TYPE1─┐ (7) ─field-length──)─┘
│ └─NULLINDLEN(───
(6) ─┼─\TYPE2─┼──)─┘
└─DEPENT(──┴─\NONE─┴──)─┘ └─ENTFMT(───
├─\TYPE3─┤
└─\TYPE4─┘
5──┬──────────────────────────────┬──┬──────────────────────────────────┬──┬──────────────────────────────────┬─────────────────5
| │ ┌─\CONFIRMED─┐ │ └─RTNSEQNBR(──&CL-variable-name──)─┘ └─RTNJRNCDE(──&CL-variable-name──)─┘
| (8) ─┴─\ALL───────┴──)─┘
└─INCENT(───
5──┬──────────────────────────────────┬──┬───────────────────────────────┬──┬──────────────────────────────────┬────────────────5
└─RTNENTTYP(──&CL-variable-name──)─┘ └─RTNRCV(──&CL-variable-name──)─┘ └─RTNRCVLIB(──&CL-variable-name──)─┘
5──┬────────────────────────────────┬──────────────────────────────────────────────────────────────────────────────────────────5%
└─RTNJRNE(──&CL-variable-name──)─┘
Notes:
1 If *ALL is specified instead of physical-file-name, the format must be library-name/*ALL.
physical-file-name: Specify the name of the physical Element 1: Starting Journal Receiver
database file for which a journal entry is retrieved. The name of the starting journal receiver can be quali-
Element 2: Member Name fied by one of the following library values:
*FIRST: An entry for the first member in the file is *LIBL: All libraries in the job's library list are
retrieved. searched until the first match is found.
*ALL: Journal entries for currently existing members in *CURLIB: The current library for the job is
the file are retrieved. searched. If no library is specified as the current
library for the job, the QGPL library is used.
member-name: Specify the name of the member for
which a journal entry is retrieved. library-name: Specify the name of the library to be
searched.
If *ALL is specified for the file-name value, this member
name is used for all applicable files in the library. For
starting-journal-receiver: Specify the name of the first must be enclosed in apostrophes. If a time sepa-
journal receiver that contains journal entries to be rator other than the separator specified for your job
retrieved. is used, this command fails.
Element 2: Ending Journal Receiver Without a time separator, specify a string of 4 or 6
digits (hhmm or hhmmss) where hh = hours, mm =
*CURRENT: The journal receiver that is currently
minutes, and ss = seconds. Valid values for hh
attached when starting to retrieve journal entries is used.
range from 00 through 23. Valid values for mm and
The name of the ending journal receiver can be qualified ss range from 00 through 59.
by one of the following library values:
TOENT
*LIBL: All libraries in the job's library list are Specifies the last journal entry considered for retrieval.
searched until the first match is found.
*LAST: The search continues until the last journal entry
*CURLIB: The current library for the job is in the specified journal receiver range is processed. If
searched. If no library is specified as the current SEARCH(*DESCEND) is specified, TOENT(*LAST) is
library for the job, the QGPL library is used. valid only if FROMENT(*LAST) is also specified.
library-name: Specify the name of the library to be *FIRST: The search continues until the first journal
searched. entry in the specified journal receiver range is pro-
cessed. If SEARCH(*ASCEND) is specified,
ending-journal-receiver: Specify the name of the last
TOENT(*FIRST) is only valid if FROMENT(*FIRST) is
journal receiver containing journal entries to be
also specified.
searched. If the end of the receiver chain is reached
before a receiver of this name is found, an error ending-sequence-number: Specify the sequence
message is sent and no journal entry is retrieved. number of the journal entry that is the final entry consid-
ered for retrieval.
Note: If the maximum number of receivers in the range
is larger than 256, an error message is sent and Note: The values specified for the FROMENT and
no journal entry is retrieved. TOENT parameter can be the same (for
example, FROMENT(234) and TOENT(234) can
FROMENT
be specified).
Specifies the first journal entry considered for retrieval.
TOTIME
*FIRST: The first journal entry in the specified journal
Specifies the date and time of the last entry considered
receiver range is the first entry considered for retrieval.
for retrieval. The first journal entry found with the speci-
If SEARCH(*DESCEND) is specified,
fied date and time, or the latest earlier journal entry is
FROMENT(*FIRST) is valid only if TOENT(*FIRST) is
the ending point for the search.
also specified.
*LAST: The last journal entry in the specified journal
ending-date: Specify the ending date using the format
defined by the system values QDATFMT and, if separa-
receiver range is the first entry considered for retrieval.
tors are used, QDATSEP.
If SEARCH(*ASCEND) is specified, FROMENT(*LAST)
is valid only if TOENT(*LAST) is also specified. ending-time: Specify the ending time. See the
FROMTIME parameter for a description of time formats.
starting-sequence-number: Specify the sequence
number of the journal entry that is the first entry consid- SEARCH
ered for retrieval. Specifies the order in which the journal entries are
searched to retrieve an entry.
FROMTIME
Specifies the date and time of the first journal entry con- *ASCEND: The journal entries are searched in
sidered for retrieval. The first journal entry found with ascending order (from the oldest entry to the newest
the specified date and time or the next later journal entry entry).
is the starting point for the search.
*DESCEND: The journal entries are searched in
starting-date: Specify the starting date using the format descending order (from the newest entry to the oldest
defined by the system values QDATFMT and, if separa- entry).
tors are used, QDATSEP.
JRNCDE
starting-time: Specify the starting time. The time is Specifies the journal codes of the journal entries being
specified in 24-hour format with or without a time sepa- considered for retrieval.
rator as follows:
*ALL: The search for the entry to retrieve is not limited
With a time separator, specify a string of 5 or 8 to a specified journal code.
digits, where the time separator for the job sepa-
*CTL: The entries considered for retrieval are the
rates the hours, minutes, and seconds. If you issue
journal entries created to control the journal functions.
this command from the command line, the string
The journal codes for these are J and F.
Element 1: Journal Code Value job-number: Specify the number of the job whose
journal entries are being considered for retrieval.
journal-code: Specify the journal code to which journal
entries are limited. Only journal entries with the speci- PGM
fied journal code are retrieved. A list of journal codes Specifies the name of a program whose journal entries
that can be specified is provided in the Backup and are considered for retrieval.
Recovery book.
*ALL: The search is not limited to entries for a specified
Element 2: Journal Code Selection program.
*ALLSLT: The journal entries with the specified journal program-name: Specify the name of the program whose
code are retrieved only if all other selection parameters journal entries are considered for retrieval. Only journal
are satisfied. entries for this program are considered for retrieval.
*IGNFILSLT: The journal entries having the specified
USRPRF
journal code are retrieved only if all selection parame-
Specifies that the journal entries to be considered for
ters, except the FILE parameter, are satisfied.
retrieval are limited to the journal entries for a specified
| Note: This value is not valid for journal code D, F or R. user profile name.
55──RTVLIBD──LIB(────library-name────)──┬─────────────────────────────────┬──┬───────────────────────────────────┬──────────────5
└─TYPE(────&CL-variable-name────)─┘ └─CRTAUT(────&CL-variable-name────)─┘
5──┬────────────────────────────────┬──┬──────────────────────────────────────┬──┬─────────────────────────────────┬───────────5%
└─ASP(────&CL-variable-name────)─┘ └─CRTOBJAUD(────&CL-variable-name────)─┘ └─TEXT(────&CL-variable-name────)─┘
┌─\LIBL/────────┐
(P) ─┬──────────────────────────────────────────────────┬────────────────────5
55──RTVMBRD──FILE(──┼───────────────┼──file-name──)────
├─\CURLIB/──────┤ │ ┌─\FIRST──────────────────────────────┐ │
└─library-name/─┘ └─MBR(──┼─\LAST───────────────────────────────┼──)─┘
│ ┌─\SAME─┐ │
└─┬─\FIRSTMBR────────────┬──┼───────┼─┘
├─\LASTMBR─────────────┤ ├─\NEXT─┤
├─member-name──────────┤ └─\PRV──┘
└─generic\-member-name─┘
5──┬──────────────────────────────────┬──┬───────────────────────────────┬──┬───────────────────────────────┬───────────────────5
└─RTNSYSTEM(──&CL-variable-name──)─┘ └─RTNLIB(──&CL-variable-name──)─┘ └─RTNMBR(──&CL-variable-name──)─┘
5──┬────────────────────────────────┬──┬─────────────────────────────────────┬──┬────────────────────────────────┬──────────────5
└─FILEATR(──&CL-variable-name──)─┘ └─FILETYPE(──&CL-variable-name──────)─┘ └─SRCTYPE(──&CL-variable-name──)─┘
5──┬───────────────────────────────────┬──┬────────────────────────────────┬──┬────────────────────────────────┬────────────────5
└─SRCCHGDATE(──&CL-variable-name──)─┘ └─CRTDATE(──&CL-variable-name──)─┘ └─EXPDATE(──&CL-variable-name──)─┘
5──┬─────────────────────────────┬──┬──────────────────────────────────┬──┬──────────────────────────────────┬──────────────────5
└─TEXT(──&CL-variable-name──)─┘ └─NBRCURRCD(──&CL-variable-name──)─┘ └─NBRDLTRCD(──&CL-variable-name──)─┘
5──┬──────────────────────────────┬──┬──────────────────────────────────┬──┬──────────────────────────────────┬─────────────────5
└─SHARE(──&CL-variable-name──)─┘ └─DTASPCSIZ(──&CL-variable-name──)─┘ └─ACCPTHSIZ(──&CL-variable-name──)─┘
5──┬────────────────────────────────┬──┬────────────────────────────────┬──┬────────────────────────────────┬───────────────────5
└─CHGDATE(──&CL-variable-name──)─┘ └─SAVDATE(──&CL-variable-name──)─┘ └─RSTDATE(──&CL-variable-name──)─┘
5──┬───────────────────────────────────┬──┬────────────────────────────────┬──┬─────────────────────────────────┬───────────────5
└─NBRDTAMBRS(──&CL-variable-name──)─┘ └─USEDATE(──&CL-variable-name──)─┘ └─USECOUNT(──&CL-variable-name──)─┘
5──┬──────────────────────────────────┬────────────────────────────────────────────────────────────────────────────────────────5%
└─RESETDATE(──&CL-variable-name──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
Optional Parameters (retrieves the attribute for a physical file member) and
*LF (retrieves the attribute for a logical file member).
MBR
Specifies the member whose description is retrieved. FILETYPE
Specifies the name of a 5-character CL variable used to
*FIRST: The first member in the database file is used. retrieve the file type. The possible values are *DATA
*LAST: The last member of the specified physical file is (retrieves the file type for a data member) and *SRC
retrieved. (retrieves the file type for a source member).
Element 1: Member to Retrieve SRCTYPE
*FIRSTMBR: The first member in a list sorted by name Specifies the name of a 10-character CL variable used
is retrieved. to retrieve the source member type (if this is a source
member). Blanks are returned if this is not a source
*LASTMBR: The last member in a list sorted by name member.
is retrieved.
SRCCHGDATE
member-name: Specify the name of the reference
Specifies the name of a 13-character CL variable used
member. The reference member is a base from which
to retrieve the century, date, and time the last source file
the *NEXT, *PRV, or *SAME member is retrieved.
member was changed. The format is
generic*-member-name: Specify the generic member CYYMMDDHHMMSS where C=Century (0=1940 through
name being retrieved. A generic name is a character 1999 and 1=2000 through 2039), Y=Year, M=Month,
string of one or more characters followed by an asterisk D=Day, H=Hour, M=Minutes, and S=Seconds. Blanks
(*); for example, ABC*. The asterisk substitutes for any are returned if no date is available or if the date of
valid characters. A generic name specifies all objects remote non-AS/400 system or non-System/38 files are
with names that begin with the generic prefix for which retrieved.
the user has authority. If an asterisk is not included with
the generic (prefix) name, the system assumes it to be CRTDATE
the complete object name. If the complete object name Specifies the name of a 13-character CL variable used
is specified, and multiple libraries are searched, multiple to retrieve the member creation century, date, and time.
objects can be retrieved only if *ALL or *ALLUSR library The format is CYYMMDDHHMMSS where C=Century
values can be specified for the name. For more infor- (0=1940 through 1999 and 1=2000 through 2039),
mation on the use of generic names, refer to “Generic Y=Year, M=Month, D=Day, H=Hour, M=Minutes, and
Object Names” in Chapter 2. S=Seconds.
RTNSYSTEM TEXT
Specifies the name of a 4-character CL variable used to Specifies the name of a 50-character CL variable used
retrieve an indication of the system from which the to retrieve the text description of the file member. More
description is retrieved. The possible values are *LCL information on this parameter is in Appendix A,
(file found on the local system) and *RMT (file found on “Expanded Parameter Descriptions.”
remote system). NBRCURRCD
RTNLIB Specifies the name of a 10-position decimal CL variable
Specifies the name of a 10-character CL variable used used to retrieve the current number of nondeleted
to retrieve the name of the library where the specified records in the member. If the member is a keyed logical
file is located. member, the number of index entries is returned. For
nonkeyed logical members, the number of nondeleted
RTNMBR records in the based-on physical file member is returned.
Specifies the name of a 10-character CL variable used
to retrieve the name of the member whose description is NBRDLTRCD
being retrieved. Specifies the name of a 10-position decimal CL variable
used to retrieve the current number of deleted records in
FILEATR this member. Zero (0) is returned for keyed logical files.
Specifies the name of a 3-character CL variable used to For nonkeyed logical files, the number of nondeleted
retrieve the file attribute. The possible values are *PF records in the based-on physical file member is returned.
SHARE USECOUNT
Specifies whether the open data path (ODP) for the Specifies the name of a 5 position decimal CL variable
member description is shared with other programs in the used to return the number of days the object has been
routing step. When an ODP is shared, the programs used. If the object does not have a last used date, 0 will
accessing the file share facilities such as the file status be returned.
and the buffer.
RESETDATE
More information on shared database files is in the DB2 Specifies the name of a 7-character CL variable that is
for AS/400 Database Programming book. used to return the date the days-used count was last
reset to 0. The date will be returned in the form
DTASPCSIZ
CYYMMDD where C=Century (0=1940 through 1999
Specifies the name of a 15-position decimal CL variable
and 1=2000 through 2039), Y=Year, M=Month, and
used to retrieve the data space size (in bytes) of this
D=Day. If the days used count has not been reset,
member. Zero (0) is returned if this is a logical member.
blanks will be returned.
ACCPTHSIZ
Specifies the name of a 12-position decimal CL variable
used to retrieve the access path size (in bytes) for this
Examples
member. Zero (0) is returned if the member is non-
keyed. Remote non-AS/400 system and non-System 38 Assume the user has a file named MYFILE in library MYLIB
files return a value of zero (0). (which is the current library) with members QMEMBER,
BMEMBER, ZMEMBER, and JMEMBER (created in that
CHGDATE order).
Specifies the name of a 13-character CL variable used
to retrieve the member change century, date, and time. Also assume the following variables are specified in the CL
The format is CYYMMDDHHMMSS where C=Century program:
(0=1940 through 1999 and 1=2000 through 2039),
Y=Year, M=Month, D=Day, H=Hour, M=Minutes, and DCL &LIB TYPE(\CHAR) LEN(1ð)
S=Seconds. DCL &MBR TYPE(\CHAR) LEN(1ð)
DCL &SYS TYPE(\CHAR) LEN(4)
SAVDATE DCL &MTYPE TYPE(\CHAR) LEN(5)
Specifies the name of a 13-character CL variable used DCL &CRTDATE TYPE(\CHAR) LEN(13)
to retrieve the member save century, date, and time. DCL &CHGDATE TYPE(\CHAR) LEN(13)
The format is CYYMMDDHHMMSS where C=Century DCL &TEXT TYPE(\CHAR) LEN(5ð)
DCL &NBRRCD TYPE(\DEC) LEN(1ð ð)
(0=1940 through 1999 and 1=2000 through 2039),
DCL &SIZE TYPE(\DEC) LEN(1ð ð)
Y=Year, M=Month, D=Day, H=Hour, M=Minutes, and
S=Seconds. Blanks are returned if no date is available. This command is run:
Remote non-AS/400 system and non-System 38 files
return blanks. RTVMBRD FILE(\CURLIB/MYFILE) MBR(BMEMBER \SAME)
RTNLIB(&LIB) RTNSYSTEM(&SYS) RTNMBR(&MBR)
RSTDATE FILEATR(&MTYPE) CRTDATE(&CRTDATE) TEXT(&TEXT)
Specifies the name of a 13-character CL variable used NBRCURRCD(&NBRRCD) DTASPCSIZ(&SIZE)
to retrieve the member restore century, date, and time.
The format is CYYMMDDHHMMSS where C=Century The requested information is placed in the CL variables as
(0=1940 through 1999 and 1=2000 through 2039), follows:
Y=Year, M=Month, D=Day, H=Hour, M=Minutes, and
The current library name (MYLIB) is placed in the CL
S=Seconds. Blanks are returned if there is no date
variable named &LIB.
available.
The system on which MYFILE was found is placed in the
NBRDTAMBRS CL variable named &SYS. (*LCL means the file was
Specifies the name of a 2-position decimal CL variable found on the local system, and *RMT means the file was
used to retrieve the number of data members for this found on a remote system.)
logical member. If the member is a physical member,
zero (0) is returned. The member name (BMEMBER) is placed in the CL var-
iable named &MBR.
USEDATE
The file attribute of MYFILE is placed in the CL variable
Specifies the name of a 7-character CL variable that is
named &MTYPE. (*DATA means the member is a data
used to retrieve the date the object was used last. The
member, and *SRC means the file is a source member.)
date will be returned in the form CYYMMDD where
C=Century (0=1940 through 1999 and 1=2000 through The creation date of BMEMBER is placed in the CL vari-
2039), Y=Year, M=Month, and D=Day. If the object able named &CRTDATE.
does not have a last-used date, blanks will be returned. The text associated with BMEMBER is placed in the CL
variable called &TEXT.
The current number of records in BMEMBER is placed RTVMBRD FILE(\CURLIB/MYFILE) MBR(ZMEMBER \PRV)
in the CL variable called &NBRRCD. RTNMBR(&MBR) CHGDATE(&CHGDATE) TEXT(&TEXT)
The size of BMEMBER's data space (in bytes) is placed The requested information is placed in the CL variables as
in the CL variable called &SIZE. follows:
This command is run next: The member name (QMEMBER since it is the member
just previous to ZMEMBER in a name ordered list) is
RTVMBRD FILE(&LIB/MYFILE) MBR(&MBR \NEXT) placed in the CL variable named &MBR.
RTNMBR(&MBR) CRTDATE(&CRTDATE) TEXT(&TEXT) The date QMEMBER was last changed is placed in the
NBRCURRCD(&NBRRCD) DTASPCSIZ(&SIZE) CL variable named &CHGDATE.
The text associated with QMEMBER is placed in the CL
Then the requested information is placed in the CL variables
variable called &TEXT.
as follows:
The next members name after BMEMBER (JMEMBER If only the first part of the member name is known, the user
since the file is searched in name order) in MYFILE is can do a Generic* (or partial name) search of the list of
placed in the CL variable named &MBR. members, as follows:
The creation date of JMEMBER is placed in the CL vari- RTVMBRD FILE(\LIBL/MYFILE) MBR(JM\) RTNMBR(&MBR)
able named &CRTDATE. CHGDATE(&CHGDATE) TEXT(&TEXT)
The text associated with JMEMBER is placed in the CL
The requested information is placed in the CL variables as
variable called &TEXT.
follows:
The current number of records in JMEMBER is placed in
The member name (JMEMBER since it is the first
the CL variable called &NBRRCD.
member starting with the characters JM in a name
The size of JMEMBER’s data space (in bytes) is placed ordered list) is placed in the CL variable named &MBR.
in the CL variable called &SIZE. The date JMEMBER was last changed is placed in the
CL variable named &CHGDATE.
The file can also be searched backwards. An example is:
The text associated with JMEMBER is placed in the CL
variable called &TEXT.
┌─\LIBL/────────┐
(P)────────────────────────────────────5
55──RTVMSG──MSGID(──message-identifier──)──MSGF(──┼───────────────┼──message-file-name──)───
├─\CURLIB/──────┤
└─library-name/─┘
┌─\JOB───────────────────────────┐
5──CCSID(──┼─\HEX───────────────────────────┼──)──┬───────────────────────────────┬──┬────────────────────────────┬─────────────5
└─coded-character-set-identifier─┘ └─MSGDTA(──&CL-variable-name──)─┘ └─MSG(──&CL-variable-name──)─┘
5──┬───────────────────────────────┬──┬───────────────────────────────┬──┬──────────────────────────────────┬───────────────────5
└─MSGLEN(──&CL-variable-name──)─┘ └─SECLVL(──&CL-variable-name──)─┘ └─SECLVLLEN(──&CL-variable-name──)─┘
5──┬────────────────────────────┬──┬───────────────────────────────┬──┬───────────────────────────────┬─────────────────────────5
└─SEV(──&CL-variable-name──)─┘ └─ALROPT(──&CL-variable-name──)─┘ └─LOGPRB(──&CL-variable-name──)─┘
5──┬─────────────────────────────────┬──┬─────────────────────────────────┬─────────────────────────────────────────────────────5
└─TXTCCSID(──&CL-variable-name──)─┘ └─DTACCSID(──&CL-variable-name──)─┘
┌─\JOB───────────────────────────┐
5──MDTACCSID(──┼─\HEX───────────────────────────┼──)───────────────────────────────────────────────────────────────────────────5%
└─coded-character-set-identifier─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose MSGF
Specifies the qualified name of the message file that
The Retrieve Message (RTVMSG) command is used in a CL contains the predefined message being retrieved.
program or REXX procedure to retrieve a specified prede-
The name of the message file can be qualified by one of
fined message from a message file and to copy it into CL
the following library values:
variables. Substitution values can be specified in the
MSGDTA parameter (as a single character string containing *LIBL: All libraries in the job's library list are
one or more concatenated message data fields) to replace searched until the first match is found.
the substitution variables in the predefined message text.
*CURLIB: The current library for the job is
The program can later write the message to an output device
searched. If no library is specified as the current
file to be printed, for example.
library for the job, the QGPL library is used.
The CL prompt for this command lists the minimum length for library-name: Specify the name of the library to be
retrieved variables next to the parameters that have a searched.
minimum length. For character variables, a single number is
shown. For decimal variables, two numbers are shown. The message-file-name: Specify the name of the message
first number indicates the minimum variable length and the file to use.
second number indicates the minimum number of decimal
positions. Optional Parameters
Restriction: The user of this command must have *USE CCSID
authority for the message file and the library in which the Specifies the coded character set identifier (CCSID) in
message file is stored. which you want your message text returned. This
Note: To see the parameter and value descriptions for this applies only to text returned in the MSG and SECLVL
command, refer to the online help text. For more parameters. When replacement data is substituted into
information about printing the help text, refer to the text returned in the MSG or SECLVL parameters,
“Printing CL Command Descriptions” in Chapter 1. only the part of the replacement data that is defined as a
character that can be converted (*CCHAR) is converted.
The rest of the replacement data will not be converted.
Required Parameters For more information about the *CCHAR field, see the
Add Message Description (ADDMSGD) command.
MSGID
Specifies the message identifier of the predefined *JOB: The retrieved message description is converted
message being retrieved from the specified message to the CCSID of the job before being returned.
file. *HEX: The retrieved message description is not con-
verted before being returned.
coded-character-set-identifier: Specify the CCSID that For more information on coding this parameter, refer to
you want your message description converted to before the description of the MSGDTA parameter in the
it is returned. SNDUSRMSG or SNDPGMMSG commands.
Note: The valid values range from 1 through 65535. MSG
See the International Application Development Specifies the name of the CL character variable in the
book for a list of valid CCSID values. Only those program into which the first-level message text from the
CCSID values that the job can be changed to are retrieved message is copied. If a CL variable name is
accepted. not specified, the text is not copied into the program.
For more information on the message handler and its The specified variable must be a character variable. If
use of CCSIDs, see the National Language Support the retrieved text is longer than the variable's field
book. length, the text is truncated. If the text is shorter, it is
MSGDTA padded to the right with blanks. Although this is a
Specifies the substitution values that are used in the variable-length field, most first-level message text is
retrieved message if the predefined message contains designed to be less than 132 characters.
substitution variables. Either a character string or a CL MSGLEN
variable containing the character string can be specified. Specifies the name of the CL decimal variable in the
As many substitution values can be specified in the program into which the total length of the text available
character string as there are substitution variables in the to be retrieved is copied. The length specified is the
predefined message. The values, which take the place total length after the substitution values (specified in the
of the substitution variables defined in the message text MSGDTA parameter) are placed in the text.
when the message was defined, must be specified by
the following rules: The specified variable must be a decimal variable that
has a length of five digits. If a CL variable name is not
Multiple values must be concatenated to form a specified, the length is not copied into the program.
single character string. The length of the entire
character string of concatenated substitution values SECLVL
cannot exceed 512 characters. The CL Program- Specifies the name of the CL character variable in the
ming book has more details. program into which the second-level message text of the
retrieved message is copied. If a variable name is not
Multiple values must be specified in the same order specified, the second-level message text is not copied
in the character string as the substitution variables into the program.
were defined in the FMT parameter of the
ADDMSGD command. If the retrieved second-level message text is longer than
the variable's field length, the text is truncated. If the
Each value must be specified as long as its associ- text is shorter, it is padded on the right with blanks.
ated variable was defined, and the specified char- Although this is a variable length field, most second-level
acter string must be the same length as the sum of message text is designed to be less than 3000 charac-
the message data fields defined in the message ters.
description.
SECLVLLEN
For multiple values, each substitution value can be
Specifies the name of the CL decimal variable in the
specified as a CL program constant or CL variable;
program into which the total length of the second-level
that is, any combination of constants and variables
message text being retrieved is copied. The length
can be specified if they are first concatenated into
specified is the total length after the substitution values
one character string and they are in the same
(specified in the MSGDTA parameter) are placed in the
format and sequence expected.
second-level message text.
The length of the substitution value should be the
The specified variable must be a decimal variable that
same length as the length defined for the substi-
has a length of five positions. If a CL variable name is
tution variables. If the substitution value length is
not specified, the length is not copied into the program.
longer than the substitution variable length, the
message data is truncated. If the substitution value SEV
is shorter, it becomes a null field. Specifies the name of the CL decimal variable into which
the severity code of the retrieved message is copied.
The message data supplied by this command that
The specified variable must be a decimal variable that
corresponds to a *CCHAR type field is assumed to
has a length of two positions. If a variable name is not
be in the CCSID of the job running this command
specified, the severity code of the retrieved message is
unless the MDTACCSID parameter is coded. For
not copied into the program.
more information on the *CCHAR type field, see the
Add Message Description (ADDMSGD) command.
ALROPT If they are not equal and they are not 65535, a conver-
Specifies the name of the CL variable into which the sion error occurred.
alert option of the retrieved message is copied. The var-
MDTACCSID
iable must be a character variable nine positions long.
Specifies the CCSID that the supplied message data is
LOGPRB to be considered in. This only applies to the parts of the
Specifies the name of the variable into which a Y (yes) replacement data that are defined as *CCHAR. The rest
or N (no) is returned indicating whether or not the of the replacement data will never be converted and is
message can be logged in the service activity log. The assumed to have a CCSID of 65535.
variable must be a character variable one position long.
*JOB: The message data supplied is assumed to be in
TXTCCSID the CCSID of the job running this command.
Specifies the name of the CL variable, if any, used to *HEX: The message data supplied is assumed to be
return the coded character set identifier (CCSID) associ- 65535 and is never converted.
ated with the text returned by the MSG and SECLVL
parameters. If a conversion error occurs, or if the
coded-character-set-identifier: The message data sup-
plied is assumed to be in the CCSID specified. Valid
CCSID you requested the text to be converted to is
values range from 1 through 65535. For a list of valid
65535, the CCSID that the message description is
CCSID values, see the International Application Devel-
stored in is returned. Otherwise, the CCSID you wanted
the text converted to is returned. If you do not want the
opment book.
text converted before it is returned to you but you do
want to know the CCSID that the message description is Examples
stored in, specify 65535 on the CCSID parameter. The
CCSID that the message description is stored in is Example 1: Replacing Substitution Variables
returned in the TXTCCSID parameter. You can also RTVMSG MSGID(UINð145) MSGF(INVN) MSG(&WORK)
check for a conversion error by comparing the CCSID MSGDTA('any old time')
you passed in against the TXTCCSID returned. If they
are not equal and they are not 65535, a conversion error This command retrieves the message text of the message
occurred. UIN0145 stored in the INVN message file. The retrieved text
is copied into the CL variable &WORK after the substitution
DTACCSID variables are replaced with the values any, old, and time.
Specifies the name of the CL variable, if any, used to This example assumes that the substitution variables &1, &2,
return the coded character set identifier (CCSID) associ- and &3 have been defined in the message as character vari-
ated with the replacement data defined as *CCHAR. All ables, each 4 characters long.
other replacement data is not converted before it is
returned. If a conversion error occurs, or if the CCSID Example 2: Retrieving First- and Second-Level Message
you requested the text to be converted to is 65535, the Text
CCSID specified on the MDTACCSID parameter is
RTVMSG MSGID(UINð15ð) MSGF(INV) MSG(&MSG)
returned. Otherwise the CCSID you wanted the text
SECLVL(&SECLVL)
converted to is returned. In the case when there is no
*CCHAR replacement data in the text, 65535 is returned. This command retrieves the first- and second-level message
You can check for a conversion error by comparing the text of the message UIN0150, which is stored in message file
CCSID you passed in against the DTACCSID returned. INV, and moves it into the CL variables &MSG and
&SECLVL.
(P)─┬────────────────────────────────┬──┬───────────────────────────────────┬──┬─────────────────────────────────┬───5
55──RTVNETA───
└─SYSNAME(──&CL-variable-name──)─┘ └─PNDSYSNAME(──&CL-variable-name──)─┘ └─LCLNETID(──&CL-variable-name──)─┘
5──┬──────────────────────────────────┬──┬───────────────────────────────────┬──┬────────────────────────────────┬──────────────5
└─LCLCPNAME(──&CL-variable-name──)─┘ └─LCLLOCNAME(──&CL-variable-name──)─┘ └─DFTMODE(──&CL-variable-name──)─┘
5──┬─────────────────────────────────┬──┬───────────────────────────────┬──┬──────────────────────────────────┬─────────────────5
└─NODETYPE(──&CL-variable-name──)─┘ └─DTACPR(──&CL-variable-name──)─┘ └─DTACPRINM(──&CL-variable-name──)─┘
5──┬──────────────────────────────────┬──┬────────────────────────────┬──┬──────────────────────────────────┬───────────────────5
└─MAXINTSSN(──&CL-variable-name──)─┘ └─RAR(──&CL-variable-name──)─┘ └─NETSERVER(──&CL-variable-name──)─┘
5──┬───────────────────────────────┬──┬─────────────────────────────────┬──┬─────────────────────────────────┬──────────────────5
└─ALRSTS(──&CL-variable-name──)─┘ └─ALRPRIFP(──&CL-variable-name──)─┘ └─ALRDFTFP(──&CL-variable-name──)─┘
5──┬─────────────────────────────────┬──┬─────────────────────────────────┬──┬───────────────────────────────┬──────────────────5
└─ALRBCKFP(──&CL-variable-name──)─┘ └─ALRRQSFP(──&CL-variable-name──)─┘ └─ALRFTR(──&CL-variable-name──)─┘
5──┬──────────────────────────────────┬──┬──────────────────────────────────┬──┬────────────────────────────────┬───────────────5
└─ALRFTRLIB(──&CL-variable-name──)─┘ └─ALRLOGSTS(──&CL-variable-name──)─┘ └─ALRCTLD(──&CL-variable-name──)─┘
5──┬──────────────────────────────────┬──┬─────────────────────────────┬──┬────────────────────────────────┬────────────────────5
└─ALRHLDCNT(──&CL-variable-name──)─┘ └─MSGQ(──&CL-variable-name──)─┘ └─MSGQLIB(──&CL-variable-name──)─┘
5──┬─────────────────────────────┬──┬────────────────────────────────┬──┬───────────────────────────────┬───────────────────────5
└─OUTQ(──&CL-variable-name──)─┘ └─OUTQLIB(──&CL-variable-name──)─┘ └─JOBACN(──&CL-variable-name──)─┘
5──┬───────────────────────────────┬──┬───────────────────────────────┬──┬──────────────────────────────────┬───────────────────5
└─MAXHOP(──&CL-variable-name──)─┘ └─DDMACC(──&CL-variable-name──)─┘ └─DDMACCLIB(──&CL-variable-name──)─┘
5──┬───────────────────────────────┬──┬──────────────────────────────────┬──┬───────────────────────────────────┬───────────────5
└─PCSACC(──&CL-variable-name──)─┘ └─PCSACCLIB(──&CL-variable-name──)─┘ └─DFTNETTYPE(──&CL-variable-name──)─┘
5──┬──────────────────────────────────┬──┬───────────────────────────────────┬──┬──────────────────────────────────┬────────────5
| └─DFTCNNLST(──&CL-variable-name──)─┘ └─ALWVRTAPPN(──&CL-variable-name──)─┘ └─ALWHPRTWR(──&CL-variable-name──)─┘
5──┬───────────────────────────────────┬──┬──────────────────────────────────┬─────────────────────────────────────────────────5%
| └─VRTAUTODEV(──&CL-variable-name──)─┘ └─HPRPTHTMR(──&CL-variable-name──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose PNDSYSNAME
Specifies the name of the CL variable that receives the
The Retrieve Network Attributes (RTVNETA) command is pending system name. Specify the name of the char-
used in a CL program or REXX procedure to retrieve the acter variable with a minimum length of 8 characters.
network attributes of the system. The value returned is blank if no pending system name
is provided. If the system name has fewer characters
The values are returned (copied) to the specified CL vari- than the variable allows, the value is padded on the right
ables. with blanks.
Restriction: The attributes of the network attribute and the LCLNETID
receiving CL variable must be compatible. Specifies the name of the CL variable that receives the
Note: To see the parameter and value descriptions for this current local network ID. Specify the name of the char-
command, refer to the online help text. For more acter variable with a minimum length of 8 characters. If
information about printing the help text, refer to the network ID has fewer characters than the variable
“Printing CL Command Descriptions” in Chapter 1. allows, the value is padded on the right with blanks.
LCLCPNAME
Optional Parameters Specifies the name of the CL variable that receives the
current local control point. Specify the name of the char-
SYSNAME acter variable with a minimum length of 8 characters. If
Specifies the name of the CL variable that receives the the control point has fewer characters than the variable
current system name. Specify the name of a character allows, the value is padded on the right with blanks.
variable with a minimum length of 8 characters. If the
system name has fewer characters than the variable LCLLOCNAME
allows, the value is padded on the right with blanks. Specifies the local location name.
-3 *REQUIRE: Data compression is required on the *ON Alert processing is currently active.
session. If the remote system does not change the *UNATTEND Alert processing is currently active, but
levels of compression to the local system's exact the system is unattended.
requested levels, the session is not established.
The data compression levels that the local system *OFF Alert processing is currently inactive.
requires are the specified levels. ALRPRIFP
DTACPRINM Specifies the name of the CL variable that receives the
Specifies the name of the CL variable that receives the primary alert focal point. Specify the name of a char-
current level of intermediate node data compression. acter variable with a minimum length of 10 characters. If
the primary focal point value has fewer characters than
the variable allows, the value is padded on the right with The values that can be returned in the variable as the
blanks. current alert logging status are:
The values that can be returned in the variable as the *NONE Do not log alerts.
primary alert focal point are:
*LOCAL Log only locally generated alerts.
*NO The system is not an alert primary focal *RCV Log only alerts received from other nodes.
point.
*ALL Log both locally generated and incoming
*YES The system is an alert primary focal point. alerts.
ALRDFTFP ALRCTLD
Specifies the name of the CL variable that receives the Specifies the name of the CL variable that receives the
default alert focal point. Specify the name of a character name of the controller through which alert messages are
variable with a minimum length of 10 characters. If the sent to another system when alert processing is active.
default focal point value has fewer characters than the Specify the name of a character variable with a minimum
variable allows, the value is padded on the right with length of 10 characters. If the alert controller name has
blanks. fewer characters than the variable allows, the value is
The values that can be returned in the variable as the padded on the right with blanks.
default alert focal point are: The values that can be returned in the variable are:
*NO The system is not an alert default focal *NONE There is no controller for alerts.
point.
controller-name
*YES The system is an alert default focal point.
Specifies the name of the controller being
ALRBCKFP used for alerts in an alert controller session.
Specifies the name of the CL variable that receives the This controller is ignored if the system has a
name of the system that provides alert focal point ser- primary or default alert focal point (if, for
vices if the primary focal point is unavailable. You must example, the node is in another system's
specify the name of a character variable with a minimum sphere of control).
length of 10 characters. If the back up system name
ALRHLDCNT
has fewer characters than the variable allows, the value
Specifies the name of the CL variable that receives the
is padded on the right with blanks.
maximum number of alerts that are created before the
ALRRQSFP alerts are sent over the alert controller session
Specifies the name of the CL variable that receives the (ALRCTLD network attribute). The alerts are held
name of the system that is requested to provide alert (queued) by the system until the specified number of
focal point services. You must specify the name of a alerts have been created. This parameter can be used
character variable with a minimum length of 10 charac- to manage alerts that are sent over a limited resource by
ters. If the requesting system name has fewer charac- reducing the number of times alerts are sent. Specify
ters than the variable allows, the value is padded on the the name of a decimal variable with a total length of 5
right with blanks. digits without decimal positions. The maximum number
of alerts that can be created before the alerts are sent is
ALRFTR 32,767.
Specifies the name of the CL variable that receives the
Note: The ALRHLDCNT network attribute only applies
name of the active alert filter. You must specify the
when the ALRCTLD network attribute is used.
name of a character variable with a minimum length of
When management services sessions, APPN,
10 characters. If the alert filter name has fewer charac-
and sphere of control support are used, the
ters than the variable allows, the value is padded on the
ALRHLDCNT value is ignored.
right with blanks.
The value that can be returned in the variable as the
ALRFTRLIB
maximum number of alerts is:
Specifies the name of the CL variable that receives the
name of the library that contains the alert filter definition.
*NOMAX The alerts are held indefinitely. The current
Specify the name of a character variable with a minimum
alert hold count is the maximum value. The
length of 10 characters. If the library name has fewer
alerts can be sent at a later time by
characters than the variable allows, the value is padded
changing the ALRHLDCNT value to a lower
on the right with blanks.
value.
ALRLOGSTS
MSGQ
Specifies the name of the CL variable that receives the
Specifies the name of the CL variable that receives the
current alert logging status. Specify the name of a char-
group message queue name. This must be a character
acter variable with a minimum length of 10 characters.
variable with a minimum length of 10 characters. If the
message queue name has fewer characters than the value has fewer characters than the variable allows, the
variable allows, the value is padded on the right with value is padded on the right with blanks.
blanks.
The values that can be returned in the variable as the
MSGQLIB current system action for DDM requests are:
Specifies the name of the CL variable that receives the
*REJECT The system does not allow any DDM
name of the library that contains the system-default
requests from remote systems. However,
network message queue. Specify the name of a char-
the system may use DDM to access files on
acter variable with a minimum length of 10 characters. If
remote systems. (A remote system cannot
the library name has fewer characters than the variable
access any file on a system that specifies
allows, the value is padded on the right with blanks.
*REJECT).
OUTQ *OBJAUT All file requests are allowed and controlled
Specifies the name of the CL variable that receives the by the object authorizations on the system
system default network output queue name. Specify the (normal system object level security).
name of a character variable with a minimum length of
10 characters. If the output queue name has fewer
program-name
Specifies the name of the customer vali-
characters than the variable allows, the value is padded
dation program that can supplement object
on the right with blanks.
level security. This user-exit program can
OUTQLIB restrict user access to *PUBLIC and private
Specifies the name of the CL variable that receives the files. The target DDM support calls the user
name of the library that contains the system-default program for each reference to a file. The
network message queue. Specify the name of a char- user-exit program indicates to DDM if the
acter variable with a minimum length of 10 characters. If request should proceed or end.
the library name has fewer characters than the variable
DDMACCLIB
allows, the value is padded on the right with blanks.
Specifies the name of the CL variable that receives the
JOBACN name of the library that contains the DDM access
Specifies the name of the CL variable that receives the program. Specify the name of a character variable with
current job action for input streams received through the a minimum length of 10 characters. If the library name
network. Specify the name of a character variable with has fewer characters than the variable allows, the value
a minimum length of 10 characters. If the job action is padded on the right with blanks. If *REJECT or
value has fewer characters than the variable allows, the *OBJAUT is returned for the DDMACC parameter, the
value is padded on the right with blanks. value for DDMACCLIB is all blanks.
The values that can be returned in the variable as the PCSACC
current job action are: Specifies the name of the CL variable that receives the
current system action for PCS requests. Specify the
*FILE Input streams received from the network are name of a character variable with a minimum length of
filed in the queue of network files for the 10 characters. If the PCS access value has fewer char-
user to which it was sent. acters than the variable allows, the value is padded on
*REJECT Input streams received from the network are the right with blanks.
rejected. The values that can be returned in the variable as the
*SEARCH The table of network job entries is searched current system action for PCS requests are:
to determine the action for any input
*REJECT The system does not allow any PCS
streams received.
requests.
MAXHOP *OBJAUT All PCS requests are allowed and controlled
Specifies the name of the CL variable that receives the by the object authorizations on the system.
maximum number of systems in the SNADS network so
*REGFAC The registration facility is used to determine
that a distribution queue originating at this node may be
exit programs for the different servers. If no
received and rerouted on the path to its final destination.
program is defined in the registration facility,
Specify the name of a decimal variable with a total
*OBJAUT is used.
length of 5 digits without decimal positions.
program-name
DDMACC
Specify the name of the customer supplied
Specifies the name of the CL variable that receives the
Client Access/400 host system application
current system action for DDM requests from other
exit program that can supplement system
systems. Specify the name of a character variable with
object level security.
a minimum length of 10 characters. If the DDM access
*INSNET64: Indicates the INSNET64 ISDN controlled DCL VAR(&SNAME) TYPE(\CHAR) LEN(8)
DCL VAR(&HOPS) TYPE(\DEC) LEN(5 ð)
by Japan's Nippon Telephone and Telegraph Public Cor-
RTVNETA SYSNAME(&SNAME) MAXHOP(&HOPS)
poration (NTT).
*NISDN: Indicates an ISDN that uses the National This command retrieves the current system name and the
ISDN-1 or National ISDN-2 standard for North America. maximum number of systems in a SNADS network so that a
distribution queue entry can be received and rerouted on the
*NT100B29: Indicates an ISDN in the United States or
path to its destination.
Canada that uses Northern Telecom DMS100 Version
BCS-29 switching equipment. | Example 2: Retrieving Virtual APPN Support, APPC
DFTCNNLST | Device Limits, and HPR Path Switch Timers
Specifies the name of the CL variable that receives the
system default value for the ISDN connection list. The
| DCL VAR(&ALWVRTAPPN) TYPE(\CHAR) LEN(1ð) | This command retrieves the current network attribute settings
| DCL VAR(&VRTAUTODEV) TYPE(\DEC) LEN(5 ð) | for allow virtual APPN support, automatically created APPC
| DCL VAR(&HPRPTHTMR) TYPE(\CHAR) LEN(4ð) | devices on a virtual controller, and the HPR path switch
| RTVNETA ALWVRTAPPN(&ALWVRTAPPN) VRTAUTODEV(&VRTAUTODEV) |+ timers.
| HPRPTHTMR(&HPRPTHTMR)
┌─\LIBL/────────┐
(P) ─┬───────────────────────────────┬────────────5
55──RTVOBJD──OBJ(──┼───────────────┼──object-name──)──OBJTYPE(──object-type──)────
├─\CURLIB/──────┤ └─RTNLIB(──&CL-variable-name──)─┘
└─library-name/─┘
5──┬───────────────────────────────┬──┬──────────────────────────────────┬──┬─────────────────────────────┬─────────────────────5
└─OBJATR(──&CL-variable-name──)─┘ └─USRDFNATR(──&CL-variable-name──)─┘ └─TEXT(──&CL-variable-name──)─┘
5──┬──────────────────────────────┬──┬────────────────────────────┬──┬────────────────────────────┬─────────────────────────────5
└─OWNER(──&CL-variable-name──)─┘ └─PGP(──&CL-variable-name──)─┘ └─ASP(──&CL-variable-name──)─┘
5──┬───────────────────────────────┬──┬────────────────────────────────┬──┬────────────────────────────────┬────────────────────5
└─OVFASP(──&CL-variable-name──)─┘ └─CRTDATE(──&CL-variable-name──)─┘ └─CHGDATE(──&CL-variable-name──)─┘
5──┬────────────────────────────────┬──┬───────────────────────────────────┬──┬────────────────────────────────┬────────────────5
└─SAVDATE(──&CL-variable-name──)─┘ └─SAVACTDATE(──&CL-variable-name──)─┘ └─RSTDATE(──&CL-variable-name──)─┘
5──┬────────────────────────────────┬──┬──────────────────────────────────┬──┬───────────────────────────────┬──────────────────5
└─CRTUSER(──&CL-variable-name──)─┘ └─CRTSYSTEM(──&CL-variable-name──)─┘ └─OBJDMN(──&CL-variable-name──)─┘
5──┬───────────────────────────────┬──┬────────────────────────────────┬──┬─────────────────────────────────┬───────────────────5
└─USEUPD(──&CL-variable-name──)─┘ └─USEDATE(──&CL-variable-name──)─┘ └─USECOUNT(──&CL-variable-name──)─┘
5──┬──────────────────────────────────┬──┬────────────────────────────┬──┬────────────────────────────┬─────────────────────────5
└─RESETDATE(──&CL-variable-name──)─┘ └─STG(──&CL-variable-name──)─┘ └─CPR(──&CL-variable-name──)─┘
5──┬─────────────────────────────┬──┬────────────────────────────────┬──┬───────────────────────────────┬───────────────────────5
└─SIZE(──&CL-variable-name──)─┘ └─SAVSIZE(──&CL-variable-name──)─┘ └─SAVCMD(──&CL-variable-name──)─┘
5──┬──────────────────────────────────┬──┬──────────────────────────────────┬──┬───────────────────────────────┬────────────────5
| └─SAVSEQNBR(──&CL-variable-name──)─┘ └─SAVLRGSEQ(──&CL-variable-name──)─┘ └─SAVVOL(──&CL-variable-name──)─┘
5──┬───────────────────────────────┬──┬─────────────────────────────┬──┬────────────────────────────────┬───────────────────────5
└─SAVDEV(──&CL-variable-name──)─┘ └─SAVF(──&CL-variable-name──)─┘ └─SAVFLIB(──&CL-variable-name──)─┘
5──┬─────────────────────────────────┬──┬─────────────────────────────┬──┬────────────────────────────────┬─────────────────────5
└─SAVLABEL(──&CL-variable-name──)─┘ └─SRCF(──&CL-variable-name──)─┘ └─SRCFLIB(──&CL-variable-name──)─┘
5──┬───────────────────────────────┬──┬────────────────────────────────┬──┬───────────────────────────────┬─────────────────────5
└─SRCMBR(──&CL-variable-name──)─┘ └─SRCDATE(──&CL-variable-name──)─┘ └─SYSLVL(──&CL-variable-name──)─┘
5──┬─────────────────────────────────┬──┬───────────────────────────────┬──┬──────────────────────────────────┬─────────────────5
└─COMPILER(──&CL-variable-name──)─┘ └─OBJLVL(──&CL-variable-name──)─┘ └─ALWAPICHG(──&CL-variable-name──)─┘
5──┬───────────────────────────────┬──┬───────────────────────────────┬──┬───────────────────────────────┬──────────────────────5
└─APICHG(──&CL-variable-name──)─┘ └─USRCHG(──&CL-variable-name──)─┘ └─LICPGM(──&CL-variable-name──)─┘
5──┬────────────────────────────┬──┬─────────────────────────────┬──┬───────────────────────────────┬──────────────────────────5%
└─PTF(──&CL-variable-name──)─┘ └─APAR(──&CL-variable-name──)─┘ └─OBJAUD(──&CL-variable-name──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
RTNLIB CRTDATE
Specifies the name of a variable used to return the Specifies the name of a variable used to return the date
name of the library that contains the object. In a CL and time the object was created. In a CL program, the
program, the variable returned has a length of 10 char- variable returned has a length of 13 characters. The
acters. If *LIBL or *CURLIB is specified for the library value is returned in the form CYYMMDDHHMMSS, where C =
name on the OBJ parameter, the value returned is the century; '0' indicates the 20th century and '1' indicates
name of the library where the object was found. the 21st century; YY = year, MM = month, DD = day, HH
= hour, MM = minutes, and SS = seconds.
OBJATR
Specifies the name of a variable used to return an CHGDATE
extended attribute of the object, such as a program or Specifies the name of a variable used to return the date
file type. In a CL program the variable returned has a and time the object was last changed. In a CL program,
length of 10 characters. For example, the variable may the variable returned has a length of 13 characters. The
be returned with PROD (production) or CLP (control lan- variable is returned in the same format as CRTDATE or
guage program). No asterisk (*) precedes the value. is returned blank if the object has not been changed.
USRDFNATR SAVDATE
Specifies the name of a variable used to return the user- Specifies the name of a variable used to return the date
defined attribute of an object. In a CL program the vari- and time the object was last saved. In a CL program,
able returned has a length of 10 characters. Blanks are the variable returned has a length of 13 characters. The
returned if the retrieved object does not have a user- variable is returned in the same format as CRTDATE or
defined attribute. is returned blank if the object has not been saved.
TEXT SAVACTDATE
Specifies the text that briefly describes the object being Specifies the name of a variable used to return the date
retrieved. More information on this parameter is in and time the object was last saved. In a CL program,
Appendix A, “Expanded Parameter Descriptions.” the variable returned has a length of 13 characters.
Blanks are returned if the object has not been saved or
OWNER if SAVACT(*NO) was specified on the last save opera-
Specifies the name of a variable that is used to return tion for the object.
the name of the object owner's user profile. In a CL
program, the variable returned has a length of 10 char- RSTDATE
acters. Specifies the name of a variable used to return the date
and time the object was last restored. In a CL program,
PGP the variable returned has a length of 13 characters. The
Specifies the name of a variable that is used to return variable is returned in the same format as CRTDATE or
the name of the primary group for the object. If there is is returned blank if the object has not been restored.
no primary group for the object, this field contains a
value of *NONE. In a CL program, the variable returned CRTUSER
has a length of 10 characters. Specifies the name of a variable used to return the
name of the user that created the object. In a CL
ASP program, the variable returned has a length of 10 char-
Specifies the name of a variable that is used to return acters.
the auxiliary storage pool ID. In a CL program, the vari-
able returned has a decimal length of (2 0). The fol- CRTSYSTEM
lowing values can be returned: Specifies the name of a variable used to return the
name of the system on which the object was created. In
1 The object is in the system auxiliary storage a CL program, the variable returned has a length of 8
pool. characters.
2-16 The object is in a user auxiliary storage
OBJDMN
pool.
Specifies the name of a CL variable used to return the
OVFASP object domain value for an object. In a CL program, the
Specifies the name of a variable that is used to return variable returned has a length of 2 characters. A value
the Object Overflowed ASP flag. A value of 1 is of *U indicates the object is in the user domain; a value
returned if the object overflowed the ASP in which it of *S indicates the object is in the system domain.
resides. A value of 0 is returned if the object does not
USEUPD
overflow the ASP. It is not possible for an object
Specifies the name of a variable that indicates whether
residing in the system ASP to overflow its ASP, there-
the object usage information is updated for this object
fore, a value of 0 is always returned for objects in the
type. In a CL program, the variable returned has a
system ASP.
length of 1 character. The indicator is returned as 'Y' or
'N'. If 'N' is returned, the last used date for the object is variable is returned blank if the object has not been
blank. saved.
USEDATE SAVSEQNBR
Specifies the name of a 7-character CL variable used to Specifies the name of a variable used to return the tape
return the date the object was used last. In a CL sequence number generated when the object was saved
program, the variable returned has a length of 7 charac- on tape. In a CL program, the variable returned has a
ters. The date is returned in the form CYYMMDD. If the decimal length of (4 0). The variable is returned with
object does not have a last used date, blanks are zeros if the object has not been saved or was not saved
returned. | to tape. This variable will contain a sequence number
| up to 9999. If a sequence number is actually greater
USECOUNT | than 9999, -1 is returned in this variable. Parameter
Specifies the name of a variable used to return the | SAVLRGSEQ should be used to return a sequence
number of days the object has been used. In a CL | number which can be larger than 9999.
program, the variable returned has a decimal length of
(5 0). If the object does not have a last used date, zero | SAVLRGSEQ
(0) is returned. | Specifies the name of a variable used to return the tape
| sequence number (similar to parameter SAVSEQNBR).
RESETDATE | This variable can contain a larger tape sequence
Specifies the name of a variable used to return the date | number than parameter SAVSEQNBR.
on which the days used count was reset to 0. In a CL
program, the variable returned has a length of 7 charac- SAVVOL
ters. The date is returned in the form CYYMMDD. If the Specifies the name of a variable used to return the tape,
days used count has not been reset, blanks are diskette, or optical volumes used for saving the object.
returned. In a CL program, the variable returned has a length of
71 characters. The variable returns up to 10 six-
STG character volumes. Each volume ID entry is separated
Specifies the name of a variable used to return the by a single blank. The volume IDs begin in character
storage status of the object data. In a CL program, the positions 1, 8, 15, 22, 29, 36, 43, 50, 57, and 64. If
variable returned has a length of 10 characters. *FREE more than 10 volumes are used, a '1' is returned in the
is returned if the object data has been freed and the 71st character of the variable, otherwise the 71st char-
object has been suspended. *KEEP is returned if the acter is blank. The variable is returned blank if the
object data has not been freed and the object has not object was saved to a save file the last time it was
been suspended. saved, or if it was never saved.
CPR SAVDEV
Specifies the name of a variable used to return the com- Specifies the name of a variable used to return the type
pression status of the object. In a CL program, the vari- of device to which the object was last saved. In a CL
able returned has a length of 1 character. (Y) is program, the variable returned has a length of 10 char-
returned if the object is compressed. (N) is returned if acters. The variable is returned with one of the following
the object is permanently decompressed. (T) is returned values, dependent on the device used for the last save
if the object is temporarily decompressed. (F) is operation:
returned if the object is eligible for compression but is
saved with storage freed. (X) is returned if the object is *SAVF for a save file.
ineligible for compression. *DKT for a diskette.
SIZE *TAP for a tape.
Specifies the name of a variable used to return the size
*OPT for an optical volume.
of the object in bytes. In a CL program, the variable
returned has a decimal length of (15 0). The variable is returned blank if the object was not
saved.
SAVSIZE
Specifies the name of a variable used to return the size SAVF
of the object in bytes of storage at the time of the last Specifies the name of a variable used to return the
save operation. In a CL program, the variable returned name of the save file if the object was saved to a save
has a decimal length of (15 0). The variable is returned file. In a CL program, the variable returned has a length
with zeros if the object has not been saved. of 10 characters. The variable is returned blank if the
object was not saved to a save file.
SAVCMD
Specifies the name of a variable used to return the SAVFLIB
command used to save the object. In a CL program, the Specifies the name of a variable used to return the
variable returned has a length of 10 characters. The name of the library that contains the save file if the
object was saved to a save file. In a CL program, the