Using the WRKLNK command, navigate to the folder that is above the folder you want to delete and type option 2. Press Enter. From the display that appears, type option 9 (Recursive delete) next to the folder you want to remove and press Enter. The folder and all sub-folders will be removed.
Disclaimer: Vision Solutions makes every effort to provide accurate system management information and programming code; however the company cannot be held liable for the accuracy of information nor its compatibility in your own environment. Please review and test thoroughly before implementing. © Copyright 2008, Vision Solutions, Inc. All rights reserved. IBM, System i, iSeries, i5/OS and AS/400 are trademarks of International Business Machines Corporation. All other brands are property of their respective registered owners.
08/26/08 Removing IFS folders via i5/OS "green" screens
08/19/08 Command Entry screen tips
To get to the Command Entry screen from any command line, do a Call QCMD. Once you are on the Command Entry screen, to view a full screen of lines for the entry of your command, press F11. Pressing F11 again brings your screen back to a partial display mode. If you select F10 (with the screen on partial display mode) it will include all detailed messages and commands that you have previously executed and show you the request level that they were run under.
Disclaimer: Vision Solutions makes every effort to provide accurate system management information and programming code; however the company cannot be held liable for the accuracy of information nor its compatibility in your own environment. Please review and test thoroughly before implementing. © Copyright 2008, Vision Solutions, Inc. All rights reserved. IBM, System i, iSeries, i5/OS and AS/400 are trademarks of International Business Machines Corporation. All other brands are property of their respective registered owners.
08/12/08 Creating a single startup program for multiple systems
This tip is particularly useful if you are using an iSeries high availability product for disaster recovery purposes. The idea is to create one startup program that will work on two or more systems -- one source code for multiple systems.
Use a data area to define the system's role in the iSeries replication environment. For example, the production system data area would have a setting of SRC and the backup system the setting of TGT. You may also want to define a value of SWT when the system is in the process of switching.
When a system is the production system, you want production subsystems/processes to start when the system is IPL'd. When a system is the backup system, you likely do not want these subsystems/processes to be started when the backup system is IPL'd. Of course, there will be some things you will want to start on all systems regardless of its role.
In the startup program, retrieve the pre-defined data area and then process accordingly.
Example source code for the startup program:
PGM
DCL VAR(&SYSROLE) TYPE(*CHAR) LEN(3)
RTVDTAARA DTAARA(YOURLIB/SYSROLE (1 3)) RTNVAR(&RTNVAL)
MONMSG MSGID(CPF1015) EXEC(CHGVAR VAR(&RTNVAL) +
VALUE('UNK'))
SELECT
WHEN COND(&SYSROLE = 'SRC') THEN(DO)
/* INSERT COMMANDS TO RUN WHEN SYSTEM IS THE SOURCE */
ENDDO
WHEN COND(&SYSROLE = 'TGT') THEN(DO)
/* INSERT COMMANDS TO RUN WHEN SYSTEM IS THE TARGET */
ENDDO
WHEN COND(&SYSROLE = 'SWT') THEN(DO)
/* INSERT COMMANDS TO RUN WHEN SYSTEM IS MID SWITCH */
ENDDO
ENDSELECT
/* INSERT COMMANDS TO RUN REGARDLESS OF SYSTEM ROLE */
ENDPGM
Disclaimer: Vision Solutions makes every effort to provide accurate system management information and programming code; however the company cannot be held liable for the accuracy of information nor its compatibility in your own environment. Please review and test thoroughly before implementing. © Copyright 2008, Vision Solutions, Inc. All rights reserved. IBM, System i, iSeries, and AS/400 are trademarks of International Business Machines Corporation. All other brands are property of their respective registered owners.
8/4/08 Designating authorities for journaled objects
System managers who work with journals don’t always realize when they create new journals that an authority can be designated for the journal receiver that differs from the object being journaled.
For more information on managing authorities for journals and receivers, see the IBM Redbook Technote on the topic at: http://www.redbooks.ibm.com/abstracts/tips0604.html.
Disclaimer: Vision Solutions makes every effort to provide accurate system management information and programming code; however the company cannot be held liable for the accuracy of information nor its compatibility in your own environment. Please review and test thoroughly before implementing. © Copyright 2008, Vision Solutions, Inc. All rights reserved. IBM, System i, iSeries, and AS/400 are trademarks of International Business Machines Corporation. All other brands are property of their respective registered owners.
