Skip to main content
Question

JES000050E JCL parsing error: Job: 0001003 RC = 8

  • February 12, 2026
  • 9 replies
  • 38 views

sergi.yague
Forum|alt.badge.img+1

I am launching a job from Enterprise Developer for Eclipse 11 and the only thing I can see in the spool is the following message:
JES000050E JCL parsing error: Job: 0001003 RC = 8
Can anyone tell me what else I could check to try to determine what might be happening?

9 replies

Kim Hoskin
Forum|alt.badge.img+2
  • Moderator
  • February 12, 2026

Hi Sergi,

Have you checked via the ESCWA UI (typically accessible via a web browser http://localhost:10086) > Operation > Expand Directory Servers > Click your Region > JES > Spool > Click List > Double click on the relevant job entry > In DD Entries review the entries there for details such as JESYSMSG, does this provide more information to what the problem is?

Regards,
Kim


sergi.yague
Forum|alt.badge.img+1
  • Author
  • Participating Frequently
  • February 12, 2026

**** JCLCM0406E PROCEDURE NOT FOUND
Thank you Kim.


sergi.yague
Forum|alt.badge.img+1
  • Author
  • Participating Frequently
  • February 12, 2026

f the path where I have the procedure that JES cannot find is the following:

C:\Users\xxxxxx\git\backend-micro-focus-rocket\ProcedureLibrary\STS1.PROCLIB

 

In ESCWA -> Directory Servers -> MyRegion -> JES -> Configuration -> System Procedure Library I have specified:

C:\Users\xxxxxx\git\backend-micro-focus-rocket\ProcedureLibrary\STS1.PROCLIB;C:\Users\syague\git\backend-micro-focus-rocket\ProcedureLibrary\PROP.LIB.PROC

How should I specify the path so that it finds the procedure?

On the other hand, the procedure in question is currently running on a Linux server. Could the same procedure work on a Windows 11 PC?

Thanks


Kim Hoskin
Forum|alt.badge.img+2
  • Moderator
  • February 12, 2026

Will this knowledge base article help you:
Title:How to use a JCL procedure using JCLLIB statement
URL: https://my.rocketsoftware.com/RocketCommunity/s/article/How-to-use-a-JCL-procedure-using-JCLLIB-statement-1739543495428
It uses screenshots from the older legacy ESMAC UI but much of is still relevant for the newer ESCWA UI  and give you a starting point on how to configure JCL procs in your region.


sergi.yague
Forum|alt.badge.img+1
  • Author
  • Participating Frequently
  • February 12, 2026

The System Procedure Library field (also known as PROCLIB) does not expect a physical file path (absolute or relative); instead, it requires a list of cataloged Data Set Names (DSNs).

If you entered an absolute path like C:\MyProject\Procs, the JES engine failed to find your procedures because it attempted to find a mainframe-style dataset literally named "C:\MyProject\Procs" within its internal catalog.

To resolve this and make your procedures visible to the system, you must follow these two steps:

1. Catalog your folder as a Dynamic PDS

Before referencing the folder in the library settings, you must define it in the region's catalog as a Partitioned Organization (PO) dataset.

Open the Catalog: In the Server Explorer view, right-click your region and select Show Catalog.

Add an Entry: Click the "Add data set entry" icon.

DS Name: Choose a name (e.g., MY.PROCLIB).

DS Org: Select PO.

Physical File: This is where you specify the location. To ensure portability, it is highly recommended to use relative paths or environment variables (e.g., $IDE_PROJECT_LOC\procs) instead of absolute paths.

Dynamic PDS: Check the Dynamic PDS box and specify the file extension (e.g., prc or jcl).

2. Update the System Procedure Library

Once the dataset is cataloged, you can inform JES where to search.

• Go to JES > Configuration in the ESCWA administration console.

• In the System Procedure Library field, remove the physical path and enter the DS Name you created in Step 1 (e.g., MY.PROCLIB).

• You can include multiple libraries by separating them with spaces, such as MY.PROCLIB SYS1.PROCLIB.

• Click Apply.

Summary of Path Usage:

In the JES Library Settings: Only use catalog names (DSNs).

In the Catalog Entry: Use physical paths. Use relative paths or variables like $IDE_PROJECT_LOC here to prevent errors if the project is moved to a different folder or machine


sergi.yague
Forum|alt.badge.img+1
  • Author
  • Participating Frequently
  • February 12, 2026

JES000917E J0001005 User EXPGRAL has insufficient authority to access dataset STS1.PROCLIB

This error message indicates a security authorization failure within the Job Entry Subsystem (JES). The system has determined that the user EXPGRAL does not have the necessary permissions to access the dataset STS1.PROCLIB, which is required to process the job.

Why this error occurs

In recent versions of Enterprise Server, security around running programs from JCL has been enhanced. If JES security is enabled, the system performs a mandatory READ access check on any cataloged Partitioned Dataset (PDS) that contains PROC or INCLUDE files referenced in a JCL job. If the user submitting the job lacks this permission, the job is rejected with an "insufficient authority" message.

How to resolve the issue

To fix this, you must grant the user EXPGRAL at least READ (or ALTER) authority for the dataset in your security manager. Assuming you are using the default VSAM External Security Manager (ESM), follow these steps in the Enterprise Server Common Web Administration (ESCWA) interface:

1. Open ESCWA and navigate to the Security section.

2. In the navigation pane, go to ESCWA Configuration > VSAM ESM > Resources.

3. Locate and expand the DATASET resource class.

4. Select the resource entry for STS1.PROCLIB. If it does not exist, you may need to create a new resource or use a wildcard entry like ** to define broad rules.

5. In the ACL (Access Control List) field, add the user's permission using the format: allow:EXPGRAL:read (or alter if the user needs to modify the library).

6. If there are existing permissions in the ACL, ensure you separate the new entry with a semicolon.

7. Click Apply or Save to update the security rules.

Additional Considerations

Security Manager Type: If your region uses an LDAP-based security manager instead of VSAM ESM, you must apply these changes within your LDAP directory (e.g., Active Directory or OpenLDAP) using the corresponding DATASET resource class.

Applying Changes: Depending on your configuration, you may need to refresh the security manager or restart the Enterprise Server region for the new permissions to take effect


Kim Hoskin
Forum|alt.badge.img+2
  • Moderator
  • February 12, 2026

Hi Sergi, please confirm if you require any further assistance with this post, if yes is there any specific question you have?


sergi.yague
Forum|alt.badge.img+1
  • Author
  • Participating Frequently
  • February 12, 2026

I cannot access the following URL, the user I use to create posts on this forum is not valid for accessing the URL you provided me https://my.rocketsoftware.com/RocketCommunity/s/article/How-to-use-a-JCL-procedure-using-JCLLIB-statement-1739543495428


Kim Hoskin
Forum|alt.badge.img+2
  • Moderator
  • February 13, 2026

You would need to create a logon and logon with that to be able access that article.