If you can not start JES2, make sure the JES2 procedure points to the correct initialization stream. If MVS™ appears to be enqueued on STCQUE, you might try respecifying the MVS START JES2 command. Typically, the enqueue on STCQUE occurs when MVS believes it is starting a task without JES available. The most common cause of this enqueue is the misspelling of the JES2 procedure on the START command or a command to start a secondary JES2 entered the system before the primary JES2 completed initialization processing. If it seems the initialization stream is correct, start another JES2 by changing your MVS initialization to point to the JES2 you want to use.