This release is only supported with Director (Vault) versions 5.53, 6.02, and later.

---------------------------------------------------------------

1.1 Release History and Changes for Agent IBM i 6.1

January 22nd, 2010-

1st release, version 6.10.2611

_______________________________________________________________

===============================================================

2 FEATURES

Agent IBM i 6.10 Features

* System Administrator will be able to perform new installations or upgrades from Agent 5.32 orgreater.

* Improved Auto Job Creation Tool.

* The Agent supports protection of the native system.

* The Agent protects and allows recovery of IFS folders and

files includingsecurity attributes,timestamps etc.

* System Administrator has the ability to protect the IBM i system to allow full system recovery in theevent of system failure or DR test. The Agent will not depend on presence of

recovery tape.

* Documented procedure

for end user to follow to allow for successful tape recovery.

* The Agent offers the option to protect and recover not only spooled file definition but the data. Note:This capability supported in V5R4 and later versions.

* The Agent offers the option touse SAVACTWAIT parameter to set the active wait time to minimize thelikelihood of application locks during backup.

* Eliminated some errors on backup. /QDLS is supported. /QDLS, old folders aka QDOC (implementationof SAVDLO command). The IFS folder /QFPNWSSTG contains LPAR data which is now processed with theAPI to be able to recover successfully.

_______________________________________________________________

===============================================================

3 FIXES

Fixes in the 6.10 release:

IBM i system Jobs get the message "Maximum number of records reached for file QPSRVDMP".

Resolved: During the Agent installation, the Agent will increase the number of spool file records for fileQSYS/QPSRVDMP to 500,000 records. This will allow the QANEAGNT system Job to dump output incases when the Agent defers the backup and causes the IBM i API to terminate early. (16938)

QDOC and other libraries not excluded. This has been fixed in

this release. (15502)

Trigger hot backup is not working in 6.0x Agents. The userspaces required to track changes duringtrigger backup are

not created with a 6.0x Agent, so trigger hot backup will not

sync during restore. Thishas been fixed in this release.

(15485)

Restoring files in /QIBM breaks OS Java virtualmachine. If you have applications that use Java VirtualMachine, the OS

also uses Java for some IBM i Navigator functions. The Agent

IFS Restore may cause theJVM to stop working. As a preventative measure, exclude all *jar and *class from the backup. Youcanback up these files using something similar to this:

Schedule entries created using the Auto Job Creation Tool may have blank entries in "Work withSchedule" field for "Retention

Name". (17579)

Jobs

scheduled from Auto Job Creation tool may have invalid entries for Quick File Scanning with theerror "* not valid

for parameter QUICKSCAN". (17578)

If the Agent userspace does not exist, the Agent exits with abnormal termination (SIGABRT). (17017)

Trigger backup fails with "lock semaphore failed".

WORKAROUND: To clean up Agent semaphores (needed after backup

crashed and if system IPL did notoccur), run the following command: CALL BUAGENT/TRGEXTPGM PARM('C') (16931)

*Sys backup fails with "Save Configuration objects failed".

WORKAROUND: The user should do a WRKJOB SYSBK1 and look at the job log of the most recent job todetermine the system errors. If there are no job logs available then the user may look at the errors byrunning the following command manually:

"SAVCFG DEV(*SAVF) SAVF(BUAGENT/SYSSTS1)"

Typically the reason the backup fails is due to communication devices or controllers. These should bedeleted and recreated.

(16753)

IFS delta backup changes the attribute change data/time on directories and files. Symlinks are notaffected. The backup process will restore the last access timestamp to be what it was before the backup.The attribute change timestamp is affected/updated. (16385)

*SYS Restore-

restore configuration object failed due to

CPF377C".

WORKAROUND: If any errors occur during a system state restore,

(like CPF377C) then the user shouldperform DSPJOBJOG on the console session where the restore was run then review and resolve anysystem generated messages. (16174)

Restore from *IBM Job may also restore the objects inside of user libraries. (15964)

In work with task screen, last modified time/date is off by what appears to be GMT offset. (15470)

CHGAUT command errors are not reported in the agent log. (15301)

