JnextPlan problems

The following problems could be encountered with JnextPlan:

• JnextPlan fails to start
• JnextPlan fails with the database message "The transaction log for the database is full."
• JnextPlan fails with a Java out-of-memory error
• JnextPlan fails with the DB2 error like: nullDSRA0010E
• JnextPlan fails with message AWSJPL017E
• JnextPlan is slow
• A remote workstation does not initialize after JnextPlan
• A job remains in "exec" status after JnextPlan but is not running
• CreatePostReports.cmd, or Makeplan.cmd, or Updatestats.cmd, or rep8.cmd hang on Windows operating systems
• Possible performance impact on large production plans after JnextPlan