Granting Object Security for WebDocs - iSeries Edition

From Support

In order to adequately set AS/400 library security so the Image Server/400 programs can be accessed, the following commands may need to be run to provide access authority for the Image Server/400 programs if you run into security errors:

Granting Object Authorities for specific users to the RJS Image Library

1.) Sign on to the AS/400 as security officer.

2. Run the following commands to set security for the RJSIMAGE library:

Our example uses *PUBLIC as the user ID so we are setting library access for all users.

GRTOBJAUT OBJ(RJSIMAGE/*ALL) OBJTYPE(*ALL) USER(*PUBLIC) AUT(*USE)

GRTOBJAUT OBJ(QSYS/RJSIMAGE) OBJTYPE(*LIB) USER(*PUBLIC) AUT(*USE)

Setting up a special scan workstation user profile

1.) Create a user profile that has no special authorities. Example: RJSSCAN

2.) Change the user profile so it cannot sign on interactively. The scanning workstation use should not usually need to sign on to a 5250 session.

CHGUSRPRF USRPRF(RJSSCAN) INLMNU(*SIGNOFF) SPCAUT(*NONE) LMTCPB(*NO)

3.) Optional: You can change the user ID to have limited capabilities if so desired, however you also have to provide access to other CL commands the user may need. In our tests we have found that if limited capabilities is *YES, the user must be given authority to the CALL command as well.

CHGUSRPRF USRPRF(RJSSCAN) INLMNU(*SIGNOFF) SPCAUT(*NONE) LMTCPB(*YES)

CHGCMD CMD(CALL) ALWLMTUSR(*YES)

Displaying scan workstation object access errors on the AS/400

If you do receive error messages during scan testing, leave the message box on screen and sign on to the AS/400 and do the following.

1.) Run the following command to view all FTP jobs:

WRKACTJOB SBS(QSYSWRK) JOB(QTFTP*)

2.) Find a job in SELW status. This is most likely the FTP job where the scan workstation is connected to.

3.) Place option 5. (Work With) next to the selected job and press Enter.

4.) Type 10. (Display job log, if active or on job queue) and press Enter.

5.) Press F10 to display the joblog.

6.) Browse the job log and look for any relevant errors.