Problem solve

Remote Access to iSeries

• Connecting multiple iSeries systems through DDM

  Working with databases over multiple iSeries systems can be simple when remotely connecting logical partitions with distributed data management (DDM). Continue Reading

• Tracking remote access users on System i

  As remote access through FTP or iSeries Access becomes the standard, the system history log and exit point solutions are two options for tracking users on the AS/400. Continue Reading

• Controlling remote access on your IBM i

  To control remote access via network connections on the AS/400, the most secure solution is implementation of the exit point controls in the operating system. The server controls serve as gatekeepers to your iSeries, checking IP addresses of remote ... Continue Reading

• Remove character limits from domain or users on RMTUSER

  Use the STRPCCMD command or install advanced rexec daemon to allow more characters for a domain/user on a PC network. Continue Reading

• Use a virtual directory to move a .bmp file from the IFS to a remote server to run a software packag

  If a file needs to be moved quickly from the IFS to another server (Windows or a different AS/400 server) you can create a vitual directory. Continue Reading

• Displaying an image from the AS/400 on a PC, troubleshooting

  If an image from the AS/400 does not display on a PC using STRPCCMD, you may need to check to make sure the PC is connected to the iSeries. If it is not, make sure that NetServer is working. If it is, but you can't see the directory QDLS, you need ...Continue Reading

• Running a job on the iSeries after it has been transferred to a PC

  The REXEC command on a PC or the RMTCMD within iSeries Access allows you to call a program on the iSeries from a Windows PC.Continue Reading

• SQL7008 error in iSeries Access and journals

  SQL7008 error in iSeries Access is most frequently caused by trying to update a file that is not journaled or when a user lacks authority to the journal.Continue Reading

• Telnet connection repeatedly closes

  If a Telnet connection to the AS/400 keeps closing, the keep-alive settings may need to be set to lower time limits.Continue Reading

• Users unable to sign off of AS/400

  When Windows users use option 90 to sign off of AS/400 and they are automatically reconnected, this can be a problem. This can be altered by setting the ENDCNN to *yes.Continue Reading

• User authorities required to run a proceedure on another platform

  If a program automatically transfers a file from Windows to AS/400 and then runs the program on the AS/400, certain user authorities must be given in order for the program to run.Continue Reading

• User authorities for running a remote procedure on the AS/400

  Running a procedure on another platorm and transferring a file and running a remote command on the AS/400 requires specific user authorities. These don't need to be Admin settings, but certain authorities must be available to make it work.Continue Reading

• Users not recognized on iSeries when logged in from Windows 2000

  The iSeries Navigator properties control how Windows logs into the Windows server. If the user in Windows is not known to the iSeries (i.e does not exist ) you get an error. Change the properties in iSeries Navigator to use another form of user ...Continue Reading

• Remote access from behind a SonicWall firewall

  Firewall rules may be preventing remote connections from a PC to AS400. A common problem is iSeries emulation because it requires the signon port to be open (and not just the telnet port).Continue Reading

• Using remote AS400 commands in a Windows environment

  RUNRMTCMD is the AS400 implementation of REXEC client and it supports 2000 characters, but the REXEC daemon from iSeries Access only supports up to 1000 characters. To run a long command, such as a SQL Server IS package, you will want to use a ...Continue Reading