OS/400 provides two commands you can use to reduce the amount of DASD used by your application programs: Reorganize Physical File Member (RGZPFM) and Clear Physical File Member (CLRPFM).
Both commands accept a specific member name, *FIRST, or *LAST. Since neither command accepts *ALL, your "house-cleaning" can become more difficult than it has to be, especially if you keep multi-member physical files.
Weep no more! Commands Clear Physical File, all members (CLRPFMALL) and Reorganize Physical File, all members (RGZPFMALL) process all members of a database file.
3a and 3b show the command definition for CLRPFMALL and RGZPFMALL, respectively. Notice that the second parameter has been defined as being a constant. Both commands share the same command processing program (PFM001CL, in 3c). This second parameter tells the CPP whether to clear all members or reorganize all members. This second parameter is invisible to the user -- the command prompter will not display it.
Figures 3a and 3b show the command definition for CLRPFMALL and RGZPFMALL, respectively. Notice that the second parameter has been defined as being a constant. Both commands share the same command processing program (PFM001CL, in Figure 3c). This second parameter tells the CPP whether to clear all members or reorganize all members. This second parameter is invisible to the user -- the command prompter will not display it.
The logic of program PFM001CL is actually quite simple. Retrieve the name of the first member with RTVMBRD MBR(*FIRST) RTNMBR(&RTNMBR). Now, variable &RTNMBR contains the name of the first member. The program goes into a loop that runs either CLRPFM or RGZPFM on this member. This is followed by another RTVMBRD to retrieve the name of the next member using MBR(&RTNMBR *NEXT) meaning the member that follows &RTNMBR . The name of this member is placed, again, in &RTNMBR -- and the loop continues until all members have been processed.
TechTalk: Clearing/Reorganizing All Members
Figure 3A Command CLRPFMALL
CLRPFMALL: CMD PROMPT('Clear all File Members') PARM KWD(FILE) TYPE(Q1) MIN(1) PROMPT('File name') PARM KWD(ACTION) TYPE(*CHAR) LEN(4) CONSTANT(*CLR) Q1: QUAL TYPE(*SNAME) LEN(10) MIN(1) QUAL TYPE(*SNAME) LEN(10) DFT(*LIBL) + SPCVAL((*LIBL)) PROMPT('Library')
TechTalk: Clearing/Reorganizing All Members
Figure 3B Command RGZPFMALL
RGZPFMALL: CMD PROMPT('Reorganize All Members') PARM KWD(FILE) TYPE(Q1) MIN(1) PROMPT('File name') PARM KWD(ACTION) TYPE(*CHAR) LEN(4) CONSTANT(*RGZ) Q1: QUAL TYPE(*SNAME) LEN(10) MIN(1) QUAL TYPE(*SNAME) LEN(10) DFT(*LIBL) + SPCVAL((*LIBL)) PROMPT('Library')
TechTalk: Clearing/Reorganizing All Members
Figure 3C CL program PFM001CL
PFM001CL: + PGM PARM(&QF &ACTION) DCL VAR(&ACTION) TYPE(*CHAR) LEN(4) DCL VAR(&FILE) TYPE(*CHAR) LEN(10) DCL VAR(&LIB) TYPE(*CHAR) LEN(10) DCL VAR(&MSGDTA) TYPE(*CHAR) LEN(80) DCL VAR(&MSGID) TYPE(*CHAR) LEN(7) DCL VAR(&MSGF) TYPE(*CHAR) LEN(10) DCL VAR(&MSGFLIB) TYPE(*CHAR) LEN(10) DCL VAR(&QF) TYPE(*CHAR) LEN(20) DCL VAR(&RTNMBR) TYPE(*CHAR) LEN(10) MONMSG MSGID(CPF0000) EXEC(GOTO CMDLBL(SNDERRMSG)) CHGVAR VAR(&FILE) VALUE(%SST(&QF 1 10)) CHGVAR VAR(&LIB) VALUE(%SST(&QF 11 10)) CHKOBJ OBJ(&LIB/&FILE) OBJTYPE(*FILE) AUT(*OBJMGT) RTVMBRD FILE(&LIB/&FILE) MBR(*FIRST) RTNMBR(&RTNMBR) MONMSG MSGID(CPF0000) EXEC(DO) SNDPGMMSG MSG('File' *BCAT &FILE *BCAT 'has no members.') + MSGTYPE(*INFO) GOTO CMDLBL(ENDPGM) ENDDO LOOP: + IF COND(&ACTION *EQ '*CLR') THEN(DO) SNDPGMMSG MSGID(CPF9898) MSGF(QCPFMSG) MSGDTA('Clearing + member' *BCAT &RTNMBR *BCAT 'from file' *BCAT &FILE) + TOPGMQ(*EXT) MSGTYPE(*STATUS) CLRPFM FILE(&LIB/&FILE) MBR(&RTNMBR) MONMSG MSGID(CPF0000) ENDDO ELSE CMD(DO) SNDPGMMSG MSGID(CPF9898) MSGF(QCPFMSG) MSGDTA('Reorganizing + member' *BCAT &RTNMBR *BCAT 'from file' *BCAT &FILE) + TOPGMQ(*EXT) MSGTYPE(*STATUS) RGZPFM FILE(&LIB/&FILE) MBR(&RTNMBR) MONMSG MSGID(CPF0000) ENDDO RTVMBRD FILE(&LIB/&FILE) MBR(&RTNMBR *NEXT) RTNMBR(&RTNMBR) MONMSG MSGID(CPF0000) EXEC(DO) SNDPGMMSG MSG('All members of file' *BCAT &FILE *BCAT + 'processed successfully.') MSGTYPE(*INFO) GOTO CMDLBL(ENDPGM) ENDDO GOTO CMDLBL(LOOP) SNDERRMSG: + RCVMSG MSGTYPE(*LAST) MSGDTA(&MSGDTA) MSGID(&MSGID) MSGF(&MSGF) + MSGFLIB(&MSGFLIB) SNDPGMMSG MSGID(&MSGID) MSGF(&MSGFLIB/&MSGF) MSGDTA(&MSGDTA) + MSGTYPE(*DIAG) SNDPGMMSG MSGID(CPF0002) MSGF(QCPFMSG) MSGTYPE(*ESCAPE) ENDPGM: + ENDPGM
More than ever, there is a demand for IT to deliver innovation. Your IBM i has been an essential part of your business operations for years. However, your organization may struggle to maintain the current system and implement new projects. The thousands of customers we've worked with and surveyed state that expectations regarding the digital footprint and vision of the company are not aligned with the current IT environment.
TRY the one package that solves all your document design and printing challenges on all your platforms. Produce bar code labels, electronic forms, ad hoc reports, and RFID tags – without programming! MarkMagic is the only document design and print solution that combines report writing, WYSIWYG label and forms design, and conditional printing in one integrated product. Make sure your data survives when catastrophe hits. Request your trial now! Request Now.
Forms of ransomware has been around for over 30 years, and with more and more organizations suffering attacks each year, it continues to endure. What has made ransomware such a durable threat and what is the best way to combat it? In order to prevent ransomware, organizations must first understand how it works.
Disaster protection is vital to every business. Yet, it often consists of patched together procedures that are prone to error. From automatic backups to data encryption to media management, Robot automates the routine (yet often complex) tasks of iSeries backup and recovery, saving you time and money and making the process safer and more reliable. Automate your backups with the Robot Backup and Recovery Solution. Key features include:
Business users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.
IT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators with intimate knowledge of the operating system and the applications that run on it is small. This begs the question: How will you manage the platform that supports such a big part of your business? This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn:
LATEST COMMENTS
MC Press Online