Which is why I reverse them. When I allocate a new SMPPTS dataset, I make a new SMPPTSn DDDEF entry and give put the current SMPPTS DSN in it. I then put the new DSN in the SMPPTS entry. I've never had a problem doing this. There does not appear to be any relationship between the dataset name and the SMPPTSn DD name. Other than that you cannot skip a number. You must use SMPPTS, then SMPPTS1, then SMPPTS2 and so on. But you can move the DSNs around so long as the all appear a single time in one of the SMPPTSn DDDEFs.
-- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets® 9151 Boulevard 26 . N. Richland Hills . TX 76010 (817) 255-3225 phone . [email protected] . www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets® is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company®, Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM > -----Original Message----- > From: IBM Mainframe Discussion List > [mailto:[email protected]] On Behalf Of ITURIEL DO NASCIMENTO NETO > Sent: Monday, July 25, 2011 12:57 PM > To: [email protected] > Subject: RES: SMPPTS Dataset > > If i have the option of choosing a method, i would prefer to enlarge > SMPPTS because when SMPPTS is out of space, even having SMPPTS1, SMPE > tries to compress SMPPTS what may take some time. > > Atenciosamente / Regards / Saludos > > Ituriel do Nascimento Neto > BANCO BRADESCO S.A. > 4254 / DPCD Engenharia de Software > Sistemas Operacionais Mainframes > Tel: +55 11 4197-2021 R: 22021 > Fax: +55 11 4197-2814 > > > AVISO LEGAL <br>...Esta mensagem é destinada exclusivamente > para a(s) pessoa(s) a quem é dirigida, podendo conter > informação confidencial e/ou legalmente privilegiada. Se você > não for destinatário desta mensagem, desde já fica notificado > de abster-se a divulgar, copiar, distribuir, examinar ou, de > qualquer forma, utilizar a informação contida nesta mensagem, > por ser ilegal. Caso você tenha recebido esta mensagem por > engano, pedimos que nos retorne este E-Mail, promovendo, > desde logo, a eliminação do seu conteúdo em sua base de > dados, registros ou sistema de controle. Fica desprovida de > eficácia e validade a mensagem que contiver vínculos > obrigacionais, expedida por quem não detenha poderes de > representação. > LEGAL ADVICE<br>...This message is exclusively destined for > the people to whom it is directed, and it can bear private > and/or legally exceptional information. If you are not > addressee of this message, since now you are advised to not > release, copy, distribute, check or, otherwise, use the > information contained in this message, because it is illegal. > If you received this message by mistake, we ask you to return > this email, making possible, as soon as possible, the > elimination of its contents of your database, registrations > or controls system. The message that bears any mandatory > links, issued by someone who has no representation powers, > shall be null or void. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: GET IBM-MAIN INFO > Search the archives at http://bama.ua.edu/archives/ibm-main.html > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
