AS/400 administration, AS/400 backup, AS/400 command functions, AS/400 commands, AS/400 database, AS/400 DB2, AS/400 development, AS/400 error messages, AS/400 errors, AS/400 FTP, AS/400 jobs, AS/400 performance, AS/400 printing, AS/400 Query, AS/400 security, AS/400 Spool Files, AS/400 Subfiles, AS/400 user profiles, AS400 physical file, BRMS, CL, CL Program, CL programming, CL programs, CL/400, Client Access, CLLE, CLP, COBOL, DDS, i5, i5/OS, IFS, iSeries, iSeries RPG programming, iSeries V6R1, OS/400, Physical File, PTFs, RPG, RPG ILE, RPG/400, RPGILE, RPGLE, Spool files, SQLRPGLE, Subfile, V5R3, V5R4, V6R1 VIEW ALL TAGS
I am currently redesigning a process that uses started transactions to update a file that is local to our AOR on two different sysplexes. We run into issues where if the remote file update fails we have no way of knowing (NOCHECK) on the started tran so the files get out of synch. I would like to...
Does anyone have experience with splitting a sysplex with isolated dasd and tape on each new plex? How do you move tape data between the new plexes efficiently? The only methods we are aware of are very awkward at best, e.g. copy tape to dasd, ftp dasd file to other plex, copy back to tape. I know...
I seem to remember that IBM recommend that the length of time LPARs in a SYSPLEX remain on different maintenance levels is kept to a minimum. This would seem logical but I can't find any documentation actually detailing why this is important. Has anyone seen this documented to any degree?