I have converted some of my S/36 migrated menus to AS/400 DDS by going into SDA, putting in my commands, and compiling the menus. The menus work when I pull them up using the AS/400 GO command. If I assign the menu as the initial menu in a user profile that has a special environment of *S36, the menu will be displayed. However, taking an option only produces the message, "procedure or command not found." After the users sign on and get the menu displayed, they have to type GO and the menu name to force the menu options to work.
When I talked to IBM, I was told that when a menu is specified in the user profile, the menu type (i.e., S/36 or AS/400) must match the special environment. The system does not allow for an AS/400 menu to be called as the initial menu on a user profile that has *S36 as the special environment.
Business users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.
IT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators with intimate knowledge of the operating system and the applications that run on it is small. This begs the question: How will you manage the platform that supports such a big part of your business? This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn:
LATEST COMMENTS
MC Press Online