As someone already mentioned, the JECL is different. It shouldn't be hard to 
write code to translate. 

The other issue is the class structure. JES2 uses an one character class on the 
JOB card. JES3 used the  class on the JOB card or an eight character class on 
the //*MAIN JECL statement. 

Ed Jaffe has done some papers on it.
ftp://phoenixsoftware.com/pub/demo/JES3_to_JES2_User_Experience.pdf
ftp://phoenixsoftware.com/pub/demo/JES3_White_Paper.pdf 


Dennis Roach, CISSP, PMP
IAM Access Administration – Consumer – Senior Analyst 
2727 Allen Parkway, Wortham Building 3rd Floor, Houston, TX 77019
Work:  713-831-8799
Cell:  713-591-1059
Email:  [email protected] 
Report information security incidents to: [email protected] and 
(818) 673-4030 

All opinions expressed by me are mine and may not agree with my employer or any 
person, company, or thing, living or dead, on or near this or any other planet, 
moon, asteroid, or other spatial object, natural or manufactured, since the 
beginning of time.

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf 
Of Cheryl Watson
Sent: Thursday, January 14, 2016 8:14 PM
To: [email protected]
Subject: Re: JES3 to JES2 Migration (was JES2 to JES3 Migration)

Yes, Lizette - I meant to say JES3 to JES2.  Thanks!

Has anyone who has done this have an estimate of the amount of time it might 
take, and the effort?

Cheryl

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf 
Of Lizette Koehler
Sent: Thursday, January 14, 2016 9:08 PM
To: [email protected]
Subject: Re: JES2 to JES3 Migration

Cheryl,

I am guessing you meant the subject to say JES3 to JES2 migration???

The one challenge I see is the JCL is different between the two environments.  
JES2 use /* (eg. /*ROUTE) and JES3 uses //* (eg //*MAIN)   

JES2 has no master JES system, JES3 has a Master.  So in JES2 jobs can either 
run where the JCL is converted or anywhere in the JESMAS.


There is also the concept in JES3 that until all resources available, the job 
will not run.  JES2 it can run and wind up waiting on resources.

Those are about the differences I can think of off the top of my head.

Lizette


> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[email protected]] 
> On Behalf Of Cheryl Watson
> Sent: Thursday, January 14, 2016 7:01 PM
> To: [email protected]
> Subject: JES2 to JES3 Migration
> 
> A customer asked us for suggestions for performing a JES3 to JES2 migration.
> Are there products that will help in this, or do you know any 
> companies who perform this migration?  You can reply off-list if you prefer.
> 
> Thanks so much,
> Cheryl
> cheryl at watsonwalker.com

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
[email protected] with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
[email protected] with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to