A file name with an apostrophe (') single quote or double quote (") characters that are not matched inname, fails on CHGAUT. (15300)

IFS backup of long paths may fail with "Fatal error in processing job". (15234)

User libraries that begin with Q are backed up as IBM default

libraries as the Agent uses IBM’s internallisting to obtain the list of ALLUSR and *IBM. (14406)

During an *ALLUSR restore, an OS message may not be displayed properly in thelog "REST-W-4096CPF3756 USRQ QTMFQ00021 not restored to QUSRSYS" as well as in some other cases. (13725)

During an *ALLUSR restore, the incorrect message is logged as "REST-E-7365 failed to restore CPD372EFILE QAMOPVR not restored to Q". The REST-E-7365

message should contain the file

name and notrepeat the prior REST-W-4096 message. (13724)

During an *ALLUSR restore, the error appearing as "DISK-E-4954 Error writing data, ThreadApi is nolonger in open status."

The issue is that the API is not closing correctly after processing a 0 size FILEobject because the file was locked during backup and the following object does not restore correctly.

WORKAROUND: Restore the object by itself. It should then restore correctly. (13723)

Error in restore log may appear as written twice-

"Error clearing data member clearing data member".Restore should complete while the information error is redundant. (13708)

Possible error that "Database creation is already in progress ......" may occur. As the Job Creation Tool

isa one time use tool, if, while the database is getting created, the process dies, then this message will bedisplayed and the database creation will not occur.

WORKAROUND: Re-install the Agent. (13666)

On an IFS restore you may receive the error "Unable to set file UID and GID for file". This message canappear if the user profile that owned the object at the time of the backup does not exist when therestore is done. For example, during a DR test, the *SYS Job was not run prior

to running any other Jobsor a user profile was deleted from the system and the restore is being done from an older safeset

whichhad an object that was owned by this deleted user profile.

WORKAROUND: The user needs to review the messages and change the object to the proper objectowner to allow their applications to function. (13606)

Following re-registration, if there is a Job where synch fails, they will sit in wrkactjob and must be endedby the user. (13588)

If you have created a retention (with Job Creation Tool and after database creation) and then delete theretention, the deleted retention will still be displayed (option 3). (13537)

Job names exceeding 8 characters may appear truncated due to

OS limits.

The OS only allows for up to10 character system Job names so

longer Agent Job names will be truncated. The Agent uses a 2character suffix, namely _B, @B, #B, _R, #R, @R to indicate the type of process so that leaves 8characters for the system Job name. If there is already another Agent Job with the same 8 characterabbreviation, then the 8th position will be substituted with a number and the number will beincrementally

increased until a unique name is found. The process will continue for the 7th, 6th,etc...until a unique name is found. (13525)

A warning may be encountered in the safetset.log "quick file scanning turned OFF due to delta fileformat" if the backup Job has been backed up by a version 5.32 Agent. The backup with the 6.0 Agentwill re-seed.

Note: Due to the new delta format on the upgraded 6.0 Agent,

delta recreation cannot occur until a fullre-seed of the backup by the 6.0 Agent has completed. (13526)

You may see a large number of bandwidth adjustments reported

in a backup log or receive the message"Bandwidth usage for this job has been adjusted to 0kilobits per second". This may

be due to theprocess counter in ProcessManager not being synchronized. In some cases, if the job ended abnormally,the counter may not have decreased. Also the process might be

still alive in ProcessManager.

WORKAROUND: The

ProcessManager will be cleared in the next IPL.

(13501/13499)

IBM i backup log can indicate error "No files backed up" when files are backed up. Members ofmultimember PF files are considered as directories and not as files. "No files backed up" is shown

In restore of *IBM using iSeries Agent 5.34 receive numerous "Data mapping error onmember................." messages. The actual programs are restored and the warning messages only showup later under different objects. (11927)

Setup

If re-installing, you must first delete the setup library. For example: Delete TESETUP first before restoringthe savf from the ftp site.

Remove Agent / Uninstall

If any objects in the Agent library are in use when the remove command is run, then those objects willnot be deleted. The user may delete objects afterwards when they are no longer in use.

An Uninstall should be done at the beginning of a new session.

If you wish to uninstall the Agent, you should logoff and then

logon again to perform the RemoveProgram. If a failuremessage

is received, you may have to repeat the process.

Authority

Current programs run with authority of *USER, thus the user should use a profile with minimum*ALLOBJ, and *SECADM authority to ensure all objects can be backed up. Otherwise, a

user will

only beable to back up objects that they have authority to. *SAVSYS is not enough authority, since databasemembers are read programmatically, and not with save commands.

For *SYS backup, *SAVSYS isnecessary.

Database Files

IBM limits access to deleted record information, thus during restore, deleted records will not berestored. Some very old AS400 applications relied on relative record numbers for indexing therefore,you may need to check with your application

provider to see if you need to be concerned with relative

record numbers and deleted records. Note: IBM strongly discourages the use of relative recordsnumbers in applications

since it is a system controlled value and gets changed whenever

a RGZPFMcommand (databasedefrag) is run.

WORKAROUND: If relative record numbers are sensitive in your

application then use the API option toback up database files.

Naming Convention

For Vault, Jobs, and Retention names, you must follow the IBM convention of:

WORKAROUND: If needed, use ENDJOBABN command to forcefully end any non-responding Agent jobs.Note: This can only be done 10 minutes after the job has entered ending status.

Reconnection Settings

We highly recommend using the default reconnection settings on

the Agent as they are optimized forthe Vault/Agent. Only change the settings with technical support's guidance.

The default times are:

Reconnect Delay = 30 sec.

Retry Timeout = 3600 sec.

Object Restore Fails if Object Already Exist

Restore objects of *DTAQ, *MSGQ, *JOBQ, *USRQ, *JRN, *JRNRCV types will fail if the object alreadyexists. The Agent will skip over these objects continue. The error message "Command exceptionoccurred using QaneSava API" will show in the log file. If you wish to restore/replace these types ofobjects, you must first make sure they don't exist or have beendeleted before restoring them from thevault.

Object of specific type Fails when Restoring to alternate library. Types include the following:

*SQLPKG, *JRN

Member attribute and text are not restored when the target system's QMLTTHDACN system value hasbeen set to 3.

WORKAROUND: For a restore, switch the QMLTTHDACN to 2 and then

reset it to 3 when the restore iscomplete.

IFS device, block, special character

and socket files are

typically created by the OS install or OS runningprograms. The

Agent does not restore these objects and some errors will be

listed in the log file whenattempted to restore these files.

Communication / Pre-Installation Requirements

There is an IBM OS bug on the network interface where the 100 Mbit interface can degrade to 0.4 Mbps.

WORKAROUND: Use the same settings as your Hub, Switch, or Router (typically *AUTO) on the DUPLEXparameter on the CHGLINETH command to solve the problem.

(Note: IBM default is *HALF) Pleaseperform a FTP transfer test to and from the IBMIto a local PC and ensure the network is runningoptimally. We also recommend the following values for optimal network performance.

On the Ethernet line desc (description) set these values:

GENTSTFRM(*NO)

LINKSPEED(100M) (Use maximum value for the interface)

LINESPEED(100M) (Use maximum value for the interface)

DUPLEX(*AUTO)

On TCP/IP interface: TOS(*MAXTHRPUT)

On TCP/IP Route: TOS(*MAXTHRPUT)

If you have the Defer

option enabled, and the backup does not complete in the allotted time, the systemwill stop the backup,

and complete it during the next backup time. To be able to stop

the backup, theoperating system must “abnormally” stop the backup job (the backup API). This will create errors in the

Backup.log, but they are normal in this case. The log will also have a message similar to:

“BKUP-W-0363 backup window expired, intra-file defer.”

All object related errors after this line may be safely ignored, since theobject that was deferred will bebacked up during the subsequent backup.

Restore Database Performance. When restoring a database,

performance will be enhanced if thedatabase does not already

exist in the destination location as the replace operation is

more timeconsuming.

Do not use IBM Advanced Scheduler for submitting Agent Jobs. The Agent uses the standard jobscheduler, which requires multi-threading. IBM Advanced Scheduler uses RCLRSC command internally,which is not compatible with multi-threadedapplications. (10844/5865)

Error CPF3876 file not saved because of dependency on data dictionary. Error message CPF3876 "Thefile cannot be saved or

restored unless the data dictionary is also being saved or restored."

WORKAROUND: Create a CL programwith SAVOBJ command to back up

the database file and thedepending data dictionary in one step

and output it so a SAVF. Then specify the CL in the pre-commandand specify the SAVF in the include statement on the task.

To get best delta results, back up only one PF and one dictionary per SAVF. Dump multiple SAVF to aspecific library and then back up that library with the Agent after the pre-command completes. (9221)

Install program errors when you upgrade an Agent using Agent profile. You can't use the Agent profileduring an upgrade. You must logon with "QSECOFR" level user ID to upgrade the Agent. (9021)

ANY STEP TODOWNLOAD, SET-UP, INSTALL OR USE THIS SOFTWARE, YOU AGREE, ON BEHALF OF YOURSELF ANDYOUR

COMPANY, IF THE SOFTWARE IS TO BE USED FORBUSINESS PURPOSES, (COLLECTIVELY“LICENSEE”), TO BE BOUND BY ALL OF THE TERMS AND CONDITIONS OF THIS AGREEMENT. IF YOU

DO NOT AGREE TO THESE TERMS AND CONDITIONS, CLICK “I DO NOT ACCEPT” AND YOU WILL NOT BEPERMITTED TO DOWNLOAD THE SOFTWARE OR IF YOU RECEIVED A CD CONTAINING THE SOFTWARE,RETURN THE SOFTWARE TO LICENSOR. IF WE HAVE AN EXISTING FORMAL WRITTEN SOFTWARE LICENSEAGREEMENT GOVERNING THE SOFTWARE, THEN THE TERMS IN THAT SOFTWARE LICENSE AGREEMENTWILL SUPERSEDE ANY CONTRARY TERMS IN THIS AGREEMENT.

Agent software (the “Software”) on one device for internal business purposes only. Licensee

is permitted to make a single copy of the Software for backup purposes. Except as expressly authorizedabove or as permitted by applicable law, Licensee will not: copy, in whole or in part, Software or anyrelated documentation; modify the Software; reverse compile, reverse engineer, disassemble or reverseassemble all or any portion of the Software; rent, lease, license, sublicense, distribute, transfer or sellthe Software; create derivative works of the Software; or use the Software to process data or provideany service bureau activity for any third party. Licensee obtains no rights in the Software except thosegiven in this limited

license.

--------------------------------------------------------

2. Ownership. The Software, any related documentation and all intellectual property rights therein areowned by

Licensor, its affiliates and/or its suppliers. The Software is licensed, not sold. Copyright lawsand international copyright treaties, as well as other intellectual property laws and treaties, protect the

Software. Licensee will not remove, alter or destroy any

copyright, proprietary or confidential noticesplaced on the Software or any related documentation. Licensee agrees

that aspects of the Software,including the specific design and structure of individual programs, constitute trade secrets and/orcopyrighted or patented material of Licensor, its affiliates and/or its suppliers. Licensee agrees not todisclose, provide, or otherwise make available such trade secrets or material in any form to any thirdparty without the prior written consent of Licensor. Licensee agrees to implement reasonable securitymeasures to protect such trade secrets and material.

--------------------------------------------------------

3. NO WARRANTIES. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW AND SUBJECT TO ANYSTATUTORY WARRANTIES THAT CANNOT BE EXCLUDED, THE SOFTWARE AND ANY RELATEDDOCUMENTATION ARE PROVIDED TO LICENSEE "AS IS." LICENSOR

MAKES NO WARRANTIES, EXPRESSOR IMPLIED, AND EXPRESSLY DISCLAIMS AND EXCLUDES TO THE MAXIMUM EXTENT PERMITTED BY

APPLICABLE LAW ALL REPRESENTATIONS, ORAL OR WRITTEN, TERMS,

CONDITIONS, AND WARRANTIES,INCLUDING, WITHOUT LIMITATION,

IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR APARTICULAR PURPOSE, SATISFACTORY QUALITY AND NONINFRINGEMENT. WITHOUT LIMITING THEABOVE, LICENSEE ACCEPTS THAT THE SOFTWARE MAY NOT MEET LICENSEE’S REQUIREMENTS, OPERATEERROR FREE, OR IDENTIFY ANY OR ALL

ERRORS OR PROBLEMS, OR DO SO ACCURATELY. LICENSEE USESTHE

SOFTWARE AT HIS/HER OWN RISK. This Agreement does not affect anystatutory rights Licenseemay have as a consumer.

--------------------------------------------------------

4. EXCLUSION OF CONSEQUENTIAL AND OTHER DAMAGES. TO THE

MAXIMUM EXTENT PERMITTED BYAPPLICABLE LAW, IN NO EVENT WILL LICENSOR, ITS AFFILIATES OR ITS SUPPLIERS BE LIABLE TOLICENSEE, LICENSEE’S CUSTOMERS, OR OTHER USERS, FOR DAMAGES OF ANY KIND INCLUDING,WITHOUT LIMITATION, DIRECT, CONSEQUENTIAL, SPECIAL, INCIDENTAL, OR INDIRECT DAMAGES OF

ANY KIND ARISING OUT OF THE LICENSE OF, USE OF, OR INABILITY TO USE THE SOFTWARE (INCLUDING,WITHOUT LIMITATION, DATA LOSS OR CORRUPTION, ECONOMIC LOSS, LOSS OF ACTUAL OR

ANTICIPATED PROFITS, LOSS OF CONFIDENTIAL INFORMATION, BUSINESS INTERRUPTION, LOSS OFPRIVACY, FAILURE TO MEET ANY DUTY OF REASONABLE CARE OR NEGLIGENCE) EVEN IN THE EVENT OFTHE FAULT, TORT, STRICT LIABILITY, BREACH OF CONTRACT, BREACH OF STATUTORY DUTY OR BREACHOF WARRANTY OF LICENSOR, ITS AFFILIATES OR SUPPLIERS AND EVEN IF LICENSOR, ITS AFFILIATES ORITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES OR SUCH DAMAGES WEREFORESEEABLE. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF INCIDENTALOR CONSEQUENTIAL DAMAGES SO THE ABOVE EXCLUSION OR LIMITATION MAY NOT APPLY.

--------------------------------------------------------

5. LIMITATION OF LIABILITY. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENTWILL LICENSOR’S LIABILITY EXCEED THE LICENSE FEE PAID BY LICENSEE OR US$5.00, WHICHEVER ISGREATER. THIS LIMITATION OF LIABILITY AND RISK IS REFLECTEDIN THE PRICE OF THE SOFTWARE.NOTWITHSTANDING THE FOREGOING, NOTHING IN THIS AGREEMENT SHALL EXCLUDE OR LIMITLICENSOR’S LIABILITY TO LICENSEE FOR ANY LIABILITY THAT CANNOT, AS A MATTER OF APPLICABLELAW, BE EXCLUDED OR LIMITED.

--------------------------------------------------------

6. INDEMNIFICATION. BY ACCEPTING THIS AGREEMENT, LICENSEE AGREES TO INDEMNIFY ANDOTHERWISE HOLD HARMLESS LICENSOR, ITS OFFICERS, EMPLOYEES, AGENTS, SUBSIDIARIES, AFFILIATES,SUPPLIERS AND OTHER PARTNERS FROM ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,CONSEQUENTIAL OR EXEMPLARY DAMAGES ARISING OUT OF, OR RELATING TO, OR RESULTING FROM

LICENSEE’S USE OF THE SOFTWARE OR ANY OTHER MATTER RELATING TO THE SOFTWARE.

--------------------------------------------------------

7. Termination. Licensor may immediately terminate this Agreement and the license granted hereunderif Licensee fails to comply with the terms and conditions of this Agreement. Upon such termination,Licensee must cease using the Software, destroy or delete all copies of the Software and upon therequest of Licensor, certify the destruction or deletion of the Software. Licensee may terminate thisAgreement and the

license granted hereunder at any time by destroying or deleting all copies of theSoftware. ALL DISCLAIMERS, LIMITATIONS OF LIABILITY AND ANY OTHER PROVISIONS INTENDED TOSURVIVE TERMINATION WILL SURVIVE ANY TERMINATION AND CONTINUE IN FULL FORCE AND EFFECT.

--------------------------------------------------------

8. International Trade Compliance. The Software and any related technical data is subject to thecustoms and export control laws and regulations of the United States ("U.S.") and may also be subject tothe customs and export laws and regulations of the country in which the download iscontemplated orCD containing the Software is acquired. Further, under U.S. law, the Software and any related technicaldata may not be sold, leased or otherwise transferred to restricted countries, or used by a restrictedend-user or an end-user engaged in activities related to weapons of mass destruction including, withoutlimitation, activities related to designing, developing, producing or using nuclear weapons, materials, orfacilities, missiles or supporting missile projects, or chemical or biological

weapons. Licenseeacknowledges that it is not a citizen, national, or resident of, and is not under the control of thegovernment of Cuba, Iran, North Korea, Sudan or Syria or any other country on the U.S. Statedepartment’s list of state sponsors of terror, and that Licensee will not download or otherwise export orre-export the Software and

any related technical data directly or indirectly to the above mentionedcountries nor to citizens, nationals, or residents of those countries. Licensee will comply with allapplicable export, re-export and foreign policy controls and restrictions imposed by the United Statesand will take the necessary actions and precautions to ensure that it complies with all such laws orregulations.

--------------------------------------------------------

9. Governing Law. The laws of the State of California, United States, without regard to conflicts of lawsprinciples, govern this Agreement. If applicable law does not permit the parties to agree to thegoverning law, the laws

of the country in which Licensee downloads or acquires the Software governthis Agreement. To the extent permitted by applicable law, any dispute arising under this Agreement orrelating to the Software shall be resolved by a court of proper jurisdictionin Santa Clara County,California, United States. Licensee and Licensor irrevocably submit to the jurisdiction of such courts andwaive any and all objections to jurisdiction a party may have under applicable law. Notwithstanding theforegoing, if the Software is downloaded or acquired in the People’s Republic of China, any disputearising under this Agreement or relating to the Software shall be resolved by binding arbitration, held inSanta Clara County, California, United States, under the Judicial Arbitration and Mediation Services(JAMS) International Arbitration Rules.

--------------------------------------------------------

10. Legal Effect. This Agreement describes certain legal rights. Licensee may have other rights underapplicable law. This Agreement does not change Licensee’s rights under applicable law if such laws donot permit the Agreement to do so.

--------------------------------------------------------

11. Miscellaneous. This Agreement constitutes the entire agreement between Licensor

and Licenseeand governs Licensee’s use of the Software, superseding any prior agreement between Licensor andLicensee relating to the subject matter hereof. Any change or modification to this Agreement will onlybe valid if it is in writing and signed on

behalf of Licensor and Licensee. A failure by either party toenforce its rights under this Agreement is not a waiver of those rights or any other rights it has underthis Agreement. The parties disclaim the application of the United Nations Convention on

theinternational Sale of Goods. The terms of this Agreement are severable. If any term is unenforceable forany reason, that term will be enforced to the fullest extent possible, and the Agreement will remain ineffect. The Software and any related technical data are provided with restricted rights. Use, duplication,or disclosure by the U.S. Government is subject to the restrictions as set forth in subparagraph (c)(1)(iii)of DFARS 252.227-7013 (The Rights in Technical Data and Computer Product) or subparagraphs (c)(1)and (2) of 48 CFR 52.227-19 (Commercial Computer Product–

Restricted Rights), as applicable. To theextent permitted by applicable law, Licensee may not assign this Agreement, and any attemptedassignment will be null and void. UbiStor,the UbiStor logo and other UbiStor and SafeStor names andlogos are the trademarks of Ubistor, Inc.